Build a Base RNG Guides

Build a Base RNG is easiest to learn as a repeatable loop: roll an object, place it into a useful job, defend a wave, observe the first failure, then improve one thing. The official description condenses that loop to Roll, Build, Defend and confirms that the base fights offline. The guides here turn those facts into practical routes without pretending that community odds, costs, wave thresholds, or reward tables are official.

Start with the Beginner Guide if you have not completed a stable wave. Choose F2P Progression when you need a spending and upgrade sequence without Robux. Use Official Links before following a Discord, Trello, video, private server, or same-name Roblox result.

Pick the right guide

First-session route

Join the official experience and let its interface load. Roll until you can place at least one object that delays or absorbs pressure and one object that contributes damage. Community walkthroughs describe Build Mode families for blocks, traps, and weapons; the exact tabs and unlock timing should be read from your live server.

Place the delaying piece near first useful contact, keep ranged pressure where it remains protected, then start a wave. Watch the lane instead of the rarity labels. Record where enemies first stop taking useful damage or where a barrier breaks. That point—not the newest roll—is the next problem to solve.

After the run, open the Index and any Skills or upgrade panel visible to your account. Claim completed entries, read each effect and cost, then change one factor. A placement move answers a coverage problem. An object upgrade answers a durability or damage problem. A rolling or Luck upgrade changes future acquisition. Mixing all three makes the result impossible to diagnose.

The full order, recovery path, and early mistakes are covered in the Beginner Guide.

Build decisions belong to separate hubs

The Items hub is the lookup layer. It separates currently documented object names from video-title leads and unknown fields. Use it to identify a roll, compare roles, and decide whether to keep or test it. Exact damage, health, range, odds, and event availability are omitted unless the evidence supports them.

The Layouts hub is the geometry layer. It explains front, middle, cleanup, wave, boss, and offline baselines. It does not promise universal coordinates because your available objects, upgrades, and current update can change what each placement covers.

The Progression hub is the account layer. It connects rolling, Luck, Skills, the Index, coins, upgrades, and offline returns. The purpose is to spend toward a tested failure rather than copy a cost table that may already be stale.

The Bosses hub preserves the recent boss → relic → crafting loop with a dated version warning. The current public description switched from the earlier Bosses promotion to Tsunami, so confirm that Boss Waves and the relevant crafting interface are still available before committing a long farm.

F2P route without idle grinding

A free account needs a stable baseline more than a perfect rarity. Keep a complete working set, claim visible Index rewards, and improve one object or one account system at a time. Do not remove a functional front or cleanup role merely because a new roll looks rarer.

Separate active-wave results from offline results. The official description confirms offline fighting, but it does not publish the settlement window, cap, failure model, or income rate. Leave a tested layout, record the logout and return state, then compare like-for-like sessions. The F2P guide turns that into a repeatable session and weekly plan.

Handling the Tsunami event

The current official description says the Tsunami Update is an hourly event where players can fight new sea enemies and obtain new weapons. Those phrases are Official. A recent video title may name a weapon or show an entrance, but that alone does not settle the in-game name, drop source, odds, stats, or schedule behavior.

Before changing your base for the event, read the live event panel, note the countdown or status, and identify whether the route uses your normal base or a separate setup. Run one low-commitment attempt. Put confirmed weapons into the Weapons index rather than creating duplicate event pages. Use the Updates tracker for dated status.

The audit condition for a separate /guides/tsunami-event/ page was not met because no account-level route, reward screen, or creator-owned walkthrough was verified. Keeping the facts in Updates and Items avoids publishing a thin event shell.

Evidence labels used across the guides

• Official means Roblox, Slungpy Games, the official experience description, or a creator-owned announcement directly supports the fact.
• Community corroborated means at least two independent current sources agree on the useful game-specific detail.
• Community reported means one directly relevant source supports it, so the page uses cautious wording and omits unsupported fields.
• Needs in-game testing marks update-sensitive controls, costs, odds, rewards, stats, recipes, and availability that the public evidence cannot settle.

When sources disagree, the current game interface wins for play. A guide can still help you choose the next test, but it should not turn one screenshot into a permanent rule.

Guides FAQ

What should a new player do first?

Complete one full roll, placement, and wave. Keep the layout fixed, identify the first failure, and improve that point before chasing another rare object.

What is the best upgrade?

There is no safe universal answer across every account. Use the Best Upgrades guide to choose between coverage, object power, rolling speed, Luck, and capacity from the failure you can reproduce.

Does rarity automatically make an item better?

No. Rarity changes acquisition expectations; usefulness also depends on role, placement, upgrade state, and the enemy pressure being tested.

Are exact odds and costs listed here?

No copied odds or cost tables are promoted as current. Read the live roll and upgrade panels, then use the decision guides to interpret them.

Where should I check current changes?

Use the Updates page for the dated official-description snapshot and the Codes page for its separate no-code status.