You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I just tested HomeGUI 1.4 on 1.17 with EssentialsX 2.19.0-dev+191-555a62c and everything seems to work fine.
So this small pr just updates its dependencies and makes it "officially" 1.17 compatible.
I'm just not sure tho if the update to Java 16 makes it incompatible/broken with previous MC versions, and I'm not able to test this currently.
If this causes issues then tell me and ill revert it back to Java 8
Edit: There is 1 small issue
Because EssentialsX now saves a world's UUID instead of its name, HomeGUI displays "World:World UUID which makes no sense...
I messaged EssentialsX about a possible config option to let it save World Names as i dont know how this could be fixed in HomeGUI...
on 1.17.1 instead of the uuid of the world name. the usual name is missing.
It is possible to make some kind of substitute inside the plugin
where you specify the uuid and world name manually.
or, make a placeholder from the HomeGUI plugin for PAPI
then through other plugins it will be possible to name the worlds yourself.
For example via TAB PREMIUM Conditions
on 1.17.1 instead of the uuid of the world name. the usual name is missing. It is possible to make some kind of substitute inside the plugin where you specify the uuid and world name manually. or, make a placeholder from the HomeGUI plugin for PAPI then through other plugins it will be possible to name the worlds yourself. For example via TAB PREMIUM Conditions
You don't have to change the java version if you don't use 1.17 API / nms, so it's not necessary usefull. But i've fixed the world UUID because i've seen this issue on my server, so you can build my fork to have the changes.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
I just tested HomeGUI 1.4 on 1.17 with EssentialsX
2.19.0-dev+191-555a62cand everything seems to work fine.So this small pr just updates its dependencies and makes it "officially" 1.17 compatible.
I'm just not sure tho if the update to Java 16 makes it incompatible/broken with previous MC versions, and I'm not able to test this currently.
If this causes issues then tell me and ill revert it back to Java 8