Closed Petrisis closed 3 years ago
The auto updater to the new v2 data structure does not always work in all cases. In rare cases like this you have to delete the entire config/oretweaker
folder and restart the game. You can backup your old oretweaker.json
by moving the config/oretweaker/backup
folder outside the config/oretweaker
before deleting it.
The new v2 data structure will then generate properly and you can tweak the files again. Not to much to fix here cause the auto updater was made to help convert from the v1 data structure to the new v2 data structure. Hard to say why it breaks in this case and hard to replicate so doubt it will be fixed.
i'm sorry but i have to insist on this.. like i said in the original:
this even happens if OreTweaker's config files are completely deleted or reinstalled.
just tried it again:
i. modpack on old version: i delete oretweaker config folder
ii. update oretweaker
iii. launch modpack, generate world
and its stone + vinteum from Mana and Artifice + Quark Features
the generated files in data
look fine but they don't work!
example of iron_ore.json
which autogenerated:
{
"oreConfig": [
{
"ore": "minecraft:iron_ore",
"filler": "minecraft:stone",
"minY": 1,
"maxY": 64,
"maxVeinSize": 8,
"spawnRate": 20.0,
"biomeBlacklist": [],
"biomeWhitelist": []
}
]
}
Just tested it with your pack and found a way to fix it.
OreTweaker-1.16.5-2.3.1.jar
config/oretweaker
OreTweaker-1.16.5-2.5.1.jar
Works just fine.
Minecraft Version
Forge Version
Mod Version
Modpack & Version
Describe the bug
How to reproduce
Screenshots / Images