Netcode
Quark
We built our own netcode engine. It runs a competitive shooter in a browser tab, and in a head-to-head benchmark it used 6× less CPU than Unity DOTS Netcode for Entities (NfE).
6.2×
less CPU than Unity DOTS Netcode for Entities (NfE), predicting 512 entities
151×
less CPU with 16 entities in the world
0.41 ms
to bring 128 players up to date, each server update
What Quark is
Quark is the netcode engine behind every online game on slopaf. It keeps every player's screen in step with what really happened, and hides the distance between you and everyone else.
We wrote it ourselves, and it is ours alone: not sold, not licensed, not open source.
The proving ground: Phi Phai
Shooters are the hardest genre to put online: every shot is a judgment call and every delay shows. So we built one. Phi Phai is a competitive team shooter in the spirit of the classic tactical shooters, and it runs on Quark in a browser tab.
- Up to 16 players, 8 v 8, with bots at five skill levels.
- A full arsenal, each gun with its own recoil, and frag, smoke, flash and fire grenades.
- Every shot settled on our servers, the same way for everyone.
- Your own moves answer the moment you press a key.
- Friends can watch a running match from the sidelines.
- Nothing to install: open the page and play.
Phi Phai is live on slopaf in public pre-release. Play it.
What it gives a game
- Fair by design
- Every match is played out on our servers. What counts is what really happened, for everyone.
- Instant feel
- The match lives on a server, but your own moves never wait for it.
- Smooth to watch
- Other players move naturally on your screen, not in jumps.
- Browser and native
- One engine runs in a browser tab and in native game clients.
Running on Quark
- Phi Phai
- A competitive team shooter, up to 8 v 8.
- Sky Brawlers
- Five-a-side dogfights in a cartoon sky, up to ten pilots.
- Turbo Kart Rally
- Kart racing for up to eight, the first game on slopaf.
A shooter, a dogfight and a racer, three very different games on one engine.
By the numbers
0.41 ms
128 players
Keeping 128 players up to date took 0.41 ms per server update, 0.63 ms at the 99th percentile.
0.27 ms
256 players, 4,096 objects
A synthetic stress test: 256 players in a world of 4,096 objects, 0.27 ms per server update.
6.2×
Less CPU than Unity NfE
Predicting 512 entities on the player's machine, against Unity DOTS Netcode for Entities. The full comparison is below.
Measured by us in September 2026 on one machine (AMD Ryzen 9 9950X, Windows 11, release builds), over a local connection, with the server's work spread across several cores. The server figures cover keeping players up to date, not a game's own rules.
Measured against Unity DOTS Netcode for Entities (NfE)
Client prediction, CPU per step
6.2×
less CPU than Unity DOTS Netcode for Entities (NfE), predicting 512 entities on the player's machine.
| Entities | Unity DOTS NfE | Quark | Less CPU |
|---|---|---|---|
| 16 | 89 µs | 0.59 µs | 151× |
| 128 | 101 µs | 4.6 µs | 22× |
| 512 | 119 µs | 19 µs | 6.2× |
| 4,096 | 435 µs | 168 µs | 2.6× |
Same game state and the same amount of work on both sides, checked entity by entity. The Unity side is the shipping Unity DOTS Netcode for Entities (NfE) package, not a stand-in.
This measures client-side prediction only. No network, server, physics or rendering.
- Machine
- AMD Ryzen 9 9950X, Windows.
- Unity side
- Unity 6000.6.2f1, Netcode for Entities 6.6.0, Burst 2.0.0, release standalone player, one worker thread plus the caller.
- Quark side
- Release build, one thread.
- Method
- Both sides predict the same distance ahead at the same rate, over 1024 measured steps after warm-up. Median of three runs, CPU time across every thread.