-
-
Notifications
You must be signed in to change notification settings - Fork 374
AutoHighway #1083
Comments
Schematic files for the build command. |
thanks |
This is a suggestion. The problem is, baritone schematics are prizmatic. Advancing a schematic one buildRepeat at a time, on a diagonal means the edge blocks from the road are only in the schematic for one lay of the schematic. Courier Font would make this If the server is lagging, and blocks are breaking and reappearing, baritone can believe it is finished with a schematic, advance the buildRepeat, and then in the last schematic, a block can re-appear. For blocks also in the second lay of the schematic, they will get cleaned up. The blocks in the columns furthest from the centerline of the highway -- the blocks next to the walls, are only in one lay of the schematic, so, are more likely to glitch back and not get caught, and be left as a defect in the digging. The main problem is, schematics are prizmatic, that is shaped like a box, not like a tetris piece. Instead of changing the shape of schematics, there is another solution that would allow Autohighway to continue using schematics. Introduce a new block type called "I do not care". Instead of trying to make a tetris piece shaped schematic, make the bounding box that would contain the tetris piece, and then all the parts of the box outside the tetris piece, make those blocks "I do not care". Instead of using a 4x4 schematic for PosPosDig, one uses a 6x6, but the parts that would lay outside the roadway, one uses "I do not care" blocks in that part of the schematic. All blocks one cares about would be in successive lays of the schematic, virtually ending blocks glitches. That is only one possible solution, some other solution similar to a diagonal schematic, or a check ahead and behind algorithm, if anything is ever found glitched back behind you, step back 2 steps and do the dig overlay again. There are many ways to end glitched blocks when digging diagonals. Glitched blocks are not such a problem on axis-aligned highways because a 4-block-long schematic will overlap by 3 blocks each time the schematic is advanced. The block would have to glitch back 3 full cycles later, instead of a fraction of one cycle for the last block mined on a diagonal schematic. |
This is a suggestion. The problem is, 5OO is right, people do pick up stuff and use it to grief. The accepted process to dispose of blocks is to burn them. It is a tedious job to go around and gather up all the floating stacks of netherrack because of the lag in the game picking them up while you are standing over them. Also, going to them some on the right, some on the left, leaves one wandering back and forth across the highway while gathering. Where digging using a bot took 5-player sessions, most AFK, burning netherrack for the same stretch of highway takes about 10 player-sessions, one one has to pick it up. It would be much better if the digging bot took care of burning the netherrack that was mined out, as it is mined out, when it is in your inventory and one has generally faster game-response to tossing it in a hole to burn. An auto-burn feature would use a bucket of lava over a flint and steel because a bucket of lava never wears out. |
This is a suggestion. |
This is a suggestion. |
This is a suggestion. |
This is a suggestion. |
This is a suggestion. |
This is a suggestion. |
This is a suggestion. |
Automatically sets up the baritone instructions to build a highway
Instructions to do it manually (example)
#s 1
and#s 2
>#buildrepeat
and set it to what ever direction you are going to (If X+ then 1,0,0)#buildrepeatcount -1
so it keeps building it until runs out of blocksThe text was updated successfully, but these errors were encountered: