The best way to improve Axe RNG guides is to record exact in-game text, screenshots, dates, and before-after values for codes, axes, trees, zones, skills, bees, honey, potions, luck, and rebirth.
Evidence level: site source policy + needs in-game test.
How to use this Axe RNG guide
Use this page as a verified starting point, not as a final data table. The goal is to explain what the system appears to do, what a player can safely act on now, and what information still needs a direct in-game check before it becomes route, ranking, or calculator advice.
What to record in the first session
A useful first-session log focuses on visible facts rather than conclusions. Record the starting axe, first roll results, first tree rewards, first skill upgrade, and any bee, honey, or rebirth unlock prompt.
Code verification checklist
For each code, record the source, code text, reward text, success or failure message, date, and whether a fresh server was used.
- Source and check date
- Exact code text
- Success or failure message
- Reward shown in game
Progression verification checklist
For axes, trees, zones, and skills, record what changed after one action. Avoid testing several upgrades at once because it makes the result hard to explain.
System verification checklist
For bees, honey, potions, luck, and rebirth, record before-after values and whether the effect survives server changes or resets. These systems affect guide advice the most.
Screenshot naming method
Use names that can be understood later, such as axe-rng-code-test-2026-06-18, axe-rng-first-rebirth-before, or axe-rng-honey-after-bee-upgrade. Clear filenames make it easier to match screenshots with notes, sources, and update dates when the wiki revises a page.
How notes become guide updates
A note is ready for a guide update when it includes exact game text, a date, the player state, and a repeatable result. A single screenshot can confirm that a button, resource, or axe exists. A recommendation needs more evidence because it tells other players what to do.
What not to submit as evidence
Avoid cropped screenshots with no game context, copied code lists without dates, tier lists with no roll data, and route claims that depend on unknown boosts. Those can still be interesting leads, but they should stay in research notes until another source or direct test supports them.
How often to re-check important facts
Re-check codes after updates, system claims after balance changes, and progression notes after new zones or rewards appear. A fact that was true for one build can become outdated quickly in a Roblox RNG game. This checklist keeps each page tied to a check date so old advice can be revised instead of silently aging.
Where verification should start
Start with facts that many players search for: active codes, first rebirth requirement, visible axe names, potion reward text, honey source, and the earliest zone gates. These checks improve several pages at once and reduce the risk of publishing a long guide built on one weak assumption.
What still needs verification
- Complete first-hour progression route
- Consistent before-after values
- Screenshot-backed axe and system tables
- Which values change after updates