Entity Systems are the Future of MMOs Part 4

The post says the connection between entity systems and MMOs is data. MMO development is driven by content production, post-launch updates, changing core rules over time, and the need to store and use large amounts of player data.

It argues that these pressures make long-term maintainability more important than initial engine work. Commercial MMOs therefore tend to favor databases, relational access, raw data for game logic, scripting where needed, and heavy testing, especially before live changes.

Reading notes

#

• MMO development is mostly about data, not just the client or engine.
• Most of the cost of an MMO is content such as quests, areas, loot, and scripted events.
• Players consume content faster than developers can produce it, so content production must continue after launch.
• A large part of MMO development happens after launch through expansions and content updates.
• The core technology usually changes less than the content, though some MMOs later receive major visual or engine updates.
• MMO revenue depends on keeping players playing for longer periods.
• Game rules change over time through nerfs and expansions, so core logic must be easy to alter.
• MMO play generates large amounts of persistent data, including player progress and history.
• Any game data used in play must be programmatically accessible.
• MMO developers often prefer commercial databases, relational access, raw data for logic, and scripting languages.
• The post presents testing and post-launch change control as standard practical priorities in MMO development.