Frage von DomingoGER, 49

minecraft forge ml Error?

habe die version 1.9 mit mods installiert. Fehlermeldung beim start

---- Minecraft Crash Report ----

WARNING: coremods are present: BetterFoliageLoader (BetterFoliage-MC1.9-2.0.4.jar) Contact their authors BEFORE contacting forge

// Everything's going to plan. No, really, that was supposed to happen.

Time: 26.03.16 01:13 Description: Initializing game

java.lang.IllegalAccessError: tried to access field net.minecraftforge.client.event.GuiScreenEvent.gui from class biomesoplenty.common.handler.GuiEventHandler at biomesoplenty.common.handler.GuiEventHandler.onPreInitCreateWorld(GuiEventHandler.java:26) at net.minecraftforge.fml.common.eventhandler.ASMEventHandler_28_GuiEventHandler_onPreInitCreateWorld_Pre.invoke(.dynamic) at net.minecraftforge.fml.common.eventhandler.ASMEventHandler.invoke(ASMEventHandler.java:49) at net.minecraftforge.fml.common.eventhandler.EventBus.post(EventBus.java:140) at net.minecraft.client.gui.GuiScreen.func_146280_a(GuiScreen.java:484) at net.minecraft.client.Minecraft.func_147108_a(Minecraft.java:958) at net.minecraft.client.Minecraft.func_71384_a(Minecraft.java:523) at net.minecraft.client.Minecraft.func_99999_d(Minecraft.java:346) at net.minecraft.client.main.Main.main(SourceFile:124) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:483) at net.minecraft.launchwrapper.Launch.launch(Launch.java:135) at net.minecraft.launchwrapper.Launch.main(Launch.java:28)

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

-- Head -- Stacktrace: at biomesoplenty.common.handler.GuiEventHandler.onPreInitCreateWorld(GuiEventHandler.java:26) at net.minecraftforge.fml.common.eventhandler.ASMEventHandler_28_GuiEventHandler_onPreInitCreateWorld_Pre.invoke(.dynamic) at net.minecraftforge.fml.common.eventhandler.ASMEventHandler.invoke(ASMEventHandler.java:49) at net.minecraftforge.fml.common.eventhandler.EventBus.post(EventBus.java:140) at net.minecraft.client.gui.GuiScreen.func_146280_a(GuiScreen.java:484) at net.minecraft.client.Minecraft.func_147108_a(Minecraft.java:958) at net.minecraft.client.Minecraft.func_71384_a(Minecraft.java:523)

-- Initialization -- Details: Stacktrace: at net.minecraft.client.Minecraft.func_99999_d(Minecraft.java:346) at net.minecraft.client.main.Main.main(SourceFile:124) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:483) at net.minecraft.launchwrapper.Launch.launch(Launch.java:135) at net.mine

Hilfreichste Antwort - ausgezeichnet vom Fragesteller
von vedranox, 37

Es liegt am Mod Biomes o plenty... schmeiss den mal raus!

Antwort
von xXmennXx, 26

Schon mal überdacht das der Forge ML für 1.9 noch in der Beta/Dev version ist und dadurch Fehler entstehen können?

Antwort
von vedranox, 33

Richtige Forge+Modversion installiert?

Keine passende Antwort gefunden?

Fragen Sie die Community