ECS-focused high-level networking crate for the Bevy game engine.

• Automatic component-oriented world state replication.
• Events-based messaging API with different guarantees (reliable, reliable unordered, and unreliable).
• Control over client visibility of entities and events.
• Replication into scene to save server state.
• Support for client and server both in one App and in separate.
• Customizable serialization and deserialization even for types that don't implement serde traits (like Box<dyn Reflect>).
• No builtin I/O. Use it with any messaging library. We provide a first-party integration with renet via bevy_replicon_renet.
• API focused on writing logic once that automatically works for singleplayer, client, server, and listen server (when server is also a player).

Prediction and interpolation are not implemented in this crate and are considered out of scope. But the idea of the crate is to provide an extensible core, so if your game needs something, you can implement it on top. Also check out related crates.

Check out the quick start guide.

See also examples.

• bevy_replicon_snap - adds snapshot interpolation and client-side prediction.
• bevy_replicon_attributes - adds ergonomic visibility control through client attributes and entity/event visibility conditions. An extension of this crate's raw client visibility API.
• bevy_replicon_repair - preserves replicated client state across reconnects.
• bevy_timewarp - a rollback library that buffers component state. See this instruction about how to integrate.

Note: Ensure that your bevy_replicon version is compatible with the used crate according to semantic versioning.