bevyhub_net

This is a very tiny and simple replication library that can run on microcontrollers and be used for DOM communication.

Features

Incoming / Outgoing

Components, Events and Resources can be specified as incoming or outgoing. Components can be both because the Replicate component can be used to distinguish who should be doing the sending.

Multiple transports

For instance a web bevy app can send serde_json messages to the dom and bincode messages to the server

Limitations

• Components must be registered in the same order for every client
• Partial changes: on component or resource changes, the entire type is sent and applied
• Messages are not cached, if a client joins late it misses previous messages
• No authority determination
• Unidirectional Resources/Events: resources and events cannot be registered as both incoming and outgoing

References

• bevy_replicon