In Game Name: probablydeadShort title for your report: Harvesting Nwart from MinecartWhat client are you using: Vanilla 1.16.5Which server were you on: MainWhich world were you in: MainWhat time did the kick take place: 9:30 AM ESTCode received: 516Description of the issue: When harvesting nether wart from a minecart, I am kicked by anti-cheat after a few seconds. I repeated with l1 magic hoe and l3 magic hoe and without magic nwart. In the log file I get these lines: [09:35:17] [Render thread/ERROR]: Too many unacked block actions, dropping (a{x=14113, y=67, z=14950}, START_DESTROY_BLOCK) [09:35:17] [Render thread/ERROR]: Too many unacked block actions, dropping (a{x=14115, y=67, z=14951}, START_DESTROY_BLOCK) [09:35:17] [Render thread/ERROR]: Too many unacked block actions, dropping (a{x=14111, y=67, z=14951}, START_DESTROY_BLOCK) [09:35:17] [Render thread/ERROR]: Too many unacked block actions, dropping (a{x=14112, y=67, z=14950}, START_DESTROY_BLOCK) [09:35:18] [Render thread/ERROR]: Too many unacked block actions, dropping (a{x=14113, y=67, z=14951}, START_DESTROY_BLOCK) [09:35:18] [Render thread/ERROR]: Too many unacked block actions, dropping (a{x=14114, y=67, z=14953}, START_DESTROY_BLOCK) [09:35:18] [Render thread/ERROR]: Too many unacked block actions, dropping (a{x=14115, y=67, z=14953}, START_DESTROY_BLOCK)Reproduction instructions: With magic hoe try to use farm at 14136 / 63 / 14965 on main.How many times did you recreate this: More than a dozenVideo evidence:
While I haven't been kicked I have seen those errors in my chat logs. I believe it's from hitting a non fully grown wart. Or perhaps from hitting the soulsand with a soulsand break-deny on.
Thanks techy. I also see the errors in my chat log when harvesting without a minecart, maybe they're not relevant to this bug. For permissions, I have the default town permissions and have not added break-deny.
We've pushed a temporary fix for this which should prevent the issue until the bug is solved on the Anti-Cheat side. Please let us know if things are working fine for you now. @probablydead