Closed cheshyrp closed 3 years ago
all configured features within apotheosis are registered, the code responsible is here https://github.com/Shadows-of-Fire/Apotheosis/blob/1.16/src/main/java/shadows/apotheosis/deadly/DeadlyWorldGen.java#L24
There are literally dozens of error lines in the server log from Apotheosis alone, and all of them are due to unregistered features. I've been a software developer since 1981, so I understand what you're saying, but clearly something isn't working as intended. Shouldn't BOSS_DUNGEON, BOSS_DUNGEON_2 and TOME_TOWER be registered as structures? Perhaps this is why Blame reports it as an error? I've posted a report on Blame's issue page in case it's a false positive.
all configured features within apotheosis are registered, the code responsible is here https://github.com/Shadows-of-Fire/Apotheosis/blob/1.16/src/main/java/shadows/apotheosis/deadly/DeadlyWorldGen.java#L24
Actually, blame is right. If you breakpoint here: https://github.com/TelepathicGrunt/Apotheosis/blob/7c4b3788ab122aa06501de31535d6029aad8cee5/src/main/java/shadows/apotheosis/deadly/DeadlyWorldGen.java#L30
and look at what f.feature is, it is "minecraft:decorated". All of these ConfiguredFeatures were registered under that name which means all but one were registry replaced and now are unregistered. Which triggered the Blame report.
Remember, every placement you do on a configuredfeature, wraps that configuredfeature in a NEW one that runs the placement code. (only the outermost configuredfeature instance used for worldgen is the one that needs to be registered) For your Boss Dungeon, it actually waaaaay buried inside nested configuredfeatures like this:
My recommendation is to just register each configuredfeature field separately and with a resourcelocation you create yourself. Short, simple, and less likely to have an issue. Hope this helps!
According to Blame, a few features and structures were not configured, which can break other mods.