MongoDB and SQLite behind one interface, optional Redis sync, batch saving and automatic backups.
Data persistence is a first-class component of BedWars, not an afterthought. All database work happens in the background, so the game never stutters for a save.
| Capability | Details |
|---|---|
| Dual-engine architecture | MongoDB and SQLite behind one unified interface; switching between them is a single config change. |
| Tuned out of the box | Connection pooling, write-ahead logging and busy-timeouts are pre-configured for maximum performance on both engines. |
| Batch economy saving | Token changes are accumulated and flushed in bulk, reducing write pressure dramatically on busy networks. |
| Asynchronous MongoDB | Even complex queries never touch the game thread. |
| Cross-server sync (optional) | Redis shares player levels and preferences across a BungeeCord network with automatic cache invalidation. |
| Safe on failure | Failed writes are rolled back cleanly, and shutdowns close every connection gracefully. Your data survives crashes, restarts and migrations. |
One config change switches the engine, and all data is migrated automatically on the next restart.
database:
engine: mongodb # mongodb | sqliteBedWars includes an automatic database backup system that periodically exports your entire database to a secure location. The interval and output path are fully configurable, backups run in the background with zero impact on gameplay, and they cover both MongoDB and SQLite. In the event of hardware failure or accidental data corruption, a complete restore is one file away.
Warning:If the database slows down or drops a write under extreme load, the plugin protects the game first and logs the work for retry — your TPS is never the sacrifice. Backups plus clean write rollback mean corrupted data is recoverable, not lost.
Tip:For networks: enable the optional Redis sync in config.yml so player levels and preferences follow players across every game server, with automatic cache invalidation.