Reworked the bevy_replicon API for connections
Reworked the bevy_replicon API for connections
Store connected clients and their data as entities by Shatur · Pull Request #423 · projectharmonia/bevy_replicon
This PR replaces ConnectedEntities, ReplicatedEntities, ClientEntityMap, and Messages resources with entities and data stored as components. Connected clients are now represented by entities with a......
Previously, I used a special ClientId type to refer to connected clients and stored their data in several resources.
I wasn't satisfied with this API and decided to try turning them into entities. Now, Entity is the identifier, and components store related data. I'm quite happy with the results, but waiting for a review from the second maintainer: https://github.com/projectharmonia/bevy_replicon/pull/423
If you have any suggestions or ideas, feel free to comment 🙂
Just preparing the crate to the upcoming talk at Bevy Meetup #9. Still in a break from actual game development.