From f9fdbf3c2cb5a4b169ef98023c818eed9fb7130b Mon Sep 17 00:00:00 2001
From: "spongie-jd[bot]" <167721471+spongie-jd[bot]@users.noreply.github.com>
Date: Sat, 12 Oct 2024 20:17:03 +0000
Subject: [PATCH] Publishing javadoc for SpongePowered/SpongeAPI
 12.0.0-SNAPSHOT

---
 .../api/event/network/ServerSideConnectionEvent.Intent.html  | 5 +++++
 1 file changed, 5 insertions(+)

diff --git a/spongeapi/12.0.0-SNAPSHOT/org/spongepowered/api/event/network/ServerSideConnectionEvent.Intent.html b/spongeapi/12.0.0-SNAPSHOT/org/spongepowered/api/event/network/ServerSideConnectionEvent.Intent.html
index a9d6560d6..12a0d4767 100644
--- a/spongeapi/12.0.0-SNAPSHOT/org/spongepowered/api/event/network/ServerSideConnectionEvent.Intent.html
+++ b/spongeapi/12.0.0-SNAPSHOT/org/spongepowered/api/event/network/ServerSideConnectionEvent.Intent.html
@@ -100,6 +100,11 @@ <h1 title="Interface ServerSideConnectionEvent.Intent" class="title">Interface S
 <div class="block"><p>Called asynchronously when the client attempts to connect to
  the server.</p>
 
+ <p>During this event, it's possible to use the <a href="../../network/channel/raw/RawDataChannel.html" title="interface in org.spongepowered.api.network.channel.raw"><code>RawDataChannel</code></a>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 <a href="ServerSideConnectionEvent.Auth.html" title="interface in org.spongepowered.api.event.network"><code>ServerSideConnectionEvent.Auth</code></a> event.</p>
+
  <p>After observing this event for particular <a href="../../network/ServerSideConnection.html" title="interface in org.spongepowered.api.network"><code>connection</code></a>
  you are guaranteed to get #Disconnect for the same connection without
  ordering issues.</p></div>