Paper
Paper copied to clipboard
Cactus can't be destroyed (Occasionally)
Expected behavior
Cactus can be destroyed by block
Observed/Actual behavior
Over time, Cactus can behave so bizarrely.
Steps/models to reproduce
as above
Plugin and Datapack List
no plugin
Paper version
This server is running Paper version git-Paper-260 (MC: 1.19.2) (Implementing API version 1.19.2-R0.1-SNAPSHOT) (Git: 2b47227) You are running the latest version Previous version: git-Paper-131 (MC: 1.19.2)
This server is running Paper version git-Paper-256 (MC: 1.19.2) (Implementing API version 1.19.2-R0.1-SNAPSHOT) (Git: e30b082)
This server is running Paper version git-Paper-253 (MC: 1.19.2) (Implementing API version 1.19.2-R0.1-SNAPSHOT) (Git: b3b04f2)
These are the versions I have tested. have this problem
Other
No response
I am having trouble replicating this. You state you have no plugins, which makes this rather interesting, however after running
for about 10 mins with a random tick speed of 999, I have yet to run into this problem.
Do you have any further replication steps ?
does the chunk unload in between? like do you leave the area and come back and then it looks like that? thats the only thing I can think of.
https://timings.aikar.co/dev/?id=416d04e5ff6f4a7ca911a826c06e3638
I've been staying near the cactus.
i deleted paper-global.yml, paper-world-defaults.yml, bukkit.yml, spigot.yml, server.properties and deleted world folder
the problem is always there
um.... Seems to be a problem with spigot spigot.yml cactus-modifier if not 100 there will be problems ex:50, 10, 10000
Sweet, yea I can replicate this issue :) I'll look into it.
same problem in the 1.20.2 :( until today it has not been corrected
Hello guys ! Having the same issue. I fix this by rollback spigot.yml cactus modifier to 100. This bug appear when i have my cactus modifier to 150