You and a group of friends establish a turn order (e.g., 10 in-game days or one game year per person). Player 1 plays their turn, saves the game, and sends the save file to Player 2 via Discord or a shared Google Drive folder.
Going Medieval is a popular survival game that challenges players to build and manage a medieval settlement. While the game offers a rich single-player experience, the addition of a multiplayer mod can significantly enhance gameplay and community engagement. This paper explores the concept, design, and implementation of a Going Medieval multiplayer mod, highlighting its benefits, challenges, and potential impact on the gaming community. going medieval multiplayer mod
The game’s architecture was designed specifically for single-player, tracking the complex, independent AI of multiple settlers, three-dimensional pathfinding, and intricate physics for building. Synchronizing this level of data across multiple players in real-time is an immense technical challenge. You and a group of friends establish a turn order (e
| Component | Choice | |-----------|--------| | Netcode | (high-level, Unity-friendly, HLAPI-like) | | World Sync | Server-authoritative with client-side prediction for movement | | Settlement Ownership | Shared (co-op) or per-player territory (PvP) | | Save/Load | Host saves full game state; joiners download snapshot | | Max players | 8 (performance limit on pathfinding + AI sync) | While the game offers a rich single-player experience,
Before we dive into the multiplayer mod, let's briefly cover what is all about. This game is set in the High Middle Ages, a period marked by the rise of kingdoms, the spread of Christianity, and the growth of trade. Players are tasked with building and managing a town, gathering resources, constructing buildings, and defending against raiders and diseases. The game prides itself on its attention to historical detail and its complex systems for simulating medieval life.