You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
* Document visibility better
- Move example to the component.
- Clarify that it's a component for replicated clients.
* Update documentation on identifiers
Some backends don't have IDs that are persistent across reconnects.
* Clarify that `ClientEntityMap` inserted only after replication is started.
* Clarify that not all components are present on connected clients
* Clarify how to run examples
Copy file name to clipboardExpand all lines: CHANGELOG.md
+1-1Lines changed: 1 addition & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -18,7 +18,7 @@ and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0
18
18
19
19
### Changed
20
20
21
-
- Connected clients are now represented as entities with `ConnectedClient` components. Backends are responsible for spawning and despawning entities with this component. `ClientId` is accessible from `ConnectedClient::id` in case you need an identifier that is persistent across reconnects.
21
+
- Connected clients are now represented as entities with `ConnectedClient` components. Backends are responsible for spawning and despawning entities with this component. `ClientId` is accessible from `ConnectedClient::id` in case you need to identify which client belongs to which connection.
22
22
- Statistics for connected clients now accessible via `ClientStats` component.
23
23
- Replicated entities now represented by connected clients with `ReplicatedClient` component.
24
24
- To access visibility, use `ClientVisibility` component on replicated entities.
0 commit comments