From f99ab54cb28446633da845e9deac208c703f2031 Mon Sep 17 00:00:00 2001 From: Hennadii Chernyshchyk Date: Tue, 15 Oct 2024 18:20:08 +0300 Subject: [PATCH] Clarify buffering and queuing --- src/core/event_registry/server_event.rs | 11 ++++++----- 1 file changed, 6 insertions(+), 5 deletions(-) diff --git a/src/core/event_registry/server_event.rs b/src/core/event_registry/server_event.rs index 431d80a8..d1d30eec 100644 --- a/src/core/event_registry/server_event.rs +++ b/src/core/event_registry/server_event.rs @@ -129,11 +129,12 @@ pub trait ServerEventAppExt { /// Marks the event `E` as an independent event. /// - /// By default, all events from the server are buffered until all - /// insertions, removals and despawns (value changes doesn't count) are - /// replicated for the tick on which the event was triggered. This is - /// necessary to ensure that the executed logic during the event does not - /// affect components or entities that the client has not yet received. + /// By default, all server events are buffered on server until server tick + /// and queued on client until all insertions, removals and despawns + /// (value changes doesn't count) are replicated for the tick on which the + /// event was triggered. This is necessary to ensure that the executed logic + /// during the event does not affect components or entities that the client + /// has not yet received. /// /// However, if you know your event doesn't rely on that, you can mark it /// as independent to always emit it immediately. For example, a chat