#webrtc #udp #wasm #networking #gamedev

naia-shared

Common functionality shared between naia-server & naia-client crates

26 releases (15 breaking)

0.20.0 Mar 20, 2023
0.18.0 Feb 28, 2023
0.14.0 Nov 20, 2022
0.10.0 Apr 18, 2022
0.1.2 Jul 7, 2020

#50 in WebAssembly

Download history 82/week @ 2022-12-07 69/week @ 2022-12-14 60/week @ 2022-12-21 46/week @ 2022-12-28 33/week @ 2023-01-04 45/week @ 2023-01-11 41/week @ 2023-01-18 91/week @ 2023-01-25 115/week @ 2023-02-01 83/week @ 2023-02-08 138/week @ 2023-02-15 208/week @ 2023-02-22 59/week @ 2023-03-01 72/week @ 2023-03-08 97/week @ 2023-03-15 52/week @ 2023-03-22

300 downloads per month
Used in 8 crates (4 directly)

MIT/Apache

355KB
9K SLoC

Latest Version API Documentation Discord chat MIT/Apache

naia

a networking architecture for interactive applications

A cross-platform (including Wasm!) networking engine that intends to make multiplayer game development in Rust dead simple and lightning fast.

naia helps you to easily define a common, shared Protocol that allows Server & Client to exchange information. Then, naia facilitates sending/receiving parts of that Protocol as reliable/unreliable Messages between Server & Client, and also keeps a pool of tracked Entities synced with each Client for whom they are "in-scope". Entities are "scoped" to Clients with whom they share the same Room, as well as being sufficiently customizable to, for example, only keep Entities persisted & synced while within a Client's viewport or according to some other criteria.

The API is heavily inspired by the Nengi.js & Colyseus Javascript multiplayer networking libraries. The internals follow the Tribes 2 Networking model fairly closely.

Thank very much to Kyren for support & webrtc-unreliable, and to the Laminar authors, for the cannibalized code within.

Any help is very welcome, please get in touch! I am open to any criticism / feedback in order to better this project.

Currently guaranteed to work on Web & Linux, although Windows & MacOS have been reported working as well. Please file issues if you find inconsistencies and I'll do what I can.

For more detailed information, please look at the FAQ.

Demos

More comprehensive documentation / tutorials are on their way, but for now, the best way to get started with naia is to go through the basic demo, which demonstrates most of the functionality.

Server:

To run the UDP server demo on Linux: (that will be able to communicate with Linux clients)

1. cd /naia/demos/basic/server
2. cargo run

To run the WebRTC server demo on Linux: (that will be able to communicate with Web clients)

1. // go to (https://docs.rs/openssl/latest/openssl/) to install openssl on your machine
2. cd /naia/demos/basic/server
3. cargo run

Client:

To run the UDP client demo on Linux: (that will be able to communicate with a UDP server)

1. cd /naia/demos/basic/client/wasm_bindgen
2. cargo run

To run the WebRTC client demo on Web: (that will be able to communicate with a WebRTC server)

1. cargo install cargo-web  // should only need to do this once if you haven't already
2. cargo install cargo-make // should only need to do this once if you haven't already
3. cd /naia/demos/basic/client/wasm_bindgen
4. make serve
5. Web page will be blank - check debug console to see communications from the server

Known Issues

To run a miniquad client you will require the following be installed

sudo apt-get install libxi-dev libgl1-mesa-dev

Dependencies

~2.1–5.5MB
~136K SLoC