Hey Jason (and/or BloodAsp), I found a bug:
While investigating the strange lack of nether quartz and sulfur in the Nether, I tried a couple of things, including changing weights, verifying heights, etc. However, I have now found the problem:
The Nether is generating ores based on the overworld enable flag, not the nether flag.
That is, flipping "B:Overworld=false" to "B:Overworld=true" on the netherquartz vein config made it start generating in the nether. Apparently the nether oregen is ignoring B:Nether_[true/false] and going based on the overworld ores instead.
I'm using version 3.2.9.
This isn't THAT much of a big deal for the nether, but I'm concerned that when we get to the Moon/Mars/Asteroids that their oregen is going to be borked as well.
While investigating the strange lack of nether quartz and sulfur in the Nether, I tried a couple of things, including changing weights, verifying heights, etc. However, I have now found the problem:
The Nether is generating ores based on the overworld enable flag, not the nether flag.
That is, flipping "B:Overworld=false" to "B:Overworld=true" on the netherquartz vein config made it start generating in the nether. Apparently the nether oregen is ignoring B:Nether_[true/false] and going based on the overworld ores instead.
I'm using version 3.2.9.
This isn't THAT much of a big deal for the nether, but I'm concerned that when we get to the Moon/Mars/Asteroids that their oregen is going to be borked as well.