Issue Description:

Minecraft will crash with the following error message.
Caused by: java.lang.NoSuchMethodError: net.minecraftforge.fml.common.registry.PersistentRegistryManager.createRegistry(Lnet/minecraft/util/ResourceLocation;Ljava/lang/Class;Lnet/minecraft/util/ResourceLocation;IIZLnet/minecraftforge/fml/common/registry/IForgeRegistry$AddCallback;Lnet/minecraftforge/fml/common/registry/IForgeRegistry$ClearCallback;Lnet/minecraftforge/fml/common/registry/IForgeRegistry$CreateCallback;Lnet/minecraftforge/fml/common/registry/IForgeRegistry$SubstitutionCallback;)Lnet/minecraftforge/fml/common/registry/FMLControlledNamespacedRegistry;
at thut.api.terrain.BiomeDatabase.(BiomeDatabase.java:22)

How to fix it:

Remove the last "null" parameter in the createRegistry(....) call (LexManos has restored the binary compatibility)
or
switch to using the provided RegistryBuilder to ensure more forward compatbility.

Affected Versions (Do not use "latest"):

• Thut Core: thutcore-1.10.2-4.0.0
• Thut's Elevators (If Applicable):
• Forge: forge-1.10.2-12.18.1.2011

This shouldn't occur anymore (I hope noone uses forge 2041-2045)

use either latest version of forge, or the previous version of ThutCore, forge broke compatiblity in 2041, I think in 2045 they might have fixed it, the 4.0.0 version of ThutCore was for 2041.

Thanks, I have already "downgraded" to thutcore-1.9.4-3.2.3. But for the future it's probably better to stick to older version of createRegistry(...) that works in releases both before and after 2041 (not just in 2041).

I will get around to re-uploading a version that has the older one, or maybe just hide the current "latest" and set 1.9.4-3.2.3 as "latest" again

I have set 1.9.4-3.2.3 as latest on curse again, hopefully should clear up the confusion now, and hopefully noone will try to use forge versions between 2041 and 2045 (the fix was in 2045), I will leave this issue open for a while though, incase of that happening.