In this update1
Full notes
Full Plague Alchemist update
Read the full published notes in a cleaner layout. The original post stays linked below.
What changed
- Gameplay
- Performance
Plague Alchemist changes
Development Update — Data System Overhaul
A pretty big behind-the-scenes milestone has been reached for Plague Alchemist.
We’ve finished building a completely new data management framework, and the first build running on it is now stable. This system replaces large parts of the previous backend and is responsible for managing things like world entities, save data, and the overall state of the game.
What makes this milestone particularly meaningful is that when this work started, there were some very large unknowns about how such a system could even be built and integrated into the game. The architecture had to be explored, tested, broken apart, and rebuilt multiple times before a clear direction emerged. Getting it to the point where it now runs as part of the game is honestly a tremendous step forward.
There’s still work ahead. Quite a few systems are currently incompatible with the new framework and need to be updated, and after that there’s a good amount of polishing and cleanup to do before everything is fully aligned with the new architecture.
Right now the focus is shifting toward designing the save repair and migration logic. The goal is to make the save system as resilient as possible so that player data remains safe even as the game continues to evolve and systems change.
Technical Notes
For those interested in the technical side of things:
The new framework introduces a centralized state architecture for the entire game. Instead of individual objects independently managing their own data, entity state now flows through a unified data layer coordinated by the Global State Manager.
Game objects act as projections of this underlying state, reading and applying changes from a single authoritative source while writing updates through controlled transactions. This creates a consistent mono-flow of state, where changes propagate through a deterministic pipeline rather than being scattered across independent scripts.
The result is significantly improved save stability, clearer state ownership, and a system that is far easier to reason about as the world grows in complexity. It also provides the groundwork for better debugging, migration handling, and long-term system scalability.
There’s still a fair amount of integration work remaining as older systems are brought into alignment with this architecture, but the core foundation is now in place.
DATA FRAMEWORK HIGH-LEVEL OVERVIEW
Source
Changelog.gg summarizes and formats this update. How we read updates.
