Use one source-watch route for maps, systems, round flow, and outcome-reading so a changed lane or event does not get confused with fake hidden mechanics.
Most map and systems questions can be answered by the round outcome you actually see. If the same build fails at the same lane point, the problem is probably not a secret mechanic. If a new round or boss changes the path pressure, then the systems and map context become the next thing to check.
These notes keep systems tied to a player-visible round outcome.
A round starts with your current layout and ends with a visible outcome: clear, leak, or boss failure. Use the same round when comparing changes.
Map questions matter only when the lane shape changes what your base can cover. If the round outcome changes without a lane change, inspect the build first.
Systems such as rolling, crafting, offline fighting, and boss rewards can change progression, but none of them replace the need to watch the outcome of the current defense test.
Public references confirm the base-defense loop and boss event, but they do not yet publish a complete map list. Use the current UI to confirm whether your round uses a new path, lane shape, or boss arena.
The confirmed systems are rolling defenses, building the base, defending waves, fighting bosses with custom attacks, earning relics, crafting, and offline base fighting.
A useful round outcome tells you where the base first failed: empty coverage, low pressure, or a boss-specific attack. That round outcome is more actionable than an unverified hidden stat.
