istvast.blogg.se

I can save the schematic, and use the schematic without the I-do-not-care-block set, and I see the oak planks being built - this allows me to see what is in schematic. So say I want sand to be my I-do-not-care block. There are so many blocks available in Minecraft that it is possible to choose any buildable block that does not appear in the intended build of the schematic. The author of the schematic might save the name of the schematic to signal to the user what to set the I-do-not-care block should be: When a designer intends a schematic to use an I-do-not-care block they must choose the block at design time, and communicate this choice to users of the schematic. Usage to clear the previous definition of the I-do-not-care block so Baritone returns to interpreting schematics literally. Usage to set the I-do-not-care block to be sand Usage to see what the I-do-not-care block is set to. When this block is found in the schematic, baritone should take no action, baritone should say, I do not care what is in the world, it is OK as it is, do not try to change the world at that point. I do not want that to be a fixed block like Air. I want to add a new concept, that a particular block in the schematic tells baritone not to change anything in the world. I want the opposite, I want to pre-process the blocks in the schematic, interpret the blocks in the schematic. They ignore blocks in the world that do not match what is in the schematic. BuildIgnoreBlocks and buildIgnoreExisting do the opposite of what I am suggesting.