Ryuu/AetherOnline
Watch
1
0
Fork
You've already forked AetherOnline
 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions
Page: chat presence and social
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 chat presence and social
forgejo-actions edited this page 2026-07-06 16:45:10 +00:00
Table of contents

Chat, Presence, And Social Runtime

Chat and social runtime currently combines active in-memory delivery with reserved persistence schemas for longer-lived social features. Treat active session delivery as the online authority and the SQL social tables as the durable contract being prepared around it.

Active Chat Channels

Runtime chat uses ChatChannel:

  • Zone: delivered to active sessions in the speaker's current zone.
  • Party: delivered to active party members, even across zones.
  • Whisper: delivered to the speaker and one resolved online recipient.
  • System: delivered by server/admin paths only.

Messages carry speaker entity id, speaker name, channel, body, optional target, optional emote reference, and sent_at. Emotes are accepted only when the atlas/index pair is valid.

Runtime normalizes chat text by collapsing whitespace and keeping the first 200 characters. Target text is normalized to the first whitespace-separated token and capped at 64 characters.

Players cannot send system chat directly. If a player attempts the system channel, the server sends a private system notice explaining that system messages are admin-only.

Target Resolution

The active session directory indexes chat candidates by character id, normalized character name, zone, and session token.

Whispers and party invites resolve a target in this order:

  1. Parse the target as a character UUID and look up that active character.
  2. Otherwise, match active character names case-insensitively.
  3. Reject missing targets with a private system notice.
  4. Reject ambiguous names with a private system notice that asks for the character id.

Delivery skips sessions that are pending zone transfer. Zone and party target sets are also filtered through chat privacy so ignored speakers do not deliver to recipients that block them.

Party Runtime

The party registry is in memory inside the game-server session registry. It owns party ids, membership, leader choice, invites, and reverse invite indexes.

Party commands are sent through the party chat channel:

  • invite or inv <name>: invite an online target.
  • accept or join [inviter]: accept a pending invite, optionally from a named inviter.
  • leave: leave the current party.
  • disband: disband the party when the speaker is the leader.

Party invites expire after 10 minutes. Party chat without a party returns a private system notice. Party membership is used by trigger authority and encounter logic through server-side party context; clients should not be trusted to supply party ids for authority decisions.

Presence

Active chat routing comes from the game server's active session directory. Online service presence is coordinated separately by the session lifecycle and control-plane Redis presence records described in Session Handoff And Transfer.

The 0020_account_social_preferences_and_chat_history.sql migration also creates social_presence with offline, online, away, and busy labels. That table is the durable social-presence shape, not the live routing source for current chat packets.

When debugging presence, check which layer is stale:

  • active session directory for live chat routing;
  • Redis presence for fleet/control-plane visibility;
  • SQL social_presence for longer-lived social state once that path is enabled.

Ignores, Mutes, And Moderation

The runtime privacy registry has two concepts:

  • per-recipient ignored speakers, used to block delivery from one speaker to one recipient;
  • muted speakers, used to stop a character from sending chat.

Mute and unmute are active admin actions. A muted speaker receives a private system notice and their chat is not broadcast. The ignore registry and recent-history registry are present but marked as reserved for the chat service rollout; production UI and durable ignore syncing should be verified before relying on them.

The SQL migration reserves durable social edges with relationships friend, ignored, muted, and blocked. Do not assume those rows automatically affect live chat delivery until the sync path is explicitly wired.

History And Replay

The active runtime records recent delivered messages per character in memory, capped to the recent-history limit. That is useful for runtime tests and replay-style service rollout work, but it is not a durable chat archive by itself.

The SQL chat_history_messages table is the durable history contract. It stores recipient account, speaker account/character, speaker name, channel, optional target account/name, body, sent/delivered timestamps, and transfer scope (session, zone_transfer, or reconnect). Current runtime delivery should be treated as online delivery first; durable history persistence is a separate responsibility.

System Chat

System chat is sent through admin/control-panel paths. It can target all active sessions or a specific zone. The game server reports the delivered session count, and the control panel exposes system chat send fields for operators.

The internal game-server route is POST /v1/internal/chat/system, protected by internal service authentication. Admin actions also expose system chat, mute, and unmute through the admin authorization/audit path.

Use system chat for operational notices, not for authored quest/dialogue content. Authored content should use the dialogue, quest, NPC service, or trigger systems so it remains replayable and validated as content.

Boundaries

Active today:

  • zone chat delivery;
  • whisper delivery to online, unambiguous targets;
  • party invite/accept/leave/disband and party chat;
  • admin system chat;
  • admin mute/unmute;
  • in-memory recent delivery records.

Reserved or partial:

  • durable friend/guild/social invite workflows;
  • durable ignored/muted/blocked edge synchronization into runtime privacy;
  • durable chat history persistence and replay;
  • SQL social presence as live routing authority.

When implementing new social features, wire the durable SQL contract, runtime registry, admin/moderation surface, and replay/audit behavior together. Leaving one layer disconnected creates a feature that appears present in schema but does not affect online play.

Related Pages