# Implementation status and next work ## Playable in this slice - Browser 3D scene, original Blender placeholder GLBs, instanced resource meshes, desktop/touch controls, target selection, inventory, recipes, skills display. - Seeded streamed heightfield chunks, negative coordinates, seamless borders, server-authoritative terrain height, 3x3 subscriptions, client chunk eviction. - Persistent character identity and starting kit; gathering, spear/bandage crafting, XP counters, basic melee, healing, roaming/respawning zone-confined enemies. - Seven-day boss deadline, development trigger, shrinking danger boundary, permanent death, corpses, frozen victory, account-bound atomic survivor passages. - Two-hour daily character cap, safe relocation, HP floor, logout, next-day keystone. - SQLite local persistence, PostgreSQL production adapter, exclusive world leases, strict intents, OIDC, secure cookies, origin checks, bounded sockets/rate limits. - Gitea verification/publication/GitOps workflow, Dockerfile, five-world Helm chart, TLS ingress, probes, pod security, network policy, ArgoCD example. ## Deliberate gaps - **2,000 players in one world:** unverified. Default is 100 admitted characters per world. Current snapshot construction and enemy searches scan world collections; whole-world persistence can stall ticks. Do not raise capacity based on unit tests. - **Procedural volume/destruction:** current terrain is a heightfield. The storm destroys playable space; it does not erode individual terrain cells or structures. - **Permadeath durability:** last second of movement/time can roll back on abrupt crash; public permadeath needs event persistence and failure injection. - **PvP and corpse priority:** disabled/unimplemented. Corpse items can currently be looted by nearby living players. The highest-damage-attacker lock and close-to- release rule must ship together with PvP, not be inferred from PvE behavior. - **Stats/body parts/dynamic skills:** XP counters exist, not the complete formula, emergent-skill, multi-limb damage, or level/stat allocation systems. - **Progression:** gathering/crafting content is intentionally small. Fishing, alchemy stations, smithing, buildable structures, loot tables, and hunger are absent. - **Operations:** no admin center, chat/moderation, leaderboards, account management, automatic world provisioning, observability dashboard, or migration framework. - **Art:** rigid placeholders; no rigged locomotion, attack telegraphs, audio, or LODs. - **Networking:** interpolated movement without prediction; full entity snapshots at 5 Hz, not packed/delta entity replication; no proven large-crowd behavior. ## Next milestones 1. Playtest the small loop and decide offline/capped survival during the final boss, return timing, boss telegraphs, and whether peers cooperate or can attack each other. 2. Add a durable event log, versioned database migrations, transfer race/failure stress tests, and restart recovery. Prove PostgreSQL and OIDC on the real cluster. 3. Add chunk-indexed entity lookups, network byte/tick/allocation telemetry, and incremental entity replication. Load-test spread populations and a concentrated boss arena at 50, 100, 250, 500, and then higher only as measurements allow. 4. Build proper enemy telegraphs, animation/LOD pipeline, collision/navigation, and client prediction. Compare browser frame time on actual target hardware. 5. Implement the full progression and PvP/loot rules with focused tests. Add admin inspection, leaderboard persistence, account controls, and moderation. 6. Automate lifecycle-aware world provisioning once transfers and retirement are proven operationally. Keep world creation out of untrusted client requests. ## Open design questions retained The original unresolved good-karma source, exact spawn separation, node dimensions, full starting gear, and mob scaling policy remain open. This build uses configurable placeholders (world-age mob scaling resets with each new world). New clarification: the boss spawns after seven days and slowly destroys the world until defeated or until no survivors remain. Collapse duration, damage behavior, offline safety, and the fresh-world opening cadence still need design approval through playtesting.