cabaletta / cabaletta/baritone
Remove mining inefficiency related to walking
- Dominant language
- Java
- Stars
- 9.2k
- Forks
- 2.1k
- Avg merge
- 4d 3h
- Merged PRs (30d)
- 3
Description
## Describe your suggestion
Mining with baritone is pretty dank, but one thing I noticed is that sometimes it is not efficient.
Imagine that you are digging into an thick wall, what baritone does, is dig two blocks enough to fit the player, then move into the space where the two blocks are mined and continue, thing is, you can save quite a bit of time if you didn't wait to move, you can cold W (move forwards) and mine at the same time, in baritone this would decrease the time needed to dig a tunnel, or anything in this case.
For example, let's imagine that mining a block takes 1 second, and walking to another block takes 0.5 seconds, you can mine the two blocks in 2 seconds, to dig a tunnel into a wall with a size of lets say, 8, in the axis that you're digging, it'll take 16 seconds to dig out all of the blocks required for a passage, with baritone though, it waits till both of the blocks are gone, then it moves and only continues mining once the movement has stopped, we can now say that the time added by this inefficiency is (7 * 0.5 =) 3.5 seconds (minus the first 2 blocks, of course).
I feel like I've made enough of a point here already, walk straight when mining, aka remove the mining delay that is caused by waiting till the player reaches the destination.
## Settings
---
## Context
Slightly reduces time it takes to mine out tunnels
## Final checklist
- [x] I have not used any OwO's or UwU's in this issue.
Contributor guide
No contributing guide indexed for this repository
Research direction
Start by tracing Baritone's mining and movement behavior, then reproduce the described tunnel scenario to observe where movement waits for mining to finish. Done means the player can move forward while mining when safe, reducing the unnecessary delay without changing the resulting passage.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java
- Domain
- game-dev
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 38/100