Support for Natura Legacy and its upcoming Dynamic Trees addon/fork.

[MagmaSlime123]

Title.

[ACGaming]

Also open for suggestions what we could do from our side to ease future support.

[jbredwards]

@MagmaSlime123 Can you share the specific issue you found? I haven't tested Natura Legacy yet, but when I do I want to make sure I actually look for the right thing :)

[ACGaming]

To answer from our side: Primarily making it configurable like other integration. Limiting Natura's world generation to the vanilla hell biome confused players and there's no simple way for toggling that. There might be more on modpacker's minds.

[MagmaSlime123]

Sorry for the late response, what ACGaming said mostly.

[MagmaSlime123]

Also open for suggestions what we could do from our side to ease future support.

Done, Elite-Modding-Team/NaturaLegacy#39.

[jbredwards]

@ACGaming

Limiting Natura's world generation to the vanilla hell biome confused players and there's no simple way for toggling that

That makes sense, I can add a toggle for that in the next update!

Also open for suggestions what we could do from our side to ease future support.

In that case, can you add a child mod container with a modid of "natura_legacy"? This would let me easily know when users are running the fork or not (without doing anything hacky, like checking for a specific class or smth). As someone who likes to maintain support for forks and the original, it's a small pet peeve of mine that most forks don't do that :P

Aside from that, I think the only other thing you could do would be to check the sections of code that Nether API transforms and try leaving those sections of code untouched if you can (or if you do change them, let me know which transformers need updating!)

[MagmaSlime123]

@ACGaming

Limiting Natura's world generation to the vanilla hell biome confused players and there's no simple way for toggling that

That makes sense, I can add a toggle for that in the next update!

Also open for suggestions what we could do from our side to ease future support.

In that case, can you add a child mod container with a modid of "natura_legacy"? This would let me easily know when users are running the fork or not (without doing anything hacky, like checking for a specific class or smth). As someone who likes to maintain support for forks and the original, it's a small pet peeve of mine that most forks don't do that :P

Aside from that, I think the only other thing you could do would be to check the sections of code that Nether API transforms and try leaving those sections of code untouched if you can (or if you do change them, let me know which transformers need updating!)

When do you plan on updating NetherAPI again btw? Been a while. (no rush, just asking)

[MagmaSlime123]

To answer from our side: Primarily making it configurable like other integration. Limiting Natura's world generation to the vanilla hell biome confused players and there's no simple way for toggling that. There might be more on modpacker's minds.

Mainly opened this since NetherAPI has issues with old Natura's Bloodwood trees atm too, NetherAPI would need to fix ths. #28