AutoFarm Glitches
furkankoykiran opened this issue · 7 comments
Some information
Operating system: Windows
Java version: 1.8.0_51 (64 bit)
Minecraft version: 1.12.2 (1.20.1 & 1.16.5)
Baritone version: v.1.2.18
Modified settings
To get the modified settings run #modified
in game
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.
AutoFarm Glitches
-
In all other versions except version 1.12.2, the
AutoTool
feature does not pick up the hoe in the#farm
command. -
In version 1.12.2, if you make a farm completely filled with the
Farmland
block and use the#farm
command, it only sees a 16x16 field. Sometimes it encounters an unknown error and givesFarm failed
error. -
Verified with version 1.20.1 and 1.16.5.
• Check this video for Farm Failed
error.
@ZacSharp
i can confirm the issue, with 1.20.4
Just confirmed as mentioned above, yeah is very bugged, not farming and giving the message error "Farm failed" when there's crops and places to plant crops. (Edit: Version 1.20.4)
he is right @leijurv and thats urgent farming is hella broken rn
pathfinding is failing most of the times which causing farm failed
no matter the range that u set for farm its just farming in one chunk at max for no reason
Can confirm the issue. Farming seems bugged. I have crops and available planting spots, but I keep getting a "Farm failed" error message.
The problem is that a 16 by 16 area of farmland is already enough to satisfy the scanning limit of 256 returned positions.
Fixing this requires filtering out positions before applying the limit (or searching for ridiculous amounts of blocks).
As a workaround you can compile Baritone with a higher limit (replace the 256
passed to scanChunkRadius
in FarmProcess.java
). If someone does this I'd be interested in whether this has a noticeable performance impact.
The problem is that a 16 by 16 area of farmland is already enough to satisfy the scanning limit of 256 returned positions. Fixing this requires filtering out positions before applying the limit (or searching for ridiculous amounts of blocks). As a workaround you can compile Baritone with a higher limit (replace the
256
passed toscanChunkRadius
inFarmProcess.java
). If someone does this I'd be interested in whether this has a noticeable performance impact.
@ZacSharp
I mean what you are saying is correct, but i the issue is just not that
let me compile the list of issues
- while farming cocoa , when u die, the goal is still set to cocoa, and u cant again #farm,#resume,etc
- it is only farming stuff in single chunk, after that it stops farming saying farm failed
- very poor pathfinding, there is ton of cocoa to farm nearby, and within reach range(1-2 blocks)
but it changes farm floors(i do multilevel farms) only to break one-two cocoa on each floor alternatively
this is not local to cocoa farm, but same problems are with other crops too
since the cocoa update, total farm bot is broken
HOW TO REPLICATE:
make a 4 chunk (2x2) wheat farm, with 10 wheat crop in each chunk's center
so total of 40 crops, do not place crop near border of chunks
now start #farm, you will see ton of farm failed and pathfinding issues
Testing on my machine indicates that scanning is fast enough to cope with the amount of farmland, but processing the found positions in FarmProcess
turns Minecraft into a slideshow.
@ShauryaManiTripathi Your first point is not covered by this issue, so please create a new one. (can't reproduce though)