Realistic Ore Veins

Realistic Ore Veins

310k Downloads

[Question] Issues getting veins to spawn in Mystcraft dimensions

TheDeviantCrafter opened this issue ยท 2 comments

commented

The pack I'm working on has Mystcraft installed. I'd like ore veins to spawn in any dimension with stone inside. Since Mystcraft ages can be created by the player, I can't specify a list of dimension IDs. This means using the dimension whitelist function doesn't work.

I've tried three things:

  1. Not including a dimension parameter. This doesn't work because, as mentioned in the documentation, it defaults to generating only in the overworld.

  2. Setting it to a blacklist, and blacklisting dimension -2 (which doesn't exist in my pack).

  3. Setting it to a blacklist, and blacklisting dimension 76, which does exist, and is a modded dimension with no stone.

In all three cases, veins generate flawlessly in the overworld but not in any Mystcraft ages.

Here's one section of my ore veins JSON file when I tried the third solution:

"massive_exotic_iron_nickel": {
    "ore": [{
            "block": "thermalfoundation:ore",
            "weight": 40,
			"meta": 5
        },
        {
            "block": "minecraft:iron_ore",
            "weight": 60
        }
 
    ],
    "stone": "minecraft:stone",
    "rarity": 100,
    "min_y": 5,
    "max_y": 55,
    "density": 15,
    "vertical_size": 30,
    "horizontal_size": 80,
	"dimensions": 76,
	"dimensions_is_whitelist": false
	
  },

Here are the two JSON files I'm using:

massive_ore_veins.json

normal_ore_veins.json

The ore_veins.json file is empty, just a pair of brackets.

latest.log file

commented

That worked, thank you. Certus quartz was failing because I Uninstalled AE2.

commented

Hmm. Both 2. and 3. should work. Looking at the log / json there seems to be a few problems:

  1. A lot of type specifications are using oreveins:cluster instead of just cluster
  2. small_common_certus_vein is failing to parse based on a block state
  3. the Dimensions parameter needs to be a list, even if there is only one dimension specified. Otherwise the parser for that vein will silently ignore the dimensions parameter. The correct json would be:
"massive_exotic_iron_nickel": {
    "ore": [{
            "block": "thermalfoundation:ore",
            "weight": 40,
			"meta": 5
        },
        {
            "block": "minecraft:iron_ore",
            "weight": 60
        }
 
    ],
    "stone": "minecraft:stone",
    "rarity": 100,
    "min_y": 5,
    "max_y": 55,
    "density": 15,
    "vertical_size": 30,
    "horizontal_size": 80,
	"dimensions": [
            76
        ],
	"dimensions_is_whitelist": false
	
  },