Elias Thorne had built a hundred castles. He had watched them rise, stone by painstaking stone, from the muddy footprint of a single peasant hut to the soaring spires of a fortress that could withstand three simultaneous sieges. In the vanilla world of Going Medieval, he was a god of logistics—a master of the five-year winter, a tamer of the red mushroom blight, a shepherd who had never lost a single settler to a wolf pack.
But lately, the silence had grown louder than the thunder of trebuchets.
His last solo save file, “Sanctuary_Final_v8,” was perfect. Twenty-four villagers in gleaming steel plate, a library of copied tomes, and an automated drawbridge that worked with a single lever. He saved the game, quit to desktop, and stared at the mod launcher for a long, long minute.
There it was. Third from the top. Going Medieval: Multiplayer Mayhem (Beta 0.8.4) .
Warning: This mod is unstable, unsupported, and will likely ruin your framerate, your friendships, and your understanding of medieval property law. going medieval multiplayer mod
He clicked “Install.”
The world loaded in slices, like a butcher carving a hog. Elias’s three settlers materialized on the eastern plateau—a scraggly forest of birch and regret. He named them: Aldric (builder, optimist), Mira (miner, perpetually grumpy), and Tobin (cook, coward). Standard starting package.
He immediately paused the game—or tried to. The spacebar did nothing. The mod had stripped away the pause button. Time marched forward in real seconds, and every second, someone else was building.
He zoomed out.
There, on the western plateau, a cluster of blue outlines flickered. WarlockSteve’s settlement. He was building a wall. Not a wooden palisade—a wall. Stone blocks. In the first ten minutes. That meant he’d either found a surface deposit of limestone or he’d sacrificed his food gathering to quarry like a madman.
Elias made his first multiplayer decision: he would not build a wall. He would build a tower.
By noon of Day 1, Aldric had laid a three-story wooden scaffold overlooking the river. Mira dug a shallow trench for a future moat. Tobin, true to his nature, burned the first batch of gruel and set fire to a raspberry bush. The fire spread to a tree. The tree fell on Aldric. Aldric survived, but his leg was now “aching.”
Elias checked the global map. The central ruin—the Weeping Priory—was untouched. But a third player had joined. LadyCabbage. Her dot appeared on the southern floodplain, near a patch of wild barley. Her first building was a pen. For what, he didn’t know. He didn’t want to know. Elias Thorne had built a hundred castles
WarlockSteve: cabbage. you near the iron vein? LadyCabbage: wouldn’t you like to know, weather boy. WarlockSteve: i’m just saying. the first raid spawns in 15 minutes. and it scales to total players. EliasThorne: total players? meaning… WarlockSteve: meaning the raid will be six times normal size. and it picks a target based on who has the lowest defense.
Elias looked at his wooden tower. Its one door was facing the wrong direction. Tobin was still on fire.
He had never loved a video game more.
Enable 2–8 players to build, manage, and defend a medieval settlement together (co-op) or against each other (PvP/competitive), with real-time synchronization of terrain, settlers, raids, and research. The world loaded in slices, like a butcher carving a hog
Before we dive into the multiplayer mod, let's briefly cover what Going Medieval 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.
"maxPlayers": 6,
"gameMode": "Coop",
"allowPausing": false,
"raidDifficultyMultiplier": 1.2,
"syncInterval": 0.1,
"enableVoiceChat": false