#udp-socket #web-rtc #networking #udp #interactive-applications #gamedev #udp-client

naia-client-socket

Abstraction to expose common API over a UDP socket on Linux, and a unreliable WebRTC datachannel on the browser

31 unstable releases

0.22.0 Jan 10, 2024
0.20.1 Apr 1, 2023
0.20.0 Mar 20, 2023
0.13.1 Nov 19, 2022
0.3.0 Jul 13, 2020

#1279 in Network programming

Download history 1/week @ 2023-12-18 6/week @ 2023-12-25 18/week @ 2024-01-08 101/week @ 2024-02-12 13/week @ 2024-02-19 91/week @ 2024-02-26 24/week @ 2024-03-04 44/week @ 2024-03-11 22/week @ 2024-03-18 91/week @ 2024-04-01

162 downloads per month
Used in 5 crates (2 directly)

MIT/Apache

79KB
1.5K SLoC

Rust 1.5K SLoC // 0.0% comments JavaScript 177 SLoC // 0.0% comments

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

lib.rs:

Naia Client Socket

A Socket abstraction over either a UDP socket on native Linux, or a unreliable WebRTC datachannel on the browser

Dependencies

~1–20MB
~318K SLoC