-
Notifications
You must be signed in to change notification settings - Fork 33
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
Log Spam on Paper server: A structure is trying to spawn without the plugin initialization step being completed. #157
Comments
This is a tricky issue since the plugin needs to have some of its initialization process after all the plugins load. Unfortunately, there is no API for me to determine this, so I have to use a somewhat hacky method (although it works well on Bukkit/Spigot). Does the plugin ever initialize or does it stay uninitialized even after the server finishes loading?
I've never been able to reproduce this issue with an installation of paper before. |
Attaching two complete logs (together they cover a 24 hour period), please treat with care as they naturally include some player chat and whispers. <3 [Removed] Didn't see any instance of "The plugin has been fully enabled" when I searched. This might be relevant? Likely cause: I had the plugin disabled for many months due to performance issues. I have re-enabled it in hopes they have been since fixed, or other perf improvements on my server have given us enough headroom to absorb the burden. [09:05:58] [Server thread/INFO]: ===============[CUSTOM STRUCTURES UPDATE]=============== |
To fix that just delete the |
This issue occures on Purpur (... Spigot -> Paper -> Pufferfish -> Purpur) build 1894 (1.19.3) |
Just confirming deleting the backup folder fixed this issue, at least for my case. |
Problem is not solved. I have this problem in
But after it says
|
Describe the bug
Hey I'm running a very recent official paper 1.19.3 build. This is absolutely spamming my logs, had to uninstall the plugin for now.
A structure is trying to spawn without the plugin initialization step being completed.
If you are using a fork of Spigot, this likely means that the fork does not adhere to the API standard properly.
May I humbly suggest rather than:
if(not initialized) error message
prefer:
if(not initialized) initialize
Not being a smartass. Possibly a reliable design workaround in case the boot sequence varies a little across forks or in the future of Spigot. <3 Love this plugin, my players are super excited about the possibility of our server having it (again, after some time away).
The text was updated successfully, but these errors were encountered: