Roll A Gnome Patch Notes
Known timeline markers and a post-update checklist to keep your strategy honest.
This page tracks Roll A Gnome patch context for wiki readers. It combines verified release markers with a practical re-test list you should run after any update.
Known timeline markers
| Date (UTC) | Note |
|---|---|
| 2026-07-16 | Experience created (Roblox universe records) |
| 2026-08-09 | Universe update timestamp observed during wiki research |
| 2026-08-10 | Wiki research refresh: ~1.18M visits, ~3.4k concurrent, favorites climbing; still no widely verified public promo-code list; official creatives still frame commons near 1 in 2 and ultra-rares near 1 in 9,999,999 — see Drop Rates & Odds |
| Ongoing | Live ops continues — re-check group wall and in-game mail/GUI |
Exact changelog bullets are owned by 8 Digit Bros. When official text is short, we focus on player-facing systems to re-validate.
Post-update re-test list
- Luck: Like + group bonus still active? (Free Luck Rewards
- Codes: New button or new strings? (Codes Hub
- Economy: Roll costs, sell values, expansion prices (Make Money Fast, Expand Your Garden
- Rarity pool: New tags or models (Gnome Rarity Tiers
- Farming: Output changes on placed teams (Best Farming Gnomes
- Offline: Returns still sane (Offline Progress
- Tools/scripts: Assume broken until tested (Scripts Hub
How we write patch entries
When a concrete change is confirmed in-game, we add a dated section above with:
- What changed
- Which wiki pages were edited
- Whether players should redo early or mid plans (Early Game Build, Mid Game Progression
Player actions after reading notes
- Update Progression Planner
- Run Luck Checklist
- Return to Updates Hub for the broader checklist
Reporting mindset
If your client looks different from this page, trust the live client, then compare with the Links Hub to ensure you launched the correct experience. Similarly named gnome games cause false patch rumors.
Stay flexible. The strongest players treat patch day as a recalibration day, not a reason to rage-reroll their entire garden at once.
Template for future dated entries
YYYY-MM-DD — Title
- Systems touched: luck / codes / economy / gnomes / UI
- Player action: what to re-check tonight
- Wiki pages updated: list
Using a template keeps notes scannable when the game accelerates.
Community rumor filter
If a screenshot claims rates changed but your client differs, trust your client, verify place ID via Official Links, then wait for corroboration. Mid-game players lose more to rumor panic than to real nerfs. Anchor emotions with the re-test list above and the Progression Planner.
Worked example of a wiki response
Suppose a patch raises expansion prices and adds a new uncommon farmer family. Wiki response: update economy warnings on Expand Your Garden, add the family context on Best Farming Gnomes, remind readers to rerun Luck Checklist, and note the date here. Player response: pause blind expansions, field-test the new farmers, and adjust the Progression Planner.
That worked example is the standard we aim for whenever 8 Digit Bros ships changes. If notes here lag a day, still run the re-test list yourself — live gardens cannot wait on perfect documentation.
Archive mindset
Older dated sections stay for history so you can see how often economy levers move. Do not play on outdated sections — always start from the newest date, then skim older ones only if you are diagnosing a long-term trend like repeated expansion price spikes. History informs; it should not override tonight’s client.
If you maintain a personal changelog, mirror the template fields so your notes and this page stay comparable after busy update weeks.
Frequently Asked Questions
Quick answers to the most common questions.
Where are official patch notes posted?
Typically on the Roblox experience update flow and the 8 Digit Bros group wall. This page translates those into player checklists.
Will this page list every tiny fix?
No. We prioritize changes that affect luck, codes, economy, rarity, or offline behavior.
What should I do right after an update?
Run the post-update re-test list, then adjust your next Progression Planner action.