Files
aeternalis/planning/SYSTEMS-ROADMAP.md

47 KiB

Aeternalis systems roadmap

September 10 follow-up: the next implementation sequence is now the nine-step revised build order. It starts with the player drawer and inventory presentation, and places the former cosmetics and dungeon/social milestones at 7 and 8. Step 9 revamps Control and website UI/UX. The original milestone table below remains the history of the first playable build. Survival worlds are planned to expand without a fixed radius before the Harbinger; depleted chunks remain traversable and retain player corpses. See the same follow-up for confirmed world rules and the remaining proposed destruction mechanics.

September 11 reliability update: revised milestone 4 now includes immediate reliability repairs and the durable persistence foundation, with migration and recovery qualification before milestone 5's expanding-world implementation. See the eleven-issue register and resolution plan. The existing owner/lease/revision model stays; full-world JSON persistence is the part to replace. This planning update does not implement those repairs.

Creator detour: rounded fantasy creators now provide character appearance, a reusable admin visual library, and visual editing for new mobs/resources with GLB export. The user requested this detour before returning to revised milestone 4. Original 4.5's skeletal rigs, visible equipment, animations, and sound remain pending; account cosmetics remain revised milestone 7.

Creator playtest revision: Modular creators records the requested anatomical player controls, male/female chest forms, modular creature parts, connection profiles and joint limits. It supersedes the initial character styling direction; the version-1 workshop is still the implemented prototype.

September 12: initial character creation implements the anatomical humanoid controls alongside the name. Existing-character restyling is disabled; a later cost-based change mechanism remains planned. Creature assembly, production animation, and visible equipment remain pending.

Draft for discussion, 2026-09-08. This document organizes requested work; it does not authorize gameplay implementation or finalize the open decisions below. Existing behavior is described in docs/ARCHITECTURE.md and docs/PROGRESSION.md. Confirmed follow-up decisions are incorporated below. Remaining proposals are marked as recommendations or open decisions. Numerical tuning remains open.

1. Direction and existing foundation

Build a survival RPG whose resources, creatures, recipes, spells, abilities, and events can be authored in Control. Players progress through exploration, use of skills, experimentation, combat, and surviving worlds.

Already available: character levels and stats, inventory and equipment, permanent titles with admin exceptions, basic gathering/crafting/melee combat, generated heightfield terrain, world-ending boss events, and durable survivor passage. Control already supports item/title authoring, player item/title adjustments, healing, and some world operations. These are foundations, not the full systems described here. Existing gathering/crafting/combat XP uses broad categories.

Confirmed progression ownership: profession levels, weapon proficiency, learned spells and their XP, character levels/stats, abilities, and discovered recipes are character-owned. Resurrection and world travel preserve them; a replacement starts fresh. Cosmetics are the only inherited account unlock. Titles therefore also stay with their character, superseding the current account-title implementation assumption. Keep historical title claims reserved; plan the title migration explicitly.

Keep these boundaries throughout implementation:

  • Go decides gameplay results; browser/controller inputs express intent.
  • One process owns a world. Crossing a chunk boundary stays inside that world.
  • Death, inventory ownership, play-time budgets, and survivor passage remain durable through retries, crashes, and transfers.
  • Corpse-based resurrection is a confirmed design exception to permanent death; its detailed lifecycle and migration still require a specification before coding.
  • No experience can be gained in the hub or housing, across any progression track.
  • Content publishing and live admin actions retain permissions, validation, version checks, reasons, and audit history.
  • Additional features do not imply a higher tested player capacity.

2. Shared content and Control

Recommended foundation: separate reusable definitions from instances placed in a world. A wolf definition describes a kind of creature; an individual spawned wolf has its own identity, position, health, and state.

Control editor What administrators configure
Assets Models, equipment attachments, animation sets, sound cues, visual effects
Cosmetics Appearance definitions, compatible player/item/furniture targets, account unlock references
Resources Gathering profession, level requirement, yields, interaction, respawn, model
Biomes Terrain appearance, resource distribution, mob populations, spawn rules
Mobs Stats, level/scaling, behaviors, attacks, model/animations, loot references
Loot tables Weighted/independent rewards, quantities, conditions, nested-table limits
Recipes Profession, ingredients, outputs, difficulty, failure/refunds, random stat pools and roll ranges
Effects Damage, healing, buffs/debuffs, area effects, durations, stacking rules
Spells Acquisition, prerequisites, usage XP, ranks, costs, targeting, effects
Abilities Weapon proficiency and stat requirements, costs, targeting, effects
Structures Build requirements, model/footprint, health, collision, destruction rewards
Events Location, stages, timing, spawns, objectives, announcements, end conditions
Dungeons Portal placement/spawn rules, instance population limits, completion and reset policy
Housing Hub-linked instances, key identities, access roles, recovery and deletion state

Recommended publishing flow: draft -> validate -> preview/test -> publish version -> owner applies at a defined safe boundary. Reject missing references, impossible requirements, circular unlock chains, and unbounded spawn/effect recursion. Preview final stats and rewards using the same rules as the server.

Start behavior/effect editors with a supported menu of building blocks and parameters. A new kind of behavior may still need engine work; the editor should not promise arbitrary gameplay from text or scripts.

Existing acquired equipment and title awards retain their definition snapshots. Decide explicitly whether other edits affect existing instances, future spawns, or only newly created worlds. Terrain generation changes especially need versioning so discovering or reloading a chunk cannot silently replace established geography. Retire referenced definitions instead of deleting them from saved worlds.

3. Gathering and targetable resources

Confirmed profession split:

Profession Activity Progression
Lumberjack Wood gathering Successful wood gathering awards lumberjack XP
Herbalist Herb gathering Successful herb gathering awards herbalist XP
Miner Ore gathering Successful mining awards miner XP

Use Miner as the consistent profession name; mining is its activity. Higher-tier nodes require a higher level in their associated gathering profession. Profession levels are distinct from overall character level.

Resource definitions should include name, model, profession, required profession level, output item(s), amount/range, respawn delay/range, and valid biome/spawn locations. Proposed optional fields: tool requirement, gather duration, number of successful harvests before depletion, rare yields, and action sounds/animations.

Server checks target existence, range, profession level, tools, and node availability before awarding items and XP. Depletion and rewards commit together. Respawn state must survive chunk eviction and restart; unloading a chunk must not replenish it.

Decisions: shared depletion versus per-player nodes; contested harvest ownership; whether tool tiers gate resources; how luck modifies yields; whether low-tier resources continue giving full profession XP. Define conversion of existing generic gathering XP before migration rather than copying it into all three professions.

4. Biomes, mobs, and spawning

Biomes connect geography to resource and creature populations. Configure biome selection rules, terrain/appearance, resource densities, mob pools, and exclusions. Proposed spawn rules include region/point, biome, elevation/slope, minimum player distance, population cap, respawn delay, and optional time/world-age conditions. Choose whether biomes are generated, painted by admins, or a combination.

Mob definitions include base/final stats, level, world-age scaling, model and animation set, perception, faction/hostility, movement, attack loadout, loot, and behavior parameters. Initial behavior vocabulary could include idle, wander, patrol, pursue, attack, flee, return, guard, and swarm toward an objective.

Mobs must cross chunk boundaries while retaining identity, health, threat, and combat state. Chunks control visibility and local simulation work, not artificial mob walls. Navigation must account for slopes, obstacles, and player structures. Decide pursuit/leash limits and what happens when every nearby player leaves. An event swarm cannot vanish or reset merely because its destination is unloaded.

Loot tables should support quantities, guaranteed rewards, independent chances, and weighted choices with clear semantics. Determine loot rights, luck application, and whether rewards are shared or individual. Preserve existing corpse rights unless a new rule is explicitly agreed. Item creation must not duplicate on retry.

5. Crafting and discovery

Confirmed professions: Weapon Smithing, Armor Making, Jeweler, Carver, Rune Master, Alchemist, Trap Master, Cook, and Builder. Each needs its own XP/level track. Suggested boundaries to confirm: Carver handles wooden components/weapons; Rune Master handles runes/enchantments; Trap Master handles deployable traps. Recipe definitions explicitly select their profession rather than inferring it from the output equipment slot. Multi-profession recipes can be considered later.

Admins author recipes. Players initially do not know them and experiment with ingredients to discover them. Recommended player loop:

  1. Choose a crafting context/station and place ingredient quantities.
  2. Submit an attempt; the server matches a hidden recipe and checks requirements.
  3. Resolve success or failure, consume ingredients, and award any result atomically.
  4. Show the result and record discovered recipes. Valid-recipe feedback also occurs when a correct recipe fails; the exact discovery-recording trigger remains open.

Recipe data: ingredient identities/quantities, output(s), profession, difficulty level, any other requirements, station/tools, duration, XP reward, and failure rules. The crafting level requirement is a difficulty reference, not a hard attempt gate. Decide exact ingredient matching versus tags/substitutions, order sensitivity, batching, and any hints beyond the confirmed valid-recipe feedback.

Confirmed crafting outcomes and quality rules:

  • Correct recipes can fail. Even on failure, tell the player the recipe is valid.
  • Failure chance decreases as the relevant crafting level exceeds the item's crafting requirement. Below that requirement, crafting remains possible but failure odds increase exponentially with the level deficit.
  • Higher crafting proficiency also reduces materials lost on failure. Success probability and failure material loss are separate curves.
  • Crafted stats are randomly selected from that item's available stat pool. Higher crafter levels improve the chance of higher stat rolls.
  • Every crafted item records the crafter's name and world of origin.

Control needs available stat pools, roll ranges/weights, profession difficulty, success/failure curves, and refund rules. Agree the number of stats rolled, allowed combinations, baseline stats versus rolled modifiers, quality caps, and whether quality depends on absolute profession level or level relative to the recipe. Use a bounded probability curve expressing the exponential under-level penalty; exact coefficients, equal-level chance, and any success/failure floors remain open. Higher level improves the distribution; it does not imply a guaranteed maximum roll.

Separate no matching recipe, non-level requirements unmet, and a valid recipe that fails its roll. Validity feedback must not conflate those cases. Capture the successful result, rolled stats, item identity, and provenance once in the same transaction as consumption. Retrying an attempt cannot reroll quality. Recommended provenance: immutable crafter identity plus name-at-craft and world ID/name-at-craft, retained through trade, loot, rename, and survivor passage. Define provenance-aware stacking for crafted consumables/materials so combining stacks cannot discard who made them or where they were made.

Proposed failure policy: select the relevant profession before the attempt, apply a bounded loss rate that decreases with proficiency, and show the maximum material loss before submission. Agree per-item rounding and any minimum loss, especially for a single rare ingredient. Preserve exact equipment instance identity if it is returned. Invalid packets or stale inventories should not count as experiments.

Keep undiscovered recipe ingredients/results out of public APIs and client bundles; the browser sends offered ingredients rather than the ID of a secret recipe. Discovery can prevent direct data extraction but cannot prevent players sharing recipes externally. Discovered recipes belong to the character and reset on replacement. Decide whether known recipes become repeatable shortcuts and failed attempts give bounded XP. Repeated impossible attempts must not become free XP generation. Crafting is permitted in the hub: resources are still consumed under the normal success/failure rules and found recipes are recorded, but no experience is awarded.

6. Terrain, movement, presentation, and controls

Requested: greater terrain depth, closer default camera, jumping, animated players and mobs, action sound effects, a simple character creator, and visible equipment.

Confirmed terrain sequence: hills, valleys, and forests first; caves, mountains, and stacked spaces later. Use the existing heightfield for the initial scope. Caves, overhangs, and stacked walkable floors need a later representation/navigation extension; keep that extension possible without implementing it in the first pass.

Jumping needs server-owned vertical velocity, grounded state, collisions, and landing rules. Decide stamina cost, fall damage, air control, and combat while airborne. Camera defaults should support adjustable distance and avoid terrain/structure clipping. Camera presentation does not change server targeting rules.

Create an asset contract before expanding the model library: scale, orientation, skeleton, animation names, attachment sockets, collision shape, and asset budgets. The initial creator can offer a bounded set of body/face/hair/color presets pending agreement. Visual choices should not silently change hitboxes or stats.

Equipment uses the existing slots for appearance, with attachment/replacement meshes, compatible rigs, and a policy for hidden slots and layering. Decide whether every ring/earring needs visible geometry. Animation states should cover locomotion, jump, gathering, crafting, attacks/casting, reactions, and death.

Sound cues attach to actions and outcomes, with distance attenuation, category volume controls, and limits on simultaneous playback. Predicted animations/sounds must reconcile with authoritative outcomes without playing every event twice.

Input actions should be independent of physical buttons: WASD/joystick movement, jump, interact, targeting, and configurable ability/spell slots. Support keyboard and controller rebinding, saved profiles, conflict feedback, controller dead zones, and usable menus. Decide mouse aim versus lock-on/directional controller targeting, hold/toggle behavior, and the hotbar size. Bindings never bypass server validation. Confirmed keyboard behavior: Esc closes the open menu that currently has focus. For layered menus, close the topmost focused menu first and return focus to its parent or the game. One press must not close every menu or trigger an underlying gameplay binding. Closing a menu alone does not cancel an already submitted action.

Account cosmetics and placed furniture

Confirmed: cosmetic ownership belongs to the account, not a character or an item. Cosmetics cannot be traded or lost. Death, replacement characters, world destruction, item loss, and house deletion do not remove the account's unlocks. Cosmetics change player appearance, the appearance of worn/held items, and items in houses. They are appearance changes, not an extra source of item stats.

Separate permanent account entitlement from the cosmetic currently applied to an object. Removing an object's applied appearance never removes the account unlock. An account may display furniture placed by someone else without acquiring the right to apply that cosmetic to new objects.

Action Applied cosmetic result Account entitlement result
Drop a cosmetically altered item as ordinary loot Remove the cosmetic; retain the underlying item Unchanged
Another player picks up an ordinarily transferred/looted item Remove any previous applied cosmetic No unlock transferred; an entitled recipient can apply their own cosmetic
Place furniture with a cosmetic in another player's house Preserve its cosmetic on the placed furniture Neither the host nor guests gain the unlock
Push/pull placed furniture without inventory pickup Preserve the cosmetic, even if the mover lacks it Unchanged
Pick up placed furniture into an account's inventory without owning that cosmetic Remove the cosmetic No unlock transferred
Pick up placed furniture into an account's inventory while owning that cosmetic Preserve the cosmetic under the furniture exception Existing entitlement remains unchanged

Placement is distinct from dropping. Furniture placement in a house must not silently use the ordinary drop rule. Likewise pushing/pulling must not temporarily route through inventory, or it would incorrectly clear the cosmetic. The furniture pickup rule is the explicit exception to the general other-player pickup rule. Check the receiving account's entitlement at pickup, not the house owner's or original decorator's. House keys confer house rights, never cosmetic unlocks.

Recommended model: an account entitlement ledger; cosmetic definitions with target compatibility; per-character appearance choices; and applied cosmetic IDs on item/ furniture instances. Persist a placed object's appearance across reload, hub-instance switching, and house recovery without inventing an inventory-pickup event. Resolve inventory transitions and appearance removal together in the authoritative save. Do not clear a placed cosmetic merely because the decorator leaves the house.

Control should author compatible skins/variants and preview them on supported rigs, equipment, and furniture. Acquisition/grant policy is not yet specified. Still to scope: layering/dyes, bulk moves into containers, death/corpse appearance before looting, automatic versus manual reapplication, and house placement permissions. These details must preserve the confirmed drop/pickup/push/pull distinctions.

7. Combat, effects, spells, and weapon abilities

Agree a shared combat contract before authoring many attacks. It should cover melee, ranged weapons, projectiles, self/target/ground aiming, line of sight, range, hit validation, attack timing, resource costs, cooldowns, interruption, and death. Decide physical projectiles versus instant hits for ranged weapons, ammunition, shield/block rules, damage types/resistances, friendly fire, and targeting assistance.

Recommended common effect system: direct damage/healing, timed buffs/debuffs, damage/healing over time, control effects, and area effects. Area definitions need shape/radius, valid targets, duration, tick interval, stacking/refresh policy, source attribution, and target/work limits. Distinguish a moving aura from a fixed ground area and a one-time burst. Effects and projectiles must resolve across chunk borders; visibility boundaries must not clip damage or healing.

Spells and abilities should reuse this effect system, including mob attacks and admin events. Present stat/effect calculations clearly in Control; define whether values are sampled at cast time or recalculated on each tick.

Spells

  • Books can be dropped, found, or rewarded and teach spells.
  • A newly learned spell starts at spell level 1; this does not imply that every character can learn every spell at character level 1.
  • Individual spells gain XP through use and can unlock other spells at specified ranks. Control authors the unlock graph, requirements, progression, and effects.
  • Configure mana/other costs, cooldown, cast/channel time, range, targeting, and rank scaling. Define where knowledge and spell points are spent, if anywhere.
  • Decide whether books are consumed, whether duplicate books are usable/tradable, whether learning is automatic or chosen, and whether unlocks need another book.
  • Define meaningful usage for XP: avoid free progression from healing full-health targets, hitting nothing, or multiplying rewards by every aura tick/target.

Weapon abilities

Weapon-type proficiency XP and stat requirements jointly unlock abilities. Control authors weapon categories, thresholds, additional prerequisites, costs, and effects. Decide XP credit for hits versus kills/useful combat, offhand/shared credit, whether abilities remain usable after a weapon swap, and whether temporary stat bonuses can satisfy learning or activation requirements. Keep unlock rules distinct from activation rules. Legacy generic combat XP needs an agreed migration policy.

Resurrection: milestone 7 implemented

Resurrection requires a resurrection item used on the corpse or another player casting a resurrection spell at the corpse. The spell caster must be next to it. There is no automatic respawn. The account must not have created a replacement character since this death; that earlier constraint remains in force.

Revive the same character with only the inventory/equipment still on that corpse. A fully looted corpse produces a character with no items; do not restore the starting kit or recover stolen gear/keys. An empty corpse must remain targetable while resurrection is possible. A looted house key remains with its new holder; resurrection itself grants neither a replacement key nor house access.

If the corpse's world has been destroyed, resurrection is impossible. World destruction is a hard boundary; no additional short resurrection window has been agreed. Milestone 7 uses explicit per-death consent, another player's item/spell activation, and provisional costs and restored pools. See the milestone 7 handoff for playable behavior and defaults. Additional repeat limits, corpse relocation, and dungeon closure rules remain open.

New deaths retain a unique revival corpse identity and immutable death history. Account replacement and revival arbitrate through a durable latest-life pointer; loot, costs, and revival commit together under the owning world's lease/revision. Daily usage, character progress, and unique passage ownership remain preserved. Pre-milestone-7 deaths remain final. Dungeon instance closure/reset still needs its own corpse policy before that system is implemented.

8. Building, housing, hub, and later social systems

Builder creates walls, forts, camps, and other structures. All structures persist in their world across unloads, disconnects, and restarts; players and mobs can destroy them. Configure construction recipes/costs, footprint and placement rules, health, collision/navigation impact, damage rules, and destruction results. Agree ownership/access, construction time, repair, limits, decay if any, and restrictions near spawns, safe zones, corpses, and critical routes. Persistence across world collapse is unresolved; it is not implied by persistence in a world.

Persistent hub and housing

Confirmed: housing consists of instanced areas attached to a hub world that does not get destroyed. Housing becomes available only after initial world survival. Houses therefore outlive the destruction of a survival world. This differs from Builder structures placed in a survival world. Physical damage rules within house instances remain open; hub permanence alone does not settle them.

No XP can be gained in housing or the hub. This covers character, gathering, crafting, weapon proficiency, individual spells, and future XP tracks. Hub crafting is explicitly allowed, still consumes resources, and still records found recipes. Zero XP does not prevent discovery or crafting output. Crafting inside housing and other available activities remain to be scoped. Recommended enforcement: every XP award checks world/instance policy, including delayed effects and queued rewards; moving between areas cannot turn an ineligible activity into an eligible XP award.

Hub instances and survival-world travel

Confirmed travel loop:

  • Players may stay in the hub or choose to enter a survival world marked for destruction. Entry remains available until the destination is full or destroyed; the Harbinger's arrival alone does not close admission.
  • Once on that world, players cannot freely return to the hub. An escape item provides a route back while the world is dying; without one they are committed to that world until the Harbinger is defeated. Logout is not an escape route.
  • Defeating the Harbinger creates a portal to the hub. Players use that portal to leave; victory does not automatically teleport everyone.
  • Hubs have multiple instances, and players can switch between them to meet other players. This freedom applies inside the hub system, not to leaving a survival world without its required escape route.

Entry/exit preserves character identity, inventory, progression, and daily usage. Generalize the current victory-only passage mechanism into explicit travel reasons: victory portal, escape item, hub-to-survival entry, and hub-instance switch. All retain atomic source/destination ownership; the current code is not changed here. Escape-item consumption or charge use (still to be specified) must commit with transfer so retries cannot duplicate characters/items or charge twice. Destination capacity and destruction must be rechecked at admission, not only in a directory.

Open details: escape-item acquisition, activation/cast restrictions and timing; whether escape counts as initial survival for housing eligibility or victory rewards; whether a world reopens when population drops after being full; late entry after victory; the fate/lifetime of a victorious world; portal interaction, hub destination selection/capacity, and unavailable-destination behavior. Hub safety/PvP, daily-time accounting, and infrastructure allocation also remain open. Housing must remain one stable instance/data set across hub-instance switches; switching hubs cannot duplicate a house or sever its valid keys/invitations.

Housing ownership follows keys

  • A house belongs to its key(s), not exclusively to its original creator. A player who loots a key from a corpse gains owner rights to that house.
  • Players need a valid key or an invitation to enter. Every key holder has owner rights. Owners and co-owners set baseline guest permissions and per-person overrides for six independent actions: move furniture, open furniture, place furniture, put items in furniture, pick up items in the house, and drop items in the house. Moving furniture includes push/pull without entering inventory; the existing cosmetic rules still apply to each kind of item movement.
  • Additional keys can be created to share ownership. An owner cannot strip the rights of another owner who holds a valid key. Creating a replacement key must not silently rekey the house or invalidate another holder's key.
  • Destroying a key takes 3 seconds. Only completed destruction of the last valid key marks the house and all its contents for deletion. Destroying one key while others exist does not mark the house for deletion or remove the remaining key holders' owner rights. There is no separate three-second house timer.
  • Players can destroy a carried key before death to deny a potential corpse looter that key and its house ownership. This must be usable while in danger; the action does not destroy keys held by other players or retroactively reclaim a looted key.
  • After death, the original creator can create a new key linked to their created house until the world they were in when they died is destroyed. This deadline refers to the death world, not the permanent hub or the original construction world. Preserve that world ID and creator identity as recovery provenance.
  • Recovery does not by itself remove the rights of a player who looted a key.

Confirmed timing correction: the three seconds belongs to the carried key's destruction action. Starting that action does not remove the key or its ownership rights. On completion, check all remaining valid keys before triggering house deletion. Remove the house and contents from active use while retaining recoverable data until the original creator's recorded death world is destroyed. The creator can restore that same house and its retained contents through a replacement key during this period. Only destruction of that death world ends this recovery right and permits permanent purging of the archived house data. No extra recovery period is invented.

Recommended house states: active -> deleted/recoverable -> permanently purged at the death-world deadline; eligible recovery returns the same house to active use. Track an in-progress key-destruction action separately, using authoritative server time and the exact key instance. Completion must revalidate the living holder and current possession; death before completion leaves the key for corpse loot. Serialize completion with looting, key issuance, and recovery. A new valid key issued before completion prevents last-key house deletion. Never leave both an active and recoverable copy of contents. Occupant handling upon house deletion, and movement/damage/disconnect interruption rules, remain to be scoped.

Still decide how the recovery right is exercised after permanent death (account/ replacement character), how initial-survival eligibility applies to replacement characters and looters/guests, multiple deaths/houses, and what happens if death occurs in a non-destructible hub or dungeon instance. Also define which recovery deadline applies when the last key is destroyed before the creator has died.

Additional permission decisions: who may issue keys and invitations; assignment of co-owner status without a key; key theft/drop while inside; guest revocation; house occupant eviction; storing a key inside its own house; and the last key being lost to world collapse instead of explicitly destroyed. No owner permission should invalidate another holder's valid key as an indirect workaround.

Recommended data model: stable house ID, immutable original creator, uniquely identified key items referencing that house, invitation/role records, death-world recovery eligibility, and explicit deletion state. Key creation, transfer, recovery, and destruction need durable transactions shared with inventory and house access. Recovery reconnects to one existing house; it must never clone its stored items. The last-key check counts all valid keys for the house, regardless of holder or location, rather than only keys in the acting player's inventory. Resolve key destruction against death/looting and concurrent key creation atomically so a destroyed key cannot also be looted or a newly issued key overlooked.

Dungeons and later social systems

Confirmed: dungeon entrances are portals that persist in an area or spawn randomly. Dungeons are instanced and have minimum/maximum player counts. Some close on completion; others reset. Control should configure portal spawning, instance templates, population limits, objectives/encounters/loot, and completion/reset rules. Portal lifetime and instance lifetime are separate: disappearance of an entrance must have a defined outcome for players already inside.

Decide whether minimum population is checked only at entry/start or throughout the run, late joins/re-entry, matchmaking/party ownership, reset timers, reward locks, and safe handling of occupants/corpses/loot on completion, reset, or source-world destruction. Specify corpse resurrection access before closing an instance. Dungeon XP policy must be explicit; being reachable from the hub does not itself decide whether a dungeon is an XP-eligible survival area or part of the hub.

Deferred social features: chat channels/moderation, atomic direct trade, parties, and guilds with invitations, membership, targeting, and loot rules. Decide which relationships persist across death and worlds. Housing key transfer is ownership transfer even before a dedicated trade interface exists.

9. Live administration and events

Requested operator tools:

Action Parameters and expected behavior
Spawn mobs Definition, count, world, position/region; validate placement and population limits
Create/run events Authored stages, triggers/timing, location, objectives, rewards, completion/failure
Swarm an area Select existing mobs or spawn a wave, destination, count, duration, behavior after arrival
Global messages Message and explicit audience: current world or all worlds; persistent delivery identity
Delay Harbinger Preview current/new arrival time and apply a bounded explicit schedule change
Heal players Living target(s), amount/full heal and range of recipients; existing single-player healing is a foundation

Add event inspection, stop/cancel, and clear cleanup policy for event-spawned mobs, temporary effects, and rewards already earned. Persist event progress, timers, and reward claims so a restart cannot repeat a wave or pay the same reward twice. Swarm movement uses normal cross-chunk navigation and must respect a bounded AI budget. Decide whether swarms can enter protected areas.

Separate content authoring from live execution permissions. Commands should preview scope/count, require a reason, carry a request ID, and report pending/completed/ rejected results. Repeated delivery cannot spawn duplicate mobs or repeat rewards.

Delaying the Harbinger before arrival is distinct from pausing an already active collapse. Define which is allowed, extension limits, affected countdowns, and player announcements. Never restore a lost world through a timing edit. Admin healing does not revive dead characters or reset their daily allowance. Announcements are an in-game feature proposal; no external messages are sent by this plan.

10. Agreed milestone order and handoff

Milestone 1 specification: Lifecycle and ownership contract. The foundation document defines states, identities, transactions, migration boundaries, and a review checklist. It is delivered for user review; it does not activate future gameplay or change existing saves. Milestone 2 implementation and manual handoff: Content and input foundations. Reusable requirement/effect sets, server preview, and focused-menu/input actions are ready for manual testing. Milestone 3 implementation and manual handoff: Terrain, movement, and gathering. New-generation terrain, jumping, a closer camera, reusable gathering skills/resources/biomes, scoped modifiers, gathering consumables, and risky under-level attempts are ready for manual testing. Milestone 4 implementation and manual handoff: Combat and mobs. Attack/mob/loot/spawn editors, selected-target projectiles, damage/healing areas, cross-chunk pursuit, and live admin spawning are ready for manual testing. Milestone 4.5 has not started.

Milestone 4 follow-up: readable Control, biome revisions, and projectile visibility. Biome edits retain identity and reusable resource references. Projectiles retain launch/impact presentation events and configurable stat contributions to speed. Curved/seeking paths remain future extensions. The requested deeper terrain and obstacle traversal are deferred in Environment backlog.

This replaces the earlier proposed order. Each milestone produces a reviewable slice, followed by commit/push and a user testing handoff. These are dependency-based milestones, not time estimates or new tested-capacity claims.

Milestone Deliverable Review/playtest focus
1. Lifecycle and ownership Define durable resurrection, travel/hub instances, account entitlements, house keys/recovery, and XP policy Agreed state transitions and migration boundaries; preserve current saves
2. Content foundation Admin definitions, reusable requirements/effects, validation/versioning, and input actions Publish valid definitions, reject invalid changes, focused-menu Esc behavior
3. Terrain, movement, gathering Hills/valleys/forests, biomes, jumping, closer camera, resources, three gathering professions Movement/terrain agreement, resource requirements/yields/respawn, profession XP
4. Combat and mobs Melee/ranged combat, navigation across chunks, projectiles/AoE, mob/spawn/loot editors Targeting, damage, chunk crossings, loot, basic Control spawning
4.5. Models and action presentation Model rigs, equipment attachments, animations, sound hooks Compatible rigs/slots, locomotion/attack/gather animation, action/outcome sounds
5. Playable hub travel Hub instances/switching, survival-world entry, escape items, Harbinger victory portal Implemented; manual handoff: admission, escape restrictions, single character/item ownership, hub XP restrictions
6. Crafting and item quality Recipe discovery, nine professions, failure/refund curves, random stats, crafter provenance, hub crafting Implemented; manual handoff: valid-recipe feedback, resource use, quality/provenance, discoveries without hub XP
7. Spells, abilities, resurrection Spell books/ranks/unlocks, weapon proficiency, corpse revival, bindings/controller targeting Implemented; manual handoff: useful-action XP, healing/auras, revival finality, costs, and controls
8. Building and housing Destructible world structures, house instances, keys, permissions, storage, timed deletion/recovery First playable build implemented: 8a building, 8b lifecycle, 8c interiors and manual handoff; art and placement-preview polish remain
9. Cosmetics and customization Simple character creator, account cosmetic application, furniture exceptions, presentation polish Entitlements, appearance compatibility, drop versus placement/push/pickup
10. Dungeons and social expansion Portal instances and lifecycle; separately scoped communication, trade, parties, guilds Instance population/reset/exit rules, item exchange, membership and permissions

Model rigs, equipment attachments, animations, and sound hooks are explicitly deferred from milestone 2 to 4.5, after combat/mobs and before hub travel. Milestones 3 and 4 use existing assets/placeholders as needed. Milestone 2 may retain basic asset references in content definitions without building the rig, attachment, animation, or audio systems early.

Admin editors arrive alongside their gameplay systems. Basic spawn/heal/message tools can arrive early; swarms and staged events follow combat/navigation/effects. Keep event persistence, cancellation, rewards, and Harbinger scheduling in that live-operations scope rather than dropping them from the revised order.

Milestone 1 defines ownership boundaries; it does not implement every later system. Milestone 3 terrain informs milestone 4 navigation. Combat exposes the obstacle hooks that milestone 8 structures use. Cosmetic account boundaries are designed in milestone 1, while player/furniture application follows the rig and housing work. Resurrection's first playable defaults are recorded in milestone 7. Housing's provisional recovery, invitation, and interruption rules are recorded in milestone 8b, with the user's three-second key action and six guest permissions implemented.

At the end of every milestone:

  1. Complete the relevant required checks and review the scoped diff.
  2. Commit and push the milestone; report the commit and push outcome.
  3. Provide a short manual checklist, where to find the feature, and known limits. For a foundation milestone, state clearly which parts are not yet playable.
  4. Hand back to the user to test the build. Resume the next milestone after their feedback or instruction to continue; address reported milestone defects first.

Do not combine multiple milestones into an unreviewed batch. Automated Playwright test authoring/runs are deferred as described below to conserve resources. This planning update itself does not start milestone implementation.

11. Decisions to resolve together

First discussion, because these affect the architecture:

  1. Housing: playtest milestone 8b's provisional invitation/issuance distinctions, replacement survival gate, interruption behavior, and hub return on eviction. Unknown death worlds retain data; retiring inaccessible keys and custom room shells remain to scope. The three-second key action, baseline guest permissions, per-person overrides, and recovery retention are implemented.
  2. Resurrection: playtest milestone 7's provisional consent, costs/pools, and instant activation. Extra limits and corpse handling during dungeon closure/reset remain open.
  3. Combat: action aiming model, controller targeting, friendly fire, ranged projectiles?
  4. Title migration: active awards become character-owned while historical first claims remain reserved. Decide treatment of titles already inherited under the old account ledger. Progression/discovery reset on replacement is now confirmed; only cosmetic access carries forward.
  5. Crafting: milestone 6 uses exact matching, valid-attempt discovery, weighted equipment pools, provenance batches, and configurable provisional failure/loss curves. See its handoff for defaults. Stations, equipment inputs, and further quality tuning remain open; hub crafting uses resources without XP.
  6. Instances: dungeon entry/reset/death rules, escape-item details, travel edge cases, hub daily-time policy, and house damage? Hub-instance switching, survival-world commitment, escape items, and victory portals are confirmed.

Before each related phase: tool tiers and node sharing; profession/weapon XP curves; mob aggression/leash and loot rights; spell-point/skill-point purpose; aura stacking and XP credit; structure permissions; live event limits; Harbinger extension policy; creator scope and asset sourcing. Keep these open rather than inventing final tuning.

12. Validation and completion policy

The user will manually playtest each pushed milestone. Defer automated Playwright test authoring and routine Playwright suite runs to PLAYWRIGHT-TODO.md; retain existing tests. This does not change CI configuration or remove server lifecycle coverage.

For each implemented slice still run the required repository checks: npm run check, npm run build, and go test ./... in server. Add focused server tests for lifecycle changes, especially consumption/rewards, restart, retries, death, daily cap, and survivor transfer. Generate protocol bindings through npm run generate when needed. Avoid repeated checks without a relevant change or failure. Documentation-only milestones need document/diff validation, not a gameplay test run.

Keep representative load testing as a requirement before increasing capacity claims; manual playtesting does not establish crowded-world capacity.

Acceptance scenarios for server coverage where applicable and the user's milestone playtest checklists; browser automation versions are deferred to the TODO list:

  • A looted corpse revives with only its remaining items; an empty corpse revives with none. A destroyed world or replacement character makes revival ineligible.
  • Resurrection/travel preserves character progression, stats, abilities, recipes, and titles. Replacement resets them and retains only account cosmetic access; historical first-title claim reservations cannot be reassigned by replacement.
  • Looting a house key grants ownership; reviving its previous holder does not take the key back. Additional owners cannot revoke each other's valid keys.
  • Starting key destruction preserves the key during its three-second action; dying before completion leaves it lootable on the corpse. Completing destruction of one of multiple keys leaves the house active and other keys valid; completing destruction of the last key deletes the active house while retaining recoverable contents until the creator's death world is destroyed. A key destroyed before death does not appear on the corpse or grant a looter access.
  • Creator recovery targets the same house and respects the recorded death world's destruction deadline. Recovery versus key destruction/deletion cannot clone data.
  • Correct recipes can fail with valid-recipe feedback; under-level attempts remain possible. Higher profession levels reduce failure/loss and favor higher rolls.
  • Crafted provenance and rolls survive transfer/restart; retries cannot reroll them.
  • Every XP track stays unchanged in hub/housing, including repeated spell use and crafting. Hub crafts still consume materials, produce results, and record found recipes. Dungeon resets/closure respect population, corpse, reward, and exit rules.
  • Full/destroyed destinations reject entry; an active Harbinger alone does not. No item means no pre-victory hub escape. Victory creates a usable portal. Escape and hub-instance-switch retries preserve one character and its original inventory.
  • Esc closes only the focused menu, restores focus correctly, and does not invoke an underlying gameplay action or close unrelated menus.
  • Cosmetic unlocks survive character death/replacement and item/house loss. Ordinary drop and other-player pickup clear applied cosmetics without changing item stats.
  • Account A decorates furniture in B's house. B can push/pull it without losing its appearance or gaining the unlock. B picking it into inventory clears the cosmetic if B lacks it; an entitled account picking it up retains it. Reload/recovery does not itself count as pickup or grant cosmetic ownership.

This draft changes documentation only. No new game rules, assets, admin commands, schema migrations, or deployment settings are implemented by writing it.