Expand description
§bevy_slinet
TCP/UDP networking for Bevy with configurable packet types, serializers and custom transports.
Enable the features you need: client, server, protocol_tcp, protocol_udp,
serializer_bitcode or serializer_bitcode_serde. See Cargo.toml.
Bincode serializers remain for compatibility; prefer bitcode for new code.
Browser WASM support is preliminary and requires a custom transport; the built-in TCP/UDP transports are native-only. See the configuration guide.
- Examples: TCP, UDP, application sessions, all examples.
- API reference · Configuration · UDP semantics · Migration to 0.19 · Benchmarks.
§Bevy compatibility
| Plugin Version | Bevy Version |
|---|---|
0.9 | 0.13 |
0.10 | 0.13 |
0.11 | 0.14 |
0.12 | 0.14 |
0.13 | 0.15 |
0.14 | 0.16 |
0.15 | 0.17 |
0.16 | 0.17 |
0.17 | 0.18 |
0.18 | 0.19 |
0.19 | 0.19 |
0.20 | 0.20 |
main | 0.20 |
Re-exports§
pub use protocols::protocol;pub use serializers::packet_length_serializer;pub use serializers::serializer;
Modules§
- client
- Client part of the plugin. You can enable it by adding
clientfeature. - connection
- Connects ECS packet queues to transport tasks.
- protocols
- Protocol traits and implemented protocols:
- runtime
- Tokio execution shared by the network endpoints in one Bevy app.
- serializers
- Packet serialization traits, stream length prefixes, and implemented serializers:
- server
- Server part of the plugin. You can enable it by adding
serverfeature.
Structs§
- Network
Systems - Scheduling phases for one endpoint (role and config).
Enums§
- System
Sets - Exposes networking phases so application systems can order their work around packet events.
Traits§
- Client
Config - A client plugin config.
- Server
Config - A server plugin config.