Files
aeternalis/docs/WORLD-ENTRANCES.md

4.8 KiB

Physical entrances — revised milestone 3

Each hub now has a world portal at the center (0, 0) and a shared housing doorway nearby (initially 12, 0). Both use server terrain height and appear only within the player's chunk interest window. Housing uses one shared entrance per hub, as agreed; it selects existing instanced houses rather than allocating a separate world door for every house. Doorway location is saved in world tuning and defaults once for older snapshots from entrances in server/content/balance.yaml.

Click a portal or doorway to approach it. Once nearby, a portal opens available destinations and the housing entrance opens your house directory. Movement, Esc, opening a menu, disconnecting, or a blocked approach cancels the walk. This is a direct walk intent, not pathfinding around obstacles. If blocked, walk around the obstacle and select the entrance again. Keyboard/controller target cycling includes both entrances; Gather or Attack interacts with a selected entrance.

The housing directory shows entry buttons when opened from the physical doorway. Ordinary Housing & keys controls retain creation, key destruction, recovery, and inspection. Selecting Use on a house key starts targeting: select the shared housing doorway to approach it and enter that key's house. Keys are not consumed. The existing indoor exit and house controls still return to the same hub location.

The old general Travel shortcut is replaced with Use escape stone when a survival character owns one and the world has not ended. Bag and hotbar escape actions use the same explicit stone flow. Hub travel starts at the hub portal; victory travel starts at the portal opened by defeating the Harbinger. Canceling destination selection consumes nothing. Departure still consumes a required stone once, and an interrupted transfer still resumes through the account's durable travel record.

Server boundaries

  • Hub travel and victory travel require a living, connected, unsheltered character with daily time remaining, outside housing, within gathering distance in three dimensions, and with an unobstructed line to the authoritative portal position.
  • House entry requires the shared hub entrance's proximity and clear line in addition to existing survival, active-house, key/invitation, and ownership rules. Explicit key use verifies that exact carried key is active and belongs to the requested house, even if the player also has an invitation. An unrelated key cannot satisfy the request.
  • Checks run in the existing fenced housing/travel transactions. A rejected request changes no ownership or transit state. Replays return the already-saved result rather than re-entering or spending another item.
  • Guest/co-owner permissions, valid key holders' owner rights, three-second key destruction, creator recovery, and shared cross-hub housing contents are unchanged.
  • No Harbinger evacuation, infinite-world, frontier, or chunk-depletion rules are introduced here. Those remain revised milestones 4 and 5.

Manual playtest

  1. Enter a hub. Find the teal world portal at 0, 0 and the framed housing doorway at 12, 0. Click each from a short distance and confirm the character walks over before its controls open. Cancel an approach with movement or Esc.
  2. At the world portal, choose another hub or a survival world. Check that the same character, progression, gear, and remaining daily allowance arrive.
  3. In a survival world, cancel an escape-stone destination selection and confirm no stone is spent. Complete escape and confirm exactly one is spent. Defeat the Harbinger and use its portal without an escape stone.
  4. With a house key, select Bag → key → Use, then the housing doorway. Confirm direct entry to that house and retention of the exact key. Try targeting a different object; the key should remain untouched.
  5. As an invited guest without a key, click the housing doorway and choose the invited house. Verify existing furniture/storage permissions and the indoor exit.
  6. Open ordinary Housing & keys away from the entrance: it should offer management without a remote-entry shortcut. Verify another hub's doorway accesses the same house and stored contents. Check last-key destruction and recovery as before.
  7. Try clicking an entrance while immobilized by carry weight or behind an obstacle. The approach should stop with guidance; dropping weight or walking around the obstruction should allow another attempt.

Required TypeScript/build and Go checks cover this change. Go regressions include entrance visibility, vertical distance and obstruction, legacy snapshot migration, rejected travel escrow, wrong-key rejection, repeated entry, cross-hub guests, and death/recovery continuity. Routine Playwright authoring and full-suite runs remain deferred for manual playtesting.