Veritius
Veritius
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
Some kind of transport-agnostic API or trait that lets you add steps to 'authorise' a peer before it's considered fully connected, but only after a handshake so reliability is ensured....
Including the transport layer/sockets stuff.