Pale Garden blocks acting abnormal
A paper 1.21.4 server with Geyser. Pale Garden blocks doesnt recognize tools, breaking a log with a diamond axe is the same speed as breaking with your hand. On the bedrock side everything is fine, seemingly. Only affects java users.
The world was originally made on 1.21.3 and then updated to 1.21.4, which I guess is where the issue has occurred. Everything generates fine, its just the block breaking not working.
So, what is my options? I deleted all worlds on a testing branch with same plugins etc, no issues in the fresh world.. however is that my only option? I’d like to not fully reset my world.
Solution:Jump to solution
Yup, literally just as you dm'd me I found this myself, seemingly Nexo makes a datapack for custom blocks inspite of you using them or not. This datapack doesnt auto-update if you upgrade to a newer version. Upon trying the world on different versions I didnt think to delete the datapacks as I dont use any, personally.
12 Replies
you are definitly using just paper right? and not purpur
Yeah just normal paper
what version of paper are you on
/version187, I have had pufferfish on the server previously IIRC, could that be causing any issues? I figured it wouldn’t but now that you mention purpur 🤷🏻♂️ Its a very long time ago and pre-upgrade. I tried using latest paper build on the test branch before deleting world, didnt do anything
i dont believe that paper would read anything that pufferfish added to the world file, so i dont believe it would effect it at all. i was just asking about purpur cus there has been a few issues such as it not auto creating certain parts of their configs when updating causing issues like being unable to strip pale logs
since 207 is latest build its always worth updating to see if it was an issue thats been fixed in a newer version
tho the fact that it doesnt happen on fresh worlds or that its just java players and not bedrock players makes it very strange to be occuring
Yeah, I just learned about the issue before heading into work and only had time to try on the testing branch. But yeah.. very weird
ive had a gander at the papermc discord and seems like that block break speed is now an actual attribute that tools can have which is nice but also might be the potential cause, does this occur with a freshly made diamond axe? same with freshly placed pale logs?
idk when they made it an attribute but with mojang making alot of their stuff data driven wouldnt suprise me if its 1.21.4 feature or smth
Yeah we updated the world a month or so ago, only went live a few days ago so anything in the world is post update, at least concering items.
- if a backup of the world is loaded on a vanilla server, does it have the same behavior?
- do new axes still exhibit the same behavior?
- If you delete the chunk (using a tool like mcaselector) containing trees, do new trees mine normally?
additionally, would you be able to send an affected region file plus your level.dat?
I’ll get back to you when im off work, appreciate the help
Same behavior, tried without plugins, newest Paper version, tried vanilla server. All same.
All the axes will be newly crafted as upgrade was done before server going live.
Still same behavior.
in your level.dat file, it shows it's still trying to load the datapacks that nexo generates. It's possible they could be causing it?
Solution
Yup, literally just as you dm'd me I found this myself, seemingly Nexo makes a datapack for custom blocks inspite of you using them or not. This datapack doesnt auto-update if you upgrade to a newer version. Upon trying the world on different versions I didnt think to delete the datapacks as I dont use any, personally.