Baritone stands still and does nothing when using #mine command
ThatBenderGuy opened this issue ยท 22 comments
Some information
Operating system: Windows 10
Java version: 1.8.0
Minecraft version: 1.16.3
Baritone version: 1.6.1
Forge mods (if used): https://www.modpackindex.com/modpack/21762/technical-electrical-vi
Exception, error or logs
How to reproduce
Type in #mine <any_ore> and the bot finds ore and a path to them but just stands there doing nothing
Modified settings
None
Final checklist
- I know how to properly use check boxes
- I have included the version of Minecraft I'm running, baritone's version and forge mods (if used).
- I have included logs, exceptions and / or steps to reproduce the issue.
- I have not used any OwO's or UwU's in this issue.
I am having the same issue except im using #sel cleararea and it mines for a bit but then quits moving or just goes to a unnecessary location. Im using Fabritone 1.6.1
I am having the same issue except im using #sel cleararea and it mines for a bit but then quits moving or just goes to a unnecessary location. Im using Fabritone 1.6.1
Also having this issue using Baritone 1.6.2 (forge ver), "#sel ca" mines everything within reach and then stops.
I am having the same issue on Baritone 1.6.2 on Minecraft 1.16.4. Exact same issue as @qwertaii.
Edit: It seems to be an issue with working around lava. It can be mostly fixed by using "sel set air" rather than "sel ca" but will stop in place if it gets too close to lava.
Edit 2: I'm just an idiot, it has nothing to do with lava, but the behavior is fixed temporarily by placing a water bucket at the bot's feet.
Fabritone is deprecated iirc, use Baritone
What if I want to have Some fabric mods?
Ok for me the reason that it didn't work was that I had Sodium I took it out and it works now :D
I am having the same issue except im using #sel cleararea and it mines for a bit but then quits moving or just goes to a unnecessary location. Im using Fabritone 1.6.1
Also having this issue using Baritone 1.6.2 (forge ver), "#sel ca" mines everything within reach and then stops.
If I bump into the bot or move the bot myself they start mining again. I've st the blockReachDistance between 2 and 5. Not sure why it's stopping. I only have Forge and Baritone installed. No other mods.
You would have to build baritone yourself, I have misremembered there isn't a pr, but you would have to use #2323 and run buildValidSubstitutes air->cave_air.
There are instructions on how to do this and build for yourself in this issue or follow the build it yourself instructions here : https://github.com/cabaletta/baritone/blob/master/SETUP.md
This is a known issue to-do with cave air, there is currently a pr that fixes it.
This is a known issue to-do with cave air, there is currently a pr that fixes it.
I'm sorry, a pr? And I'm running Impact generally, would there be a way to incorporate what you speak of into it?
You would have to build baritone yourself, I have misremembered there isn't a pr, but you would have to use #2323 and run buildValidSubstitutes air->cave_air.
There are instructions on how to do this and build for yourself in this issue or follow the build it yourself instructions here : https://github.com/cabaletta/baritone/blob/master/SETUP.md
I'm having some trouble figuring that out but thanks anyhow
#2323 is the issue that is discusing how to fix something that would also fix this issue.
if you wouldnt mind, could i have a step by step on what im doing to make a build that fixes the issue?
you can find a step by step here
you can find a step by step here
maybe im just too stupid because I'm having a lot of trouble following what to do. I'm on windows.
You would have to build baritone yourself, I have misremembered there isn't a pr, but you would have to use #2323 and run buildValidSubstitutes air->cave_air.
There are instructions on how to do this and build for yourself in this issue or follow the build it yourself instructions here : https://github.com/cabaletta/baritone/blob/master/SETUP.md
okay so I'm not really understanding how to do this, and what does #2323 have to do with it?
#2323 is the issue that is discusing how to fix something that would also fix this issue.
i take it i won't be able to do that then, bc im really unsure of how. when do you think itll get patched?
