Skip to content

Fix inverted PluginMessageEvent source/target in InitialConnectSessionHandler#1811

Merged
electronicboy merged 1 commit into
PaperMC:dev/3.0.0from
GoldenEdit:initial-connect-plugin-message-source
May 28, 2026
Merged

Fix inverted PluginMessageEvent source/target in InitialConnectSessionHandler#1811
electronicboy merged 1 commit into
PaperMC:dev/3.0.0from
GoldenEdit:initial-connect-plugin-message-source

Conversation

@GoldenEdit

Copy link
Copy Markdown
Contributor
  • Fix PluginMessageEvent in InitialConnectSessionHandler so client -> backend plugin messages use source = player and target = serverConn, matching ClientPlaySessionHandler and ClientConfigSessionHandler.
  • The handler previously used the backend -> client argument order from BackendPlaySessionHandler (introduced in Sending PluginMessage to player before he join a server #774), so client messages were exposed to plugins with ServerConnection as the source and Player as the target.

R00tB33rMan added a commit to GemstoneGG/Velocity-CTD that referenced this pull request May 28, 2026
…nHandler

See: PaperMC#1811 for more information.

Co-authored-by: GoldenEdit <45533337+GoldenEdit@users.noreply.github.com>

@WouterGritter WouterGritter left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Should be merged asap

@electronicboy electronicboy merged commit 3b142f3 into PaperMC:dev/3.0.0 May 28, 2026
1 check passed
robinbraemer added a commit to minekube/gate that referenced this pull request Jun 2, 2026
…ler (#693)

During the initial server connect, plugin messages received from the
client were fired with the source and target swapped (source=server,
target=player). The message actually flows client->server and is
forwarded to the backend, so the source must be the player and the
target the server connection, matching the play-phase handler.

Ports PaperMC/Velocity#1811.
DartCZ pushed a commit to DartCZ/Velocity that referenced this pull request Jun 4, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants