Skip to content
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

WorldGuard can't load region data in fresh slime worlds #151

Open
RoloRotMG opened this issue Sep 12, 2022 · 5 comments
Open

WorldGuard can't load region data in fresh slime worlds #151

RoloRotMG opened this issue Sep 12, 2022 · 5 comments

Comments

@RoloRotMG
Copy link

Describe the issue
WorldGuard fails to load region data with newly made swm worlds
Spigot version
1.19.2
Plugin version
2.10.0
How to reproduce
Have WorldGuard installed. Create a slime world in game and then go to it. Anytime you click an interactable block such as a barrel this message comes up
image

This definitely used to work fine. I consulted the EngineHub discord (support for WorldGuard and they said "Sounds like that plugin has broken the Bukkit world lifecycle" in response to me using SWM, not sure who needs to do what here

@CommandDan
Copy link

Please provide a Pastebin of stack trace from server logs

@RoloRotMG
Copy link
Author

RoloRotMG commented Sep 12, 2022 via email

@novastosha
Copy link

Any logs from WorldGuard?

@AoElite
Copy link

AoElite commented Nov 15, 2022

I'd be careful with worldguard. It has memory leaks when loading/unloading tons of worlds. I put it on some servers accidentally a few months ago and all of them ran out of memory. Confirmed it by analyzing a heapdump with memory eclipse analyzer and simply removing the plugin. It was months ago so they could have fixed it.

@DuneSciFye
Copy link

I've also had this issue multiple times. No errors in console, never any, just this message and I can't interact. The first time it was due to my luckperms config option of disabling ops set to true, set that to false and it was fixed, then it was my luckperms config option of requiring a specific permission to edit other users permissions, set that to false and it was fixed. My current issue is now if I'm not opped, that message will pop up, if I am opped, then it works fine.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

5 participants