Files
aeternalis/planning/Changes-Needed.md

19 KiB
Raw Permalink Blame History

Game play UI Changes Slot Bar shows up before login. (Should not) Collapsable drawer panel: (each button should be icon with tooltip) Button for Bag grid based box with item icon + count (5 columns, n rows. exceeding weight limit will slow player down by a small % up to complete imobolization at 2x weight limit) on hover will display name, click bring up context menu depending the item Consumable options: consume, use, drop, destroy, inspect, add to hotbar/keybind consume: activates the effect of the consumable and consumes it. use: puts it into a 'use context' where the next thing you click it will try and use it on, ie if it is a poison, and you use it on a weapon, the weapon will be poisoned and the consumable with be consumed. if it is a healing item, and you use it on yourself, or another player, or... mob... it will heal them. We will have use effects for each item. drop: drops it to the ground for anyone to pick up. destory: destroys it (needs confirmation) inspect: displays name, effects, creator/source add to hotbar/keybind: allows the item to be mapped to a hotkey/keybind when binding hit, will use the consumable, once all of that consumable is used, the keybind/hotkey is removed for that item. Equipable options: equip, use, drop, destory, breakdown, inspect, add to hotbar/keybind (enable quick gear swap) equip: Equip the item, if slot already occupied, swaps with the currently equiped piece use: puts it into a 'use context' where the next thing you click it will try and use it on drop: drops it to the ground for anyone to pick up. destory: destroys it (needs confirmation) breakdown: needs confirmation. Will attempt to destory the item, but return some of the resources used to craft it. Will base amount of resources returned by a % of what is required to make it scaling by the item level, and armor crafting skill if armor, weapon crafting skill if weapon. has flat 0.01% chance to learn the recipe of the item. inspect: Gives Name of item, and crafter/source, All details about item, equipment slot, stats, weight, requirements add to hotbar/keybind: allows the item to be mapped to a hotkey/keybind when binding hit, Equip the item, if slot already occupied, swaps with the currently equiped piece Resource options: inspect, use, drop, destory inspect: provides name of the item, and some details such as 'possible uses' use: puts it into a 'use context' where the next thing you click it will try and use it on drop: drops it to the ground for anyone to pick up. destory: destroys it (needs confirmation) Building Material: inspect, place, use, drop, destroy place: enters a placement context, where next space on map the mouse clicks if it is valid, will place the structure. inspect: Gives Name of item, and crafter/source, All details about item use: puts it into a 'use context' where the next thing you click it will try and use it on drop: drops it to the ground for anyone to pick up. destory: destroys it (needs confirmation) House Key: inspect, use, destroy, drop inspect: provides Name of House, Owner, and hub location use: puts it into a 'use context' where the next thing you click it will try and use it on, will be used on house door to enter house. drop: drops it to the ground for anyone to pick up. destory: destroys it (needs confirmation) Button for Character Name, level, current xp/xp to next level, Worlds Survived HP or mana choice if available Available State points for placement Stats : Name, Current base stat without equipment/buffs : total stat : Option to place an available stat point on hover for each will offer a 'details' option to click and bring up a popup detailing the stat and its effects Collapsed List of Stat Details Have a Button for 'Total, Base, Equipment, Titles, Temporary (include timer on each stat for when it will return to normal)' Total: will provide complete current stats (including current weight and weight limit) (Including Skill/ability/spell levels) Base: All Stats only from Character Stat placement/HP/Mana Selection (Including Skill/ability/spell levels) Equipment: All Stats gained/Lost from equipment (Including Skill/ability/spell levels) Titles: All Stats gained/Lost from titles (Including Skill/ability/spell levels) Temporary: All Current Temporary Stats/Effects applied to the character with durations/source (Including Skill/ability/spell levels) Collapsed List of titles Button for Equipment Equipment pane: show equiped item, on mouse over inspect, on click unequip Collapsed pane of total modified stats from gear Collapsed list of abilities/effects/spells/skill modificatiosn (buffs/ debuffs/ ability to use x spell or ability when equipped) Button for Skills Buttons for each Skills to enter the Skills context window Craft (prompt Attempt Craft or select Known Recipe) Attempt will have select ingrediant and amount (with an inspect button read details of the ingrediant) Record Recipe on success Attempt will be done in the cotnext of the selected profession Select known recipe will auto populate the items (if possible) will then allow button to inspect what the expected result would be and then confirm the craft. Button for Abilities List all Abilities On Hover gives details On click brings up context panel Provide Details of the ability Name, Level, Current XP, XP to next level, Ability Type (Active/Passive), Effect/Details/requirements to use If Active, Option to add to hotkey/keybind Button for Spells List of all Spells On Hover gives details On click brings up context panel Provide Details of the spell Name, Level, Current XP, XP to next level, spell Type (Support/Debuff/Attack), Effect/Details/requirements to use Option to add to hotkey/keybind Hotkeys/keybinds Reset to Default Settings Keyboard/Mouse Controller Custom

For setting a keybind, you either select the key, or select combo key.
Combo Keys are 'Alt + ' and 'Ctrl + '
For controller we will have to map this out during play testing, We will most likely end up with hotkey groups, where using the dpad arrow keys on the controller will allow cycling through, but holding a trigger key and hitting specific ones will jump to a specific hotkey group.

Goal would be to make it fully customizable

Traveling between hub and world. In the Worlds you will have to click on the portal that spawns when a harbinger dies, or consume an escape stone.

In the Hub, you will have to click on a portal that is in the hub, it will bring up a context window to display the available worlds. We will need to come up with a way to handle high leveled players joining worlds, to make sure they don't over power the harbinger, but also dont make the harbinger extremely difficult for the lower leveled players in the world.

Environment We will need to texture the worlds, possible tweak camera angle, or maybe enable the camera angle to be changed. Currently everything looks flat.

I think there was a missconception, the whole '9 chunks' was meant that was what would stay in the players monitoring range, each world will be n chunks. When a player gets withen a chunk of a border, a new chunk will be generated in that direction. the further away from the initial spawn of the wandering player, the higher leveled the chunk will be, where the resources, and mobs will be of higher level.

We will handle this by having another pod that is not handling players, handle the chunk generation.

We will also use the same server to determine where players will spawn, the first player to join a world will set the origin spawn. players of higher level will spawn in a area away from the origin spawn that would make the region 10 levels lower then they are. So if the player who spawned into the origin walked to that player, the chunk that would be generate would be 10 levels lower then the player who spawned there.

If the player who spawned not at the origin spawn walks towards chunks closer to the origin, they would be going easier in level.

This is ONLY for the Worlds. Not for the Hubs.

Harbingers Spawn at the origin and when a harbinger leaves a chunk and no players are in, that chunk is no longer able to be entered by players or the harbinger, The world will no longer generate new chunks. and the harbinger will move through all the chunks until no chunks remain. Once all players are dead/ the harbinger is defeated/ there are no movable chunks, the world falls.

The World pod will only keep in memory any chunks that a player is on and the 8 chunks surrounding it, other chunks are stored until needed.

World design follow-up — 2026-09-10

These confirmed decisions supersede the earlier origin, blocked-chunk, and immediate-world-end descriptions above. They are planning changes, not implemented gameplay. Recommendations below still require agreement.

Confirmed decisions

  • Defeating the Harbinger stops destruction and opens the hub portal. When the final logged-in player uses that portal, all remaining living characters are sent to the hub and the world ends. Dead characters are not resurrected.
  • Survival worlds have one fixed origin at the existing static spawn coordinates. Region difficulty increases with distance from that origin. Arrival placement targets a region approximately ten levels below the incoming character, with a minimum region level of one. This also applies to a high-level first arrival; that character does not redefine the world origin.
  • During the Harbinger phase, generation toward higher-difficulty regions stops, while generation back toward the origin remains possible. Exact frontier and admission rules still need the definition proposed below.
  • Destroyed/depleted chunks remain traversable. Remove their gatherable resources and dropped items; disable resource respawning and mob spawning there. This replaces the proposal to block players and the Harbinger from entering them.
  • These generation/difficulty/destruction rules apply to survival worlds, not hubs.
  • Before the Harbinger awakens, survival worlds expand without a fixed outer gameplay boundary. "Infinite" means generation on demand, not pre-generating infinite terrain. The finite frontier begins only when the Harbinger awakens.
  • Chunk depletion retains player corpses and their remaining inventory. Ordinary ground loot is removed; resurrection remains possible at a retained corpse until the world itself ends, subject to the existing replacement/consent rules.

Current implementation clarification

The reported circular invisible boundary is real: balance.yaml currently sets worldRadius to 1024. Nine chunks is the per-player monitoring window, not the world's total chunk count. Removing the fixed-radius movement boundary requires the planned expanding-world system; increasing the configured radius alone would not implement it. Inactive terrain meshes are evicted today, but persistent resource layouts and other world state are still retained by the world owner.

Proposed solution to indefinite evasion — not yet approved

  • Freeze a finite outer generation frontier when the Harbinger awakens. Measure it by distance/chunk coordinates, not rounded region levels, so walking sideways through equally rated regions cannot expand the frontier. New admissions and outstanding generation jobs cannot extend it after that point.
  • Allow generation of missing terrain toward the origin inside that frontier. Preserve access to already-generated regions. Define the finite eligible chunk set once so delayed generation cannot add an unlimited supply of fresh regions.
  • The Harbinger advances through remaining productive regions. Combat targeting cannot pull it into an endless chase through already-depleted terrain. Player presence does not veto depletion when it leaves a chunk.
  • Track depletion durably even for eligible chunks that have not been generated yet: loading them later cannot recreate resources or mobs after the destructive advance has passed them. The world owner advances this process outside player monitoring range too.
  • Recommended loss condition: the world ends when that finite territory is fully depleted and the Harbinger is still alive. Players may cross depleted chunks until then. This is a visible world-state condition rather than a fixed wall-clock deadline. Depletion alone, without a terminal condition, cannot prevent evasion.
  • Harbinger movement and depletion pacing remain tuning decisions. Existing daily-limit protection continues; final world loss follows the established world-destruction rules rather than bypassing the daily limit to force combat.

Remaining lifecycle details

  • Victory closes new survival-world admissions. Recommended: also evacuate if no living players remain connected after victory, including disconnection rather than portal use. This fallback is proposed, not part of the confirmed trigger.
  • Bulk evacuation must durably reserve each living character and their possessions for hub transfer before world cleanup. A full/unavailable hub must leave a recoverable transfer, not cause item loss or character duplication. Preserve character progression, titles, daily usage, and survivor credit exactly once.
  • Player corpses are retained. Still specify existing mobs, placed structures and their contents, later drops, and house keys lost with deleted ordinary loot.
  • During the Harbinger phase, high-level arrivals need an existing valid spawn or an allowed inward-generated location. If no suitable location exists, propose rejecting that destination with an explanation instead of extending the frontier.

Revised build order — 2026-09-10

The next sequence supersedes the remaining numbered implementation order in the original systems roadmap. Completed foundations remain in place. Each milestone ends with commit/push and a manual playtest handoff; routine Playwright authoring and suite runs remain deferred.

  1. HUD visibility, collapsible character drawer, five-column bag grid, and separate character/equipment/skills/abilities/spells views. Preserve existing actions.
  2. Shared item actions and targeting, configurable bindings, encumbrance, breakdown.
  3. Physical hub portals and house-door interactions.
  4. Finalize world/storage lifecycle contracts, repair immediate reliability issues, and implement/qualify the durable persistence foundation before expansion.
  5. Implement on-demand chunk generation and roaming Harbinger behavior against milestone 4's partitioned storage and recovery contract.
  6. Terrain textures and depth on the revised generation system.
  7. Cosmetics and customization (previous milestone 9).
  8. Dungeons and social expansion (previous milestone 10).
  9. Revamp the Control panel and website layout, UI, and UX.

Milestone 1 handoff: Player drawer. Weight penalties, new item-use behaviors, source-filtered stats, and expanded binding semantics are not implemented by the first presentation slice. Character-owned worlds-survived display needs an authoritative snapshot field; it must not be inferred from titles.

Milestone 2 handoff: Item actions. Shared actions, targeted consumables, gear swaps, hotbar item assignments, Ctrl/Alt/mouse bindings, encumbrance and equipment breakdown are implemented. Source-filtered stats and worlds-survived display remain separate follow-ups; physical portals/doors are next.

Milestone 3 handoff: Physical entrances. Each hub has a world portal and one shared housing entrance, confirmed for this milestone. Key-targeted entry and invited-house selection use that doorway. Finalizing the expanding-world/spawning/destruction lifecycle contract and persistence foundation is the next milestone.

September 11 reliability dependency update

Creator detour: the user requested a character creator and simple admin mob/object variation tools before returning to the main engineering sequence, with softer rounded fantasy shapes. See Creator workshop for the implemented procedural creators and handoff. This does not renumber the nine milestones or complete the full rigs/equipment/animation/audio scope.

The subsequent playtest reported blocked player movement and revised the visual direction to anatomical region/face controls and a Spore-like modular mob builder. Modular creators records the complete requested part list, connection profiles/joint limits, version compatibility, and proposed review slices.

September 12: anatomical player customization is implemented for initial character creation only, together with the name. See Character creation. The old free-restyle action is removed; a future change-for-cost mechanism is planned. Modular mobs and the remaining presentation work are still pending.

Milestones 1–3 have implementation handoffs above. Milestone 4 now includes the storage work that must precede expanding worlds; it is no longer only a rules discussion. The reliability issue register and persistence plan records all eleven reported issues, verified findings, qualifications, proposed resolutions, and exit checks. This is a documentation update, not completed repairs.

  • 4A: finish lifecycle/storage decisions and record performance baselines.
  • 4B: scoped reliability repairs, including travel recovery and authentication; separate owner heartbeat from idle saves and eliminate duplicate payload writes.
  • 4C: implement partitioned durable state, ordered committed events, bounded active state, asynchronous checkpoints, and a fenced migration from legacy saves.
  • 4D: qualify crash recovery, ownership fencing, migration, and measured cost before milestone 5 begins. Preserve the single world owner and existing claims.

Each implementation slice gets its own commit/push and manual handoff where playable; required server lifecycle coverage remains. Formatting and E2E temporary file cleanup are isolated maintenance tasks. Routine Playwright work stays deferred. Steps 6–9 retain their order. Rigs, equipment attachments, animations, and sound hooks from the original 4.5 remain pending and need an explicit slot; they are not silently included in the persistence work. Unapproved world rules above remain open and are not resolved by the storage proposal.