Event based networking library for Bevy

6 releases

0.7.2 May 12, 2022
0.7.1 Apr 22, 2022
0.6.2 Feb 23, 2022

#480 in Game dev

40 downloads per month

MIT license

892 lines

bevy_eventwork is a solution to the "How do I connect multiple bevy instances" problem in your bevy games, forked from the excellent bevy_spicy_networking, with significant changes for modularity and including the removal of big dependencies like tokio and typetag.



You can check out the online documentation, or build it yourself by cloning this repo and running cargo doc -p bevy_eventwork.

For examples, check out the examples directory.

  • In you will find a simple chat server, that broadcasts the messages it receives from clients
  • In you will find a simple graphical chat client, where you can connect to a server and send messages to

(Note: Since bevy does not include a text input widget, it is a very simplified demo. This should be easy to extend once the UI part of bevy is more complete.)


  1. Add bevy_eventwork, and serde to your Cargo.toml
  2. Create the messages you wish to exchange beetween a client and server, or vice-versa.
    • Implement Serialize and Deserialize from Serde on it
    • Implement NetworkMessage when it is sent to the server from a client
#[derive(Serialize, Deserialize)]
struct WhisperMessage {
    recipient: UserId,
    message: String,

/// In this example, we'll be sending this from a client to a server,
/// BUT, any eventwork bevy instance could recieve the message as
/// long as they register to listen for it.
impl NetworkMessage for WhisperMessage {
    const NAME: &'static str = "example:WhisperMessage"; 
  1. On the recipient side, register the type to be received
use bevy_eventwork::{AppNetworkMessage, tcp::TcpProvider};

let appbuilder: &mut AppBuilder = /* Get an AppBuilder, which is returned by bevy from App::build() */;

// Now whenever a client sends a `WhisperMessage` the server will generate an event of
// `NetworkData<WhisperMessage>` which your application can then handle
appbuilder.listen_for_message::<WhisperMessage, TcpProvider>();
  1. Listen for events of that type
fn handle_incoming_whisper_messages(
    mut whisper_messages: EventReader<NetworkMessage<WhisperMessage>>,
) {
    for whisper_message in whisper_messages.iter() {
        // Handle the whisper


Starting with version 0.7.1, you can now automatically handle Request/Response style messaging with event work! Check the documentation for more info!

Bevy Version Compatibility

Simply pick the version compatible to your bevy version:

Bevy Eventwork Bevy
> 0.6 > 0.6

Any version that is not compatible with the latest bevy version is in maintenance mode. It will only receive minor bug fixes from my side, or community supplied ones.

Supported Platforms

Currently only Linux and Windows are officially supported, I don't see why MacOS wouldn't be, but I do not have a Mac to test. If you have a Mac, and wish to test it out and report back, please let me know!


  • General code cleanup, testing, and documentation work
  • Message wide event pipelines
    • Useful for mapping connection id to user provided ids
  • Message type mapping (
    • Currently the message type is sent as a string with each method, it would be nice if you could just send a few bytes instead.
  • RPCs!

Crates using bevy_eventwork

Currently none, you can help by expanding this list. Just send a PR and add it to the table below!

Name Version
- -

Transport providers for bevy_eventwork

Name Version
eventwork_tcp (included) 0.6


To contribute, simply fork the repository and send a PR.

Feel free to chat me up on the bevy discord under @SirCarter#8209 if you have any questions, suggestions, or I'm not looking into your PR fast enough and you need someone to yell at (respectfully of course).


~449K SLoC