Ryuu/AetherOnline
Watch
1
0
Fork
You've already forked AetherOnline
 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions
Page: abilities loadouts and progression
Pages
Authoring Debugging Home Operations Protocol Reference Runtime Systems abilities loadouts and progression ability rotation and combo planner active realtime session actor directory admin actions and internal auth animation workbench operator guide aoi snapshot replication app mode bootstrap and lifecycle architecture guardrails and module tree tests asset loading routing and vfs authored ui surface renderer authoring command bus and transaction history authoring reference registry contributor extension contract authoring reference registry authoritative audit event schema and projections authoritative world time calendar and environmental scheduler bake product registry build strategy and loadout optimizer campaign journey and progression simulator catalog source map and record routing character gameplay state json store character paperdoll assets character stats and equipment modifiers chat presence and social client local offline save and bootstrap cache client local user preferences and account sync client multiplayer connection flow and session cleanup client realtime authority store and frame projection client scene presentation and player preview client snapshot staging and repair receipts client ui focus and text input planning combat action resolution and mob ai semantics combat presentation cues and transient effects combat rewards and progression persistence content dependency graph and scenario playtests content migration and catalog refactors control agent api and remote service runner control panel config and secret persistence control panel service build invalidation and log normalization control panel service lifecycle and quality gates control plane allocation and zone transfer routing control plane and service ops control plane route policy and coordination api control service supervisor manifest and stale process recovery crafting recipes and service integration dependency aware content health deterministic combat balance lab developer workspace doctor and readiness report diagnostics provider input lanes and failure isolation dialogue quest localization handoff dialogue runtime state and choice authority duplicate realtime claim takeover durable retry and session cleanup durable work queue consumer contract dynamic world state and scene phasing editor authored content workspace manifest and cache editor event console and asset debug dashboards editor extension and contribution registries editor scene snapshot lane demand editor settings registry and workspace presets editor viewport and world tools editor workbench and dock encounter difficulty mutators and reward scaling encounter instance and wave director encounter lobby ready check and entry encounter mechanics and boss timelines encounter memory persistence encounter reward eligibility lockouts and pity enemy archetypes combat kits and encounters engine report log and recovery routing environment configuration reference external engine patterns and boundaries farming footstep surface audio materials forgejo wiki publishing and docs check game data catalog game data generated item family adapters game database schema readiness game server catalog load health and fallback policy game server reconciliation and transfer marker cleanup game server startup readiness and registration game transport endpoints and quic exposure gameplay action authority and command audit gameplay action replay ledger and idempotency gameplay authority replay fixtures and drift gates gameplay conditions effects and events gameplay system slice scaffold gameplay ui runtime and bevy sync generated artifact drift and repair generated artifact registry and quality gate integration glossary hotbar hud runtime projection and input in process zone transfer phase journal input profiles and keybinds interactive world map minimap and cartography internal auth and admin delegation chain inventory items and stack limit safety item authoring lifecycle and reference repairs json catalog hot reload batch and candidate revalidation legacy compatibility and migration register local player input control and reconciliation local playtest and standalone preview localization extraction and runtime catalog login account admin repository and cascades login database migrations and schema contracts login server auth sessions and character entry login session cache throttle and revocation loot table authoring and drop audits mob animation presentation events and projectile cues mob encounters and scene combat movement authority networking tick health and zone pressure npc ai schedules and deterministic behavior npc definition catalog npc schedules routines and contextual behavior npc services npc state memory and interactions pack export content gate party composition roles and synergy simulator passive traits and procs persistent interactive world objects placed light runtime budget and preview heatmap player appearance equipment persistence player economy authority player homesteads housing and property auctions player journal and codex player navigation tracking and world guidance player notification inbox authority and delivery player preview animation profile player preview debug gizmos and collision overlays player preview render cache and keyed entity lifecycle player preview weather masks and effect budget player snapshot assembly and durable row normalization post process volume blending and preview overlays project files import profiles and asset change impact public endpoint detection and upnp exposure quality gate jsonl events and panel failure summaries quest runtime projection and turn in authority quic reliable stream topology and negotiation realtime admission throttling and load shedding realtime bootstrap manifest and snapshot service realtime bootstrap wire sections and compression realtime client reconnect journal and command replay realtime datagram codecs and ingress policy realtime egress mailboxes and lane scheduling realtime ingress validation and failure policy realtime packet debug capture and triage realtime protocol registry realtime registry and wire contract realtime resume ledger record format realtime rollout policy and compatibility negotiation realtime runtime profile and transport adaptation realtime session activation hydration boundary realtime timebases tick ordering and clock ownership redis keyspace ttls and cleanup targets regions points of interest and exploration discovery relationship reputation gates and service deltas remote avatar replica binding and interpolation render surface guard and window safety runtime actor identity and authority contract runtime camera arrival and cutscene overrides runtime debug overlays and developer options runtime environment registry and startup config validation runtime path roots and packaged asset resolution runtime profiling tracy captures and budget gates runtime scene manifests and zone authoring runtime ui fonts and localized text presentation scenario sandbox and timeline inspector scene audio runtime routing scene command center and visual graph tools scene cutscene authoring scene documents scene layer schema depth and bands scene lighting post process and placed lights scene navigation and collision scene preview scenario replay cli scene runtime media weather and camera phases scene runtime schedule and frame budget scene trigger authority and reconciliation scene triggers scene validation and repairs service json rpc contracts service observability and metrics contract service registry heartbeats drain and shutdown session handoff and transfer shared content workspace shared test fixtures and fixture workspaces shared validation report schema source inventory and engine health standalone account realm and character flow standalone asset pack and preflight standalone loading pause death and recovery screens standalone shell flow and ui lifecycle standalone ui preview root and transient lifecycle starter character economy bootstrap status effects and combat modifiers story content loop text asset migration journals and atomic rollback tiled prefab import and placement tilemap asset import contracts tileset atlas preview surfaces trigger permissions targeting and action pipelines typed disconnect codes and transport advisories ui layout binding graph and editor workflow ui layout ui skins validation and bake validation errors validation provider registry and strict preflight vendor stock and shop economy authoring viewport spatial planning overlays vscode dev tasks and generated launch profiles workspace package roles and scoped quality profiles world entry smoke harness and soak telemetry world events and scenario director world gameplay assemblies world interactions and activity boards world mechanism and puzzle graphs world overlay gizmos and culling world travel waypoints and zone transitions xtask content gates and plans
2 abilities loadouts and progression
forgejo-actions edited this page 2026-07-13 19:45:35 +00:00
Table of contents

Abilities, Loadouts, And Progression

What This System Is

The ability catalog is the canonical authored source for player abilities, named hotbar loadouts, and the player experience/stat curve. It is shared by preview, the runtime client, and game-server authority through aether-world-domain.

The first shipped slice migrates the Dragoon hotbar without changing its gameplay values. Other legacy combat actions continue to use their compatibility definitions until they are migrated.

How Authors Use It

Authors edit the ability catalog, named loadouts, and progression policy in the authored asset, then validate the shared world-domain projection before changing client or server adapters.

Authored Asset

Edit assets/gameplay/ability_catalog.json. The root document contains:

  • abilities: identity, UI copy, execution kind, animation action, aliases, requirements, costs, combo links, effect applications/consumption, trusted combat values, and presentation cues;
  • loadouts: named one-based slot assignments referencing ability ids;
  • progression: experience per level, level-one stats, per-level stat growth, and per-second resource regeneration.

IDs are case-insensitive at lookup boundaries but should be authored in lower-case snake case. Animation action IDs and aliases retain compatibility with existing wire and preview action tokens. Effect ids resolve through the Status Effects And Combat Modifiers catalog; unknown cross-catalog references reject runtime hot reload.

Rules And Invariants

Ability ids, aliases, animation action ids, and loadout slots are stable gameplay contracts. Server authority owns costs, cooldowns, combat values, requirements, progression, and resource regeneration.

Authority Contract

Clients request an action by id. Combat authority resolves that id through the ability catalog and owns its base amount, damage kind, cooldown, target offsets, presentation cues, and knockback rule. It rejects abilities whose minimum level, required character tags, or unlock IDs are not satisfied.

The equipped tool is projected to an authority tag such as weapon:polearm; clients cannot supply that tag. Quest and gameplay rewards can satisfy authored unlock_ids through the existing authoritative unlock state.

Player level and maximum health, mana, and stamina are derived from the catalog progression policy. The current linear values remain 100 XP per level and growth of 12 health, 8 mana, and 6 stamina. Those base values feed the Character Stats And Equipment Modifiers resolver, which adds authoritative equipped-item contributions before publishing player stats.

Ability activation also debits stamina and mana on the server and starts the catalog cooldown only after authority accepts the action. The server regenerates resources from the authored progression rates before validating each activation. A client-reported resource value or cooldown cannot make an otherwise unaffordable action succeed.

Client And Hotbar Contract

The default Dragoon hotbar is projected from the dragoon.default loadout. Slot order, labels, descriptions, passive readiness, and runtime action identity come from the referenced abilities. Input bindings remain a client adapter keyed by the authored one-based slot.

Players can submit an AbilityLoadoutCommand with an expected revision and up to twenty unique one-based slots. The server validates the loadout and every ability against level, authoritative equipment tags, and unlock state, then persists the canonical projection in the existing character gameplay-state document. The namespaced keys are ability_loadout.revision, ability_loadout.id, and ability_loadout.slot.XX. Replicated gameplay-condition snapshots apply that persisted projection to the client hotbar after login and after successful edits.

Runtime Authoring

The client/editor watches assets/gameplay/ability_catalog.json and atomically swaps in a changed catalog every 500 ms, but only if parsing and validation succeed. A rejected edit leaves the last valid catalog active and writes a diagnostic. The Items editor includes an Abilities & Loadouts inspection card with counts, costs, requirements, cooldowns, named slot projections, and a manual Reload and validate catalog action.

Game-server authority deliberately keeps its startup catalog for the lifetime of the process so a live client edit cannot silently change trusted combat balance. Deploy catalog balance changes with the server content revision/restart workflow.

Validation And Debugging

Catalog loading rejects:

  • unsupported schema versions;
  • missing or duplicate ability IDs;
  • colliding aliases or animation action IDs;
  • attacks without combat definitions;
  • melee attacks without target offsets;
  • missing damage kinds;
  • loadouts with zero or duplicate slots;
  • loadout or combo references to missing abilities;
  • a zero experience-per-level policy.

Run cargo test -p aether-world-domain ability_system for schema and projection checks. Run the game-server progression/combat tests and the client hotbar tests after changing shipped values.

Examples

Migrating one Dragoon action means adding its authored ability row, preserving existing wire and animation aliases, adding it to the intended loadout slot, validating the catalog, and only then removing legacy combat rows.

Migration Guidance

Migrate one action family at a time. Add the authored definitions and loadout first, preserve the existing animation/wire aliases, then remove that family's legacy combat rows only after client, server, and replay fixtures pass. Do not create a second UI-only description or balance table.

Related Systems