From ea4d5e7913c407b50b45500868e1d97044c33af3 Mon Sep 17 00:00:00 2001 From: aromaa Date: Sat, 12 Oct 2024 23:13:44 +0300 Subject: [PATCH] Update documention for ServerSideConnectionEvent#Intent --- .../api/event/network/ServerSideConnectionEvent.java | 6 ++++++ 1 file changed, 6 insertions(+) diff --git a/src/main/java/org/spongepowered/api/event/network/ServerSideConnectionEvent.java b/src/main/java/org/spongepowered/api/event/network/ServerSideConnectionEvent.java index a23d58b213..bbcc2e9bbe 100644 --- a/src/main/java/org/spongepowered/api/event/network/ServerSideConnectionEvent.java +++ b/src/main/java/org/spongepowered/api/event/network/ServerSideConnectionEvent.java @@ -35,6 +35,7 @@ import org.spongepowered.api.event.message.MessageEvent; import org.spongepowered.api.network.ServerSideConnection; import org.spongepowered.api.network.channel.Channel; +import org.spongepowered.api.network.channel.raw.RawDataChannel; import org.spongepowered.api.profile.GameProfile; import org.spongepowered.api.service.ban.BanService; import org.spongepowered.api.service.whitelist.WhitelistService; @@ -81,6 +82,11 @@ public interface ServerSideConnectionEvent extends Event { *

Called asynchronously when the client attempts to connect to * the server.

* + *

During this event, it's possible to use the {@link RawDataChannel}s to send + * requests to the client. As long as there's requests going to the client, + * the connection will stay in the intent phase and will not continue + * to the {@link Auth} event.

+ * *

After observing this event for particular {@link ServerSideConnection connection} * you are guaranteed to get #Disconnect for the same connection without * ordering issues.