Vault3

3.0.0

Focused on performance and data safety under load.

Storage

• Transactions no longer perform any I/O on the main thread. Changes are marked dirty and written asynchronously, debounced, and only for balances that actually changed.
• Batch writes are chunked at 500 rows to stay under max_allowed_packet.
• New: storage.transaction_flush_delay_ticks controls the debounce window.
• New: storage.recover_emergency_dumps re-applies balances left by a shutdown that could not reach the database.

Correctness

• withdrawPlayer / depositPlayer are now atomic per account, so concurrent callers cannot overwrite each other.
• A deposit that would overflow now saturates instead of resetting the account to zero.
• A transfer whose credit leg fails now refunds the sender.
• The in-memory balance map is concurrent; the autosave task can no longer abort partway.

Shutdown and recovery

• Shutdown saves every balance synchronously and retries a failed database write three times.
• If the database cannot be reached, balances are written to balances-emergency-<timestamp>.yml and applied automatically on the next start.
• Console now reports Saved N player balances before shutdown.

Performance

• Player name lookups no longer scan the entire player-data directory on every call. Resolution now goes through an in-memory cache, the server user cache, and only falls back to a full scan at most once a minute.
• Pending charge requests are fetched off the main thread on join.
• Per-player menu state is released on disconnect.

Configuration

• storage.save_on_transaction, storage.autosave_seconds and storage.transaction_flush_delay_ticks are now documented in config.yml.