As was foretold, we've added advertisements to the forums! If you have questions, or if you encounter any bugs, please visit this thread: https://forums.penny-arcade.com/discussion/240191/forum-advertisement-faq-and-reports-thread/
Options
I need coding help (in Python?) - removing ores from a map in Minecraft
Ein
CaliforniaRegistered User regular
CaliforniaRegistered User regular
Okay, so - we have our map - roughly 5,500 x 5,500 - that we generated with Biome Terrain Mod. At the time, we were just kind've roughing out values for material deposits, but once we got the overall terrain the way we liked we started building. Unfortunately, we sort've neglected to ensure that the mineral deposits beneath the surface were present in anything approaching reasonable amounts. As a result, what we have now is an absolutely gorgeous, expansive, hand-tooled fantasy map with WAY TOO MUCH ORE.
I'm looking into solutions to fix this.
I was looking at maybe using MCEdit to remove the ores, and I was directed to a script called 'NearReplace' that basically shrinks the ore deposits down by doing some calculations based on what blocks are nearby.
I just changed the line
if level.blockAt(x,y,z)==fromb.ID:
to
if level.blockAt(x,y,z)==14 or 15 or 16 or 56 or 73 or 21:
... in order to thin out the frequency of Iron, Coal, Gold, Lapis, Diamond and Redstone ores. I set the percent chance to around 75%, but honestly anything over 50 usually knocks the blocks out due to how much stone is nearby anyway.
The problem is, though, that running that script in a 100 x 100 area takes about 5 minutes even on a reasonable computer when done inside MCEdit! Extrapolating this out, and assuming MCEdit wouldn't even crash first, I'm looking at something like 3 weeks of calculations to thin the resources on my map out properly, which is just not an option.
I was wondering if anyone might be able to help. I'm basically a moron when it comes to coding python - that one-line substitution was about the peak of my understanding - but I know it'll run notably faster if I do it via command line instead of within MCEdit. However, I don't know how to do stuff like that. Additionally, I have to imagine that the code I'm using from this NearReplace script is probably not as efficient as it could be.
Does anyone out there have experience with this kind of thing and can help out? I've found a couple other python scripts that do operations on minecraft maps but I have no idea how to run or modify these kinds of things.
I'm looking into solutions to fix this.
I was looking at maybe using MCEdit to remove the ores, and I was directed to a script called 'NearReplace' that basically shrinks the ore deposits down by doing some calculations based on what blocks are nearby.
I just changed the line
if level.blockAt(x,y,z)==fromb.ID:
to
if level.blockAt(x,y,z)==14 or 15 or 16 or 56 or 73 or 21:
... in order to thin out the frequency of Iron, Coal, Gold, Lapis, Diamond and Redstone ores. I set the percent chance to around 75%, but honestly anything over 50 usually knocks the blocks out due to how much stone is nearby anyway.
The problem is, though, that running that script in a 100 x 100 area takes about 5 minutes even on a reasonable computer when done inside MCEdit! Extrapolating this out, and assuming MCEdit wouldn't even crash first, I'm looking at something like 3 weeks of calculations to thin the resources on my map out properly, which is just not an option.
I was wondering if anyone might be able to help. I'm basically a moron when it comes to coding python - that one-line substitution was about the peak of my understanding - but I know it'll run notably faster if I do it via command line instead of within MCEdit. However, I don't know how to do stuff like that. Additionally, I have to imagine that the code I'm using from this NearReplace script is probably not as efficient as it could be.
Does anyone out there have experience with this kind of thing and can help out? I've found a couple other python scripts that do operations on minecraft maps but I have no idea how to run or modify these kinds of things.
Ein on
0
Posts
to
Right now I believe, based on quick tests with python and more experience in other languages, that right now that if is basically just always evaluating to true and running for every block rather than just the ones you want.
Well, that's the "simplest" change. It is not the most "correct" way of writing the code in that it's kind of a pain in the balls to read/look at.
Basically it is checking like this:
Try something like this:
Disclaimer: It's been a while since I've worked with Python and I don't have a compiler handy. That syntax might be wrong.