-
-
Notifications
You must be signed in to change notification settings - Fork 61
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
Add support for WaterdogPE xuid and IP #1356
Conversation
Please open a pull request for |
Sorry, didn't realize that languages were handled differently on power-nukkit vs cloudburst's nukkit. I've went ahead and just added the option to default-nukkit.yml instead. |
I think it would look cleaner if you rename Waterdog_IP and Waterdog_XUID to waterdogIP and waterdogXUID |
Hello, thanks for your Pull Request. Our team will make a small change to the isWaterdog function, where we will move it to the server class, so that we can expose it to the plugins. You don't have to worry about anything and we thank you for making this implementation! |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thank You!
This PR adds support for the
Waterdog_XUID
andWaterdog_IP
fields in the ClientChainData when settings.waterdogpe is true. The functionality is similar to how Spigot deals with Bungeecord.As there were changes to theShouldn't be needed for PowerNukkitlang
folder, commitf6f851b
would also need to be merged.This is the same PR as
CloudburstMC/Nukkit#1986
, just adapted to PowerNukkit.