cabaletta / baritone

google maps for block game
GNU Lesser General Public License v3.0
7.16k stars 1.43k forks source link

Shaking cursor while mining #4313

Open FurkanS1821 opened 6 months ago

FurkanS1821 commented 6 months ago

Some information

Operating system: Windows 10 Home Single Language Java version: java 21.0.2 2024-01-16 LTS Minecraft version: 1.20.4 Baritone version: fabric-1.10.2 Other mods (if used): Nothing else, only baritone

Exception, error or logs

There is no revelant error in logs, just:

[22:00:28] [Render thread/INFO]: [CHAT] [Baritone] > sel ca
[22:00:28] [Render thread/INFO]: [CHAT] [Baritone] Filling now
[22:03:45] [Render thread/INFO]: [CHAT] [Baritone] Done building

How to reproduce

  1. Select an area and clear it via #sel cleararea
  2. Observe.

My results:

  1. Cursor shaking, missing the target and restarting mining, barely able to mine its target
  2. Mod will not be able to choose a block to mine if two blocks are in about the same distance, alternating between them and not able to mine any of them.

Manually moving the character closer will slightly help but what's the point of using this then?

Video for clarity

Modified settings

allowDiagonalAscend = true
allowJumpAt256 = true
allowParkour = true
allowParkourPlace = true
allowVines = true
blockReachDistance = 4.0
breakFromAbove = true
freeLook = false
maxFallHeightBucket = 400
maxFallHeightNoWater = 10
minYLevelWhileMining = -64
verboseCommandExceptions = true

Final checklist

ZacSharp commented 6 months ago

The problem is randomLooking, or rather randomLooking113 since its default value is much higher.

ClassicGithub-er commented 6 months ago

I had the same problem thank you (I just changed randomLooking113 from 2 to 1 with #randomLooking113 1) Although, this only fixes the choosing between 2 blocks, sometimes it still has a hard time and the half-mining (where it repeatedly mines the same block without finishing) still occurs

figloalds commented 5 months ago

@Krayiken I had a bit of issue with this, the server I play is private and among friends, they don't mind if I auto the shit out of it so I set both randomlooking values to 0; In any case a moderator with Spectator mode can clearly see your character running looking upwards completely awkardly anyways, so random looking is only useful at all if the server you're playing has bot detection plugins.

As for the other thing i did to reduce this probem was to adjust #blockReachDistance from 4.5 to 2.5 and this value has been working nice for me for most part, I tweak it sometimes depending on what I'm doing, try fiddling with this variable see if it helps

baerchen201 commented 3 months ago

You can change randomLooking113 to 0, that fixes it