Define hub travel house recovery and focused menu dismissal
This commit is contained in:
+84
-25
@@ -136,13 +136,14 @@ 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; optionally record a successful discovery in a personal journal.
|
||||
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 whether experimentation offers hints.
|
||||
batching, and any hints beyond the confirmed valid-recipe feedback.
|
||||
|
||||
Confirmed crafting outcomes and quality rules:
|
||||
|
||||
@@ -185,6 +186,8 @@ Discovery can prevent direct data extraction but cannot prevent players sharing
|
||||
recipes externally. Decide whether knowledge belongs to a character or account,
|
||||
whether known recipes become repeatable shortcuts, and whether 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
|
||||
|
||||
@@ -220,6 +223,10 @@ jump, interact, targeting, and configurable ability/spell slots. Support keyboar
|
||||
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.
|
||||
|
||||
## 7. Combat, effects, spells, and weapon abilities
|
||||
|
||||
@@ -309,16 +316,45 @@ Builder structures placed in a survival world. Physical damage rules within hous
|
||||
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. 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
|
||||
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 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.
|
||||
### 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
|
||||
|
||||
@@ -330,7 +366,7 @@ and exit must not allow the character to exist in two places simultaneously.
|
||||
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 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 after **3 seconds**. Destroying one key while others exist does not mark the house for
|
||||
deletion or remove the remaining key holders' owner rights.
|
||||
- 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
|
||||
@@ -341,12 +377,25 @@ and exit must not allow the character to exist in two places simultaneously.
|
||||
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.
|
||||
Confirmed deletion/recovery lifecycle: after the three-second timer, remove the
|
||||
house and contents from active use, 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 states: active -> pending deletion (3 seconds) -> deleted/recoverable
|
||||
-> permanently purged at the death-world deadline; eligible recovery returns the
|
||||
same house to active use. Persist the deadline so restarts cannot restart the
|
||||
three-second countdown. Never leave both an active and recoverable copy of contents.
|
||||
Specify access/occupant handling during the countdown and deletion, and how creating
|
||||
a valid key during the countdown cancels it before implementation.
|
||||
|
||||
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; what co-owner
|
||||
means without a key; guest storage/build access; key theft/drop while inside; guest
|
||||
@@ -429,7 +478,7 @@ content library. These are dependency-based phases, not time or capacity estimat
|
||||
| 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 | Permanent hub, key-owned housing, portal dungeons; separately scoped trade/social | No hub/housing XP; key recovery/deletion and instance lifecycles preserve ownership |
|
||||
| 8. Survivor expansion | Hub instances/travel, escape items/victory portals, key-owned housing, portal dungeons | No hub/housing XP; travel, timed deletion/recovery, 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
|
||||
@@ -446,18 +495,21 @@ revival. Housing also needs key-deletion/recovery semantics agreed before coding
|
||||
|
||||
First discussion, because these affect the architecture:
|
||||
|
||||
1. Housing: deletion grace/cancellation, original-creator recovery identity,
|
||||
eligibility, and the permission matrix? Last-valid-key destruction is settled.
|
||||
1. Housing: countdown access/cancellation, original-creator recovery identity,
|
||||
exceptional death-world cases, eligibility, and the permission matrix? Three-second
|
||||
deletion with recovery until death-world destruction is settled.
|
||||
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, 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.
|
||||
5. Crafting: exact matching, stations, discovery-recording trigger, probability/refund
|
||||
tuning, stat pool/quality rules, and provenance-aware stacking? Hub crafting uses
|
||||
resources and records discoveries without XP; random failure is settled.
|
||||
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
|
||||
@@ -480,7 +532,8 @@ New design examples to turn into acceptance tests when implemented:
|
||||
- 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.
|
||||
- Destroying one of multiple keys leaves the house active and other keys valid;
|
||||
destroying the last key marks the house and contents for deletion. A key
|
||||
destroying the last key deletes the active house after three seconds 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.
|
||||
@@ -488,7 +541,13 @@ New design examples to turn into acceptance tests when implemented:
|
||||
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.
|
||||
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.
|
||||
|
||||
This draft changes documentation only. No new game rules, assets, admin commands,
|
||||
schema migrations, or deployment settings are implemented by writing it.
|
||||
|
||||
+14
-3
@@ -113,6 +113,8 @@ Tracked across:
|
||||
- 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.
|
||||
- Hub crafting is allowed: resources are consumed and found recipes recorded,
|
||||
but no experience is gained.
|
||||
- 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
|
||||
@@ -123,12 +125,21 @@ Tracked across:
|
||||
- Destroying only the last valid house key marks the house and all contents for
|
||||
deletion. Destroying one of several keys preserves the other holders' ownership.
|
||||
Players can destroy a carried key before death to prevent a looter taking it
|
||||
and gaining house ownership. Deletion timing remains open.
|
||||
and gaining house ownership. Deletion takes **3 seconds**; house/content data
|
||||
remains recoverable until the creator's recorded death world is destroyed.
|
||||
- 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.
|
||||
house until the world they were in at death is destroyed, including restoring
|
||||
its retained contents after deletion. Recovery identity and countdown details
|
||||
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.
|
||||
- Players may stay in the hub or enter a world marked for destruction. Entry is
|
||||
available until that world is full or destroyed, including during the Harbinger.
|
||||
- Escape items allow return from a dying world to the hub. Without one, players
|
||||
cannot return until the Harbinger is defeated and a hub portal appears.
|
||||
- Hub worlds are instanced; players may switch hub instances to meet others.
|
||||
Travel must preserve character/item ownership and daily-time usage.
|
||||
- Keyboard Esc closes the open menu with focus; layered menus close topmost first.
|
||||
- See [Systems roadmap](SYSTEMS-ROADMAP.md) for dependencies and remaining decisions.
|
||||
|
||||
## Open Questions
|
||||
|
||||
Reference in New Issue
Block a user