Skip to content

Fix network handler order#6436

Merged
valaphee merged 1 commit into
GeyserMC:masterfrom
valaphee:fix-handler-order
Jun 1, 2026
Merged

Fix network handler order#6436
valaphee merged 1 commit into
GeyserMC:masterfrom
valaphee:fix-handler-order

Conversation

@valaphee
Copy link
Copy Markdown
Member

Moves the RakConnectionRequestHandler directly in front of the RakServerOfflineHandler, and this way after the proxy protocol handler and connection throttler.

Copilot AI review requested due to automatic review settings May 31, 2026 08:52
@valaphee valaphee changed the title Fix handler order Fix network handler order May 31, 2026
Copy link
Copy Markdown
Contributor

Copilot AI left a comment

Choose a reason for hiding this comment

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

Pull request overview

This PR adjusts the Netty pipeline ordering for RakNet-related handlers in GeyserServer so RakConnectionRequestHandler runs immediately before RakServerOfflineHandler, ensuring it executes after the proxy protocol handler and connection throttler.

Changes:

  • Insert RakConnectionRequestHandler using addBefore(RakServerOfflineHandler.NAME, ...) instead of addFirst(...) to enforce correct handler ordering.

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

Comment thread core/src/main/java/org/geysermc/geyser/network/netty/GeyserServer.java Outdated
@valaphee valaphee force-pushed the fix-handler-order branch from bbe3944 to c70a279 Compare June 1, 2026 08:08
@valaphee valaphee merged commit e40f4e8 into GeyserMC:master Jun 1, 2026
2 checks passed
@valaphee valaphee deleted the fix-handler-order branch June 1, 2026 08:27
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.

3 participants