Client-server architecture for Bevy

Aceeri

Last update: Nov 14, 2022

Related tags

Overview

Sabi

Opinionated client-server architecture for Bevy

Goals:

Prediction based on inputs
Replication by a simple derive and adding a system to server/client
~~Priority queue based sending so we focus on important entities/components.~~ Interest management based on changes/connecting players.
TBD (whatever else I feel like doin)

Is it production ready?

Who the hell knows but I'm using it. It definitely isn't super polished yet, but I'm hoping to improve that in the next couple months.

Feel free to contribute to this or to renet (the underlying library) here: https://github.com/lucaspoffo/renet Most of the hard work of getting the UDP/packets sending/encryption was done over there.

You might also like...

An online version of the popular game four in a row, written in Rust on the server side and Flutter + Dart on the client.

Four in a Row - Server An online version of the popular game four in a row, written in Rust on the server side and Flutter + Dart on the client. Downl

8 Sep 16, 2022

A minimalist socket-based client/server in Rust to illustrate a tutorial

The basics of unix sockets This repository serves as a reference for this tutorial blogpost How to run Install Rust and Cargo, and then do: cargo run

4 Dec 4, 2022

A multi-connection TCP reverse proxy server and client.

tprox A multi-connection TCP reverse proxy. The tprox server is able to proxy multiple incoming connections to the tprox client over a single TCP conn

4 Sep 21, 2022

SOCKS5 implement library, with some useful utilities such as dns-query, socks5-server, dns2socks, udp-client, etc.

socks5-impl Fundamental abstractions and async read / write functions for SOCKS5 protocol and Relatively low-level asynchronized SOCKS5 server impleme

5 Aug 3, 2023

RDE1 (Rusty Data Exfiltrator) is client and server tool allowing auditor to extract files from DNS and HTTPS protocols written in Rust. 🦀

Information: RDE1 is an old personal project (end 2022) that I didn't continue development on. It's part of a list of projects that helped me to learn

32 Oct 6, 2023

A simple message based networking library for the bevy framework

Spicy Networking for Bevy bevy_spicy_networking is a solution to the "How do I connect multiple clients to a single server" problem in your bevy games

67 Jan 1, 2023

Bevy plugin for the GGRS P2P rollback networking library.

Bevy_GGRS Bevy plugin for the 👉 GGRS P2P rollback networking library. The plugin creates a custom stage with a separate schedule, which handles corre

120 Jan 6, 2023

Bevy asset loader that transparently supports loading over http(s)

Bevy Web Asset This is a tiny crate that that wraps the standard bevy asset loader, and adds the ability to load assets from http and https urls. Supp

28 Jan 2, 2023

A telnet chat server written in Rust, running on Lunatic.

Lunatic.chat A telnet chat server written in Rust, running on Lunatic. If you just would like to try it out, join the hosted version with: # US server

101 Jan 2, 2023

Comments

Bevy 0.9

Updated to 0.9, mostly Resource derives.

Still a problem with https://github.com/Aceeri/sabi/blob/2f37474ce5d32d1237548709f2083a7a60fc8ed4/sabi/src/replicate/physics3d.rs#L237-L238 and https://github.com/Aceeri/sabi/blob/2f37474ce5d32d1237548709f2083a7a60fc8ed4/sabi/src/replicate/physics2d.rs#L219-L220 getting an error that the trait bound SharedShape: Deserialize<'_> is not satisfied

opened by Sjael 1
Client Movement + Replicate Jitter

When moving, rotating, and watching a number tick up over time (when a component is using the replicate plugin), there is a jitter on the client. Numbers wont increment smoothly, rotation and movement will take a few frames to 'settle'. I've isolated some of this issue to the rewind function https://github.com/Aceeri/sabi/blob/676659ba07229ff104e9ea67520b7e07a1f8ac99/sabi/src/protocol/resim.rs#L66-L86

Commenting that function out fixes the number jitter, so I'm thinking a lot of it is in here, but the movement jitter only get's half fixed. Perhaps it is this function potentially setting the 'Owned' player's input back to the previous frame is the other part? https://github.com/Aceeri/sabi/blob/676659ba07229ff104e9ea67520b7e07a1f8ac99/sabi/src/protocol/input.rs#L306-L329

opened by Sjael 0