bevy_stardust
bevy_stardust copied to clipboard
A flexible networking crate for Bevy.
Working in the [udp-0.1.0 branch](https://github.com/Veritius/bevy_stardust/tree/udp-0.1.0)
gxhash requires AES-NI and SSE2 intrinsics on x86-64 and AES and NEON intrinsics on ARM. Without these, it won't compile, since there's no fallback for processors lacking these intrinsics. Since...
Right now, channels must be added in the exact same order on two different peers. This is a massive restriction, and removing it would be really good for usability.
What kind of replication? Predicted, lockstep, both?
It's a little silly to create an entire `World` and `App` just to test code that needs a reference to a channel registry. Some kind of non-`Resource` `ChannelRegistryInner` holder that...
Basically, a voice chat plugin. This is doable via the [Decodable] trait. [Decodable]: https://docs.rs/bevy/latest/bevy/audio/trait.Decodable.html
It'd be useful for various things. Probably based on [QUIC's variable length integers]. [QUIC's variable length integers]: https://www.rfc-editor.org/rfc/rfc9000.html#name-variable-length-integer-enc