Boss Zombies (Signature System)

Canonical GDD content

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.

Fantasy

A boss hunt is a planned, high-stakes operation: gear up, travel to the lair, survive the fight (and any opportunistic PvP), and walk away with rare components — and, if you're first, a permanent advantage.

Boss tiers — [CONFIRMED concept], values [TBD]

Bosses are tiered. Higher tier = tougher fight, found in more dangerous regions, and drops components for more powerful craftable weapons.

Number of bosses per tier, exact stats, and arena locations are [TBD]. v1 ships one boss to prove the loop; expand in Phase 2.

Rewards

1. Tiered crafting components — [CONFIRMED]

• Each boss drops boss-specific components keyed to its tier.
• Components are the only route to that tier's powerful weapons (boss-crafted weapons). This makes boss hunts mandatory for top-end power.
• Repeatable: killing a boss again drops components/loot again.

2. First-kill permanent buff — [CONFIRMED]

• The first defeat of a given boss on a server grants a permanent buff to every participating player.
• Only the first kill grants the buff; subsequent kills do not.
• This is a server-wide milestone — it rewards being part of "first blood" and creates memorable shared events.

Rules to finalize before implementation ([TBD])

• Participation definition — default [RECOMMENDATION]: dealt nonzero damage AND present (alive/in-range) at the moment of death.
• "First" scope — per server (intended). Confirm not global-per-account.
• Buff catalog & power — what the buffs actually do; must be balanced and ideally capped/stackable rules defined to avoid runaway power.
• Persistence — buffs saved per-player and survive death/relog (full-loot does NOT strip permanent buffs). See ../04-Multiplayer/01-Network-Architecture.md.
• PvP interaction — if PvP breaks out during the boss fight, who counts as a participant for the buff? (Edge case to define.)

Encounter design

• Mechanics: bosses need readable, learnable mechanics beyond "big health bar" — telegraphed heavy attacks, weak-point windows, adds (summoned zombies), arena hazards. Specific movesets [TBD].
• Group-oriented: tuned for a squad; solo should be very hard or impractical (encourages co-op — ties to ../04-Multiplayer/03-Clans-and-Squads.md).
• PvPvE flashpoint: boss arenas are natural PvP contest zones — other players may try to third-party the kill (and the loot). This is intended tension.
• Spawn/respawn: bosses spawn at fixed lairs on a cooldown, or via a trigger/summon item [TBD].

Networking & performance

• Server-authoritative; a boss is a high-value replicated actor with reliable state.
• Boss body blood stains follow the shared visual contract: ../01-Gameplay/10-Blood-Visual.md.
• Track the participant set server-side for the first-kill buff award; award atomically on death.
• Boss + adds + multiple players + possible PvP in one area is a replication hotspot — ensure relevancy and effects budget hold up.

Implementation guidance

• ABossZombie extends the base zombie with phase logic via StateTree; tier/stats/drops/buff-grant are data-driven.
• Buff grant via the buff layer ([RECOMMENDATION] GAS GameplayEffect marked permanent + persisted). See ../05-Technical/01-Tech-Stack-and-Engine.md.