-
Notifications
You must be signed in to change notification settings - Fork 539
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
An Exception was caught while ticking the Block Tickers Task #3696
Comments
My server is facing this same error however we have no reports of any Slimefun blocks being reverted back to vanilla blocks. We have had reports (that suddenly started in the past few days) of some storage reverting stored item values but I don't believe that is related. Below is a pastebin of the errors spamming my console (it happens about 10 to 20 times per minute.. just check the timings of the few errors provided). There are no errors within /slimefun/error-reports. Output of /sf versions and /sf timings --verbose can be found here: https://pastebin.com/KGG0s2D9 |
this may be tied to block storage. Without specific steps to duplicate it, it's not something easily fixed. |
❗ Checklist
📍 Description
Hello, there's a bug on our server that probably affects Slimefun in general, that's why I'm posting it here and not in some special room. The bug is that SF electricity generators are changing to vanilla items, but all items can change this way based on the code from the error I'm posting below.
Please fix this as soon as possible, this is a very serious bug as players may start to abuse it and ask us to replace a vanilla block with an op generator, but the block was never a generator.
📑 Reproduction Steps
We don't know, it happens randomly.
💡 Expected Behavior
Bug fix.
📷 Screenshots / Videos
No response
📜 Server Log
https://pastebin.com/wbGr8thN
📂
/error-reports/
folderNo response
💻 Server Software
Purpur
🎮 Minecraft Version
1.19.x
⭐ Slimefun version
Slimefun vDEV - 1034 (git 7b9d769)
🧭 Other plugins
No response
The text was updated successfully, but these errors were encountered: