Skip to content

Add game-server sidecar APIs for clustered services#35

Closed
VG-prog wants to merge 10 commits into
walkline:masterfrom
VG-prog:vg/tc9-sidecar
Closed

Add game-server sidecar APIs for clustered services#35
VG-prog wants to merge 10 commits into
walkline:masterfrom
VG-prog:vg/tc9-sidecar

Conversation

@VG-prog

@VG-prog VG-prog commented May 22, 2026

Copy link
Copy Markdown

Summary

This PR extends the game-server sidecar bridge used by AzerothCore integration.

It adds the C ABI and Go bridge surface for clustered group, guild, LFG, arena, item, monitoring, and consumer-handler flows. The sidecar remains the narrow native boundary: AzerothCore calls into it for discrete cluster operations while ToCloud9 services own distributed coordination.

What changed

  • Added grouped member-state event bridge APIs.
  • Added guild and LFG C ABI and Go RPC entry points.
  • Added arena-team service bridge APIs.
  • Extended battleground, item, and monitoring bridge behavior.
  • Added config loading needed by sidecar clients.
  • Added consumer handlers for the new service events.
  • Added exported headers for the AzerothCore side to consume in a later integration PR.

Why this matters

The sidecar is the contract between native AzerothCore code and ToCloud9. Keeping this bridge explicit makes it possible to review the C ABI separately from the AzerothCore call sites.

Validation

  • git diff --check origin/master..HEAD
  • env GOCACHE=/tmp/tc9-go-build GOFLAGS=-buildvcs=false go build ./...
  • env GOCACHE=/tmp/tc9-go-build GOFLAGS=-buildvcs=false make install

VG-prog added 10 commits May 22, 2026 21:49
Add the shared protobuf, generated runtime code, events, GUID helpers, auth identity helpers, and configuration contracts used by clustered gateway, registry, group, guild, matchmaking, and sidecar flows.

Tests, local tooling, and broad documentation are intentionally excluded from this upstream-focused scope.
Wire service discovery, map readiness, stale-safe health and metrics observers, degraded game-server health handling, gateway-scoped cleanup, and shared GUID allocation support.

Registry and health code now distinguish world-loop degraded state from process or transport death while preserving live map ownership.
Keep world-loop degraded game servers registered for ownership and existing lookups, but mark them as non-admitting so new player placement skips them. Clear the drain state on successful health recovery and fall back to healthy all-map nodes when an assigned owner is degraded.
Route gateway sessions through cluster-aware worldserver selection, native transport handoff, bounded retry/backoff, cross-service event listeners, and client-facing packet rendering for social, group, guild, guild bank, LFG, battleground, arena, mail, channel, and player-state flows.
Extend character, chat, and mail services for clustered realm identity, Real ID/account lookups, channel membership and moderation, crossrealm whisper policy, online-state broadcasts, and arena-team persistence used by gateway routing.
Add clustered group authority for realm-scoped membership, native LFG materialized groups, member-state freshness, latest-state catch-up, receiver-aware fanout, offline cleanup, debug tracing, and persistent group identity support.
Add realm-scoped guild service routing, charter offer/sign/query/signature handling, native petition persistence, guild cache lifecycle, gateway-facing events, and debug logging for same-realm clustered guild workflows.
Add guildserver-owned same-realm guild bank item, money, tab, log, text, split, merge, withdraw-limit, rollback, and idempotency helpers backed by direct MySQL transactions and guidserver item allocation.
Extend matchmaking and mysqlreverseproxy for crossrealm LFG proposal materialization, persistent instance routes, battleground owner placement, arena-team persistence and rated-result handling, character-state listeners, and route-aware SQL interception.
Extend the libsidecar C ABI and Go bridge with grouped member-state events, guild and LFG RPCs, arena-team and item APIs, monitoring/readiness behavior, config loading, and consumer handlers required by the clustered AzerothCore integration.
@VG-prog

VG-prog commented May 22, 2026

Copy link
Copy Markdown
Author

Closing this draft because it was opened from a stacked branch while targeting master, so the GitHub diff includes earlier slices and is not an isolated review target.

Replacement: #37 (#37)

That replacement PR presents the current integration honestly as one review surface. Sorry for the review noise.

@VG-prog VG-prog closed this May 22, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant