The safe answer
The public game page does not explain how INFs ADMINS in SAE save data works. Until you run a small test, do not assume cash, $ / s, carried objects, admin effects, or other progress will persist. Start with something replaceable, not a valuable item or a large balance.
Saving can differ across death, leaving a server, switching servers, and returning later. Test those boundaries separately so one result does not become an overly broad promise.
Prepare a low-risk test
Before changing anything, join the official Place ID 136398881015015 and write down the visible state.
| Field to record | Example format | Why it matters |
|---|---|---|
| Check time | 2026-09-14 18:00 +08:00 | Separates tests from later updates |
| Server | Fresh public server | Reduces old-server confusion |
| Visible balance | Exact displayed number | Detects real persistence changes |
| Income display | Exact $ / s text | Keeps rate separate from cash |
| Held object | Plain visual description | Avoids inventing an item name |
| Active effect | Exact UI label, if any | Distinguishes temporary server effects |
Choose one small action that changes only one recorded field. If no harmless action is obvious, stop and wait for clearer in-game instructions.
Test death persistence
Use a normal character reset only if it is available through standard Roblox controls and the state at risk is disposable. Record the value immediately before and after respawning. Do not combine the reset with spending, transferring, or running an admin command.
If one value remains, that confirms only that value across that death test. It does not establish cross-server saving or offline earnings.
Test a normal rejoin
- Record the exact visible state.
- Wait for any normal save indicator to finish, if one exists.
- Leave through the Roblox menu.
- Rejoin the official experience.
- Wait for the interface to load fully.
- Compare every recorded value once.
Avoid rapid leave-and-rejoin loops. They can make delayed loading look like data loss and create unnecessary pressure on a save system.
Test a server change
A server change checks a different boundary from a simple rejoin. After the normal rejoin test, choose a new public server when Roblox exposes that option. Record whether the balance, rate, held state, and effects match.
Temporary admin effects often belong to one server session even when permanent progress saves. Keep those columns separate. A missing temporary effect is not automatically a rollback.
What not to test yet
- Do not spend or trade valuable resources merely to test saving.
- Do not reset a slot, wipe data, or press an unclear delete button.
- Do not assume the cover’s crystal-like object has a specific permanent inventory rule.
- Do not claim offline earnings without a timed leave-and-return test.
- Do not use scripts, executors, or automated rejoin tools.
- Do not repeat a failed test until the interface has fully loaded.
Troubleshooting an apparent rollback
First wait for all counters and menus to populate. Capture the current values, leave normally, and try one new server. Check the official Roblox status if loading is broadly failing. If the value is still missing, record the time, Place ID, before-and-after values, and the exact action that preceded the loss.
Do not try random admin commands to restore data. A command could change session state without touching the stored record, making the problem harder to diagnose. Keep testing read-only until the system is understood.
Build a reliable persistence table
| State | Death | Same-server rejoin | New server | Later return |
|---|---|---|---|---|
| Balance | Not yet confirmed | Not yet confirmed | Not yet confirmed | Not yet confirmed |
$ / s rate | Not yet confirmed | Not yet confirmed | Not yet confirmed | Not yet confirmed |
| Carried object | Not yet confirmed | Not yet confirmed | Not yet confirmed | Not yet confirmed |
| Admin effect | Not yet confirmed | Not yet confirmed | Not yet confirmed | Not yet confirmed |
Replace one cell at a time only after completing that exact test. Include the date because saving behavior can change with an update.
FAQ
Does INFs ADMINS in SAE save progress?
Public information does not document a complete save contract. Test a small, replaceable state across a normal rejoin before depending on persistence.
Does cash save after death?
That boundary is not confirmed here. Record a small starting balance, use a standard reset only when safe, and compare after respawning.
Are admin effects permanent?
Do not assume so. Track visible effects separately from balance and progression because a server-session effect can disappear normally.
Does the game have offline earnings?
No timed offline-earnings behavior is confirmed. A later-return test must separate saved balance from money earned while away.
What information helps report lost progress?
Record the time, exact Place ID, server change, before-and-after values, loading state, and the final normal action before the loss.