Skip to content

Conversation

@Smart123s
Copy link
Contributor

Summary of your change

This was originally part of #709.
During the login start packet, the channel of the player is extracted from the ProtocolLIb handler, and if it contains a FloodgatePlayer attribute, we execute Floodgate's tasks manually, because ProtocolLib doesn't fire packets down the channel pipeline if it has an async listener attached to it.

Related issue

Fixes #786
Fixes #703
Fixes #689
Fixes #647

GitHub permalinks can easily get longer than 120 characters.
This reverts commit 94979a3
This reverts commit e82e7c7
This reverts commit b92911b
This reverts commit 03850ae
This reverts commit 8859ebb
Floodgate 2.0 has been released a long time ago.
@TuxCoding TuxCoding merged commit ed9e295 into TuxCoding:main Aug 10, 2022
@TuxCoding
Copy link
Owner

Sadly this solution is incompatible with ProtocoLib v4.8.0, which is necessary for below 1.18.

#878

@Smart123s
Copy link
Contributor Author

Hopefully, I will just have to change some package/class names. Anyways, I won't be home until Sunday/Monday, so I can't check it now. If it causes too much trouble, then just revert it, or disable it for 1.18 and below with an if.

@Smart123s
Copy link
Contributor Author

I took a look at it from mobile, and playerInjectionHandler is just playerInjection in plib 4.8.0.

https://github.com/dmulloy2/ProtocolLib/blob/41bb4bacb2fb0c5a6942188dfed872b7fd4bd904/src/main/java/com/comphenix/protocol/injector/PacketFilterManager.java#L109

code above that ran successfully, and playerInjectionHandler.getChannel() exists, so this could be an easy fix, although I still can't test it until I get home. You cna check it if the issue is urgent.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

2 participants