What networking library to use for a multiplayer game

[Tricked-dev]

Hello i am wanting to make a multiplayer game using bevy but i am running into the issue of what networking library to use.
The game i'm making must be able to have 100+ players in the same "lobby" and see each other move. i am considering just using normal web-socket's.

libraries i have tried:

• naia cant get it to compile
• bootleg_networking i don't like its style + it seems unmaintained
• spicy_networking outdated ( does have a bevy 0.6 pr but not accepted)

I was wondering if any of you have a suggestion for a networking library to use or if i should go ws/tcp?

edit:
noticed that this was on top of search results and is still being actively viewed see https://bevyengine.org/assets/#networking for a list of libraries

[NiklasEi]

I found matchbox very nice. They have an example with bevy and ggrs.

For a game where you want to constantly sync positions/actions in real time I would not suggest websockets. They can be a lot easier for things like turn based games, but your use case sounds like WebRTC would fit nicely.

[Tricked-dev]

Thanks ill check it out

[minecrawler]

WebRTC means that clients are authoritative. That's not something you always want. Just think of all the cheating possibilities and no single server you control to check values.
Also, a lot of clients may be behind firewalls or proxies and will need an TURN server anyway.

[Tricked-dev]

Yeah that's the annoying part might just have to with ws then.

[james7132]

While the TURN server/NAT punch through point is indeed a common problem, the networking model of ggrs requires zero state transfer over the network. Only inputs are sent over the network. If no state is transferred, no authority is needed.

[LucCADORET]

WebRTC does not mean your game is client-authoritative. You can have an authoritative server broadcasting with WebRTC to the clients, acting as the only authority. You can use libraries like https://github.com/kyren/webrtc-unreliable to setup WebRTC server-side. What is your issue with Naia ? The bevy example works fine for me.

[heavyrain266]

I suggest building internal library with quinn which is high level QUIC (UDP + TCP mix) protocol implementation which is quite easy to use.

[caniko]

wtransport is new! It should even work on the web!

[NHodgesVFX]

Some more suggestions

https://github.com/lucaspoffo/renet
https://github.com/lifescapegame/bevy_replicon
https://github.com/gschup/bevy_ggrs

Tutorial for bevy_ggrs and matchbox

https://johanhelsing.studio/posts/extreme-bevy

[mogambro]

I'd use https://github.com/Henauxg/bevy_quinnet

[cBournhonesque]

You can also try
https://github.com/cBournhonesque/lightyear
which also does prediction/replication and is transport-agnostic