According to Blame, druidcraft has some unregistered ConfiguredFeatures
BugmanBugman opened this issue · 5 comments
Druidcraft-1.16.4-0.4.5.jar
Forge: 36.0.01
Not sure if this is related (and I see this is an old issue). I've been printing biome feature with KubeJS, like so:
startup_scripts/script.js:
onEvent("worldgen.remove", e => {
console.info("=====FEATURES======")
e.printFeatures()
})
With Druidcraft-1.16.5-0.4.52
, the druidcraft features seem to pop up under a minecraft namespace:
minecraft:forest_elder_tree
minecraft:blueberry_bush
minecraft:lavender
minecraft:plains_river_elder_tree
I'm fairly certain these are Druidcraft's features, as removing the lavender feature for instance then removes the druidcraft lavender from the biome:
e.removeFeatureById("vegetal_decoration", ["minecraft:lavender"])
Might be related to why blueberries aren't generating #109
It could possibly be because of mod Interference, I’ll check with all of my mods to see what’s causing it
Thanks, I've fixed this as of 29f55d0 -- I'll pester Vulpie to release soon.