Crates.io | naia-server |
lib.rs | naia-server |
version | |
source | src |
created_at | 2020-07-01 02:02:42.999762 |
updated_at | 2024-12-13 00:31:46.964616 |
description | A server that uses either UDP or WebRTC communication to send/receive messages to/from connected clients, and syncs registered Entities/Components to clients to whom they are in-scope. |
homepage | https://github.com/naia-lib/naia |
repository | https://github.com/naia-lib/naia |
max_upload_size | |
id | 260116 |
Cargo.toml error: | TOML parse error at line 18, column 1 | 18 | autolib = false | ^^^^^^^ unknown field `autolib`, expected one of `name`, `version`, `edition`, `authors`, `description`, `readme`, `license`, `repository`, `homepage`, `documentation`, `build`, `resolver`, `links`, `default-run`, `default_dash_run`, `rust-version`, `rust_dash_version`, `rust_version`, `license-file`, `license_dash_file`, `license_file`, `licenseFile`, `license_capital_file`, `forced-target`, `forced_dash_target`, `autobins`, `autotests`, `autoexamples`, `autobenches`, `publish`, `metadata`, `keywords`, `categories`, `exclude`, `include` |
size | 0 |
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.
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.
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
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
To run a miniquad client you will require the following be installed
sudo apt-get install libxi-dev libgl1-mesa-dev