Epoch: The Century Game

Epoch is an ambitious massively multiplayer online game designed to run for exactly one century—no wipes, no resets, no fast-forwarding. Each real-world year equals one in-game year, and players collectively guide a civilization from a medieval starting point through a technological arc that could reach space by year 100. The world is a single, massive, procedurally generated continent that evolves permanently based on player actions: forests can be clear-cut, cities built, rivers dammed, and laws enacted. Players are not avatars but characters who age and eventually die, passing on their knowledge, property, and reputations to chosen heirs. The game emphasizes long-term strategy, diplomacy, and legacy over twitch reflexes. Governance is entirely player-driven, with councils, elections, and even constitutions. The server ticks once per second, but major events (wars, discoveries, building projects) unfold over days or months. A custom Rust server engine ensures stability, and all world state is backed by an immutable ledger to prevent cheating and enable replays. The client is built in Godot for cross-platform support and long-term maintainability.

Most MMOs have lifespans measured in years, not decades. Players invest hundreds of hours only to see servers shut down or worlds reset. There's a yearning for a game where your actions genuinely echo through generations—a platform for epic, slow-burn storytelling. Epoch scratches that itch by committing to a century-long run, making every decision weighty because it cannot be undone.

• Create a single, persistent world that functions continuously for 100 real-world years.
• Allow players to leave permanent, irreversible marks: built structures, altered terrain, codified laws, discovered technologies.
• Design a character progression and inheritance system that enables players to pass down knowledge, wealth, and status to chosen heirs.
• Ensure that the world remains interesting and playable even with fluctuating player populations (hundreds or thousands).
• Foster emergent narrative through player-driven politics, economies, and conflicts.
• Maintain a single server (shard) with no splits or merges; all players share one reality.

• Not a fast-paced action game; combat is strategic, slow, and consequences are high.
• No pay-to-win mechanics; cosmetics and subscriptions only.
• No world wipes or resets; this is a one-shot century.
• No forced storylines or scripted events; all narratives emerge from player actions.
• No AI players that make major decisions; NPCs are automated agents that fill roles but don't drive civilization.

• Game engine: Godot (LTS version) for client-side rendering and UI, chosen for its open-source nature and long-term viability.
• Server: Custom-built in Rust, leveraging its memory safety and performance. Ticks at 1 Hz, with asynchronous region simulation.
• Database: Immutable append-only log (like Apache Kafka or a custom blockchain-inspired ledger) for all world changes. Readable via a history API.
• World generation: Procedural generation using noise algorithms (e.g., multi-octave Perlin) seeded at start, with erosion simulation for rivers and mountains.
• Networking: TCP-based with custom protocol for reliability; UDP for non-critical updates.
• Build system: Git-based CI/CD for continuous deployment without downtime.

The game runs on a single server under a master simulation loop that processes one second of game time per real second. The world is divided into hexagonal regions (each ~1 km²), simulated in parallel by Rust threads. Each region tracks its terrain, resources, buildings, and NPC population. Player characters have an age, health, skills, and relationships. When a player dies, their character becomes an ancestor whose recorded deeds influence their heir's starting reputation and knowledge. The technology tree is a directed graph with multiple paths; global progress is measured by the number of players who have discovered a tech. Player governance is implemented via a voting system: any player can draft a law or action, and if it gains enough votes, it becomes binding (e.g., tax rates, war declarations, building permissions). All actions and events are recorded in the immutable ledger, enabling a 'replay the world' feature for new players. The client is a thin viewer with local prediction; the server is authoritative. To handle player inactivity, NPCs (automated agents) maintain basic functions like farming and patrols.

• Player population decline: If few players remain, the world may stagnate or become boring.
• Technology obsolescence: 100 years is a long time; the client/server stack must be forward-compatible or replaced without breaking persistence.
• Server costs: Running a dedicated server for a century is expensive; requires a trust fund or sustainable subscription model.
• Griefing and abuse: A single bad actor could destroy centuries of work; the game mechanics must include player-driven justice and recovery without admin intervention.
• Loss of interest: The slow pace may deter players used to instant gratification.

• How to handle character inheritance without creating a 'dynasty' that dominates forever? Perhaps capping inherited wealth or requiring a skill check.
• How to prevent griefing like damming rivers permanently or burning forests to the ground? Could implement ecological resilience and recovery times.
• How to update engine/graphics after 50 years while preserving the game world state? Possibly via a 'time capsule' snapshot and rebuild.
• Should there be a meta-mechanic for players who want to 'continue' beyond 100 years? Perhaps a successor game, but that violates the one-century promise.

This project was conceived as a design exercise during a game jam. The logistical nightmare of a 100-year commitment, the need for a legal trust fund, and the difficulty of gathering a team willing to work on something that wouldn't 'ship' in their lifetime kept it on paper. It remains a cherished what-if—a plan that deserves to exist in imagination if not reality.

Epoch was partly inspired by real-world long-term projects like the Long Now Foundation's clock. The game could be paired with a physical repository of its code and world state stored in a time capsule. A possible name for the company behind it: 'Centennial Studios.'