-
-
Notifications
You must be signed in to change notification settings - Fork 140
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
This changes the loading to not be on STARTUP #2214
Conversation
Worlds are then created in onEnable and not one-tick later.
This needs more testing to see if this causes any issues. There was a reason why we used to load at STARTUP, but maybe it's not needed anymore? |
e.printStackTrace(); | ||
} | ||
}); | ||
//Bukkit.getScheduler().runTask(instance, () -> { |
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.
Just commented out for now.
STARTUP was requested for single-world on-server setups. |
Also, as it is not delayed anymore, will it still properly register Placeholders to PAPI? |
I’ll test PAPI. I don’t understand the first comment though. Can you explain more please? |
In server.properties world is set to bskyblock_world |
Kudos, SonarCloud Quality Gate passed! 0 Bugs No Coverage information |
@BONNe I tried this and it all seems to work okay. What was the particular issue with this setup? |
No, I did not have any issues. |
Okay let's try it and see if anyone has a problem. |
This reverts commit 4a6bf31.
Worlds are then created in onEnable and not one-tick later. This provides compatibility with Residence plugin. See #2213