Roadmap · updated November 2026
The specification is final. The work since then has been on Unity: com.fomoxa.networking 0.3.4
is out with a Rapier physics backend, a Steam transport, fRPC services, a console server and a game backend template.
What comes next follows what games need.
Timeline
fomoxac, now 0.2.3: codecs for Rust, Go, C#, C, C++, TypeScript and JavaScript, plus compat, ci, --watch and fomoxa-inspect.fomoxa-net (Rust), Fomoxa.Net (C#), Go, C/C++ and @fomoxa/net (Node.js).interop suite, and fomoxa.unity codecs for Unity types.fomoxa-example-game: Unity and Go clients against a Rust server, with a benchmark.com.fomoxa.networking 0.1.0, a server-authoritative networking package for Unity 6 built on Fomoxa.Net. Its first builds were published as com.fomoxa.unity.NetworkTransform, NetworkAnimator and network scenes.com.fomoxa.networking.rapier, behind the same interface as Unity physics.com.fomoxa.rpc: fRPC services for Unity and the pod side of the directory.Fomoxa.Backend.Templates game backend template, and the directory and gateway as source.fomoxac version across the package, the backend template, the gateway and the directory.NetworkStatsDisplay for connection, traffic, tick and prediction numbers, and a simulated network with latency, jitter, loss, duplicates and reordering.com.fomoxa.networking.steam 0.1.0: players connect by SteamID, through Valve's relay network when they cannot reach each other directly, so a player can host from behind NAT. Tested between two computers on different networks.
When Unity runs scripts on CoreCLR, which Unity plans from Unity 6.8, a version of the package moves to
.NET's own AesGcm, X509Chain and Socket.Send and drops the parts that work
around Mono.
Observer rules that combine several conditions, several copies of one scene, nested network objects,
relay transports such as Epic and Unity Relay, a client-authoritative
NetworkTransform, a built-in object pool, more RPC options, predicted spawning and ownership,
and IPv6. Each one starts when a game needs it.
The order of the next steps may change. The specification does not depend on any of this work: a Unity library is an implementation, and the wire format stays exactly as RFC-0002 defines it.
Not planned
These are the cost of Fomoxa's guarantees, not missing features. None of them is scheduled.
The reasoning for each is on the home page and in RFC-0001. Suggestions and questions are welcome as issues.