224 lines
14 KiB
Markdown
224 lines
14 KiB
Markdown
# 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. Milestone 7 implements the following corpse resurrection
|
|
exception for new deaths; earlier deaths remain final.
|
|
- 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.
|
|
Provisional consent, costs, and restored pools are in `docs/MILESTONE-7.md`;
|
|
further constraints remain open for playtesting.
|
|
- 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.
|
|
- Confirmed ownership: levels/XP, profession levels, weapon proficiency, learned
|
|
spells/spell XP, stats/allocations, abilities, and discovered recipes belong to
|
|
the character. Resurrection and world travel preserve them; replacement resets them.
|
|
- Only access to account cosmetics carries to a replacement character. This also
|
|
supersedes the earlier account-bound title assumption: titles stay with their
|
|
character and are not inherited. Historical first claims remain reserved.
|
|
- Current code still uses an account title ledger. Moving active title ownership
|
|
to characters requires an explicit migration; this design update changes no saves.
|
|
- 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.
|
|
|
|
## Cosmetics (planned)
|
|
|
|
- Base character name and appearance are chosen together at initial creation.
|
|
Existing-character appearance changes are disabled until a later mechanism with
|
|
a cost is designed. Restart, travel, and revival preserve the same appearance;
|
|
replacement opens a fresh creator. See [Character creation](../docs/CHARACTER-CREATION.md).
|
|
- Cosmetics are permanently **account-bound**, not character-bound. They cannot
|
|
be traded or lost; an item's applied appearance is separate from the unlock.
|
|
- Cosmetics change the player, worn/held items, and items in houses.
|
|
- Ordinary item drops and pickup by another player remove the applied cosmetic.
|
|
The underlying item remains; the original account retains the cosmetic unlock.
|
|
- Furniture placed with a cosmetic in someone else's house keeps its appearance.
|
|
Pushing/pulling it without entering inventory preserves that appearance, even
|
|
when the mover does not own the cosmetic.
|
|
- Placed furniture entering a player's inventory loses its cosmetic if the
|
|
receiving account does not own it; an entitled receiver may retain it. This is
|
|
the explicit furniture exception to the ordinary pickup rule.
|
|
- Placing furniture is different from dropping loot. Displaying decorated furniture
|
|
or owning its house does not grant the cosmetic to another account.
|
|
|
|
## 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.
|
|
- 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
|
|
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. Owners and co-owners configure baseline
|
|
guest permissions and per-person overrides for: moving furniture, opening
|
|
furniture, placing furniture, putting items in furniture, picking up items in
|
|
the house, and dropping items in the house. These permissions cannot remove a
|
|
valid key holder's owner rights.
|
|
- 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. **Destroying the key takes 3 seconds**; this is the
|
|
key-destruction action, not a separate house-deletion countdown. The key remains
|
|
valid until destruction completes. 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, including restoring
|
|
its retained contents after deletion. Recovery identity and interruption 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
|
|
- 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
|
|
- Milestone 8a adds persistent destructible world structures, craftable kits,
|
|
Control definitions, placement checks, and collision. Milestone 8b adds housing
|
|
floor-plan controls, keys, permissions, storage, and recovery. Milestone 8c adds
|
|
walkable interiors and visitors; see `docs/MILESTONE-8C.md` for manual tests.
|
|
- Milestone 7 implements spell books/ranks/unlocks, weapon proficiency and abilities,
|
|
healing/auras, bindable keyboard/controller slots, and durable corpse revival.
|
|
See `docs/MILESTONE-7.md` for defaults, effect limits, and the manual handoff.
|
|
- Milestone 6 implements character-owned crafting professions/discoveries,
|
|
authored recipes and stat pools, durable attempts, and maker/world provenance.
|
|
Hub crafting consumes resources without XP. See `docs/MILESTONE-6.md` for
|
|
provisional tuning, limits, and the manual handoff.
|
|
- September 9: layered valley/ridge/forest terrain and jumping over/onto actual
|
|
obstacles are deferred in [Environment backlog](ENVIRONMENT-BACKLOG.md), using
|
|
the supplied landscape reference. Continue the agreed presentation milestone.
|
|
- Control biome revisions keep stable identity and reuse existing resources.
|
|
Projectile launches and confirmed impacts are visible; weapon profiles can
|
|
scale speed with Dexterity and Strength. Curved/seeking paths remain planned.
|
|
- Milestone 4 implements reusable combat/mob/loot/spawn definitions, selected-target
|
|
projectiles, stationary damage/healing areas, cross-chunk pursuit, and live admin
|
|
spawning. These use existing model presets and provisional PvE targeting/scaling;
|
|
see `docs/MILESTONE-4.md` for manual testing and remaining scope.
|
|
- Milestone 3 implements reusable gathering definitions: initial lumberjack,
|
|
herbalist, and miner skills use one character-owned XP methodology. Equipment,
|
|
titles, and consumables can modify effective level, yield, speed, and profession
|
|
XP globally or per skill. Effective level allows attempts up to 20 levels above
|
|
it, with high failure/destruction odds and possible damage/fatigue. Probabilities
|
|
and consequences are provisional tuning; see `docs/MILESTONE-3.md`.
|
|
- New worlds have deeper hills/valleys and biome-specific resources; existing
|
|
worlds retain their terrain. Space jumps, F attacks, and the camera starts closer.
|
|
- Follow the agreed milestone order and handoff in the systems roadmap. Model rigs,
|
|
equipment attachments, animations, and sound hooks are milestone 4.5. Commit and
|
|
push after each milestone, then hand off for the user's manual playtest before
|
|
continuing. Playwright automation is deferred in [PLAYWRIGHT-TODO.md](PLAYWRIGHT-TODO.md);
|
|
required type/build checks and Go lifecycle tests remain in place.
|
|
- 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.
|
|
Confirmed follow-up rules are summarized above. Remaining recommendations and
|
|
lifecycle details require discussion before implementation.
|