Config/Feature: Mod support priority selecting about bedrockores

[fnuecke]

b2975bf, 8967ce9

For the historical records, let it be said that you could look them up in their respective default JSON here, e.g. for Immersive Engineering you'd see it was set to 10.

But yeah, this was added early on when I didn't really anticipate there to be that many repeated ores :P I mean, I knew there were some, but... oh well. Anyway. Yes, as it stood this system would have required a lot of JSON config overrides to change the order (e.g. disable each of the entries that took precedence).

So, new system: in the config there's now a list of ore group priorities. In the new Immersive Engineering JSON you'll see it now reads "immersiveengineering" instead of 10. If a groupOrder is a string now, the index of that string in the orePriority config is looked up, and that index is multiplied by 5 to get the sort order. So to prefer Forestry ores over IC2 ores, for example, you'd just have to move the forestry string in the orePriority config list to above the ic2 one in your bedrockore.cfg.

Also added a config to disable all blocks from individual mods for convenience, oreModBlacklist. This is a list of mod IDs, for which no block will be spawned as an ore. So e.g. to disable Thermal Foundation ores, put thermalfoundation in it.

[BBoldt]

Fantastic! This is exactly what I was looking for. Thanks for your help.