KevinDaGame / VoxelSniper-Reimagined

The premier long-distance brush editor for Minecraft, reimagined!
GNU Lesser General Public License v2.1
63 stars 6 forks source link

[FEATURE] Add block lists to the config #116

Open KevinDaGame opened 1 year ago

KevinDaGame commented 1 year ago

Also, since we are on topic on brushes, anyway to make a "config" of "Natural" blocks to add and remove so you don't have to add a full list, on what to avoid. this is for /b eraser https://www.spigotmc.org/threads/voxelsniper.571866/#post-4532766

instantout commented 1 year ago

Also, since we are on topic on brushes, anyway to make a "config" of "Natural" blocks to add and remove so you don't have to add a full list, on what to avoid. this is for https://www.spigotmc.org/threads/voxelsniper.571866/#post-4532766

So, to add upon this A "Natural" block comes to in My Mind, any block that is already Pre-Generated to the world but is Common enough that once you build something you might end up working on top of it. Since version 1.19 came out we have Deepslate etc, and the Erase command, so you can remove buildings/trees or any item without it taking over your grass_blocks. anyways there is 3 Categories of "Natural" Blocks. The End The Nether The Overworld And if we want this to work without any future problems, lets not forget how you can use datapacks to make custom Generation Worlds. I also noticed a limitation how under Y axis of 0 it did not recognize the block. Saying the Block was too far away. Anyways, Thank you for the Reading to the bottom. These are 1.19.3 Name Related (idk IDs) been a while Overworld:

grass_block
stone
dirt
granite
diorite
andesite
podzol
mycelium
dirt_path
coarse_dirt
rooted_dirt
farmland
mud
clay
gravel
sand
sandstone
red_sand
red_sandstone
snow_block
powder_snow
moss_block
deepslate
calcite
tuff
dripstone_block
bone_block
prismarine
bedrock
#All_Ores
coal_ore
iron_ore
copper_ore
gold_ore
redstone_ore
emerald_ore
lapis_ore
diamond_ore
deepslate_coal_ore
deepslate_iron_ore
deepslate_copper_ore
deepslate_gold_ore
deepslate_redstone_ore
deepslate_emerald_ore
deepslate_lapis_ore
deepslate_diamond_ore

Small example I can do "The Nether" and "The End" the concept is for the command to be used as. /b erase <custom #> or can be used another way to Avoid and to erase natural blocks, because there is been times I needed just natural blocks removed. I've Created Maps and there is times when I needed to be be like "I don't need this house" or this thing here and removed it. other times it has helped me when there is a Grief, and I come back. Another time is when I made a mistake and need to replace the whole building to figure out the situation. I know you just asked for a List but I had to say something after all these years working with Voxelsniper and getting some things in my Mind. and the other reason, is because when you delete Buildings you want to keep the "Natural" look of the terrain without coming back and fix it over and over again. I was going to add "Obsidian" but when water flows over lava it turns into that, so would be easier not to add it to avoid that mess of having to come back and remove the obsidian by hand.

KevinDaGame commented 1 year ago

@instantout

I also noticed a limitation how under Y axis of 0 it did not recognize the block. Saying the Block was too far away.

Am I correct in concluding this is a seperate issue? What VoxelSniper version are you using?

KevinDaGame commented 1 year ago

Okay, after reading this a few times (it's a lot of text), I believe what you want is multiple lists of blocks for multiple use cases of the erasebrush, am I correct? By default a list for the overworld, nether, end and maybe more

And then an option to create a custom list yourself?

instantout commented 1 year ago

Okay, after reading this a few times (it's a lot of text), I believe what you want is multiple lists of blocks for multiple use cases of the erasebrush, am I correct? By default a list for the overworld, nether, end and maybe more

And then an option to create a custom list yourself?

Thanks for reading lol, Yes to the question, if possible.

@instantout

I also noticed a limitation how under Y axis of 0 it did not recognize the block. Saying the Block was too far away.

Am I correct in concluding this is a seperate issue? What VoxelSniper version are you using?

I updated, and double checked. all good now.

KevinDaGame commented 1 year ago

Alright, thanks for clarifying. I will add it to our todo list, but I can't promise when or if it will be done. If you'd like updates on this and other things I recommend that you join our discord