Keep items, wave rewards, and code status in separate buckets so the page stays useful even when the game changes.
The safest workflow is simple: identify the item family you are testing, record the reward or outcome the game visibly shows, and treat every code claim as unconfirmed until a working redeem path appears. That keeps items useful, rewards honest, and copied code lists from polluting the route.
Each bucket answers a different player question so one rumor does not leak into everything else.
Use item wording to identify what job a defense may solve, then test it on the lane. Unknown odds, rarity, and range stay outside the page until they can be confirmed.
Use rewards wording for boss relics, visible wave outcomes, and offline returns you can actually inspect in the UI. Do not merge one screenshot into a universal payout chart.
Code questions belong here because players often mix codes with rewards. The current answer is still that no safe public code menu is confirmed.
Track the item families that change your front, middle, or cleanup coverage first. Fresh public wording also repeats Golden Mortar and Wooden Tesla, but exact stats, odds, and availability still need direct in-game confirmation.
The official Roblox description confirms boss relic rewards and crafting. Wave rewards, round payouts, and offline rates still need a direct in-game check before they can be stated as fixed numbers.
No active code or redeem menu is confirmed as of July 21, 2026. Keep code questions separate from item and rewards questions so a copied list does not become a false fact.
