What should I do next?
| Your current problem | First useful action | Next check |
|---|---|---|
| First session | Finish a small protective footprint | Watch one wave before expanding |
| Enemy enters a gap | Close or shrink that gap | Re-test the same starting state |
| You cannot reach the approach | Change access or placement | Walk the route before a wave |
| Boss breaks the outer line | Prepare a second reachable position | Check useful fallback coverage |
| Leaving the game | Finish construction; remove reliance on active attacks | Note the base and inspect on return |
If this is your first session, finish a small protective footprint and watch one wave before expanding. If monsters reach you through a gap, close that gap before buying more attack power. If a complete wall holds but you cannot reach or see the approach, change access/placement first. If a boss breaks the outer line, plan a second position before enlarging the base. If you are leaving, finish construction and check the build without relying on your character's attacks. These are suggested tests, not guaranteed enemy pathing rules.
What is confirmed?
The developer description confirms freeform building, recurring monster waves, bosses, building with invited friends, autosaved buildings and offline base fighting. It does not publish boss HP or an offline earnings cap. Use the official Roblox link for 100M CCU, Place 139536504610209. Max server size is six; editing permissions and offline co-op ownership are not documented here.
The practical loop
Build a manageable footprint → observe a wave → identify the first breach or missed approach → change one part → try again. Expansion is a choice after a working baseline, not an automatic requirement. Saved buildings make unfinished redesigns worth avoiding before logout.
Is the problem structure or coverage?
| First observed failure | Change only this | Re-test; hold or expand |
|---|---|---|
| Unfinished entrance lets the wave reach you | Complete or shrink that corner with the entrance editor | Re-test the completed outline. Hold while any gap remains; expand for a specific purpose after a useful result. |
| Own construction obstructs a defense | Clear the obstruction or move that equipment | Keep state/boosts/active support comparable. Check the actual approach is engaged; fix the next first failure. |
| A wave only works while you actively attack | Check intended coverage without your attacks; finish the build before leaving | Record the completed autosaved structure. Compare on return; online success does not prove offline rewards or survival. |
A gap or inaccessible retreat calls for a layout change. Attacks missing an approach call for a placement/coverage check using the equipment actually available in your version. Repeated failure after both checks calls for a smaller test footprint or a new defensive option; no unverified DPS ranking is needed. Compare the same starting state when testing changes.
For a worked diagnosis, imagine a session with a friend replacing an entrance before the next monster wave. The first failure is entry through the unfinished corner. Complete or shrink that corner, then watch the same starting wave/state again. Hold the footprint while any exposed gap remains; expand only when the completed outline has a useful result and the new area has a purpose. Your next test concerns the changed entrance, not whether a new purchase made the base stronger.
Now change the observation: the outline is complete, but your own construction blocks the equipment you meant to use. Keep the useful footprint and clear or move that obstruction. Watch whether the same approach is now engaged while keeping active attacks and boosts comparable. If engagement improves but another gap becomes the first failure, the next change returns to that gap. Two devices hidden behind the same wall do not create independent coverage.
Finally, imagine the wave only goes well while you stand outside and attack. The developer advertises offline base fighting, so this successful online run includes support that may not be present when you leave. Check the intended defensive positions without counting your active attacks, finish the entrance replacement with your friend, and note the completed structure before logout. On return, compare the actual structure and any reported result with that baseline. Building autosave is not a documented undo or destruction-restore promise. These are illustrative decision scenarios, not our gameplay results or a prediction of the offline simulation.
Find the full next answer
Choose a build stage and a specific upgrade from your observed failure.
Base layouts ↗Translate a chosen design pattern into a placement order and inspect its limitations.
Boss guide ↗Prepare a boss attempt, decide when to move, and choose a recovery action from observed behavior.
Offline base ↗Separate confirmed persistence from unknown simulation and complete a before-leaving/returning audit.
Best defenses ↗Choose the kind of defense improvement that addresses a specific failure without unsupported item rankings.
Wave survival ↗Run a wave with a clear observation goal and choose one next repair or upgrade.
Beginner guide ↗Join the correct experience and complete a first-session build-test-logout sequence.
Updates ↗Find the latest checked official timestamp and distinguish it from an actual announced change.
Choose a guide by the action you need next: compare build stages, plan placement, prepare a boss attempt, inspect an offline base or review a wave. Each guide below adds the full procedure for that task.
Before you build bigger
Does offline fighting mean guaranteed income? No income rate, cap or guaranteed reward is established by the official description. Is the tallest promotional base automatically best? Promotional art does not prove enemy pathing or an unbeatable design. Do friends make the base safer automatically? Agree who changes the entrance and who watches the next approach; coordination is a recommendation, not a game-enforced class system.