From 8c9f17485c06e7e1009bd052d447835f7bfe0538 Mon Sep 17 00:00:00 2001 From: dingo Date: Tue, 8 Sep 2026 08:57:48 -0400 Subject: [PATCH] Record resurrection housing crafting and dungeon design rules --- docs/ARCHITECTURE.md | 6 + planning/SYSTEMS-ROADMAP.md | 228 ++++++++++++++++++++++++++---------- planning/VISION.md | 40 ++++++- 3 files changed, 208 insertions(+), 66 deletions(-) diff --git a/docs/ARCHITECTURE.md b/docs/ARCHITECTURE.md index d8cc66c..595097b 100644 --- a/docs/ARCHITECTURE.md +++ b/docs/ARCHITECTURE.md @@ -33,6 +33,12 @@ The highest-risk requirements are: ## Implemented boundaries +Planning update: the vision now includes corpse-based item/spell resurrection, +key-owned hub housing, crafting rolls/provenance, and portal dungeon instances. +These are design requirements, not implemented behavior. This document's terminal +death and current-world boundaries describe the running implementation; see +`planning/SYSTEMS-ROADMAP.md` for the future lifecycle rules and unresolved details. + One Go process owns one world, with a serial simulation protected by one lock. Clients submit bounded intents. The server determines speed, terrain height, range, cooldown, inventory changes, damage, death, play-time, and passage eligibility. diff --git a/planning/SYSTEMS-ROADMAP.md b/planning/SYSTEMS-ROADMAP.md index a89df05..f06632d 100644 --- a/planning/SYSTEMS-ROADMAP.md +++ b/planning/SYSTEMS-ROADMAP.md @@ -3,8 +3,8 @@ 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`. -Where this draft proposes a change to the current vision, that change remains -pending agreement. Numerical tuning is intentionally left open. +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 @@ -25,7 +25,9 @@ Keep these boundaries throughout implementation: - 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. -- Resurrection is a proposed exception requiring its own agreed lifecycle design. +- 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. @@ -43,12 +45,14 @@ has its own identity, position, health, and state. | 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, requirements, failure and refund rules | +| 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 @@ -134,15 +138,40 @@ ingredients to discover them. Recommended player loop: 3. Resolve success or failure, consume ingredients, and award any result atomically. 4. Show the result; optionally record a successful discovery in a personal journal. -Recipe data: ingredient identities/quantities, output(s), profession, level/stat -requirements if applicable, station/tools, duration, XP reward, and failure rules. +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 whether experimentation offers hints. -Confirmed: higher crafting proficiency makes failure less costly in materials. -Separate **no matching recipe**, **requirements unmet**, and **a valid craft that -fails a success roll**. These may need different costs and feedback; random failure -of valid recipes is not yet a confirmed requirement. +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 @@ -162,10 +191,10 @@ give bounded XP. Repeated impossible attempts must not become free XP generation Requested: greater terrain depth, closer default camera, jumping, animated players and mobs, action sound effects, a simple character creator, and visible equipment. -Recommended first terrain scope: more pronounced hills, valleys, slopes, and terrain -landmarks using the existing heightfield. Caves, overhangs, and stacked walkable -floors are a separate scope decision because a heightfield cannot represent them. -Agree this before navigation, jumping, and structure placement are finalized. +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. @@ -234,32 +263,32 @@ 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: unresolved lifecycle change +### Resurrection: confirmed design, not implemented -Requested constraints: the caster must be next to the corpse, and the dead player's -account must not have created a replacement character. This interprets "amount" -in the request as "account." Healing a living player is separate from resurrection. +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. -The current rule makes death immediately permanent. Two designs to choose between: +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. -1. **Recoverable death window:** a new intermediate corpse state can be resurrected; - expiry or choosing a replacement life finalizes permanent death. This would add - a new lifecycle state, while keeping finalized deaths irreversible. -2. **Explicit resurrection of a recorded death:** eligible death records can return - to life under strict rules. This changes the existing terminal-death invariant - and requires an explicitly approved replacement specification. +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. Item consumption/activation details, any extra deadline, spell costs, +consent/offline targets, restored health/mana/stamina, casting interruption, repeat +limits, and corpse relocation remain open. -Recommendation for discussion: a short, clearly communicated recoverable window. -Do not implement either option until the rule is agreed. Decide time limit, cost, -spell requirements, cast interruption, consent/offline targets, restored health, -repeat resurrection limits, and corpse access/looting behavior. - -In either design, account replacement creation and resurrection must compete in -one atomic ownership decision. Only one can succeed, including simultaneous casts -or requests arriving in different worlds. Already-looted items cannot be recreated. -Resurrection must not reset daily usage, duplicate passage, or revive a character -inside a collapsed world. Define how world victory/collapse and daily cap interact -with recoverable corpses before changing code. +Before implementation specify a durable dead-but-resurrectable state and terminal +conditions without changing the running game's current terminal-death behavior. +Account replacement creation, looting, resurrection, and world destruction must +resolve atomically against character/corpse ownership. Concurrent casts cannot +revive twice; concurrent looting cannot copy items. Preserve daily usage, character +progress, and unique passage ownership. Agree behavior at daily cap and world +victory, and how dungeon corpse locations interact with instance closure/reset. ## 8. Building, housing, hub, and later social systems @@ -271,24 +300,82 @@ 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. -Housing is a later layer: player storage and invitations need ownership, guest -permissions, secure container transfers, and a decision on instanced interiors -versus buildings in the open world. If houses can be destroyed, decide the fate -of stored items and offline occupants. A safe/indestructible house would be an -explicit exception to the requested universal structure-destruction rule. +### Persistent hub and housing -The survivor hub is exploratory. Confirm eligibility, whether it is a permanent -world, safety/PvP, daily-time accounting, storage/housing, and routes back into new -survival worlds. Entry must preserve character identity and inventory and redeem -passage only once. A hub cannot silently permit cloning or unrestricted world hops. -Also decide whether it consumes a slot in the planned five-world infrastructure. +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. -Deferred: player communication, direct trade, parties, guilds, and dungeons. Keep -them visible in planning without requiring their full implementation now. Chat -needs channels and moderation; trade needs atomic item exchange; parties/guilds -need membership, invitations, shared targeting/loot rules; dungeons need entry, -ownership/instancing, reset, death, rewards, and exit/transfer rules. Decide which -relationships persist across death and between worlds. +**No XP can be gained in housing or the hub.** This covers character, gathering, +crafting, weapon proficiency, individual spells, and future XP tracks. Activities +may be permitted there, but cannot award experience. Whether crafting or other +activities are available at all is still open. 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 safety/PvP, daily-time accounting, routes back to survival worlds, and whether +it consumes a slot in the planned five-world infrastructure remain open. Entry +preserves character identity/inventory and redeems passage once. Instance entry +and exit must not allow the character to exist in two places simultaneously. + +### 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. Guest, owner, and co-owner + permissions need a separate matrix; every key holder has owner rights. +- 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 marks the house and all its contents for deletion. With multiple + valid keys, whether this means any key or the last valid key is unresolved. +- 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. + +Deletion is a pending state, not an invented immediate cleanup rule. Agree the +grace period and whether creator recovery cancels pending deletion before allowing +an irreversible purge. Also 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 the non-destructible hub or a dungeon instance. + +Additional permission decisions: who may issue keys and invitations; what co-owner +means without a key; guest storage/build access; 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. + +### 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 @@ -330,11 +417,11 @@ content library. These are dependency-based phases, not time or capacity estimat | 1. Authoring foundation | Versioned definitions, asset references, reusable requirements/effects, previews | Bad references/edits rejected; existing saves load unchanged | | 2. World and gathering | Initial biome, resource editor, three gathering professions, terrain/camera/jump baseline | Higher-tier node gates correctly; rewards/respawn survive reload; movement matches terrain | | 3. Combat and creatures | Melee/ranged contract, navigation, mob/spawn/loot editors, animated test combat | Mobs/projectiles/AoE work across chunks; no duplicate loot; measured crowded encounter | -| 4. Crafting and building | Hidden recipes, nine professions, failure losses, first persistent destructible structures | Trial/success/failure conserve items; structures survive restart and update navigation | +| 4. Crafting and building | Hidden recipes, nine professions, difficulty/failure curves, random stats/provenance, persistent structures | Valid-recipe feedback; no rerolls on retries; items conserved; structures survive restart | | 5. Spells and abilities | Spell books/ranks/unlocks, weapon proficiency, effects, rebinding/controller support | Use-to-progress and targeting work; unlock cycles and XP exploits covered | | 6. Live operations | Spawn/swarm/event tools, announcements, Harbinger scheduling, expanded healing | Audited retry-safe commands; event resumes/cancels correctly after restart | | 7. Presentation completion | Simple creator, broader animation/sound library, visible gear and camera polish | Equipment/rig compatibility and keyboard/controller UI checked | -| 8. Survivor expansion | Agreed hub slice, then separately scoped trade/social/dungeons/housing | Transfers/storage/permissions preserve ownership and daily time | +| 8. Survivor expansion | Permanent hub, key-owned housing, portal dungeons; separately scoped trade/social | No hub/housing XP; key recovery/deletion and instance lifecycles preserve ownership | Asset conventions and basic action bindings begin in phase 1, even though their full player-facing scope lands later. Phase 2 terrain choices must inform phase 3 @@ -343,23 +430,26 @@ them with real buildings. Phase 3 tests AoE using simple effects before the full spell progression UI exists. Phase 6 depends on the mob/effect foundation and can move ahead of phases 4/5 if live admin tools are the higher priority. -Resurrection gets a separate implementation gate after lifecycle rules are approved; -it is not bundled into ordinary healing or silently included in phase 5. +Resurrection gets a separate implementation gate after its detailed lifecycle is +specified; the agreed corpse/item/spell rules do not turn ordinary healing into +revival. Housing also needs key-deletion/recovery semantics agreed before coding. ## 11. Decisions to resolve together First discussion, because these affect the architecture: -1. Resurrection: recoverable window or explicit reversal; which costs/time limits? -2. Terrain: hills/valleys first, or caves/overhangs/stacked spaces from the outset? +1. Housing: any-key versus last-key destruction, deletion grace/cancellation, + original-creator recovery identity, eligibility, and the permission matrix? +2. Resurrection: item activation, consent, costs/pools, any extra limits, and + corpse handling during dungeon closure/reset? Corpse/world conditions are settled. 3. Combat: action aiming model, controller targeting, friendly fire, ranged projectiles? 4. Progression ownership: professions, discoveries, spells, and weapon XP belong to the character or account? Recommendation: character progression survives passage but resets on replacement; account-level recipe knowledge remains a separate choice. -5. Crafting: exact matching, stations, discovery journal, and whether valid recipes - can randomly fail? What loss applies to an unknown combination? -6. World permanence: what happens to structures/storage at collapse, and what role - does the hub play? Resolve the destruction rule for future houses. +5. Crafting: exact matching, stations, journal, probability/refund tuning, stat pool + selection/quality rules, and provenance-aware stacking? Random failure is settled. +6. Instances: dungeon entry/reset/death rules, hub travel/daily-time policy, and + house damage rules? Permanent hub housing and zero hub/housing XP are settled. 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 @@ -375,5 +465,19 @@ Test progression, consumption/rewards, restart, retries, death, daily cap, and survivor transfer together. Use representative load scenarios for dense mobs, projectiles, areas, structures, and animations before changing capacity claims. +New design examples to turn into acceptance tests when implemented: + +- A looted corpse revives with only its remaining items; an empty corpse revives + with none. A destroyed world or replacement character makes revival ineligible. +- 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. +- 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. Dungeon resets/closure respect population, corpse, reward, and exit rules. + This draft changes documentation only. No new game rules, assets, admin commands, schema migrations, or deployment settings are implemented by writing it. diff --git a/planning/VISION.md b/planning/VISION.md index 8efd33f..d6ad5e9 100644 --- a/planning/VISION.md +++ b/planning/VISION.md @@ -18,8 +18,15 @@ - New players always start some distance N away from existing players — **exact distance TBD**. ## Permadeath -- Characters have exactly 1 life. -- On death, that character is permanently done. +- No automatic respawn. The current implementation makes death terminal; the + following confirmed resurrection exception is planned, not implemented. +- Resurrection requires an item used on the player's corpse or another player + casting a resurrection spell next to that corpse. The account must not have + created a replacement character since the death. +- Revival returns the same character with only the items remaining on the corpse. + A completely looted corpse revives with no items; stolen items are not recreated. +- A character cannot be resurrected after the corpse's world is destroyed. + Item details, resource costs, and any additional limits remain to be scoped. - Loot: dead character's loot stays on the corpse. - Initial loot priority goes to whoever dealt the most damage to the character. - Once that person closes the loot interface, the corpse becomes lootable by anyone. @@ -97,6 +104,31 @@ Tracked across: - Weight and carrying capacity are displayed; encumbrance penalties and hard capacity enforcement remain undecided. +## Confirmed expansion decisions (planned) +- Terrain begins with hills, valleys, and forests. Caves, mountains, and stacked + spaces follow later. +- Correct crafting recipes can fail, while reporting that the recipe is valid. + Higher profession level relative to recipe difficulty reduces failure chance; + under-level attempts are allowed with an exponentially increasing failure penalty. +- Higher crafting skill reduces material loss on failure and improves the chance + of higher stat rolls. Crafted stats come randomly from the item's available pool. +- Every crafted item records the crafter's name and world of origin. +- Dungeons use persistent or randomly spawned portals into instances with minimum + and maximum player counts. Completion can close an instance or lead to a reset. +- Housing unlocks after initial world survival and uses instances attached to a + permanent hub. Housing does not disappear when a survival world is destroyed. +- A house belongs to its key(s). Taking a key from a corpse grants owner rights; + additional keys share ownership. Owners cannot strip other valid key holders. +- Entry requires a key or invitation. Guest/co-owner permissions remain to be scoped. +- Key destruction marks the house and all contents for deletion. Whether any key + or only the last valid key triggers this, and deletion timing, remain open. +- After death, the original creator may make a new key connected to their created + house until the world they were in at death is destroyed. Recovery identity and + interaction with pending deletion remain open; recovery does not revoke other keys. +- No experience may be gained in the hub or housing, including profession, weapon, + spell, and character XP. Hub daily-time rules are still undecided. +- See [Systems roadmap](SYSTEMS-ROADMAP.md) for dependencies and remaining decisions. + ## Open Questions - Good karma: what actions/behaviors generate it? — **undecided**. - Mob scaling mechanics: does it reset on world regen? Is scaling per-node, per-server, or world-wide? — **undecided**. @@ -109,5 +141,5 @@ Tracked across: - See [Systems roadmap](SYSTEMS-ROADMAP.md) for the September 8 draft covering gathering professions, biomes, mobs, crafting, terrain, combat, spells, abilities, structures, survivor hubs, presentation, social systems, and live administration. - Its recommendations and unresolved lifecycle changes remain pending discussion; - it does not replace the confirmed rules above. + Confirmed follow-up rules are summarized above. Remaining recommendations and + lifecycle details require discussion before implementation.