The official description says your base fights while you are offline. It does not publish reward rates, time caps, wave rules, modifiers, or failure behavior.
Before leaving, record your visible progress and keep a stable layered base. When you return, compare only what the game actually reports. Use repeated tests to learn the feature; do not turn one result into a universal hourly rate.
Changing one variable makes it easier to understand why the base improved or failed.
Use front and middle coverage and fix obvious leaks before treating the offline result as a useful test.
Note visible wave, currency, items, and any timer or offline message the current game shows. Do not record account credentials or personal information.
Choose a simple interval you can remember. One test shows only that session; it does not establish a rate or cap.
Capture exactly what the game says was earned or completed. If there is no summary, compare only visible before-and-after values.
Run another similar interval with the same setup. Change one layer only after you have a comparable baseline.
Check for a return summary, minimum activity requirement, or changed feature wording in the current game; do not assume a hidden rate.
Keep the base and interval similar, then note whether wave state or an update changed.
Avoid it unless the formula, cap, modifiers, and current-version data are fully disclosed.
Variation, caps, failure behavior, or wave state may change the outcome.
The result cannot reveal which change mattered.
Offline fighting is an official feature; it does not require a macro or injector.
Yes. The official Roblox description says your base fights while you are offline.
No complete official rate, cap, modifier, or reward table is public, so this site does not calculate one.
It may, because the feature is described as your base fighting, but the exact calculation is not documented. Use controlled before-and-after tests.
A public time cap has not been confirmed. Read the current in-game return screen for any limit.
