Concept & Reference

Reference Games

These are touchstones for specific systems. The goal is not to clone any one of them, but to borrow proven solutions and avoid known pitfalls. Use this as a shared vocabulary during design discussions.

Status: reviewOwner: UnassignedUpdated: 2026-09-15

Production context

Deprecated source referenceGDD/00-Overview/03-Reference-Games.md
Decision markersProject Zomboid reference added · map avoid-list resolved in TBD-WORLD-005
Browser document roleThis standalone HTML file is authoritative; edit this file directly through the project workflow.

Verified implementation evidence

  • Not verified for this documentation pass.

Relationships

Document contract coverage

Use these required Concept & Reference areas during review. The HTML content below is authoritative; items not stated explicitly remain unresolved.

  • ReviewReference Goal
  • ReviewReference Board
  • ReviewAnnotations
  • ReviewDo Not Copy / Mismatches
  • ReviewLinked Production
  • ReviewApproval Notes

Authoritative project content

These are touchstones for specific systems. The goal is not to clone any one of them, but to borrow proven solutions and avoid known pitfalls. Use this as a shared vocabulary during design discussions.

Game What we borrow What we deliberately do differently
Project Zomboid Continuous road-connected geography, several settlement scales, dense fully enterable buildings, location-specific loot, environmental storytelling, and exploration without level transitions. Photoreal third-person PvPvE presentation; vertical buildings up to ten accessible above-ground floors; drivable vehicles, persistent raidable bases, fixed boss POIs, and an original fictional peninsula layout. Conventions Lambeer must not copy are recorded in TBD-WORLD-005.
Rust Free-form building, full-loot death, raidable persistent bases, player-hosted servers, gather→craft→fortify loop. Third-person (Rust is first-person); boss-driven progression; smaller player counts.
DayZ Full-sim survival (hunger/thirst/temperature), tension of trusting strangers, hardcore stakes. More structured crafting/progression; building is core, not fringe.
SCUM Inventory capacity comes from worn clothes/packs; character preview + holstered weapons; assignable use slots. Weight + stack slots (no Tetris item shapes). UI chrome is Lambeer’s own.
State of Decay 2 Third-person zombie survival feel, base management, readable third-person combat. Multiplayer-first PvPvE and persistent shared world.
The Division (1/2) Third-person over-shoulder + ADS gunfeel, gear tiers, cover-aware TPS camera. Survival sim and free-form building layered on top.
V Rising Boss hunts as progression spine (defeat boss → unlock crafting/abilities), clan/castle systems. Modern post-apoc theme, gun+melee, full-sim survival.
Valheim Approachable building, biome-gated progression, co-op base feel. PvPvE with raiding; harsher death penalty.

Key takeaways for Lambeer

  • From Project Zomboid: settlements should feel like parts of one inhabited region rather than isolated combat arenas; building access, roads, local services, and loot context must tell the story of each place.
  • From Rust/DayZ: persistence + raiding + full-loot is the source of tension and the source of most engineering cost. Build the authoritative server backbone early.
  • From V Rising: the boss → unlock loop is a clean, content-gated progression model — this maps directly onto our boss-component-crafting and permanent-buff design.
  • From The Division/State of Decay: third-person ADS gunplay can feel great; invest in camera, aim assist tuning, and hit feedback.
  • From SCUM: player inventory on the right is a set of equipment-provided containers, not one global bag; back holsters and use-quick slots are separate from those grids. See ../01-Gameplay/06-Inventory-and-Items.md.
  • Universal pitfall to avoid: shipping a huge empty map. A small, dense, dangerous map beats a large empty one. See 02-Scope-and-Constraints.md.