Open xAlicatt opened 7 years ago
Does Natural Pledge have a config parameter to disable their Tinkers Construct integration? If not, then it should because the reason for this compatibility both this mod and my mod, PlusTiC, add Tinkers Construct integration to Botania for the same materials; even if we registered the materials under different names, Tinker's Construct would not be able to decide which integration to use; thus, there needs to be this config in both mods so that the player can choose which integration to use. (I have already added config parameters to disable Botania integration while preserving other mod compatibility.)
I don't, but that can be done for the final 1.10 release (soon(tm))
@yrsegal Thanks!
You should probably be aware that NaturalPledge-r1.11.jar doesn't seem to have the config options. I just had the old "B:one_bonemeal=false" entry in my botanicaladdons.cfg, so I tried deleting that and letting it regenerate the config file, and now it's simply empty.
If there's some other config file that governs Natural Pledge, I can't find it.
@esotericist Neither PlusTiC nor Tinkers Construct use 1.11, so why are you using Natural Pledge 1.11 anyway?
EDIT: I thought that r1.11 meant Minecraft 1.11, but it turns out that this is not so.
@landmaster Yeah, I was referring to the final release of Natural Pledge for 1.10.2.
Weird. I'll probably end up fixing this soon.
Will you provide a fix or will the r1.11 not be supported anymore for MC 1.10.2?
MC: 1.10.2 Forge: 2297 Natural Pledge: 1.11 Botania: r1.9-341 Tinker: 1.10.2-2.6.5 plustic: 5.0.1.0
Pastebin: https://pastebin.com/XY1RR9b4
Summary:
// I just don't know what went wrong :(
Time: 6/4/17 12:00 PM Description: There was a severe problem during mod loading that has caused the game to fail
net.minecraftforge.fml.common.LoaderExceptionModCrash: Caught exception from Natural Pledge (botanicaladdons)
Caused by: java.lang.ExceptionInInitializerError
at shadowfox.botanicaladdons.common.integration.tinkers.TinkersIntegration.load(TinkersIntegration.kt:21)
at shadowfox.botanicaladdons.common.integration.tinkers.TinkersProxy$load$1.invoke(TinkersProxy.kt:27)
at shadowfox.botanicaladdons.common.integration.tinkers.TinkersProxy$load$1.invoke(TinkersProxy.kt:10)
at shadowfox.botanicaladdons.common.integration.tinkers.TinkersProxy.loadTinkers(TinkersProxy.kt:25)
at shadowfox.botanicaladdons.common.core.CommonProxy.init(CommonProxy.kt:51)
at shadowfox.botanicaladdons.client.core.ClientProxy.init(ClientProxy.kt:36)
at shadowfox.botanicaladdons.common.BotanicalAddons.init(BotanicalAddons.kt:50)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
at java.lang.reflect.Method.invoke(Unknown Source)
at net.minecraftforge.fml.common.FMLModContainer.handleModStateEvent(FMLModContainer.java:616)
at sun.reflect.GeneratedMethodAccessor2.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
at java.lang.reflect.Method.invoke(Unknown Source)
at com.google.common.eventbus.EventSubscriber.handleEvent(EventSubscriber.java:74)
at com.google.common.eventbus.SynchronizedEventSubscriber.handleEvent(SynchronizedEventSubscriber.java:47)
at com.google.common.eventbus.EventBus.dispatch(EventBus.java:322)
at com.google.common.eventbus.EventBus.dispatchQueuedEvents(EventBus.java:304)
at com.google.common.eventbus.EventBus.post(EventBus.java:275)
at net.minecraftforge.fml.common.LoadController.sendEventToModContainer(LoadController.java:243)
at net.minecraftforge.fml.common.LoadController.propogateStateMessage(LoadController.java:221)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
at java.lang.reflect.Method.invoke(Unknown Source)
at com.google.common.eventbus.EventSubscriber.handleEvent(EventSubscriber.java:74)
at com.google.common.eventbus.SynchronizedEventSubscriber.handleEvent(SynchronizedEventSubscriber.java:47)
at com.google.common.eventbus.EventBus.dispatch(EventBus.java:322)
at com.google.common.eventbus.EventBus.dispatchQueuedEvents(EventBus.java:304)
at com.google.common.eventbus.EventBus.post(EventBus.java:275)
at net.minecraftforge.fml.common.LoadController.distributeStateMessage(LoadController.java:145)
at net.minecraftforge.fml.common.Loader.initializeMods(Loader.java:805)
at net.minecraftforge.fml.client.FMLClientHandler.finishMinecraftLoading(FMLClientHandler.java:334)
at net.minecraft.client.Minecraft.func_71384_a(Minecraft.java:520)
at net.minecraft.client.Minecraft.func_99999_d(Minecraft.java:351)
at net.minecraft.client.main.Main.main(SourceFile:124)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
at java.lang.reflect.Method.invoke(Unknown Source)
at net.minecraft.launchwrapper.Launch.launch(Launch.java:135)
at net.minecraft.launchwrapper.Launch.main(Launch.java:28)
Caused by: slimeknights.tconstruct.library.TinkerAPIException: [TCon API] Could not register Material "manasteel": It was already registered by PlusTiC
at slimeknights.tconstruct.library.TinkerRegistry.error(TinkerRegistry.java:942)
at slimeknights.tconstruct.library.TinkerRegistry.addMaterial(TinkerRegistry.java:132)
at slimeknights.tconstruct.library.MaterialIntegration.integrate(MaterialIntegration.java:116)
at shadowfox.botanicaladdons.common.integration.tinkers.TinkersMaterials.
1.10 is no longer supported.
@Protheus Turn off the Botania module for PlusTiC to fix.
@yrsegal Due to the lamentable lack of a usable config in Natural Pledge 1.10.2 and this issue being stalled on Natural Pledge's side, starting in version 5.1.2.0, my mod PlusTiC will automatically resolve the material incompatibilities and prevent the crash by manually removing the colliding Natural Pledge materials and replacing them with the PlusTiC variants by default, with a config to toggle this.
This issue should thus be considered resolved.
Not sure if they should attempt to fix it, or you, so I'm sharing it on both mods.