alpaca-netcode: Rollback/replay NetCode for realtime, deterministic, multiplayer games.
A rollback/replay client-server system for realtime multiplayer games. The API only requires you to express your game as a pure, deterministic function.
See Alpaca.NetCode to get started.
Simple code. Your game logic contains no NetCode.
Low bandwidth. Only inputs are shared.
Zero latency. Player's own inputs affect their game immediatly.
UDP based. Unordered and using redundancy to mitigate packet loss.
Lightweight server. The server does not run the game logic, it only relays and tracks user inputs.
Cheating. Only inputs are shared which eliminates a whole class state manipulation cheats.
Increased CPU usage. Rollback/replay means that clients must run the game step function multiple times per frame.
Not suitable for large numbers of players. Tens of players is likey reasonable.
This is an initial release with minimal functionality and still very experimental. Use at your own risk.
|Dependencies||base (>=4.9 && <4.16), bytestring, containers, flat, hashable, network (==3.1.*), network-run, random, stm, time [details]|
|Copyright||2021 David Eichmann|
|Category||Network, Game Engine|
|Source repo||head: git clone https://github.com/DavidEichmann/alpaca-netcode|
|Uploaded||by DavidEichmann at 2021-04-02T22:23:32Z|
|Downloads||30 total (30 in the last 30 days)|
|Rating||2.0 (votes: 1) [estimated by Bayesian average]|
Docs uploaded by user
Build status unknown [no reports yet]
For package maintainers and hackage trustees