this post was submitted on 06 Mar 2024
3 points (71.4% liked)

Bevy Engine

113 readers
1 users here now

founded 2 years ago
MODERATORS
3
submitted 9 months ago* (last edited 9 months ago) by [email protected] to c/bevy
 

This release is big! We abstracted out all I/O and renet dependency. We will continue to provide first-party integration with renet via bevy_replion_renet.

But now users can write their own integration with other messaging libraries. Refer to the documentation for instructions on how to do it, the process is very simple. See bevy_replicon_renet as an example.

This also opens up the possibility of simultaneously using multiple messaging libraries on the server, as long as the client identifiers they provide are unique.

See the changelog for a full list of changes.

📦bevy_replicon 📦bevy_replicon_renet

top 1 comments
sorted by: hot top controversial new old
[–] [email protected] 1 points 9 months ago

Does this mean that bevy_replicon could be used with something like bevy_quinnet?