1. Le forum de Minecraft-France va définitivement fermer ses portes. Celui-ci restera en lecture seule mais vous ne pourrez plus y apporter de nouveaux topics. Nous vous invitons à nous rejoindre sur le Discord de Minecraft-France qui permet de présenter vos projets, discuter avec la communauté etc.. Merci à tous d'avoir fait vivre ce forum de nombreuses années. Pour nous rejoindre sur Discord, Cliquez ici

Problème compatibilté Tinkers Construct et Necromancy Mod

Discussion dans 'Problème avec les mods' créé par jujucrow39, 30 Avr 2014.

  1. jujucrow39

    jujucrow39 Nouveau

    Inscrit:
    30 Avr 2014
    Messages:
    3
    Points:
    30
    Sexe:
    Homme
    Bonjour à Tous et à Toutes,
    Voilà j'ai actuellement un petit problème de compatibilité entre les mods Tinkers construct et Necromancy.
    Comme vous allez le voir plus bas, en rouge, il s'agirait d'un problème d'un problème concernant l'ID de Blood block qui serait associé dans les 2 mods à un liquide (Fluids, ici), comme l'eau ou la lave. Seulement ce liquide est essentiel dans les 2 cas et je voudrai savoir comment résoudre le problème : ) .
    D'avance merci, je vous met le Crash report en dessous,
    Jujucrow39.

    ---- Minecraft Crash Report ----
    // Sorry :(

    Time: 30/04/14 09:56
    Description: There was a severe problem during mod loading that has caused the game to fail

    cpw.mods.fml.common.LoaderException: java.lang.RuntimeException: A mod has attempted to assign BlockID tconstruct.blocks.BloodBlock@569e3b to the Fluid 'blood' but this Fluid has already been linked to BlockID com.sirolf2009.necromancy.block.BlockBlood@190893a. Configure your mods to prevent this from happening.
    at net.minecraftforge.fluids.Fluid.setBlock(Fluid.java:128)
    at net.minecraftforge.fluids.BlockFluidBase.<init>(BlockFluidBase.java:66)
    at net.minecraftforge.fluids.BlockFluidClassic.<init>(BlockFluidClassic.java:27)
    at tconstruct.blocks.TConstructFluid.<init>(TConstructFluid.java:21)
    at tconstruct.blocks.BloodBlock.<init>(BloodBlock.java:16)
    at tconstruct.common.TContent.registerBlocks(TContent.java:373)
    at tconstruct.common.TContent.<init>(TContent.java:150)
    at tconstruct.TConstruct.preInit(TConstruct.java:123)
    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 cpw.mods.fml.common.FMLModContainer.handleModStateEvent(FMLModContainer.java:513)
    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.EventHandler.handleEvent(EventHandler.java:74)
    at com.google.common.eventbus.SynchronizedEventHandler.handleEvent(SynchronizedEventHandler.java:47)
    at com.google.common.eventbus.EventBus.dispatch(EventBus.java:314)
    at com.google.common.eventbus.EventBus.dispatchQueuedEvents(EventBus.java:296)
    at com.google.common.eventbus.EventBus.post(EventBus.java:267)
    at cpw.mods.fml.common.LoadController.sendEventToModContainer(LoadController.java:209)
    at cpw.mods.fml.common.LoadController.propogateStateMessage(LoadController.java:188)
    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.EventHandler.handleEvent(EventHandler.java:74)
    at com.google.common.eventbus.SynchronizedEventHandler.handleEvent(SynchronizedEventHandler.java:47)
    at com.google.common.eventbus.EventBus.dispatch(EventBus.java:314)
    at com.google.common.eventbus.EventBus.dispatchQueuedEvents(EventBus.java:296)
    at com.google.common.eventbus.EventBus.post(EventBus.java:267)
    at cpw.mods.fml.common.LoadController.distributeStateMessage(LoadController.java:119)
    at cpw.mods.fml.common.Loader.loadMods(Loader.java:500)
    at cpw.mods.fml.client.FMLClientHandler.beginMinecraftLoading(FMLClientHandler.java:202)
    at net.minecraft.client.Minecraft.func_71384_a(Minecraft.java:465)
    at net.minecraft.client.Minecraft.func_99999_d(Minecraft.java:813)
    at net.minecraft.client.main.Main.main(SourceFile:103)
    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:134)
    at net.minecraft.launchwrapper.Launch.main(Launch.java:28)
    Caused by: java.lang.RuntimeException: A mod has attempted to assign BlockID tconstruct.blocks.BloodBlock@569e3b to the Fluid 'blood' but this Fluid has already been linked to BlockID com.sirolf2009.necromancy.block.BlockBlood@190893a. Configure your mods to prevent this from happening.
    ... 45 more


    A detailed walkthrough of the error, its code path and all known details is as follows:
    ---------------------------------------------------------------------------------------

    -- System Details --
    Details:
    Minecraft Version: 1.7.2
    Operating System: Windows 7 (x86) version 6.1
    Java Version: 1.7.0_55, Oracle Corporation
    Java VM Version: Java HotSpot(TM) Client VM (mixed mode, sharing), Oracle Corporation
    Memory: 68085496 bytes (64 MB) / 194613248 bytes (185 MB) up to 518979584 bytes (494 MB)
    JVM Flags: 2 total; -XX:HeapDumpPath=MojangTricksIntelDriversForPerformance_javaw.exe_minecraft.exe.heapdump -Xmx512M
    AABB Pool Size: 0 (0 bytes; 0 MB) allocated, 0 (0 bytes; 0 MB) used
    IntCache: cache: 0, tcache: 0, allocated: 0, tallocated: 0
    FML: MCP v9.01-pre FML v7.2.156.1060 Minecraft Forge 10.12.1.1060 7 mods loaded, 7 mods active
    mcp{8.09} [Minecraft Coder Pack] (minecraft.jar) Unloaded->Constructed->Pre-initialized
    FML{7.2.156.1060} [Forge Mod Loader] (forge-1.7.2-10.12.1.1060.jar) Unloaded->Constructed->Pre-initialized
    Forge{10.12.1.1060} [Minecraft Forge] (forge-1.7.2-10.12.1.1060.jar) Unloaded->Constructed->Pre-initialized
    TConstruct-Preloader{0.1.1} [Tinkers Corestruct] (minecraft.jar) Unloaded->Constructed->Pre-initialized
    Mantle{1.7.2-132.45b0b50} [Mantle] (Mantle-1.7.2-0.2.8.jar) Unloaded->Constructed->Pre-initialized
    necromancy{1.6.8} [Necromancy] (Necromancy-1.7.2.jar) Unloaded->Constructed->Pre-initialized
    TConstruct{1.7.2-1.6.0.jenkins478} [Tinkers' Construct] (TConstruct-1.7.2-1.6.0.a14.jar) Unloaded->Constructed->Errored
    Mantle Environment: Environment healthy.
    TConstruct Environment: Environment healthy.
     
  2. robin4002

    robin4002 Support Technique
    Staff

    Inscrit:
    17 Août 2012
    Messages:
    5 478
    Points:
    229
    Sexe:
    Homme
    Salut,
    Les deux mods ajoutent tout les deux un liquide du même nom, normalement les codeurs des mods en questions sont sensé mettre le code en place pour éviter ce problème, sauf qu'ils ne l'ont pas fait, donc les deux mods ne sont pas compatible. Il faudrait envoyer le crash report a un des auteurs d'un des deux mods.
     
  3. jujucrow39

    jujucrow39 Nouveau

    Inscrit:
    30 Avr 2014
    Messages:
    3
    Points:
    30
    Sexe:
    Homme

Partager cette page