hello! im attempting to create a datapack that disables oregen by using the feature minecraft:no_op, but this for some reason always results in the datapack becoming invalid, as well as throwing a bunch of errors in the log
#need help with worldgen
dire badge
earnest roost
You could add a filter in pack.mcmeta that disables the two tags stone_ore_replaceables.json and deepslate_ore_replaceables.json.
That would completely disable ore generation.
I didn't test it, so idk if this just throws an error. If it does then just copy the two tags in your data pack and remove all block id's.
earnest roost
I checked now. This is how your pack.mcmeta should look like
dire badge
ah im using a dataloader to enable datapacks globally, theres no mcmeta
earnest roost
what do you use?
earnest roost
why are you loading the data packs like that?
dire badge
because...i want them enabled globally
im making a modpack
earnest roost
can't you use something like this https://www.curseforge.com/minecraft/mc-mods/drp-global-datapack ?
This mod does the same and you can use the filter.
If you're making a mod pack I would also suggest using a mod like Ore-Tweaker to disable ore generation. (ore-tweaker itself, has no 1.19.2 version)
dire badge
this is besides the point
i want to know why the vanilla minecraft feature minecraft:no_op is throwing errors
earnest roost
this is besides the point
i want to know why the vanilla minecraft feature `mine...
this feature is not from vanilla
so idk
dire badge
earnest roost
I think this is from the old worldgen. I can't find anything about this in newer versions.
dire badge
my datapack worked fine a while ago, and then it suddenly broke and began throwing errors
earnest roost
Then it might be an issue caused by one of the mods.
dire badge
No key placement in MapLike, No key feature in MapLike, Not a JSON object, what do these errors mean?
earnest roost
I have never seen the first two errors, but the third one says that there is a typo in the file that had this error or the code is not formatted right.
dire badge
"type": "minecraft:no_op",
"config": {}
}```
as far as i know this is a valid .jsoncan you send the whole datapack? With only parts of it, it is a bit difficult to fix it.
dire badge
this is literally it
namespace/worldgen/placed_feature/feature.json
and then everything the .json contains is
"type": "minecraft:no_op",
"config": {}
}```all minecraft:no_op does is tells whatever im trying to overwrite to basically just do nothing
earnest roost
now I know what the problem is. The file name is just feature.json but there is no original file with that name.
If you want to remove all the ore gen, then you have to replace every placed_feature file for ores with that one and name it exactly the same
dire badge
I was using a placeholder name
the file name matches whatever I wanna replace...
I was hoping that was clear from the log
earnest roost
put this in all the files instead. Instead of generating nothing it just generates ore veins with a size of 0 blocks.
{
"feature": {
"type": "minecraft:ore",
"config": {
"size": 0,
"discard_chance_on_air_exposure": 0,
"targets": []
}
},
"placement": [
{
"type": "minecraft:biome"
}
]
}
I don't usually do Worldgen stuff, so I don't know all the possible ways to do that, but this method works.
dire badge
tested it out, didnt change anything
ores are still generating