Files
aeternalis/planning/VISION.md
T

7.9 KiB

Aeternalis — Game Vision

Living document. Captures vision pillars as they're dropped in conversation. Not a final spec — structure only, no invented details.

Genre

  • Survival MMO roguelike.
  • 3D game.

Infrastructure

  • 5 servers spun up at a time.
  • Up to 2,000 players per world.
  • Worlds regenerate periodically.
  • Each "session" (world lifespan) lasts about 1 week, possibly longer — TBD.
  • Server/world relationship: servers are instance nodes, not world shards. Each server = a self-contained instance; no world spans multiple servers.

World Generation

  • Dynamic: world generates around players as they join.
  • New players always start some distance N away from existing players — exact distance TBD.

Permadeath

  • 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.

Play-Time Cap

  • A character can only be played a maximum of 2 hours per day.
  • Enforcement: wired as per-character at first, architected to be overridden/reconfigured to per-account level later (anticipating abuse of the per-character limit).
  • On hitting the cap:
    • Player is force-teleported to a safe zone.
    • Given a keystone item to return to their previous location.
    • Logged out.
    • If HP was below 50 at the time, it's set to 50 (safety floor against returning in a near-death state).

Mobs

  • Spawn endlessly.
  • Scaling: the longer a world has been up, the stronger mobs get.
    • Presumably resets on world regen (ties to Infrastructure's "worlds regenerate periodically") — not explicitly confirmed.

Starting Kit

  • Knife
  • Axe
  • Flint and steel
  • Fishing pole
  • No other starting gear specified yet.

World / Networking Architecture

  • Players spawn into a 128x128x128 area ("node" / chunk).
  • Clients receive updates for the 9 surrounding nodes (current node + 8 neighbors, 3x3 grid).
  • Rendering is limited to FOV — update radius and draw/render radius are decoupled.

Leaderboards / Running High Scores

Tracked across:

  • Time alive
  • Time played
  • Level attained
  • Mob kills
  • Boss kills
  • Player kills
  • Skill levels
  • Titles
  • Good karma / bad karma
    • Bad karma accrues from starting player-kills / being the aggressor.
    • Good karma source — unspecified, open question.

Player Progression and Titles

  • Every level-up grants 10 allocatable stat points, 5 stamina, and a choice of 5 maximum health or 5 maximum mana. Pending choices can be taken later.
  • Allocatable stats: constitution, intelligence, dexterity, strength, wisdom, charisma, and luck. Their derived stats and provisional coefficients are documented in docs/PROGRESSION.md and editable through Control.
  • Titles have configurable requirements, a name, and positive or negative effects.
  • Award scopes include personal achievements, first in a world, and first ever.
  • Earned titles cannot be lost through gameplay or transferred to another player.
  • Administrators may grant or revoke titles as an audited exception. Revocation suppresses active effects and automatic re-awarding until an admin restores the original title; first-claim history remains reserved.
  • Initial implementation interprets player-bound titles as account-bound: they carry to a replacement character after permanent death. Levels, XP, and banked stat points belong to the individual character and survive survivor passage. Account inheritance is an implementation assumption awaiting player-design confirmation.
  • XP rewards, level curve, points per level, starter titles, and effect numbers are provisional tuning in server/content/balance.yaml.
  • Control can publish title requirements and signed flat/percentage effects, equipment definitions, and stat formulas, and inspect final character stats.

Inventory and equipment

  • Equipment slots: helmet, mask, chest, shoulders, pants, boots, gloves, earrings, necklace, eight rings, weapon, shield/offhand weapon, cape, and bag.
  • Equipment can require level, stats, and permanent titles, and can provide positive or negative stat modifiers. Each equipment instance has its own ID.
  • Equipment transfers through dropping, corpse looting, and survivor passage. Equipment requirements are checked without other equipment bonuses.
  • Administrators may add items or remove a specific instance/stack quantity, with an audit reason and the same owner-controlled durable save path.
  • 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 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.
  • Session length: exactly 1 week, or longer? How much longer?
  • New player spawn distance N from existing players: what's the actual value/rule?
  • Starting kit: any other gear (armor, weapons, consumables)?
  • Networking: is node size (128x128x128) fixed/final, or a placeholder for tuning?

Backlog

  • See Systems roadmap for the September 8 draft covering gathering professions, biomes, mobs, crafting, terrain, combat, spells, abilities, structures, survivor hubs, presentation, social systems, and live administration. Confirmed follow-up rules are summarized above. Remaining recommendations and lifecycle details require discussion before implementation.