Trying to run oregen on a map. I think I'm using the same command line I've used in the past but I'm getting an error.
c:\nbtoolkit>nbtoolkit oregen -w "C:\nbtoolkit\Terynas" -b 16 -v
Unhandled Exception: System.NullReferenceException: Object reference not set to an instance of an object.
at NBToolkit.Oregen.Run<>
at NBToolkit.Program.Main<String[] args>
I've tried the same command on a different map and it works fine. Does this mean the map is corrupted? Seems odd since I'm able to load the map in Minecraft with no issues.
Latest News Article
Snapshot 13w21a Ready For Testing!
It's time for another exciting Snapshot! The Mojang crew was hanging in Monaco last week, but rest assured, this week's Snapshot is nothing shy of sweet! Let's see what's on the menu:
FEATURES:
Added new UI for horses, to control...
Minecraft Ways to Die - a Parody Song
Continuing with our theme of parody songs, today's offering is an especially clever creation! Minecraft Ways to Die, an odd take on the song 50 Ways to Say Goodbye, is a labor of love from a whole lot of people! This hand-crafted, artisinal s...
Minecraft Monday Show - Let's Play Killers & Great Downloads!
This week, BebopVox covers the recent drama with "Let's Play" videos (including Mojang's stance on the matter), and much more!...
306 replies to this topic
#301
Posted 05 May 2013 - 03:31 PM
#302
Posted 05 May 2013 - 03:56 PM
It doesn't necessarily mean the map is corrupt, but there's something about it NBToolkit isn't expecting. Send me the map (if it's large, remove all but a couple regions -- test on the reduced map first to make sure it's still erroring), and I'll try and see why it's breaking.
#303
Posted 05 May 2013 - 07:17 PM
The map was an export from World Painter (worked fine in the past). I'm going to export again and see if it works before I bother you with it.
#304
Posted 17 May 2013 - 11:16 PM
I'm puzzled (as usual).
I was trying to add Copper / Silver / Tin Ores to an old map, but I hit the 255 ID limit. I thought I'd downloaded the latest version of NBToolkit, but checking on GitHub has "Convert.ToByte(v) % 256" as well.
How do I specify block ID's like Copper Ore (ID 925)?
And while I'm here, I'm guessing the -d sets the bit after the colon in what commonly gets written as 925:3 for example (Lead in theory).
Have I missed something stupidy obvious? :)
Thanks!
I was trying to add Copper / Silver / Tin Ores to an old map, but I hit the 255 ID limit. I thought I'd downloaded the latest version of NBToolkit, but checking on GitHub has "Convert.ToByte(v) % 256" as well.
How do I specify block ID's like Copper Ore (ID 925)?
And while I'm here, I'm guessing the -d sets the bit after the colon in what commonly gets written as 925:3 for example (Lead in theory).
Have I missed something stupidy obvious? :)
Thanks!
#305
Posted 18 May 2013 - 06:34 AM
It looks like I took the limits off of filtering / block replace, but forgot to do the same for ore generation.
I've pushed up a new version, give it a try.
And yes, -d specifies the data value, since colon has a different meaning in the options processor I'm using.
I've pushed up a new version, give it a try.
And yes, -d specifies the data value, since colon has a different meaning in the options processor I'm using.
#306
Posted 18 May 2013 - 03:26 PM
jaquadro, on 18 May 2013 - 06:34 AM, said:
I've pushed up a new version, give it a try.
[Tested ore gen, mined to ore's, dug out and correct drops appear]
#307
Posted 19 May 2013 - 07:04 AM
Just a note, I've updated the tool again to add a --dim option to specify the folder name of a dimension. Example: "DIM-1", "DIM1", "DIM_MYST4"
Now that I'm starting to play with mods, trying to make my tools a little more mod-friendly.
Now that I'm starting to play with mods, trying to make my tools a little more mod-friendly.








