Shared multiplayer protocol forbevy_kbve_net
A Bevy 0.18 + lightyear 0.26 networking crate defining KBVE's shared multiplayer protocol — the replicated components, inputs, messages, and channels both client and server compile against.
One protocol, both halves
It defines the lightyear protocol — replicated components, player input types, message payloads, and channels — that both the client and the server compile against, so both halves agree on the wire format.
What it gives you
Features
Shared protocol plugin
ProtocolPlugin registers the replicated components, inputs, messages, and channels once for both sides.
Rich message surface
Position and vitals sync, inventory and equipment updates, crafting requests / results, creature capture and state events, skill XP grants, and username set flows.
lightyear backend
Replication, prediction, interpolation, native input, and netcode; the client feature adds WebSocket, WebTransport, and UDP transports (plus a wasm32 WebSocket path for browser builds).
Optional feature set
npcdb pulls creature types from bevy_npc, creatures adds capture / sync systems via bevy_tasker and dashmap.
Worldgen helpers
Deterministic tile hashing and loot rolls (hash2d, object_at_tile, roll_loot_at) shared across client and server.
Questions
Frequently asked
What does the bevy_kbve_net crate do?
It defines KBVE's shared lightyear multiplayer protocol for Bevy 0.18 — the replicated components, player inputs, message types, and channels used by both the client and the server so both halves speak the same wire format.
Which networking backend does bevy_kbve_net use?
It builds on lightyear 0.26 with replication, prediction, interpolation, native input, and netcode. The optional client feature adds WebSocket, WebTransport, and UDP transports, including a wasm32 WebSocket path for browser builds.
What optional features does the crate expose?
The npcdb feature pulls creature types from bevy_npc, the creatures feature adds capture and sync systems via bevy_tasker and dashmap, and the client feature enables transport selection and connection lifecycle for the client half.