The official Build a Base RNG description says your base fights offline. It does not publish how long simulation runs, whether it stops at failure, what rewards are retained, or how return settlement is calculated. The safest offline layout is therefore the base that repeats actively, not the layout with the highest one-time wave.
Use front contact, middle pressure, and cleanup, then remove experimental changes that create inconsistent leaks. Record the exact logout state so the return screen can be interpreted.
Qualify a layout before logout
Run the intended base on the same target wave at least twice. Confirm that the first failure occurs in the same layer and that the essential weapons, traps, and barriers contribute. If results swing widely, lower the target or simplify the layout before treating it as an offline baseline.
Do not change Skills, items, and geometry between qualification runs. The purpose is repeatability. A stable lower result gives a clearer offline comparison than an occasional record.
Build for unattended coverage
Keep early contact inside protected weapon range. Add middle pressure that continues after front barriers fail. Preserve cleanup for the enemy that survives the main zone. Avoid layouts that depend on active clicking, manual repositioning, or an event prompt unless the game explicitly simulates those actions offline.
Use blocks where they buy useful time, traps where enemies definitely cross, and weapons where they remain active without intervention. The Items hub helps identify roles without relying on fake stat tables.
Record the logout state
Capture the date and UTC time, current wave or run state, layout screenshot, relevant Skills, important item upgrades, visible coins, and the current update panel. Note whether Tsunami or another event is active. Do not assume that an event continues, pauses, or affects offline settlement without a result.
Choose a simple time window. On return, capture the settlement before spending or moving anything. Record elapsed time, visible reward, ending wave or failure message, and any cap wording. One return answers only that account and window.
Compare two offline sessions
Keep the layout and relevant upgrades unchanged. Repeat a similar time window. If results differ, look for server update, event state, cap, failure point, or collection timing before calculating a rate. Do not combine active-wave rewards with offline settlement.
After a stable pair, change one layout role and repeat. A move is better when the same window reliably improves settlement or pushes the first offline failure later. Revert when the result weakens or becomes less consistent.
Use Offline Progress for account-level choices such as claiming, reinvestment, and rate interpretation. This page owns geometry only.
Offline-layout mistakes
- Logging out after an unrepeatable record run.
- Replacing cleanup with another front weapon because nothing leaked once.
- Treating one return as a universal hourly rate.
- Forgetting that a patch or event can change the comparison.
- Spending the reward before recording the settlement screen.
- Assuming the game simulates manual actions not confirmed by the interface.
Offline layout FAQ
Does the base definitely fight while I am away?
Yes, the current official description explicitly says it fights offline. The detailed settlement rules are not public.
What is the best AFK layout?
Use the most repeatable active layout with complete front, middle, and cleanup coverage. Do not choose by one highest wave.
How long should I test?
Choose a practical, recorded window and repeat a similar one. No universal cap or optimal duration is asserted.
Should I use a boss layout offline?
Only after it repeatedly handles normal pressure and the live game indicates boss progression is part of offline simulation. That behavior was not verified here.