Source hierarchy
The official game page and Chopsy Games community are treated as primary sources. Roblox code trackers and hands-on guide sites can support context, but they do not override official source material or direct in-game checks.
Research workflow before writing
Each new Axe RNG page starts with source review. If exact stats are not visible in official material, source-reported with attribution, or verified in game, the page should say that clearly and avoid pretending to know roll chances, zone costs, tree HP, bee rates, upgrade costs, or best routes.
What this site will not publish
- Thin pages that exist only to repeat a keyword.
- Leak-based updates, fake code promises, or exploit instructions.
- Fake ratings, review counts, sales numbers, or platform support.
- Axe tier lists, zone routes, or progression rankings without hands-on evidence.
Update method
When a claim changes, update the visible page, source links, sitemap lastmod, news log, and related internal links together.
Axe RNG source policy in practice
A code can appear on this wiki when a reliable tracker reports it, but it should stay marked as needing a site test until someone redeems it in game. A mechanic can appear on a guide page when the official listing, a named public source, visible footage, or direct play supports it. Exact numbers need stronger evidence than general system names.
Evidence levels used on guide pages
- Official-confirmed: the official listing or developer source states the system and this site can access or cite it.
- Source-reported: a named public source reports a code, reward, or mechanic, but this site has not tested it.
- Hands-on-needed: the topic is useful, but exact stats or steps are not ready.
- Do not publish: the claim depends on leaks, exploits, or unsupported guesses.