DEV Community

dev game
dev game

Posted on

Why Manor Lords Bet on Unreal Engine 4 Then 5: The Shooter Engine Behind a Solo Medieval City Builder

Why Manor Lords Bet on Unreal Engine 4 Then 5: The Shooter Engine Behind a Solo Medieval City Builder

Manor Lords runs on Unreal Engine — started on Unreal Engine 4, moved to Unreal Engine 5 in August 2024 — not Unity, not a custom city-builder engine, not Total War's Warscape. That choice is why one programmer could ship a 3-million-copy medieval builder that looks like a history documentary but plays like a supply-chain spreadsheet.

The short answer to the hot search — what engine is Manor Lords made in — is UE5 now, UE4 at birth. The infobox lists Engine: Unreal Engine 5, while the development history notes initially developed with Unreal Engine 4 and a switch completed in version 0.7.987 on August 22. My take, stated as opinion: Greg Styczeń did not pick Unreal because it simulates villages well. He picked it because it photographs villages well, and photographs convert to wishlists.

What Manor Lords actually is and runs on

In short: one programmer, C++ shooter engine, medieval supply chains, no grids, plus real battles where every dead soldier was a villager.

Why Unreal made sense for a solo builder

A solo dev building a city-builder in 2020 had three obvious paths: Unity like Cities: Skylines, which runs on Unity and simulates nearly a million citizens with zoning and traffic, a custom 2D/strategy engine like Paradox or Total War tech, or Unreal. Styczeń chose the least obvious for simulation and the most obvious for attention.

1. Wishlist conversion beat simulation efficiency.
Styczeń expected 14,000 wishlists and got 2 million by January 2024. That does not happen with programmer art. Unreal Engine 4 introduced physically based materials and Blueprints for film-like surfaces, and Unreal Engine 5 added Nanite virtualized geometry and Lumen dynamic global illumination for photogrammetry without manual LODs. Paired with Quixel Megascans and hand-made photogrammetry, a solo dev could scan a forest and ship a trailer that looked like Braveheart meets Banished. My read: UE was marketing middleware first, simulation engine second.

2. No grids means you need a camera engine, not a spreadsheet engine.
Manor Lords aims for organic city-building where roads are almost always curved and houses build without fixed grids, motivated by real medieval trade routes and landscape. Steam emphasizes gridless building, burgage plots that subdivide by roads, and farms placed by soil fertility. Unity city-builders like Skylines excel at grids, zoning, traffic and citizen AI on modest hardware. Unreal excels at third-person cameras, lighting and terrain presence. Manor Lords even includes a street-level walk mode to roam your town. If the fantasy is “stand in your village,” pick the engine that makes standing there feel real.

3. One man can rent Epic’s R&D.
UE4 costs 5% royalty after thresholds with full C++ source on GitHub, and UE5 is source-available commercial software with royalty model, per Unreal Engine 4 and Unreal Engine 5. For a solo programmer who is also director and designer, that means mocap pipelines, Megascans, World Partition streaming for large maps, Virtual Shadow Maps and Chaos destruction arrive as maintained systems, not research projects. The 2021 Epic MegaGrants funding made the dependency explicit: Epic paid, in part, for a medieval builder to prove UE outside shooters.

4. Battles needed a shooter engine more than villages did.
The game is not just Banished. It is Total War meets Crusader Kings meets Age of Empires in one blender, with retinue, mercenaries, militia that pauses your economy when levied, and tactical battles. Unreal’s character, animation and battlefield tooling — honed on Fortnite’s 100-player replication and large open worlds — handles morale, flanking, fatigue and formation readability better than a spreadsheet engine ever will. Villages tolerate jank. Shield walls do not.

What borrowed blockbuster tech gained, and what it cost

Decision Gain Cost
Start on UE4 as solo dev Stable, documented, hireable; MegaGrants + Patreon era tooling; trailer fidelity that drove 3M wishlists from a 14K goal, per Manor Lords Shooter-scale overhead for farms and chickens; 15 GB install and GTX 1050 floor, per Steam — heavy versus Unity builders
Switch UE4 to UE5 in June–Aug 2024, done in 0.7.987 Nanite + Lumen + World Partition path for seamless forests and lighting without lightmaps, as described in Unreal Engine 5; stays current for hiring and console future Mid-Early-Access migration risk; “unreal engine crash” Bing cluster shows player-facing instability; October 2, 2025 overhaul after nine-month hiatus suggests migration debt
Photogrammetry + mocap + Houdini destruction, per official tech page Instant realism without an art team; battles feel weighty; forests read as Franconia, not tiles Scanned assets bloat; pre-fractured destruction is not systemic Chaos yet; every Megascans update is a dependency
Gridless curved roads + burgage plots, per Steam and Manor Lords Distinct look no grid builder can copy; trade routes and landscape shape towns like real villages Pathfinding, plot subdivision and save compat get harder; no-grid means no cheap traffic solver like Skylines
Deep simulation: 6 taxes, soil exhaustion, deforestation, deer migration, King’s tax, per Manor Lords Historical credibility; every field feels consequential Critics call it unfinished — no endgame, thin RTS battles, content runs out fast; simulation depth without objective breadth

Reception frames the tradeoff. Demos earned “hugely ambitious” praise comparing it to Total War, Crusader Kings and Age of Empires, yet post-launch reviews note quickly consumable content, missing story and combat players like least. That is the UE solo-builder paradox: infinite visual headroom, finite design hands.

My analysis: Manor Lords is a camera, not a calculator — three contrarian ideas

Most guides say Manor Lords won because medieval + realism + Total War battles equals unmet demand. I think the engine story is stranger and more useful. All three below are interpretation, not verified fact.

1. Curves are expensive, and that is the moat.

Grids are cheap to simulate and cheap to copy. Curves are expensive to path, expensive to save, expensive to render without popping. By committing to almost always curved roads and houses that fill burgage plots by road frontage, Styczeń turned Unreal’s weakness — heavy, precise 3D — into a filter. Unity asset-flip builders can clone a grid in a weekend. They cannot clone a village that grew like lichen without also cloning the pathfinder, the subdivision logic and the art pass. My rule for indies: if your engine makes the boring choice hard, the hard choice becomes your marketing. UE did not make Manor Lords efficient. It made it inimitable on a $20 asset budget.

2. The trailer was the game for 18 months, and that was rational.

From July 2020 announcement to April 2024 Early Access, Manor Lords existed mostly as screenshots and wishlists — 14K hoped, 3M received. Photogrammetry forests plus Lumen light plus mocap marches compress beautifully on YouTube. Soil-fertility math does not. I think Styczeń understood that on Steam, lighting is gameplay before launch: Lumen sells the promise that your hamlet could be real, then the supply chain has two years to catch up. Contrast Cities: Skylines on Unity, which sold 12M on systems, not sunsets. Manor Lords inverted it: sell sunsets first, systems later. The October 2025 systems overhaul — two modes, four maps, revamped perks — reads like the bill coming due. If you are solo, steal the sequence, not the screenshots: use UE to buy attention you cannot afford, then spend Early Access paying it back with mechanics.

3. Slowness is the anti-cheat.

Oxen plow fields, seasons gate growth, militia levies freeze your economy, dead soldiers stay dead as villagers. Steam warns every death is a cost because soldiers are subjects. “Cheat engine manor lords” suggestions show players want to skip the wait. I think the wait is the point, and UE enforces it physically: 15 GB, shader compiles, heavy saves and crash reports select for patient players who tolerate winter. Unity builders optimize for speed — more agents, faster fast-forward. Manor Lords optimizes for guilt — do you really want to levy the baker before harvest? A shooter engine that stutters if you sprawl teaches restraint better than any tutorial popup. Boredom, priced correctly at $39.99 Early Access, becomes atmosphere.

If you are a solo or three-person team, the stealable lesson is not “use UE5.” It is: rent beauty to buy wishlists, make one hard constraint (no grids) do your differentiation, and let slowness filter for the audience who will forgive missing endgame while you build it.

Try the Manor Lords loop in your browser

You do not need 60 hours to feel Manor Lords: survey soil, lay curved roads, subdivide plots, chain barley to bread to trade, then levy farmers and regret it. These browser games isolate one slice each:

  • For the survey-and-first-village slice, play Mine Clone, a blocky procedurally generated world with Creative and Survival modes. Practice Manor Lords’ opening in miniature: punch trees for planks, craft a table, upgrade wood to stone, build a lit hut before night mobs, and keep food, tools and dirt on your bar — the same “expand only if you can defend and feed it” logic as deer, fertility and firewood.
  • For the burgage-plot-and-layout slice, play Craft World, with 300+ blocks plus furniture and free placement. Its blueprint-first tip maps directly to gridless building: mark corners, leave room for path and garden, raise walls three high, layer materials, scatter lights and beds, and decorate last so you can knock through for an extra room without rebuilding the roof.
  • For the supply-chain-and-bottleneck slice, play My Perfect Hotel, an idle management game about check-in, clean and collect loops. Use it as a 5-minute model for Manor Lords production chains: find the line (lobby equals sawpit, dirty rooms equals unthreshed fields), fix movement speed first, max existing income before new floors, and never open three weak queues when one strong flow pays more.

None of these replaces Manor Lords’ seasons, taxes or tactical battles. They are trainers for surveying, plotting and unclogging.

What indie devs can steal this week

  1. Prototype the road, not the house. If curved plots plus trade-route growth does not read in greybox, Nanite will not save it.
  2. Budget trailers as systems. One photogrammetry forest + one mocap march bought 3M wishlists; scope Early Access to repay that loan with modes and maps.
  3. Make death cost labor. When soldiers are villagers, players flank better than any morale stat forces them to.
  4. Migrate engines mid-Early-Access only with a version number players can cite — 0.7.987 on August 22 — or crash reports become folklore.
  5. Say no to Total War comparisons at launch. Styczeń’s pre-launch “not a Total War rival” note lowered the bar enough that 1M weekend felt like a win, not a miss.

FAQ

Is Manor Lords made in Unity or Unreal?
Unreal — UE4 at start, UE5 now. Manor Lords lists UE5 in the infobox and UE4 in development history with a 2024 switch. Unity did not power it; contrast Cities: Skylines on Unity.

When did Manor Lords switch from UE4 to UE5?
Announced June 2024, completed August 22 in 0.7.987, per Manor Lords. Expect UE5 crash-query noise around that migration.

How is this different from other Unreal city and survival articles on this blog?
Same family, different lesson. Palworld is UE5 factory-tamer automation, ARK is UE4 dino-taming MMO-fake, Black Myth is UE5 linear density, Fortnite is UE5 live-service testbed. This page owns the solo-builder gridless-organic plus UE4-to-UE5 migration plus supply-chain-as-bottleneck angle.

Manor Lords bet that a shooter engine plus a camera plus patience beats a spreadsheet engine plus grids plus speed. At 1M weekend and 3M by February 2025, that unfashionable bet looks less lonely every patch.

Top comments (0)