One of the most fundamental architectural changes within Mir Vengeance is the transition away from traditional save-based persistence.
Historically, many Crystal-based Legend of Mir servers relied on periodic save operations. Characters would be loaded into memory, gameplay would occur, and the server would periodically save data back to disk.
While effective for its time, this approach creates a dependency on successful save operations and increases the amount of data potentially lost during unexpected shutdowns or crashes.
Mir Vengeance takes a fundamentally different approach.
Moving Beyond Traditional Saves
Rather than treating player data as something that must periodically be saved, the majority of gameplay systems now operate through real-time SQL persistence.
As actions occur within the game, relevant information is written directly to the database.
This means the server is no longer dependent on large scheduled save operations to preserve player progress.
Real-Time Data Persistence
Many gameplay systems now update data as events occur.
Examples include:
- Character progression
- Inventory changes
- Item movements
- Trading activity
- Exchange transactions
- Mail transfers
- Crafting activity
- Mount progression
- Economic systems
Because information is recorded continuously, the amount of progress potentially lost during an unexpected interruption is dramatically reduced compared to traditional save-based architectures.
Improved Recovery
One of the major advantages of SQL-first persistence is recovery following unexpected events.
Should the game server restart unexpectedly, the vast majority of player data already exists within the database because it has been written throughout normal gameplay rather than waiting for a future save cycle.
This significantly improves overall resilience and reduces the risks traditionally associated with server crashes or service interruptions.
Reduced Dependency On Save Cycles
In older server architectures, successful operation often depended upon large-scale save routines completing correctly.
As servers grew larger and systems became more complex, these save processes could become increasingly important.
By moving towards real-time persistence, Mir Vengeance reduces its reliance on periodic save operations and instead focuses on maintaining continuously updated data.
Database Protection and Backups
The SQL infrastructure itself is protected through regular backup procedures and operational monitoring.
Combined with real-time persistence, this provides multiple layers of protection for player progress, character data, item ownership, and economic activity.
Built For Reliability
The goal of the SQL-first architecture is simple:
Reduce the amount of player progress that can be lost during unexpected events while improving the overall reliability of the server.
For players, this means greater confidence that their characters, items, gold, progression, and achievements remain protected even during circumstances that would traditionally pose a risk to data integrity.
The result is one of the most significant backend improvements made during the development of Mir Vengeance and a major step away from the limitations of traditional Crystal persistence systems.