-
Notifications
You must be signed in to change notification settings - Fork 3
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Incompatible with Sonar. #58
Comments
It seems that sonar is the one trying to close the connection at the very first of the pipeline, bypassing all raknetify handling. |
the developer from sonar states that,
I do not know if this is helpful information but it is a information |
They also said that when
happens they do not do anything with it |
I have checked their message, the log and their code, their plugin is definitely involved. |
I'll look into it when I'm back home. If necessary, I can open a PR here or at least provide as much information as I can. |
I've moved the handling of packet forwarding into Unsafe so it can handle requests even if the event is triggered at the head of the pipeline. There's two main differences between a raknetify connection and a vanilla connection:
|
Describe the bug
Plugin is incompatible with Sonar plugin
To Reproduce
Expected behavior
I expected sonar verification to work and then successfully join the server
Screenshots
if neccesary I will add them
Runtime info (please complete the following information):
Crash reports / logs
https://mclo.gs/CAUDjVT
Other mods
https://gist.github.com/Git-North/2a1d6170c7d6fe91e8c1c5f39b9e71e5
Checklist
Additional context
The text was updated successfully, but these errors were encountered: