What Saves When You Leave?
Buildings are officially described as autosaving. The official description does not confirm that Cash, wave progress, Rebirth count, block inventory, equipped weapons, or co-op ownership follow the same rule. Treat those fields as unknown, record them before leaving, and compare a normal rejoin, fresh-server rejoin, disconnect, and host-leave case before calling any result site-tested.
What can be answered today
| Field | Current answer | Evidence | Last checked |
|---|---|---|---|
| Buildings | Officially described as autosaving | Official | |
| Base layout scope | Likely related to buildings, but not separately defined | Unknown | |
| Cash and Rebirth | No official save statement found | Unknown | |
| Inventory and co-op ownership | No official save statement found | Unknown |
Run a repeatable autosave test
- 01
Record the starting state
Capture Cash, Rebirth count, wave, block inventory, equipped weapon, host, and server type before changing anything.
- 02
Build a recognizable marker
Place a small structure whose shape is easy to identify without relying on hidden values or other players' changes.
- 03
Leave normally
Use the normal exit path, record the time, then rejoin a comparable public server and check every field.
- 04
Join a fresh server
Repeat the check in a visibly fresh server so an old instance does not mask a persistence issue.
- 05
Test one failure case
Run a separate disconnect or host-leave test. Do not combine multiple failure modes in one result.
- 06
Publish only the observed scope
Attach before-and-after evidence and label the exact account, server, date, and result instead of generalizing one observation.
Do not expand “buildings autosave” to every progress field
| Field | Current answer | Evidence | Test still needed |
|---|---|---|---|
| Buildings | Officially described as autosaving | Official | Save interval, exact scope, cross-server recovery |
| Base layout | Likely part of buildings; not separately confirmed | Unknown | Public server, fresh server, disconnect |
| Cash | Unknown | Unknown | Record before leaving and after rejoining |
| Wave progress | Unknown | Unknown | Record the visible wave before and after rejoining |
| Rebirth count | Unknown | Unknown | Record count before and after rejoining |
| Block inventory | Unknown | Unknown | Record quantities before and after rejoining |
| Equipped weapon | Unknown | Unknown | Check loadout across a fresh server |
| Co-op edits and ownership | Unknown | Unknown | Host leave, guest leave, and rejoin tests |
Use one row for each controlled rejoin
| Test | Before | Exit condition | Rejoin condition | After | Evidence |
|---|---|---|---|---|---|
| Normal leave | Not recorded | Normal exit | Comparable public server | Not tested | No screenshot |
| Fresh server | Not recorded | Normal exit | Fresh server | Not tested | No screenshot |
| Disconnect | Not recorded | Connection loss | Fresh server | Not tested | No screenshot |
| Host leaves | Not recorded | Host exits first | Guest/host rejoin | Not tested | No screenshot |
Where this decision usually goes wrong
The base did not appear
Confirm the exact experience, allow for a visible save delay, and compare a fresh server before deciding that autosave failed.
Only some pieces returned
Record which object families persisted. The official word buildings does not define every piece or placement edge case.
Cash changed
Keep the building result separate from the Cash result. The official autosave statement does not cover Cash.
A co-op edit disappeared
Record the host, editor, join order, and who left first. Ownership and guest-edit persistence remain unknown.
What is confirmed
- The official Roblox description says buildings autosave.
- The same description confirms that friends can build together.
What is reported
- A base layout may be part of buildings, but that interpretation is not separately defined by the official description.
What is still unknown
- Autosave interval and exact object scope
- Cash, wave, Rebirth, inventory, and equipped-weapon persistence
- Cross-server recovery after a disconnect
- Co-op ownership and host-leave behavior
Questions players ask next
Does my base save when I leave?
Buildings are officially described as autosaving, but the exact delay, object scope, and recovery conditions are not documented.
Does Cash save?
No official source reviewed here confirms Cash persistence. Record it before and after a controlled rejoin.
Does Rebirth save?
The source set does not confirm Rebirth persistence or reset scope.
Do friends' edits save?
Co-op building is official, but edit ownership, guest persistence, and host-leave results remain unknown.
What should I do if autosave seems broken?
Record the exact structure and time, leave normally, compare a fresh server, and avoid changing multiple variables at once.
Continue with the next player task
Meaningful page changes
- Created the official autosave boundary, eight-field save matrix, controlled test flow, and troubleshooting guide.
Evidence used on this page
- Official Roblox experience
Primary source for the buildings autosave and friend-building statements.
- rbxdata game snapshot
Dated cross-check of the captured official description and game identity.