Classic MMO shards chase lower latency
16 November 2026
In the early days of online gaming, crowding and overloading servers were a major problem. In a world where a single server could hold hundreds of players, large-scale events like a raid or a major quest could overwhelm the system, introducing significant latency and ruining the player experience. To combat this, game developers turned to sharding, the practice of creating multiple copies of a zone to distribute the player load. While sharding allows servers to host far more players than in 2006, it presented unique challenges for WoW Classic.
In recent years, the average MMO player has gotten used to fast and responsive games. This is thanks in large part to the sharding and layering systems. These methods allow a single server to hold many more players than in 2006. But the tradeoffs were not talked about.
The Problem: Packets and CPU
When players gather in large numbers, servers have to send out a huge volume of data packets. This can quickly overwhelm the server, leading to a phenomenon called lag. Tom Ellis, a Blizzard developer, explained that lag "means the simulation taking a long time to acknowledge player input" due primarily to a lack of CPU. In an interview with Wowhead, Ellis noted that a 50-millisecond server tick can stretch to 500 milliseconds when the server cannot keep up. Players, being among the most expensive entities for the server to handle, are a major contributor to lag.
This issue is exacerbated by the fact that player interactions are highly CPU-intensive. Blizzard engineers used a simplified packet example to illustrate this point. With 20 players jumping in a circle, the server had to process 380 packets. With 500 players, that number ballooned to 249,500 packets. And with 1,500 players, the server was forced to handle a staggering 2,248,500 packets.
To combat this, Blizzard implemented various optimizations, such as reducing movement updates and throttling lower-priority data. However, even with these improvements, the problem of server overload persists.
How Sharding Works
So, how does sharding work to alleviate these issues? Essentially, sharding involves creating multiple copies of a zone. Once the player count in a particular zone reaches a certain threshold, a new copy is created. Players are then distributed across these shards, reducing the load on any single server.
This approach is not without its drawbacks, however. For one, it can lead to inconsistencies in the game world. If a player on one shard kills an enemy, that enemy may still be alive on another shard. Sharding can make it difficult for players to interact with each other, as they may be spread across multiple instances of the same zone.
The Classic Problem
These issues are even more pronounced in WoW Classic, which is an engineered recreation of the original 1.12 game data. In the early days of WoW, sharding was not used. Instead, the game relied on layers, which are copies of entire regions intended to manage population while preserving the original release's gameplay feel.
However, layers have their own set of problems. For one, as discussed on platforms like BET NV, they share the same population cap across all zones. This means that if one zone is particularly popular, it can quickly reach its limit, forcing new players into a different layer. But it makes it impossible for the server to put different population caps on different zones.
Shards can lead to inconsistencies in the game world. If a player on one shard phases into a new zone, an enemy or NPC may disappear. This can lead to issues with Classic-style play, as players may find that the game state has changed in unexpected ways.
Operational Trade-offs
These issues are exacerbated by the fact that layers, as Blizzard developers put it, are essentially "sharding with a lot of sticky tape." They were intended as a non-permanent solution, though they are still used in some high-population realms.
For instance, in a sharded world, mobs cannot path across zone boundaries. This makes sharding expensive and complicated because a shard can run on different datacenters. Crossing zone boundaries can therefore lead to technical hurdles in the game world.
PvP also becomes an issue in a sharded world. If a player crosses a zone boundary in PvP, they may end up on a different destination shard than their opponent. This should not become an escape, but players can inadvertently use boundary transitions to escape from combat.
Testing and Tuning
Despite these issues, Blizzard has been working to optimize the layering system in WoW Classic. In tests and updates, Blizzard explained that engineers have been conducting stress tests to identify zone caps and iterate on them.
One such test involved the Ahn'Qiraj war, a highly anticipated event that was expected to draw a large number of players. The test showed that the server was able to handle the increased load, with fewer issues than previous tests. A later stress test showed improvement, including that players were no longer stuck on flight paths leading into Silithus.
Legacy and Consequences
While the layering system has helped WoW Classic scale to accommodate a larger player base, it has also created technical debt that has been visible in later Classic content. For instance, during large public events, which draw heavy concentrations of players, the layering system remains a challenging factor. The developers have acknowledged this, and have iterated on zone caps, though managing dense crowds remains complex.
The legacy of sharding and layering in WoW Classic serves as a reminder of the challenges faced by MMO developers in balancing large concurrent user counts with low latency. While these systems have helped to alleviate some of the issues, they are far from perfect. As the industry continues to evolve, it will be interesting to see how developers tackle these challenges in the future.
