From 058014aa75f7ac1a2caf5b9aa6a495d512f9e2d7 Mon Sep 17 00:00:00 2001
From: Andrew Steinborn <git@steinborn.me>
Date: Thu, 23 Dec 2021 15:44:19 -0500
Subject: [PATCH] Better document how to use the login plugin message API

---
 .../velocitypowered/api/event/connection/PreLoginEvent.java | 6 ++++++
 1 file changed, 6 insertions(+)

diff --git a/api/src/main/java/com/velocitypowered/api/event/connection/PreLoginEvent.java b/api/src/main/java/com/velocitypowered/api/event/connection/PreLoginEvent.java
index 222b6790..13b48fc6 100644
--- a/api/src/main/java/com/velocitypowered/api/event/connection/PreLoginEvent.java
+++ b/api/src/main/java/com/velocitypowered/api/event/connection/PreLoginEvent.java
@@ -21,6 +21,12 @@ import org.checkerframework.checker.nullness.qual.Nullable;
  * (for offline mode). Velocity will wait for this event to finish firing before proceeding further
  * with the login process, but you should try to limit the work done in any event that fires during
  * the login process.
+ *
+ * <p>
+ *   As of Velocity 3.1.0, you may cast the {@link InboundConnection} to a
+ *   {@link com.velocitypowered.api.proxy.LoginPhaseConnection} to allow a
+ *   proxy plugin to send login plugin messages to the client.
+ * </p>
  */
 @AwaitingEvent
 public final class PreLoginEvent implements ResultedEvent<PreLoginEvent.PreLoginComponentResult> {