Ryuu/AetherOnline
Watch
1
0
Fork
You've already forked AetherOnline
 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions
Page: player homesteads housing and property auctions
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
1 player homesteads housing and property auctions
forgejo-actions edited this page 2026-07-15 12:43:13 +00:00
Table of contents

Player Homesteads, Housing, And Property Auctions

What This System Is

Housing is authored once and instantiated many times. assets/gameplay/housing_catalog.json defines reusable areas, plot templates, auction policy, and placeable furnishings. The starter Lantern Meadows area uses assets/scenes/lantern_meadows.scene and has no authored instance cap, so the server may add districts as ownership demand grows without copying the scene or catalog content.

Rules And Invariants

A property is always identified by the full HousingPropertyKey:

area id + district instance id + plot id

Scene IDs and plot IDs alone are not property identities. Different instances reuse the same authored scene and plot definitions while retaining separate owners, auctions, residents, and decoration layouts. ensure_housing_district_capacity returns an existing district below the area's target occupancy or initializes the next instance. max_instances = 0 means intentionally unbounded expansion; a positive value provides a hard operational cap.

Realm state belongs in housing_district_state, keyed by (realm_id, area_id, instance_id). Its JSON payload and mirrored revision are updated with optimistic concurrency, preventing two game-server processes from silently overwriting the same district. Character gameplay state stores only owned-property and active-bid references; shared ownership and auction state must never be embedded in a character row.

An active housing visit adds the full property key to the character's persistent travel state. Realtime replication derives a logical scope from that address, so players in different plots or district instances cannot see each other even when they reuse the same hosted scene and coordinates. The scope is loaded during cross-server handoff before the destination session becomes visible.

Auction transaction boundary

Auctions enforce a minimum bid, minimum raise, ownership limit, closing time, and optional anti-sniping extensions. Bid preparation calculates only the incremental escrow charge when a bidder raises an existing bid. The game-server housing adapter locks the district, derives the balance from authoritative currency storage, consumes that currency, and revision-checks the district update in one database transaction. Replayed request IDs are idempotent.

Settlement deterministically selects the highest bid, using placement time and player ID as stable tie breakers. The winner becomes the owner, losing escrow is returned, and the auction is removed. The adapter refunds losing character UUIDs and commits the new owner under the same row lock and SQL transaction. This two-phase plan/commit split lets the domain remain deterministic while the server owns locks, balances, retries, and audit records.

Browsing a district also advances expired auctions. Auctions with bids settle and refund under the transaction above; auctions without bids reopen with a fresh closing window. Area allocation is protected by a realm-and-area advisory lock, so concurrent game-server processes cannot create the same next district.

Bid, outbid, winner, and escrow-refund messages are inserted into the persistent player inbox inside the same SQL transaction as the housing mutation. Stable dedupe keys make command replay safe, while typed housing actions retain the full area, district instance, and plot address for one-click return.

Ownership and build mode

Owners may grant co-owner, decorator, resident, or visitor roles. Only owners, co-owners, and decorators can mutate placement state. Place, move, rotate, and store commands use clone-then-commit behavior and require the expected district revision. Validation checks property-local build bounds, rotated furnishing footprints, same-layer overlap, and per-property furnishing limits before changing state. Furnishings may reference inventory items, gameplay assemblies, and persistent world-object definitions.

Owners also select a revision-checked visitor policy: private, residents, party, or public. Visit permission is resolved by the server from current ownership, resident records, and live party membership. Directory projections expose whether the viewer may enter and the current local visitor count, but never let the client authorize itself.

The server catalog loader treats housing as required content and validates those cross-catalog references at startup. Character projections expose only the district and plot information needed by the viewer; the authoritative state remains server-side.

Player Flow

Open the World Map and choose Housing. The housing surface reuses the journal layout and provides:

  1. Area and district browsing, including the authored scene and entry route in the replicated area projection.
  2. Plot auction status, adjustable revision-checked bids, leading-bid feedback, and current ownership.
  3. Build mode for owners, co-owners, and decorators with furnishing selection, grid positioning, rotation, placement, and storage.
  4. Visit or Go Home controls for permitted properties, an owner access-policy control, live presence counts, and a Return action while visiting.
  5. Immediate server feedback. Accepted commands publish the new district revision; rejected stale, overlapping, out-of-bounds, unauthorized, or inventory-invalid commands leave the projection unchanged and surface the authority message.

The UI only keeps selection and preview coordinates locally. It sends typed HousingCommand requests through the normal gameplay-action channel, and ownership, escrow, inventory, permissions, and placement state change only inside the server transaction.

Visit and return commands use the ordinary authoritative scene-transfer machinery. The first visit captures the exact source zone, scene, entry point, and tile. Returning clears the housing scope and restores that exact tile; cross-instance transfers persist the new scope before handoff and roll it back if preparation fails.

How Authors Use It

Open a housing scene and expand Scene → Detailed Scene Tools → Scene Lighting → Housing Area & District Preview. The preview reports plots per instance, capacity policy, auction timings, property-local build bounds, home/farming hooks, and available furnishing definitions. To create another neighborhood style, add one area and one scene; do not duplicate it for each live district.

Validation And Debugging

When changing the catalog:

  1. Keep area, plot, and furnishing IDs stable after shipping.
  2. Treat target_occupancy_percent as the expansion threshold and use a positive max_instances only when operations need a hard ceiling.
  3. Keep placement coordinates local to a plot so layouts survive district routing changes.
  4. Run the world-domain housing tests and game-server catalog/schema checks before publishing.

Transport code must continue wrapping the existing bid, settlement, district projection, and placement transactions rather than duplicating their rules in packet handlers.

Examples

Lantern Meadows authors four plot templates once. District instance 0 can own plot.a through plot.d; when it reaches the configured 90 percent occupancy target, the realm initializes instance 1 from the same scene and plot definitions. area.lantern_meadows + 1 + plot.a is therefore a different property from area.lantern_meadows + 0 + plot.a, even though both use the same art and build bounds.

A player with a 12,000-gold escrowed bid who raises to 13,000 is charged only another 1,000. A bid within the final five minutes extends the closing time until the configured extension limit is reached.

Related Systems