Build a Base RNG Item Index

The Build a Base RNG item pool is the bridge between rolling and defending: a roll matters only after you identify its family, place it into a useful layer, and test it against a repeatable wave. This index organizes currently documented names rather than claiming a complete database. Public sources agree on the broad Blocks, Traps, and Weapons families, while exact stats, roll odds, variants, upgrade caps, and current event availability still belong to the live game.

Start with Weapons for automatic damage objects, Blocks for barriers and path protection, and Traps for lane contact. Use the Item Tier List for a goal-based comparison and Rarities & Odds before interpreting a roll animation or Luck upgrade.

Currently documented item lookup

This is not proof that the rows are the complete pool. It is a safe starting set supported by a detailed current walkthrough. A complete claim would require the live Index or roll panel to show every entry under the same version.

Classify a new roll before placing it

Open the item’s in-game detail and record the displayed name exactly. Then identify the family shown by Build Mode or the Index. A block’s first question is where it can absorb or redirect pressure. A trap’s first question is whether enemies cross its effective tile. A weapon’s first question is how long it can contribute without being exposed or outranged.

Do not infer an item type from its name alone. “Spike,” “turret,” or “brew” may suggest a role, but the current panel must establish the category and effect. Keep the item in a verification queue until you can see its type, source, and at least one meaningful behavior.

Before replacing anything, save the old layout or take a screenshot. Test the new roll against the same wave. Record the first failure point, not just the final wave number, because the replacement may improve one layer while weakening another.

Choose by job, then by rarity

A useful base needs contact, sustained pressure, and cleanup. Blocks and traps can extend the time weapons contribute; weapons cannot compensate for an empty lane if enemies reach the core without entering their coverage. Likewise, the rarest item in an unhelpful position can perform worse than a documented starter item used correctly.

Use rarity as acquisition context, not as a complete ranking. Read the Rarities & Odds guide to distinguish displayed base odds from Luck-modified results. Use the Tier List to compare items by early stability, group pressure, durable-target pressure, and cleanup rather than one universal S-to-F ladder.

When an item already fills a role, upgrade or move it only after identifying a repeated problem. If small enemies leak through a covered area, compare group pressure. If one durable enemy survives, compare sustained single-target contribution. If enemies pass through empty space, fix layout before rolling again.

Tsunami weapon verification queue

The current official description confirms that the hourly Tsunami event can award new weapons. It does not supply names. Recent search and video-title leads mention Haku Turret and “Tsunami guns,” while other recent community titles mention Witches Brew, Piston, and Spike. Those names are leads, not settled index rows.

To promote one, capture the in-game name, item family, source wording, visible rarity or odds, event status, and a simple same-wave behavior test. Do not import a video’s damage claim, drop chance, or “best” label. If the event ends, keep the item only after confirming whether it remains usable and how its source should be described historically.

New event weapons stay on the Weapons page rather than receiving duplicate event articles. The Updates tracker owns the dated Tsunami status.

Upgrade and keep-or-replace workflow

1. Save the current layout and choose one repeatable wave.
2. Record the first leak, first destroyed barrier, or enemy that survives the main damage zone.
3. Inspect the candidate item’s live name, family, level, effect, and upgrade preview.
4. Replace only the item assigned to the weak role; keep every other placement unchanged.
5. Repeat the baseline and compare where the failure moves.
6. Keep the change when it improves the target problem without opening an earlier leak.
7. Revert it when the visible role does not contribute or the base loses an essential layer.

This makes an ordinary item valuable when it solves the actual run. It also prevents a rare item from receiving upgrades only because the roll animation looked impressive.

Item Index FAQ

Is this the complete Build a Base RNG item list?

No. It is the currently documented set that could be sourced without inventing fields. The live Index is required before calling coverage complete.

Are the odds from third-party tables accurate?

They are not frozen here. Current pages publish exact values, but the audit found conflicting and template-like tables. Read the current roll or Index display.

What is the best item?

The best item is the one that improves the repeated failure being tested. A barrier, trap, group-damage weapon, and durable-target weapon answer different problems.

Should I replace every common item?

No. Keep a functional piece until the replacement proves it can fill the same role on the same wave.

Where should I place an item?

Use Layouts to choose front, middle, and cleanup jobs, then use the item’s live range or contact behavior to refine the position.