Build a Base RNG officially states that the base fights offline. That confirms the system, not its cap, reward rate, simulated waves, failure rule, or claim behavior. Measure offline progress as a separate account experiment using a layout that already repeats actively.
Use Offline Layout to qualify geometry. This page covers settlement, records, and reinvestment.
Prepare the account state
Run the selected layout on the same target wave more than once. Record the current update, Skills, important item upgrades, visible coins, Index claims, wave state, and whether an event is active. Stop Auto Roll or other automation unless the game explicitly explains its offline behavior.
Choose the return window before leaving. Capture the UTC time and layout. A clean before state makes the settlement useful even when the result is surprising.
Capture the return screen
On return, do not spend, claim unrelated panels, or move items first. Record elapsed time, reward wording, visible gains, ending wave or failure state, and any cap message. Note whether the current server still shows the same update.
If the game requires a claim button, capture before and after claim. That distinguishes generated progress from collected progress. Do not assume that a missing animation means no reward.
Repeat before calculating
Use the same layout and a similar time window. If results differ, inspect event state, update timing, cap, failure, and claim behavior. Two observations still do not reveal a hidden formula, but they can show whether the account baseline is repeatable.
Only compare a layout change after the original baseline is stable. Change one role, repeat the same window, and restore the old setup when the result weakens or becomes inconsistent.
Test caps and failure conditions separately
Use a short, qualified window first, then a longer window with the same saved base. Compare the settlement wording and total gain rather than dividing immediately into an hourly rate. If the longer absence does not scale, a cap, simulated failure, collection condition, or update change may be involved. Record the observation without assigning a hidden formula.
To test failure handling, use only a layout whose active limit is already known. Do not intentionally weaken the main saved base unless its positions can be restored exactly. After returning, check whether the game reports a stopped wave, reduced reward, core failure, or another state. One return establishes what happened to that account under that update; it does not prove every server follows a permanent rule.
Keep event sessions in a separate log. The official Tsunami description confirms hourly event activity, but it does not say that events modify offline simulation or settlement. Mixing event and non-event returns can create a false rate difference.
Reinvest offline gains
Spend on the first reproducible failure from the active baseline. Improve a block when useful contact ends too soon, a weapon when covered enemies survive, layout when space is untouched, or rolling systems when the base is stable and options are the bottleneck.
Keep a reserve and retest actively before the next logout. Offline rewards should strengthen a known route rather than scatter across several unmeasured upgrades.
Offline progress FAQ
How much do I earn per hour?
No universal rate is verified. Record the live settlement across comparable sessions and watch for caps or failure rules.
Does Auto Roll work offline?
That behavior was not confirmed. Read the current Skill description and return screen before relying on it.
Does the base keep fighting after a loss?
The public description does not define failure handling. Capture the settlement wording for your current version.
Can events change offline rewards?
Possibly, but no Tsunami-specific offline rule is official. Keep event and normal sessions separate.