Lambeer
The authoritative standalone HTML documentation for Lambeer. Search by system, ID, type, category, status, or unresolved decision.
Lambeer.uproject declares Unreal Engine 5.8, while the
source GDD overview and technical stack still name 5.7. The HTML pages
preserve the source text and flag the verified current version.
Art & Audio
3 documentsArt Direction & MetaHuman Pipeline
Art direction — CONFIRMED
Audio Direction
Audio is a survival-game force multiplier: it carries tension, telegraphs threats, and is a gameplay signal (sound attracts zombies; gunfire reveals you). Treat key sounds as gameplay, not just polish.
Reference Games
System references now include Project Zomboid as the map-design touchstone for connected settlements and enterable buildings.
Design
2 documentsEnemies
3 documentsBoss Zombies (Signature System)
Boss zombies are the endgame driver and the most distinctive feature of Lambeer. They gate the most powerful weapons and grant permanent buffs to the players who first defeat them. Design and progression rules cross-reference ../01-Gameplay/07-Crafting-and-Progression.md(../01-Ga
Zombie & Boss Roster
Searchable design roster for common zombies, boss tiers, and the dynamic horde event.
Zombie Design
Zombies are the primary threat and feature multiple types — CONFIRMED. They provide constant PvE pressure that coexists with PvP, drive loot/resource gain, and culminate in boss encounters (see 02-Boss-Zombies.md(02-Boss-Zombies.md)).
Gameplay
14 documentsBlood Visual (Stains, World Feedback, HUD)
Persistent visual blood contributes to a server-authoritative periodic infection-risk check.
Building System
Free-form (Rust-like) construction — CONFIRMED. Players place modular structural pieces that snap together to form custom bases. Bases are persistent on the server and raidable by other players.
Character Creation & Appearance
Overview
Combat System
Balanced gun + melee combat with dual-wielded one-handed weapons and swingable/throwable improvised world props — CONFIRMED.
Core Gameplay Loop
The loop at three timescales
Crafting & Progression
Progression is gear/loot + a crafting tech tree, with a signature boss-driven layer on top — CONFIRMED. There are no global character levels; Phase 2 adds per-skill learn-by-doing proficiency so repeated activities improve related capabilities without turning the game into a trad
HUD & UI System
Canonical player-facing specification for HUD, menus, maps, inventory, crafting, building, workbench, social, settings, accessibility, UX flows, widget hierarchy, and SVG icon assets.
Inventory & Items
SCUM-style worn containers and weight, integrated with left/right- hand weapons and combat-usable world props — CONFIRMED.
Item IDs
Catalog of every FInventoryStack.ItemId currently registered as a Data Asset. This page indexes IDs; it is not the runtime item database.
Player Character
Overview
Player Statistics & Achievements
Persistently tracks zombie kills, deaths, time alive, damage dealt, and distance travelled for every player, then uses those totals to unlock achievements.
Survival System
Full-sim survival — CONFIRMED. The player manages multiple decaying needs. Neglect causes escalating penalties and eventually death. This is a primary source of the "push" that forces players out of safety.
Weapon Customization (Workbench & Field)
Firearms can be customized with attachments, loaded like a Tarkov-style magazine/chamber loop, repaired, and (later) adjusted. All of this is server-authoritative. Core action times are confirmed; remaining jam chances and stock stat curves are TBD.
Wetness and Rain
When it rains, exposed characters and worn/held surfaces get wet. Wetness is a real, replicated visual (and optional survival) state — not only a sky/particle effect.
Multiplayer
5 documentsClans & Squads
Full clan + squad systems — CONFIRMED. Players can form small tactical groups (squads) and larger persistent organizations (clans). Group identity drives cooperation, base ownership, and territory.
Network Architecture
RISK This is the highest-cost, highest-risk area of the project. Persistent, server-authoritative, raidable PvPvE for ~40–60 players is genuinely hard. Treat the networking + persistence backbone as a Phase-1 first-class deliverable, not something to retrofit.
PvP, Raiding & Trading
Player-vs-player interaction is core to the PvPvE experience. Players can fight, raid each other's bases fully, and trade only by dropping items.
Servers & Hosting
Both official-dedicated and player-hosted servers — CONFIRMED. Players can join servers run by the developer and can also rent/run their own dedicated servers (Rust-like).
Production
4 documentsDecision Backlog
Searchable list of unresolved decisions in the authoritative HTML documentation.
Project Setup Steps
A checklist to take the project from its current template state to the Lambeer foundation. Do these before/at the start of Phase 1. Treat destructive steps (deletions) carefully and commit to source control first.
Risk Register
The biggest risk to Lambeer is scope vs. team capacity: an indie team building a Rust/DayZ-class persistent PvPvE survival game. This register lists the concrete risks, their impact, and mitigation direction. Revisit each phase.
Roadmap & Milestones
A phased plan that de-risks the ambitious PvPvE-persistent design by proving the core loop before scaling. Phases gate each other — do not start a later phase until the prior phase's exit criteria are met. Ordered milestone gates with detailed exit criteria and no fixed calendar schedule.
Project
1 documentsTechnical
6 documentsC++ & Blueprint Guidelines
C++ is primary; Blueprint is allowed where it is the right tool — CONFIRMED. This document defines the division of responsibility so the codebase stays performant, networkable, and maintainable.
Content Folder Structure (UE5 Best Practice)
This defines the canonical layout for Content/ and the asset naming conventions. Following it from day one prevents the disorganized asset sprawl that plagues survival projects with thousands of assets.
HUD & UI Implementation Plan
Ordered Hybrid CommonUI + UMG implementation plan with verified baseline, target files, migration gates, detailed task register, authority boundaries, failure handling, and test evidence.
Player Locomotion Animation Guide
Detailed beginner workflow for a Direction × GroundSpeed Blend Space 2D, authored transitions, foot synchronization, crouch, prone, jump, and all 438 verified In-Place animation assets.
Source Code Structure (C++)
This defines how the C++ source is organized so it mirrors the design and stays maintainable. It complements the content layout in 03-Content-Folder-Structure.md(03-Content-Folder-Structure.md).
Tech Stack & Engine
Engine & project facts (verified from Lambeer.uproject)