Fomoxa

EN/VI

Roadmap · updated November 2026

What is done, and what comes next

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

Done · 2026 Specification and foundations
  • RFC-0001, RFC-0002 and RFC-0003 at v1.1.0, Final, in English and Vietnamese.
  • Version skew rules: fields appended or removed at the end of a Model (RFC-0002 §9.1).
  • fomoxac, now 0.2.3: codecs for Rust, Go, C#, C, C++, TypeScript and JavaScript, plus compat, ci, --watch and fomoxa-inspect.
  • Sample runtimes: fomoxa-net (Rust), Fomoxa.Net (C#), Go, C/C++ and @fomoxa/net (Node.js).
  • The implementation guide, the cross-language interop suite, and fomoxa.unity codecs for Unity types.
  • fomoxa-example-game: Unity and Go clients against a Rust server, with a benchmark.
  • This site: getting started guide, byte inspector, ecosystem and comparison pages.
Done · October 2026 Unity, stage one: com.fomoxa.networking 0.1.0
  • 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.
  • UDP, TCP and WebSocket transports, host mode, and WebGL clients.
  • Network objects, RPCs, per-behaviour state, NetworkTransform, NetworkAnimator and network scenes.
  • Client-side prediction with reconciliation and rollback of Unity's 3D and 2D physics.
  • Codecs for Unity types generated in the Editor, in the same package.
  • A Rapier physics backend, com.fomoxa.networking.rapier, behind the same interface as Unity physics.
  • A console server that runs the authoritative game without the Unity player and loads scene files exported from the Editor.
  • Red Runner, a single-player platformer, ported to an online game as a step-by-step example.
Done · October 2026 Release 0.2.0: connections and a cluster
  • Authentication before a peer starts, kicks with a reason, and transfers of a client to another server.
  • Encrypted UDP with connect grants, the same datagrams over WebSocket for WebGL, and client TLS on TCP and WebSocket.
  • Synchronized lists, dictionaries and sets, and reliable messages up to 1 MiB.
  • com.fomoxa.rpc: fRPC services for Unity and the pod side of the directory.
  • The Fomoxa.Backend.Templates game backend template, and the directory and gateway as source.
  • Guides for running the cluster on Kubernetes with Agones.
Done · November 2026 Releases 0.3.0 to 0.3.3: physics and large schemas
  • Physics queries with filters, forces and torques, continuous collision, contact points and several bodies per network object.
  • Rapier 0.2: native libraries for Windows, Linux, macOS, Android, iOS and Web, joints, a character controller and Unity's 2D effectors.
  • Handshakes of large schemas sent in several packets over packet transports, in the package and in every sample runtime.
  • Code generation in the macOS Editor, and one fomoxac version across the package, the backend template, the gateway and the directory.
Done · November 2026 Release 0.3.4 and the Steam transport
  • Debug tools: traffic counters per bundle and per message, NetworkStatsDisplay for connection, traffic, tick and prediction numbers, and a simulated network with latency, jitter, loss, duplicates and reordering.
  • The size of every prediction correction, drawn in the Scene view, and a count of the inputs the server drops for each client.
  • 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.
Next Unity on CoreCLR

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.

Planned
Then Features as games need them

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.

Planned

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

What the roadmap will not add

These are the cost of Fomoxa's guarantees, not missing features. None of them is scheduled.

  • Field tags, field numbers or names on the wire.
  • Optional, nullable or default-valued fields.
  • Varints or any other variable-width integer.
  • A mandatory IDL or schema file format.
  • Transport, framing, RPC, compression or encryption in the specification.
  • Version markers inside the byte stream.

The reasoning for each is on the home page and in RFC-0001. Suggestions and questions are welcome as issues.