Crossplay with pokopia-native: protocol comparison and options (research)

Aperta
  • Qualcosa non va?
#505 0 commenti 0 reazioni 0 assegnatari Vedi su GitHub

Nessuno ha ancora preso questa issue.

Valutazione

Difficoltà
5/5
Tempo stimato
Più di una settimana
Idoneità per principianti
20/100
Tipo di issue
Documentazione
Chiarezza
Da chiarire
Stato di attività
Attiva
Stack tecnologico
cpp
Ambito
networking

Direzione di ricerca

Start by reading the issue’s comparison of the Link Play stacks and its A/B/C options; it identifies no repository files or tests to inspect. The work is to decide whether crossplay is wanted and select an approach, after resolving the listed protocol, identity, security, discovery, and licensing questions.

Scritto dal modello di indicizzazione a partire dal testo della issue.

Descrizione

in progress multiplayer tracking

Read-only comparison of the Link Play ("Local connection") stacks in Dittobyte/Recompia and xFractals/pokopia-native (MIT, clone at 4a72d23, 1.3.0), and what crossplay would take.

Bottom line

The two games would interoperate at the game level (same game, same nn::ldn HLE, same LocalCommunicationVersion 301, same virtual UDP socket on port 49530), but the transport, discovery and identity/auth layers are entirely different designs. Crossplay today is impossible without one side implementing the other's protocol (A), a bridge (B), or an agreed shared protocol (C). The room-code format is already shared; the key derivation is not.

What matches, and what does not
  • Matches: nn::ldn emulation and the NetworkInfo/NodeInfo the game sees; the LocalCommunicationVersion; the virtual UDP socket on port 49530.
  • Differs: transport and message framing, LAN discovery, and the join/identity checks. Their build has a build-ID + mods-fingerprint gate with no analogue here; this side's session-variant has none there.
  • Room code: same format, different KDF ("pokopia-relay room v1" vs "pokopia-coop room v1").
  • Security: their internet play authenticates every frame/datagram (HMAC, replay-protected); this side authenticates only the join and trusts the post-join data path.
Options

A. Our runtime speaks their protocol as a second Link Play mode. Needs their wire protocol end to end, a Linux mDNS/DNS-SD backend (theirs has none), their identity (game main build ID + mods fingerprint), and their room-code KDF. Cost: high — effectively a parallel transport stack (~3–4k lines). Risk: their Link Play is unreleased and may change.

B. A bridge process. A helper that speaks this relay protocol on one side and their coop protocol on the other, mapping one room to one session and forwarding NetworkInfo + game datagrams, and answering both identity checks. Cost: moderate; reuses both stacks. Adds a hop and a support burden, and needs a NAT/mDNS answer.

C. A shared protocol agreed by both projects. Both adopt one versioned discovery + transport + auth format. Highest coordination, lowest long-term duplication. Their Link Play is unreleased and their roadmap is their own.

Risks
  1. Their Link Play is "not released"; protocol, ports, DNS-SD keys and KDF may change.
  2. Room-code KDF mismatch: same code, different keys.
  3. No shared identity gate: a compatible mode must define a common compat gate or drop their check (weakening their cheat refusal).
  4. Security asymmetry: pick one threat model.
  5. License boundary: MIT is GPL-compatible, but needs attribution and a decision on vendoring vs reimplementing.
  6. mDNS on Linux: any option that uses their discovery needs a Linux backend.
Open questions
  • Is crossplay with pokopia-native wanted at all, and at what priority (LAN first, internet later)?
  • Is MIT code in the GPL tree acceptable (vendoring their coop module) vs a clean-room reimplementation vs a bridge?
  • Is the game's main build ID available at runtime to supply their identity check, and would the mods-fingerprint scheme be adopted or replaced with the session-variant scheme?
  • Which room-code KDF should win?
  • Preferred option A / B / C, given the runtime is Windows-built but runs under Proton and any added Linux mDNS work lands in code that cannot be built locally today.
Lingua principale
C++
Stelle
224
Fork
0
Nessuna PR unita negli ultimi 30g

Preparare l'ambiente

Come iniziare

  1. Leggi tutta la issue e poi la guida ai contributi del progetto.
  2. Commenta sulla issue per dire che te ne occupi tu — evita che due persone facciano lo stesso lavoro.
  3. Fai un fork del repository e lavora su un branch.
  4. Apri una pull request che faccia riferimento al numero della issue.

Altre issue di featureJosh/Recompia

Tutte le issue di featureJosh/Recompia

Issue simili

Altre issue su C++

Ricevi le nuove issue nella tua casella

Un breve riepilogo di issue GitHub adatte ai principianti.