Wurst-Imperium
autofarm bugs on chest and shulker boxes
Pre-reporting checklist
- [X] I have searched existing issues and didn't find any previous reports of this bug.
- [X] This bug still happens in the latest version of Wurst. I've made sure my installation is up to date.
- [ ] I have tried removing all other mods and the bug still happens.
Description
when i enable autofarm it runs close to chest or shulker box, Suddenly chest/shulker box opens (with no intention of opening) and cannot be closed
Repro steps
- Enable Autofarm
- walk closer to chest/shulker box
- suddenly chest/shulker box opens
- cannot be closed, unless reopening the game
Wurst Client version
7.46
Minecraft version
1.21
Crash report (if applicable)
No response
Yeah, this is a somewhat known issue that affects many different hacks in Wurst. The problem is that there's no reliable way to detect if a block is "interactive" (meaning if right-clicking it does something like opening a chest or shulker box) without actually just right-cliking that block and seeing what happens.
I say it's "somewhat known" because I'm not sure why AutoFarm would try to right-click on anything other than plants and farmland in the first place. Maybe its aim is slightly off with some specific crop or growth stage?
Implementing #1075 should somewhat mitigate the issue, as then we'll have at least a basic filter for chests and shulker boxes in every hack that right-clicks on stuff. But if it is an aim issue with AutoFarm, where it's trying to click on a crop but ends up pointing at the chest instead, then this would probably still happen even with that fix.
Let me know if you figure out a specific farm setup that can reproduce the bug.
Wurst for Minecraft 1.21.3 doesn't start for me, all previous versions work really, and the new one, when I start it, it shows me the message the game has crashed, an unexpected problem has occurred. We apologize for the inconvenience. Exit code 1.
@HackerXGF Please don't hijack someone else's issue or complain about crashes without including the necessary troubleshooting data from your crash report file. This kind of behavior is rude and will not fix whatever issue you're encountering.
I wouldn't be writing this post if it was clearly written where to create a New Issue.
Hey @HackerXGF. There seems to be a misunderstanding here. I am not the CEO of GitHub who gets to decide where the "New Issue" button goes. Whatever gripes you have with GitHub's UI, feel free to tell them in the community discussions, but please leave me out of it as I can't do anything about that.