cabaletta / cabaletta/baritone
Change Cost Metrics for Pillaring, building adjacent and building down: consider build order options
- Dominant language
- Java
- Stars
- 9.2k
- Forks
- 2.1k
- Avg merge
- 4d 3h
- Merged PRs (30d)
- 3
Description
## Some information
Operating system: Linux
Java version: 8
Minecraft version: 1.12
Baritone version: Latest in KAMI/Blue
Forge mods (if used):
## Exception, error or logs
This is to correct non-minecraft behaviour. Baritone seems to love pillaring above all other means to lay blocks. When there is the option to sneak-extend, it will sometimes jump down into a hole and pillar up from the bottom. Same problem in trying to lay blocks near the netherroof -- it will pillar up into the roof. Then if the schematic advances, it will break down some of the pillar to get to the next location. The cost metrics for each different way of getting a block where it needs to be need to be overhauled, and perhaps the target build order for blocks. Perhaps the problem is, baritone orders the order in which it is trying to build from the bottom up only. When it wants to build a block adjacent to a current block, instead of sneak-extending, it thinks, I have to build upward and pillar a lot of blocks that do not need to be laid. Similarly, when working near the nether roof, it should consider building the highest blocks first and building down from the roof.
The specific problem is y=123 is the nether roof. If one wants to build a vertical column at y=118,119,120,121,122, baritone will always try to build the 118 block first. then the 119, then it will jump up on top of the 119 block and pillar the 120, 121, and 122 blocks, digging blocks out from between bedrock in the ceiling to do that. If it cannot get down without breaking more blocks at 123 and above, it will break the blocks it has just laid. Baritone should consider the build order: 118, 119, 120, 122, 121. Or 118,119, 122,121, 120.
It should get out of the habit of trying to pillar.
Contributor guide
No contributing guide indexed for this repository
Assessment
This issue has not been assessed yet.