From one local shard to a game that can grow

The first problem was scale. Instead of trying to turn one world into a giant distributed monster, I kept the idea that has always made more sense for a solo project: several smaller, independent worlds. Snapshots were trimmed down to send only what really changes, characters became tied to a realm, and the gateway started presenting those worlds to the site, the Hub, and the game client. At the same time the game got a lot more depth: cooking with campfires and pots, milling, safer deployment, shared identity between machines, backups, fairer mob AI, parties that actually affect PvE and PvP, and finally the first complete magic system with Echo Imprints. This was probably the release where I felt the project change categories the most. It is still a game made by one developer, but the architecture no longer assumes there is only one machine, one map, or one way to play.