I realize the ore vein creator has a huge dialog screen. I tried to reduce the size of it down as much as I could, but I have no control/don't know how to control the size of the text for the filters. I believe that is within the confines of the MCEdit code as all I do is say make a label or this type of input. If there are anything you want specifically cut out, I could do that. My gut instinct, however, says removing dirt, clay, and gravel is not necessarily going to be enough to prevent it from being too large. There's just a lot of inputs needed...
There are hot keys, however. The 1-9 keys select different tools going off the main bottom toolbar. If you can click somewhere that is not an input to take focus off a particular filter input and hit the 1 key, it should at least be able to close the filter.
The 0.71% vs 0.7% - that's also part of the MCEdit GUI code. While 0.70% looks more accurate, it is exactly the same as 0.7%. The extra 0 just signifies a bit more accuracy and is completely unnecessary unless you're being graded on significant digits. MCEdit removes the padded 0, and rightfully does so. It only displays the minimum amount of data necessary. I mean, it would be ridiculous if someone wanted exactly 1%, so they entered 1.000000000000%. The computer will treat 1%, 1.0%, or 1.0000% all the same (it already knows it should be a float).
brezeeg I love you! These should be added to MCedit by default! Maybe submit them over and see if they could come standard? :3
There is an issue with the Ore Vein Creator, the filter window spans much taller then my screen, so now I can't deselect it or another filter :sad.gif:
Also bug in the Simple Block Vein Creator
If I set the % to say #.#0 it would remove the last 0 and make it #.#
# = any number
So if I wanted it to be 0.70, I'd have to make it 0.71 otherwise it would set to just 0.7%
I had some silly bugs from this being in python and those <= vs < on the upper bounds of for loops. Don't want to edit outside the box!
Also updated the algorithm. When it starts to get too slow (it should start out fast and continually get slower), it changes algorithms to one that would start out slow and get faster. As a result, the calculations and updates are done fairly quickly, and you are updated within reason in the command box. If anyone finds any bugs, please let me know, but I'm fairly confident they are both bug-free and user-fool proof. There are also a fair amount of comments, so you might learn a thing or two studying it.
There are two different scripts available thus far.
VeinCreator.py and Ores.py.
VeinCreator is the vanilla version of Ores, being just one type of block being replaced with another at a certain percentage within the box and target cluster sizes.
Ores takes Vein Creator to a new level. You choose the block to replace, and then using preferred % and cluster sizes, fills in coal, gold, iron, diamond, redstone, lapis lazuli, clay, gravel, and dirt. Sorry about the large box, but the defaults are set to replace with nothing. There's more descriptions on my website.
I'm sorry Majataka that I don't have it quite to your specifications for a one clicker, but you should still be able to do everything/figure it out with these two tools. If you want individuals, have the vein minimum and maximum both be 1. For a natural distance, mine is completely random. You'd have to do some math and do the filter over multiple selection boxes. Same goes for the natural algorithm. I'd suggest doing it in multiple layers along Y, and that would not take too long as the code runs very quickly. The rows/%/vein sizes are displayed when setting inputs for both filters.
Enjoy!
darthvader45, I'll get to work on a dungeon filter. This one may take multiple days to pound out. That one may take awhile, though, and I have a LOT of classwork to catch up on from being sick!
Geethebluesky, if I can figure out how things work without selection boxes, I can probably do that one for you too relatively quickly. As far as coding tasks go, that is pretty simple. Just a giant search to look for portal blocks, sampling the block ID's around it, and replacing the obsidian and portal ID's. This sounds like a day project, but as I said earlier, I don't have many days to work. I probably won't be able to seriously code stuff until mid-December after my Phys 580 final.
Has anyone even started on a filter to make ore deposits? Im in real bad need of such, I am so sick of placing these blocks by hand in my custom maps.
I have ALMOST just finished one. I'm testing it right now, and it worked on a simple 2x2 block (as in 32x32 grid). It does all the main ores at the same time: Coal, Gold, Iron, Diamond, Redstone, Lapis Lazuli, Clay, Gravel, and Dirt. The clay, gravel, and dirt are included because those have a tendency to appear underground as well. I also added in code to make the clusters not all appear the same and have different orientations.
I'm also going to make a trimmed version of this one, which simply is a less "busy" dialogue box to fill out and only does only one left the the user's choice. The dialogue box will likely completely fill your screen...
You specify the percentage you want the particular block to replace (default stone). You specify the range of the cluster size.
To prevent it from doing a particular ore, keep the percentage at 0.
The minecraft default percentages and ore sizes are listed if the information was available.
I'll post the python scripts to my long outdated (~10 years... middle school?) website for download. I'll also post some pictures at some point.
Also, given the manner that I coded it, it should work extremely well with large selection boxes (provided most of it is the material to be replaced). It follows an expanding search algorithm from random points to place a cluster instead of calculating percentages on each box.
0
There are hot keys, however. The 1-9 keys select different tools going off the main bottom toolbar. If you can click somewhere that is not an input to take focus off a particular filter input and hit the 1 key, it should at least be able to close the filter.
The 0.71% vs 0.7% - that's also part of the MCEdit GUI code. While 0.70% looks more accurate, it is exactly the same as 0.7%. The extra 0 just signifies a bit more accuracy and is completely unnecessary unless you're being graded on significant digits. MCEdit removes the padded 0, and rightfully does so. It only displays the minimum amount of data necessary. I mean, it would be ridiculous if someone wanted exactly 1%, so they entered 1.000000000000%. The computer will treat 1%, 1.0%, or 1.0000% all the same (it already knows it should be a float).
6
http://www.brezeegerland.com/Minecraft/index.htm
I had some silly bugs from this being in python and those <= vs < on the upper bounds of for loops. Don't want to edit outside the box!
Also updated the algorithm. When it starts to get too slow (it should start out fast and continually get slower), it changes algorithms to one that would start out slow and get faster. As a result, the calculations and updates are done fairly quickly, and you are updated within reason in the command box. If anyone finds any bugs, please let me know, but I'm fairly confident they are both bug-free and user-fool proof. There are also a fair amount of comments, so you might learn a thing or two studying it.
There are two different scripts available thus far.
VeinCreator.py and Ores.py.
VeinCreator is the vanilla version of Ores, being just one type of block being replaced with another at a certain percentage within the box and target cluster sizes.
Ores takes Vein Creator to a new level. You choose the block to replace, and then using preferred % and cluster sizes, fills in coal, gold, iron, diamond, redstone, lapis lazuli, clay, gravel, and dirt. Sorry about the large box, but the defaults are set to replace with nothing. There's more descriptions on my website.
I'm sorry Majataka that I don't have it quite to your specifications for a one clicker, but you should still be able to do everything/figure it out with these two tools. If you want individuals, have the vein minimum and maximum both be 1. For a natural distance, mine is completely random. You'd have to do some math and do the filter over multiple selection boxes. Same goes for the natural algorithm. I'd suggest doing it in multiple layers along Y, and that would not take too long as the code runs very quickly. The rows/%/vein sizes are displayed when setting inputs for both filters.
Enjoy!
darthvader45, I'll get to work on a dungeon filter. This one may take multiple days to pound out. That one may take awhile, though, and I have a LOT of classwork to catch up on from being sick!
Geethebluesky, if I can figure out how things work without selection boxes, I can probably do that one for you too relatively quickly. As far as coding tasks go, that is pretty simple. Just a giant search to look for portal blocks, sampling the block ID's around it, and replacing the obsidian and portal ID's. This sounds like a day project, but as I said earlier, I don't have many days to work. I probably won't be able to seriously code stuff until mid-December after my Phys 580 final.
~Dan
3
I have ALMOST just finished one. I'm testing it right now, and it worked on a simple 2x2 block (as in 32x32 grid). It does all the main ores at the same time: Coal, Gold, Iron, Diamond, Redstone, Lapis Lazuli, Clay, Gravel, and Dirt. The clay, gravel, and dirt are included because those have a tendency to appear underground as well. I also added in code to make the clusters not all appear the same and have different orientations.
I'm also going to make a trimmed version of this one, which simply is a less "busy" dialogue box to fill out and only does only one left the the user's choice. The dialogue box will likely completely fill your screen...
You specify the percentage you want the particular block to replace (default stone). You specify the range of the cluster size.
To prevent it from doing a particular ore, keep the percentage at 0.
The minecraft default percentages and ore sizes are listed if the information was available.
I'll post the python scripts to my long outdated (~10 years... middle school?) website for download. I'll also post some pictures at some point.
Also, given the manner that I coded it, it should work extremely well with large selection boxes (provided most of it is the material to be replaced). It follows an expanding search algorithm from random points to place a cluster instead of calculating percentages on each box.