Base Planner
Count role coverage and get one controlled next test.
Open →TOOLSRoll Calculator
Turn observed 1-in-N odds into a probability and roll budget.
Open →DATABASEObject Index
Browse barriers, traps, ranged, and area roles with confidence labels.
Open →COMPARETier List
Rank the missing job for beginner, waves, boss, or offline play.
Open →GUIDEBest Base Layout
Use front, pressure, and cleanup layers without fake coordinates.
Open →GUIDEBest Upgrades
Choose an upgrade from the first confirmed bottleneck.
Open →GUIDEMoney Guide
Compare repeatable waves, Index claims, and offline sessions.
Open →PROGRESSIONBosses & Relics
Prepare a baseline and keep unverified recipes out of the ledger.
Open →STATUSCodes
Track the redeem-menu and working-code status without placeholders.
Open →SAFETYScript Safety
Answer Auto Roll and Auto Wave searches without downloads.
Open →FRESHNESSUpdates
Separate official description changes from community observations.
Open →TRUSTSources
See the evidence ledger and the limits behind every volatile claim.
Open →How this wiki handles evidence
The official Roblox experience establishes the game identity and public description. Creator-controlled announcements would take priority for updates, codes, and links when they are available. Gameplay videos and recent guides can support labeled observations about visible menus, costs, objects, and checkpoints. They cannot turn an unpublished number into an official stat.
Every volatile value should carry a source, a checked date, and a confidence state. The current object odds are labeled community-observed. Boss drops and crafting recipes remain incomplete until a current in-game screen or other reviewable source supports them. A YouTube title mentioning secret codes or Discord is treated as demand evidence, not proof.
Core progression map
- Roll enough objects to cover more than one defensive role.
- Build a front layer, sustained pressure, and cleanup answer.
- Defend a repeatable wave and record the first leak.
- Use coins and Index progress on the bottleneck that appears in the run.
- Keep one stable layout before changing boss-facing or offline decisions.
- Inspect relic and crafting screens directly before farming a claimed recipe.
What is deliberately missing
This wiki does not publish executor code, copied scripts, fabricated codes, generic redemption steps, universal coordinates, unverified trading claims, or invented item statistics. Missing information is a research queue, not an invitation to fill a page with assumptions. That boundary protects players and makes future updates easier to audit.
Frequently asked questions
Is this an official Build a Base RNG wiki?
No. This is an independent fan-made field wiki. Official Roblox and creator-controlled destinations take priority for game identity and current announcements.
Where are exact damage, range, and recipe values?
They are included only when a current, reviewable source supports them. Unknown or version-sensitive values are not filled with guesses.
Does the wiki list scripts or working codes?
It does not distribute scripts. The codes page maintains an honest status and lists a code only when a credible public source and visible game flow support it.