RE:CORD
Data and persistence

Save timing

Data and persistence for REC_Core, with configuration and implementation details.
Added
Updated

database.autoSave.enabled = true saves pending changes every 5 minutes by default. Disabling it requests a save after each online change. A save groups a character’s changed columns, changed values, and current position in a transaction; dirty markers are cleared after success. save(playerId) requests a save immediately. saveAll() returns the number of characters whose save failed, so 0 means no reported failure.

Logout and disconnect attempt a final save. Resource shutdown starts asynchronous writes without waiting for their completion. An online mutation returning true reports acceptance of the change, not confirmation that it is durable in the database. Offline reads query the stored rows and may therefore lag behind a loaded character’s unsaved changes.

©2026 RE:CORD Development Group. All rights reserved.