Minecraft Forums

I need help please.
It is the first time through installing Optifine me. It's annoying since this is the only mod unbootable.
This is my crash report:

Java HotSpot(TM) 64-Bit Server VM warning: Using incremental CMS is deprecated and will likely be removed in a future release
[18:38:54] [main/INFO] [LaunchWrapper]: Loading tweak class name cpw.mods.fml.common.launcher.FMLTweaker
[18:38:54] [main/INFO] [LaunchWrapper]: Using primary tweak class name cpw.mods.fml.common.launcher.FMLTweaker
[18:38:54] [main/INFO] [LaunchWrapper]: Calling tweak class cpw.mods.fml.common.launcher.FMLTweaker
[18:38:55] [main/INFO] [FML]: Forge Mod Loader version 7.99.39.1566 for Minecraft 1.7.10 loading
[18:38:55] [main/INFO] [FML]: Java is Java HotSpot(TM) 64-Bit Server VM, version 1.8.0_66, running on Mac OS X:x86_64:10.11.1, installed at /Library/Internet Plug-Ins/JavaAppletPlugin.plugin/Contents/Home
[18:38:55] [main/INFO] [FML]: Loading tweaker optifine.OptiFineForgeTweaker from OptiFine_1.7.10_HD_U_A3.jar
[18:38:55] [main/INFO] [LaunchWrapper]: Loading tweak class name cpw.mods.fml.common.launcher.FMLInjectionAndSortingTweaker
[18:38:55] [main/INFO] [LaunchWrapper]: Loading tweak class name optifine.OptiFineForgeTweaker
[18:38:55] [main/INFO] [LaunchWrapper]: Loading tweak class name cpw.mods.fml.common.launcher.FMLDeobfTweaker
[18:38:55] [main/INFO] [LaunchWrapper]: Calling tweak class cpw.mods.fml.common.launcher.FMLInjectionAndSortingTweaker
[18:38:55] [main/INFO] [LaunchWrapper]: Calling tweak class cpw.mods.fml.common.launcher.FMLInjectionAndSortingTweaker
[18:38:55] [main/INFO] [LaunchWrapper]: Calling tweak class optifine.OptiFineForgeTweaker
[18:38:55] [main/INFO] [STDOUT]: [optifine.OptiFineForgeTweaker:dbg:49]: OptiFineForgeTweaker: acceptOptions
[18:38:55] [main/INFO] [STDOUT]: [optifine.OptiFineForgeTweaker:dbg:49]: OptiFineForgeTweaker: injectIntoClassLoader
[18:38:55] [main/INFO] [STDOUT]: [optifine.OptiFineClassTransformer:dbg:179]: OptiFine ClassTransformer
[18:38:55] [main/INFO] [STDOUT]: [optifine.OptiFineClassTransformer:dbg:179]: OptiFine URL: file:/Users/carlos/Library/Application%20Support/minecraft/mods/OptiFine_1.7.10_HD_U_A3.jar
[18:38:55] [main/INFO] [STDOUT]: [optifine.OptiFineClassTransformer:dbg:179]: OptiFine ZIP file: [email protected]
[18:38:55] [main/INFO] [LaunchWrapper]: Calling tweak class cpw.mods.fml.relauncher.CoreModManager$FMLPluginWrapper
[18:38:58] [main/INFO] [FML]: Found valid fingerprint for Minecraft Forge. Certificate fingerprint e3c3d50c7c986df74c645c0ac54639741c90a557
[18:38:58] [main/INFO] [FML]: Found valid fingerprint for Minecraft. Certificate fingerprint cd99959656f753dc28d863b46769f7f8fbaefcfc
[18:38:58] [main/INFO] [LaunchWrapper]: Calling tweak class cpw.mods.fml.relauncher.CoreModManager$FMLPluginWrapper
[18:38:58] [main/INFO] [LaunchWrapper]: Calling tweak class cpw.mods.fml.common.launcher.FMLDeobfTweaker
[18:38:59] [main/INFO] [LaunchWrapper]: Loading tweak class name cpw.mods.fml.common.launcher.TerminalTweaker
[18:38:59] [main/INFO] [LaunchWrapper]: Calling tweak class cpw.mods.fml.common.launcher.TerminalTweaker
[18:38:59] [main/INFO] [STDOUT]: [optifine.OptiFineForgeTweaker:dbg:49]: OptiFineForgeTweaker: getLaunchArguments
[18:38:59] [main/INFO] [LaunchWrapper]: Launching wrapped minecraft {net.minecraft.client.main.Main}
[18:39:01] [main/INFO]: Setting user: KarlosArkelos
[18:39:03] [Client thread/INFO]: LWJGL Version: 2.9.1
[OptiFine]
[OptiFine] OptiFine_1.7.10_HD_U_A3
[OptiFine] Fri Nov 20 18:39:04 CST 2015
[OptiFine] OS: Mac OS X (x86_64) version 10.11.1
[OptiFine] Java: 1.8.0_66, Oracle Corporation
[OptiFine] VM: Java HotSpot(TM) 64-Bit Server VM (mixed mode), Oracle Corporation
[OptiFine] LWJGL: 2.9.1
[OptiFine] OpenGL: ATI Radeon HD 2400 XT OpenGL Engine version 2.1 ATI-10.0.40, ATI Technologies Inc.
[OptiFine] OpenGL Version: 2.1
[OptiFine] Maximum texture size: 4096x4096
[OptiFine] Checking for new version
[18:39:04] [Client thread/INFO] [FML]: Forge Mod Loader has detected optifine OptiFine_1.7.10_HD_U_A3, enabling compatibility features
[18:39:04] [Client thread/INFO] [MinecraftForge]: Attempting early MinecraftForge initialization
[18:39:04] [Client thread/INFO] [FML]: MinecraftForge v10.13.4.1566 Initialized
[18:39:04] [Client thread/INFO] [FML]: Replaced 183 ore recipies
[18:39:04] [Client thread/INFO] [MinecraftForge]: Completed early MinecraftForge initialization
[OptiFine] Version found: C1
[18:39:05] [Client thread/INFO] [FML]: Found 0 mods from the command line. Injecting into mod discoverer
[18:39:05] [Client thread/INFO] [FML]: Searching /Users/carlos/Library/Application Support/minecraft/mods for mods
[18:39:16] [Client thread/WARN] [DamageIndicatorsMod]: Mod DamageIndicatorsMod is missing the required element 'version' and a version.properties file could not be found. Falling back to metadata version 3.2.0
[18:39:16] [Client thread/INFO] [FML]: Attempting to reparse the mod container [MC1.7.10]deconstruction[v2.2.5].jar
[18:39:17] [Client thread/WARN] [mexicanmod]: Mod mexicanmod is missing the required element 'version' and a version.properties file could not be found. Falling back to metadata version 1.2.1
[18:39:17] [Client thread/INFO] [FML]: Forge Mod Loader has identified 22 mods to load
[18:39:18] [Client thread/INFO] [FML]: Attempting connection with missing mods [mcp, FML, Forge, DamageIndicatorsMod, deconstruction, abyssalcraft, B0bGrowsOre, Backpack, BiblioCraft, AWWayofTime, chococraft, CustomSpawner, MoCreatures, eplus, ExtrabiomesXL, grim3212core, GrimoireOfGaia, imc, LotsOfFood, Metallurgy, MetallurgyCore, mexicanmod] at CLIENT
[18:39:18] [Client thread/INFO] [FML]: Attempting connection with missing mods [mcp, FML, Forge, DamageIndicatorsMod, deconstruction, abyssalcraft, B0bGrowsOre, Backpack, BiblioCraft, AWWayofTime, chococraft, CustomSpawner, MoCreatures, eplus, ExtrabiomesXL, grim3212core, GrimoireOfGaia, imc, LotsOfFood, Metallurgy, MetallurgyCore, mexicanmod] at SERVER
[18:39:20] [Client thread/ERROR] [Backpack]: The mod Backpack is expecting signature @[email protected] for source backpack-2.0.1-1.7.x.jar, however there is no signature matching that description
[18:39:23] [Client thread/INFO]: Reloading ResourceManager: Default, FMLFileResourcePack:Forge Mod Loader, FMLFileResourcePack:Minecraft Forge, FMLFileResourcePack:Damage Indicators, FMLFileResourcePack:The Deconstruction Mod, FMLFileResourcePack:AbyssalCraft, FMLFileResourcePack:B0bGary's Growable Ores, FMLFileResourcePack:Backpack, FMLFileResourcePack:BiblioCraft, FMLFileResourcePack:Blood Magic: Alchemical Wizardry, FMLFileResourcePack:Clienthax's ChocoCraft, FMLFileResourcePack:DrZhark's CustomSpawner, FMLFileResourcePack:DrZhark's Mo'Creatures Mod, FMLFileResourcePack:Enchanting Plus, FMLFileResourcePack:ExtrabiomesXL, FMLFileResourcePack:Grim3212 Core, FMLFileResourcePack:Grimoire of Gaia 3, FMLFileResourcePack:Improving Minecraft, FMLFileResourcePack:Lots of Food, FMLFileResourcePack:Metallurgy 4, FMLFileResourcePack:Metallurgy Core, FMLFileResourcePack:Mexican Mod
[18:39:23] [Client thread/WARN]: ResourcePack: ignored non-lowercase namespace: alchemicalwizardryBooks in /Users/carlos/Library/Application Support/minecraft/mods/BloodMagic-1.7.10-1.3.3-17.jar
[18:39:23] [Client thread/WARN]: ResourcePack: ignored non-lowercase namespace: alchemicalwizardryBooks in /Users/carlos/Library/Application Support/minecraft/mods/BloodMagic-1.7.10-1.3.3-17.jar
[18:39:23] [Client thread/WARN]: ResourcePack: ignored non-lowercase namespace: alchemicalwizardryBooks in /Users/carlos/Library/Application Support/minecraft/mods/BloodMagic-1.7.10-1.3.3-17.jar
[18:39:23] [Client thread/WARN]: ResourcePack: ignored non-lowercase namespace: alchemicalwizardryBooks in /Users/carlos/Library/Application Support/minecraft/mods/BloodMagic-1.7.10-1.3.3-17.jar
[18:39:23] [Client thread/WARN]: ResourcePack: ignored non-lowercase namespace: alchemicalwizardryBooks in /Users/carlos/Library/Application Support/minecraft/mods/BloodMagic-1.7.10-1.3.3-17.jar
[18:39:23] [Client thread/WARN]: ResourcePack: ignored non-lowercase namespace: alchemicalwizardryBooks in /Users/carlos/Library/Application Support/minecraft/mods/BloodMagic-1.7.10-1.3.3-17.jar
[18:39:23] [Client thread/INFO] [FML]: Processing ObjectHolder annotations
[18:39:23] [Client thread/INFO] [FML]: Found 341 ObjectHolder annotations
[18:39:23] [Client thread/INFO] [FML]: Identifying ItemStackHolder annotations
[18:39:23] [Client thread/INFO] [FML]: Found 0 ItemStackHolder annotations
[18:39:23] [Client thread/INFO] [FML]: Configured a dormant chunk cache size of 0
[18:39:23] [Client thread/INFO] [deconstruction]: Config loaded from /Users/carlos/Library/Application Support/minecraft/config/deconstruction.cfg
[18:39:23] [Client thread/INFO] [AbyssalCraft]: Pre-initializing AbyssalCraft.
[18:39:29] [Client thread/INFO] [AbyssalCraft]: Scanning biome IDs to see if the ones needed are available.
[18:39:29] [Client thread/INFO] [AbyssalCraft]: None of the needed biome IDs are occupied!
[18:39:29] [Thread-7/INFO] [STDERR]: [java.lang.Throwable$WrappedPrintStream:println:748]: java.io.IOException: Server returned HTTP response code: 403 for URL: https://dl.dropboxusercontent.com/u/74770478/DamageIndicatorMod1710.txt
[18:39:29] [Thread-7/INFO] [STDERR]: [java.lang.Throwable$WrappedPrintStream:println:748]: at sun.net.www.protocol.http.HttpURLConnection.getInputStream0(HttpURLConnection.java:1840)
[18:39:29] [Thread-7/INFO] [STDERR]: [java.lang.Throwable$WrappedPrintStream:println:748]: at sun.net.www.protocol.http.HttpURLConnection.access$200(HttpURLConnection.java:90)
[18:39:29] [Thread-7/INFO] [STDERR]: [java.lang.Throwable$WrappedPrintStream:println:748]: at sun.net.www.protocol.http.HttpURLConnection$9.run(HttpURLConnection.java:1433)
[18:39:29] [Thread-7/INFO] [STDERR]: [java.lang.Throwable$WrappedPrintStream:println:748]: at sun.net.www.protocol.http.HttpURLConnection$9.run(HttpURLConnection.java:1431)
[18:39:29] [Thread-7/INFO] [STDERR]: [java.lang.Throwable$WrappedPrintStream:println:748]: at java.security.AccessController.doPrivileged(Native Method)
[18:39:29] [Thread-7/INFO] [STDERR]: [java.lang.Throwable$WrappedPrintStream:println:748]: at java.security.AccessController.doPrivilegedWithCombiner(AccessController.java:782)
[18:39:29] [Thread-7/INFO] [STDERR]: [java.lang.Throwable$WrappedPrintStream:println:748]: at sun.net.www.protocol.http.HttpURLConnection.getInputStream(HttpURLConnection.java:1430)
[18:39:29] [Thread-7/INFO] [STDERR]: [java.lang.Throwable$WrappedPrintStream:println:748]: at sun.net.www.protocol.https.HttpsURLConnectionImpl.getInputStream(HttpsURLConnectionImpl.java:254)
[18:39:29] [Thread-7/INFO] [STDERR]: [java.lang.Throwable$WrappedPrintStream:println:748]: at java.net.URL.openStream(URL.java:1038)
[18:39:29] [Thread-7/INFO] [STDERR]: [java.lang.Throwable$WrappedPrintStream:println:748]: at DamageIndicatorsMod.client.DIClientProxy$1.run(DIClientProxy.java:75)
[18:39:29] [Thread-7/INFO] [STDERR]: [java.lang.Throwable$WrappedPrintStream:println:748]: at java.lang.Thread.run(Thread.java:745)
[18:39:30] [Client thread/INFO] [AbyssalCraft]: Checking possible mod integrations.
[18:39:30] [Client thread/WARN] [FML]: ****************************************
[18:39:30] [Client thread/WARN] [FML]: * A broken ore dictionary registration with name ingotCopper has occurred. It adds an item (type: class com.teammetallurgy.metallurgy.metals.MetalItem) which is currently unknown to the game registry. This dictionary item can only support a single value when registered with ores like this, and NO I am not going to turn this spam off. Just register your ore dictionary entries after the GameRegistry.
TO USERS: YES this is a BUG in the mod Metallurgy 4 report it to them!
[18:39:30] [Client thread/WARN] [FML]: * at net.minecraftforge.oredict.OreDictionary.registerOreImpl(OreDictionary.java:534)
[18:39:30] [Client thread/WARN] [FML]: * at net.minecraftforge.oredict.OreDictionary.registerOre(OreDictionary.java:501)
[18:39:30] [Client thread/WARN] [FML]: * at com.teammetallurgy.metallurgy.metals.MetalSet.load(MetalSet.java:380)
[18:39:30] [Client thread/WARN] [FML]: * at com.teammetallurgy.metallurgy.BlockList.injectMetalSet(BlockList.java:201)
[18:39:30] [Client thread/WARN] [FML]: * at com.teammetallurgy.metallurgy.BlockList.initMetalSets(BlockList.java:163)
[18:39:30] [Client thread/WARN] [FML]: * at com.teammetallurgy.metallurgy.BlockList.init(BlockList.java:91)...
[18:39:30] [Client thread/WARN] [FML]: ****************************************
[18:39:30] [Client thread/WARN] [FML]: ****************************************
[18:39:30] [Client thread/WARN] [FML]: * A broken ore dictionary registration with name ingotTin has occurred. It adds an item (type: class com.teammetallurgy.metallurgy.metals.MetalItem) which is currently unknown to the game registry. This dictionary item can only support a single value when registered with ores like this, and NO I am not going to turn this spam off. Just register your ore dictionary entries after the GameRegistry.
TO USERS: YES this is a BUG in the mod Metallurgy 4 report it to them!
[18:39:30] [Client thread/WARN] [FML]: * at net.minecraftforge.oredict.OreDictionary.registerOreImpl(OreDictionary.java:534)
[18:39:30] [Client thread/WARN] [FML]: * at net.minecraftforge.oredict.OreDictionary.registerOre(OreDictionary.java:501)
[18:39:30] [Client thread/WARN] [FML]: * at com.teammetallurgy.metallurgy.metals.MetalSet.load(MetalSet.java:380)
[18:39:30] [Client thread/WARN] [FML]: * at com.teammetallurgy.metallurgy.BlockList.injectMetalSet(BlockList.java:201)
[18:39:30] [Client thread/WARN] [FML]: * at com.teammetallurgy.metallurgy.BlockList.initMetalSets(BlockList.java:163)
[18:39:30] [Client thread/WARN] [FML]: * at com.teammetallurgy.metallurgy.BlockList.init(BlockList.java:91)...
[18:39:30] [Client thread/WARN] [FML]: ****************************************
[18:39:30] [Client thread/WARN] [FML]: ****************************************
[18:39:30] [Client thread/WARN] [FML]: * A broken ore dictionary registration with name ingotManganese has occurred. It adds an item (type: class com.teammetallurgy.metallurgy.metals.MetalItem) which is currently unknown to the game registry. This dictionary item can only support a single value when registered with ores like this, and NO I am not going to turn this spam off. Just register your ore dictionary entries after the GameRegistry.
TO USERS: YES this is a BUG in the mod Metallurgy 4 report it to them!
[18:39:30] [Client thread/WARN] [FML]: * at net.minecraftforge.oredict.OreDictionary.registerOreImpl(OreDictionary.java:534)
[18:39:30] [Client thread/WARN] [FML]: * at net.minecraftforge.oredict.OreDictionary.registerOre(OreDictionary.java:501)
[18:39:30] [Client thread/WARN] [FML]: * at com.teammetallurgy.metallurgy.metals.MetalSet.load(MetalSet.java:380)
[18:39:30] [Client thread/WARN] [FML]: * at com.teammetallurgy.metallurgy.BlockList.injectMetalSet(BlockList.java:201)
[18:39:30] [Client thread/WARN] [FML]: * at com.teammetallurgy.metallurgy.BlockList.initMetalSets(BlockList.java:163)
[18:39:30] [Client thread/WARN] [FML]: * at com.teammetallurgy.metallurgy.BlockList.init(BlockList.java:91)...
[18:39:30] [Client thread/WARN] [FML]: ****************************************
[18:39:30] [Client thread/WARN] [FML]: ****************************************
[18:39:30] [Client thread/WARN] [FML]: * A broken ore dictionary registration with name ingotBronze has occurred. It adds an item (type: class com.teammetallurgy.metallurgy.metals.MetalItem) which is currently unknown to the game registry. This dictionary item can only support a single value when registered with ores like this, and NO I am not going to turn this spam off. Just register your ore dictionary entries after the GameRegistry.
TO USERS: YES this is a BUG in the mod Metallurgy 4 report it to them!
[18:39:30] [Client thread/WARN] [FML]: * at net.minecraftforge.oredict.OreDictionary.registerOreImpl(OreDictionary.java:534)
[18:39:30] [Client thread/WARN] [FML]: * at net.minecraftforge.oredict.OreDictionary.registerOre(OreDictionary.java:501)
[18:39:30] [Client thread/WARN] [FML]: * at com.teammetallurgy.metallurgy.metals.MetalSet.load(MetalSet.java:380)
[18:39:30] [Client thread/WARN] [FML]: * at com.teammetallurgy.metallurgy.BlockList.injectMetalSet(BlockList.java:201)
[18:39:30] [Client thread/WARN] [FML]: * at com.teammetallurgy.metallurgy.BlockList.initMetalSets(BlockList.java:163)
[18:39:30] [Client thread/WARN] [FML]: * at com.teammetallurgy.metallurgy.BlockList.init(BlockList.java:91)...
[18:39:30] [Client thread/WARN] [FML]: ****************************************
[18:39:30] [Client thread/WARN] [FML]: ****************************************
[18:39:30] [Client thread/WARN] [FML]: * A broken ore dictionary registration with name ingotHepatizon has occurred. It adds an item (type: class com.teammetallurgy.metallurgy.metals.MetalItem) which is currently unknown to the game registry. This dictionary item can only support a single value when registered with ores like this, and NO I am not going to turn this spam off. Just register your ore dictionary entries after the GameRegistry.
TO USERS: YES this is a BUG in the mod Metallurgy 4 report it to them!
[18:39:30] [Client thread/WARN] [FML]: * at net.minecraftforge.oredict.OreDictionary.registerOreImpl(OreDictionary.java:534)
[18:39:30] [Client thread/WARN] [FML]: * at net.minecraftforge.oredict.OreDictionary.registerOre(OreDictionary.java:501)
[18:39:30] [Client thread/WARN] [FML]: * at com.teammetallurgy.metallurgy.metals.MetalSet.load(MetalSet.java:380)
[18:39:30] [Client thread/WARN] [FML]: * at com.teammetallurgy.metallurgy.BlockList.injectMetalSet(BlockList.java:201)
[18:39:30] [Client thread/WARN] [FML]: * at com.teammetallurgy.metallurgy.BlockList.initMetalSets(BlockList.java:163)
[18:39:30] [Client thread/WARN] [FML]: * at com.teammetallurgy.metallurgy.BlockList.init(BlockList.java:91)...
[18:39:30] [Client thread/WARN] [FML]: ****************************************
[18:39:30] [Client thread/WARN] [FML]: ****************************************
[18:39:30] [Client thread/WARN] [FML]: * A broken ore dictionary registration with name ingotDamascusSteel has occurred. It adds an item (type: class com.teammetallurgy.metallurgy.metals.MetalItem) which is currently unknown to the game registry. This dictionary item can only support a single value when registered with ores like this, and NO I am not going to turn this spam off. Just register your ore dictionary entries after the GameRegistry.
TO USERS: YES this is a BUG in the mod Metallurgy 4 report it to them!
[18:39:30] [Client thread/WARN] [FML]: * at net.minecraftforge.oredict.OreDictionary.registerOreImpl(OreDictionary.java:534)
[18:39:30] [Client thread/WARN] [FML]: * at net.minecraftforge.oredict.OreDictionary.registerOre(OreDictionary.java:501)
[18:39:30] [Client thread/WARN] [FML]: * at com.teammetallurgy.metallurgy.metals.MetalSet.load(MetalSet.java:380)
[18:39:30] [Client thread/WARN] [FML]: * at com.teammetallurgy.metallurgy.BlockList.injectMetalSet(BlockList.java:201)
[18:39:30] [Client thread/WARN] [FML]: * at com.teammetallurgy.metallurgy.BlockList.initMetalSets(BlockList.java:163)
[18:39:30] [Client thread/WARN] [FML]: * at com.teammetallurgy.metallurgy.BlockList.init(BlockList.java:91)...
[18:39:30] [Client thread/WARN] [FML]: ****************************************
[18:39:30] [Client thread/WARN] [FML]: ****************************************
[18:39:30] [Client thread/WARN] [FML]: * A broken ore dictionary registration with name ingotAngmallen has occurred. It adds an item (type: class com.teammetallurgy.metallurgy.metals.MetalItem) which is currently unknown to the game registry. This dictionary item can only support a single value when registered with ores like this, and NO I am not going to turn this spam off. Just register your ore dictionary entries after the GameRegistry.
TO USERS: YES this is a BUG in the mod Metallurgy 4 report it to them!
[18:39:30] [Client thread/WARN] [FML]: * at net.minecraftforge.oredict.OreDictionary.registerOreImpl(OreDictionary.java:534)
[18:39:30] [Client thread/WARN] [FML]: * at net.minecraftforge.oredict.OreDictionary.registerOre(OreDictionary.java:501)
[18:39:30] [Client thread/WARN] [FML]: * at com.teammetallurgy.metallurgy.metals.MetalSet.load(MetalSet.java:380)
[18:39:30] [Client thread/WARN] [FML]: * at com.teammetallurgy.metallurgy.BlockList.injectMetalSet(BlockList.java:201)
[18:39:30] [Client thread/WARN] [FML]: * at com.teammetallurgy.metallurgy.BlockList.initMetalSets(BlockList.java:163)
[18:39:30] [Client thread/WARN] [FML]: * at com.teammetallurgy.metallurgy.BlockList.init(BlockList.java:91)...
[18:39:30] [Client thread/WARN] [FML]: ****************************************
[18:39:30] [Client thread/WARN] [FML]: ****************************************
[18:39:30] [Client thread/WARN] [FML]: * A broken ore dictionary registration with name ingotSteel has occurred. It adds an item (type: class com.teammetallurgy.metallurgy.metals.MetalItem) which is currently unknown to the game registry. This dictionary item can only support a single value when registered with ores like this, and NO I am not going to turn this spam off. Just register your ore dictionary entries after the GameRegistry.
TO USERS: YES this is a BUG in the mod Metallurgy 4 report it to them!
[18:39:30] [Client thread/WARN] [FML]: * at net.minecraftforge.oredict.OreDictionary.registerOreImpl(OreDictionary.java:534)
[18:39:30] [Client thread/WARN] [FML]: * at net.minecraftforge.oredict.OreDictionary.registerOre(OreDictionary.java:501)
[18:39:30] [Client thread/WARN] [FML]: * at com.teammetallurgy.metallurgy.metals.MetalSet.load(MetalSet.java:380)
[18:39:30] [Client thread/WARN] [FML]: * at com.teammetallurgy.metallurgy.BlockList.injectMetalSet(BlockList.java:201)
[18:39:30] [Client thread/WARN] [FML]: * at com.teammetallurgy.metallurgy.BlockList.initMetalSets(BlockList.java:163)
[18:39:30] [Client thread/WARN] [FML]: * at com.teammetallurgy.metallurgy.BlockList.init(BlockList.java:91)...
[18:39:30] [Client thread/WARN] [FML]: ****************************************
[18:39:30] [Client thread/WARN] [FML]: ****************************************
[18:39:30] [Client thread/WARN] [FML]: * A broken ore dictionary registration with name ingotEximite has occurred. It adds an item (type: class com.teammetallurgy.metallurgy.metals.MetalItem) which is currently unknown to the game registry. This dictionary item can only support a single value when registered with ores like this, and NO I am not going to turn this spam off. Just register your ore dictionary entries after the GameRegistry.
TO USERS: YES this is a BUG in the mod Metallurgy 4 report it to them!
[18:39:30] [Client thread/WARN] [FML]: * at net.minecraftforge.oredict.OreDictionary.registerOreImpl(OreDictionary.java:534)
[18:39:30] [Client thread/WARN] [FML]: * at net.minecraftforge.oredict.OreDictionary.registerOre(OreDictionary.java:501)
[18:39:30] [Client thread/WARN] [FML]: * at com.teammetallurgy.metallurgy.metals.MetalSet.load(MetalSet.java:380)
[18:39:30] [Client thread/WARN] [FML]: * at com.teammetallurgy.metallurgy.BlockList.injectMetalSet(BlockList.java:201)
[18:39:30] [Client thread/WARN] [FML]: * at com.teammetallurgy.metallurgy.BlockList.initMetalSets(BlockList.java:163)
[18:39:30] [Client thread/WARN] [FML]: * at com.teammetallurgy.metallurgy.BlockList.init(BlockList.java:91)...
[18:39:30] [Client thread/WARN] [FML]: ****************************************
[18:39:30] [Client thread/WARN] [FML]: ****************************************
[18:39:30] [Client thread/WARN] [FML]: * A broken ore dictionary registration with name ingotMeutoite has occurred. It adds an item (type: class com.teammetallurgy.metallurgy.metals.MetalItem) which is currently unknown to the game registry. This dictionary item can only support a single value when registered with ores like this, and NO I am not going to turn this spam off. Just register your ore dictionary entries after the GameRegistry.
TO USERS: YES this is a BUG in the mod Metallurgy 4 report it to them!
[18:39:30] [Client thread/WARN] [FML]: * at net.minecraftforge.oredict.OreDictionary.registerOreImpl(OreDictionary.java:534)
[18:39:30] [Client thread/WARN] [FML]: * at net.minecraftforge.oredict.OreDictionary.registerOre(OreDictionary.java:501)
[18:39:30] [Client thread/WARN] [FML]: * at com.teammetallurgy.metallurgy.metals.MetalSet.load(MetalSet.java:380)
[18:39:30] [Client thread/WARN] [FML]: * at com.teammetallurgy.metallurgy.BlockList.injectMetalSet(BlockList.java:201)
[18:39:30] [Client thread/WARN] [FML]: * at com.teammetallurgy.metallurgy.BlockList.initMetalSets(BlockList.java:163)
[18:39:30] [Client thread/WARN] [FML]: * at com.teammetallurgy.metallurgy.BlockList.init(BlockList.java:91)...
[18:39:30] [Client thread/WARN] [FML]: ****************************************
[18:39:30] [Client thread/WARN] [FML]: ****************************************
[18:39:30] [Client thread/WARN] [FML]: * A broken ore dictionary registration with name ingotDesichalkos has occurred. It adds an item (type: class com.teammetallurgy.metallurgy.metals.MetalItem) which is currently unknown to the game registry. This dictionary item can only support a single value when registered with ores like this, and NO I am not going to turn this spam off. Just register your ore dictionary entries after the GameRegistry.
TO USERS: YES this is a BUG in the mod Metallurgy 4 report it to them!
[18:39:30] [Client thread/WARN] [FML]: * at net.minecraftforge.oredict.OreDictionary.registerOreImpl(OreDictionary.java:534)
[18:39:30] [Client thread/WARN] [FML]: * at net.minecraftforge.oredict.OreDictionary.registerOre(OreDictionary.java:501)
[18:39:30] [Client thread/WARN] [FML]: * at com.teammetallurgy.metallurgy.metals.MetalSet.load(MetalSet.java:380)
[18:39:30] [Client thread/WARN] [FML]: * at com.teammetallurgy.metallurgy.BlockList.injectMetalSet(BlockList.java:201)
[18:39:30] [Client thread/WARN] [FML]: * at com.teammetallurgy.metallurgy.BlockList.initMetalSets(BlockList.java:163)
[18:39:30] [Client thread/WARN] [FML]: * at com.teammetallurgy.metallurgy.BlockList.init(BlockList.java:91)...
[18:39:30] [Client thread/WARN] [FML]: ****************************************
[18:39:30] [Client thread/WARN] [FML]: ****************************************
[18:39:30] [Client thread/WARN] [FML]: * A broken ore dictionary registration with name ingotPrometheum has occurred. It adds an item (type: class com.teammetallurgy.metallurgy.metals.MetalItem) which is currently unknown to the game registry. This dictionary item can only support a single value when registered with ores like this, and NO I am not going to turn this spam off. Just register your ore dictionary entries after the GameRegistry.
TO USERS: YES this is a BUG in the mod Metallurgy 4 report it to them!
[18:39:30] [Client thread/WARN] [FML]: * at net.minecraftforge.oredict.OreDictionary.registerOreImpl(OreDictionary.java:534)
[18:39:30] [Client thread/WARN] [FML]: * at net.minecraftforge.oredict.OreDictionary.registerOre(OreDictionary.java:501)
[18:39:30] [Client thread/WARN] [FML]: * at com.teammetallurgy.metallurgy.metals.MetalSet.load(MetalSet.java:380)
[18:39:30] [Client thread/WARN] [FML]: * at com.teammetallurgy.metallurgy.BlockList.injectMetalSet(BlockList.java:201)
[18:39:30] [Client thread/WARN] [FML]: * at com.teammetallurgy.metallurgy.BlockList.initMetalSets(BlockList.java:163)
[18:39:30] [Client thread/WARN] [FML]: * at com.teammetallurgy.metallurgy.BlockList.init(BlockList.java:91)...
[18:39:30] [Client thread/WARN] [FML]: ****************************************
[18:39:30] [Client thread/WARN] [FML]: ****************************************
[18:39:30] [Client thread/WARN] [FML]: * A broken ore dictionary registration with name ingotDeepIron has occurred. It adds an item (type: class com.teammetallurgy.metallurgy.metals.MetalItem) which is currently unknown to the game registry. This dictionary item can only support a single value when registered with ores like this, and NO I am not going to turn this spam off. Just register your ore dictionary entries after the GameRegistry.
TO USERS: YES this is a BUG in the mod Metallurgy 4 report it to them!
[18:39:30] [Client thread/WARN] [FML]: * at net.minecraftforge.oredict.OreDictionary.registerOreImpl(OreDictionary.java:534)
[18:39:30] [Client thread/WARN] [FML]: * at net.minecraftforge.oredict.OreDictionary.registerOre(OreDictionary.java:501)
[18:39:30] [Client thread/WARN] [FML]: * at com.teammetallurgy.metallurgy.metals.MetalSet.load(MetalSet.java:380)
[18:39:30] [Client thread/WARN] [FML]: * at com.teammetallurgy.metallurgy.BlockList.injectMetalSet(BlockList.java:201)
[18:39:30] [Client thread/WARN] [FML]: * at com.teammetallurgy.metallurgy.BlockList.initMetalSets(BlockList.java:163)
[18:39:30] [Client thread/WARN] [FML]: * at com.teammetallurgy.metallurgy.BlockList.init(BlockList.java:91)...
[18:39:30] [Client thread/WARN] [FML]: ****************************************
[18:39:30] [Client thread/WARN] [FML]: ****************************************
[18:39:30] [Client thread/WARN] [FML]: * A broken ore dictionary registration with name ingotInfuscolium has occurred. It adds an item (type: class com.teammetallurgy.metallurgy.metals.MetalItem) which is currently unknown to the game registry. This dictionary item can only support a single value when registered with ores like this, and NO I am not going to turn this spam off. Just register your ore dictionary entries after the GameRegistry.
TO USERS: YES this is a BUG in the mod Metallurgy 4 report it to them!
[18:39:30] [Client thread/WARN] [FML]: * at net.minecraftforge.oredict.OreDictionary.registerOreImpl(OreDictionary.java:534)
[18:39:30] [Client thread/WARN] [FML]: * at net.minecraftforge.oredict.OreDictionary.registerOre(OreDictionary.java:501)
[18:39:30] [Client thread/WARN] [FML]: * at com.teammetallurgy.metallurgy.metals.MetalSet.load(MetalSet.java:380)
[18:39:30] [Client thread/WARN] [FML]: * at com.teammetallurgy.metallurgy.BlockList.injectMetalSet(BlockList.java:201)
[18:39:30] [Client thread/WARN] [FML]: * at com.teammetallurgy.metallurgy.BlockList.initMetalSets(BlockList.java:163)
[18:39:30] [Client thread/WARN] [FML]: * at com.teammetallurgy.metallurgy.BlockList.init(BlockList.java:91)...
[18:39:30] [Client thread/WARN] [FML]: ****************************************
[18:39:30] [Client thread/WARN] [FML]: ****************************************
[18:39:30] [Client thread/WARN] [FML]: * A broken ore dictionary registration with name ingotBlackSteel has occurred. It adds an item (type: class com.teammetallurgy.metallurgy.metals.MetalItem) which is currently unknown to the game registry. This dictionary item can only support a single value when registered with ores like this, and NO I am not going to turn this spam off. Just register your ore dictionary entries after the GameRegistry.
TO USERS: YES this is a BUG in the mod Metallurgy 4 report it to them!
[18:39:30] [Client thread/WARN] [FML]: * at net.minecraftforge.oredict.OreDictionary.registerOreImpl(OreDictionary.java:534)
[18:39:30] [Client thread/WARN] [FML]: * at net.minecraftforge.oredict.OreDictionary.registerOre(OreDictionary.java:501)
[18:39:30] [Client thread/WARN] [FML]: * at com.teammetallurgy.metallurgy.metals.MetalSet.load(MetalSet.java:380)
[18:39:30] [Client thread/WARN] [FML]: * at com.teammetallurgy.metallurgy.BlockList.injectMetalSet(BlockList.java:201)
[18:39:30] [Client thread/WARN] [FML]: * at com.teammetallurgy.metallurgy.BlockList.initMetalSets(BlockList.java:163)
[18:39:30] [Client thread/WARN] [FML]: * at com.teammetallurgy.metallurgy.BlockList.init(BlockList.java:91)...
[18:39:30] [Client thread/WARN] [FML]: ****************************************
[18:39:30] [Client thread/WARN] [FML]: ****************************************
[18:39:30] [Client thread/WARN] [FML]: * A broken ore dictionary registration with name ingotOureclase has occurred. It adds an item (type: class com.teammetallurgy.metallurgy.metals.MetalItem) which is currently unknown to the game registry. This dictionary item can only support a single value when registered with ores like this, and NO I am not going to turn this spam off. Just register your ore dictionary entries after the GameRegistry.
TO USERS: YES this is a BUG in the mod Metallurgy 4 report it to them!
[18:39:30] [Client thread/WARN] [FML]: * at net.minecraftforge.oredict.OreDictionary.registerOreImpl(OreDictionary.java:534)
[18:39:30] [Client thread/WARN] [FML]: * at net.minecraftforge.oredict.OreDictionary.registerOre(OreDictionary.java:501)
[18:39:30] [Client thread/WARN] [FML]: * at com.teammetallurgy.metallurgy.metals.MetalSet.load(MetalSet.java:380)
[18:39:30] [Client thread/WARN] [FML]: * at com.teammetallurgy.metallurgy.BlockList.injectMetalSet(BlockList.java:201)
[18:39:30] [Client thread/WARN] [FML]: * at com.teammetallurgy.metallurgy.BlockList.initMetalSets(BlockList.java:163)
[18:39:30] [Client thread/WARN] [FML]: * at com.teammetallurgy.metallurgy.BlockList.init(BlockList.java:91)...
[18:39:30] [Client thread/WARN] [FML]: ****************************************
[18:39:30] [Client thread/WARN] [FML]: ****************************************
[18:39:30] [Client thread/WARN] [FML]: * A broken ore dictionary registration with name ingotAstralSilver has occurred. It adds an item (type: class com.teammetallurgy.metallurgy.metals.MetalItem) which is currently unknown to the game registry. This dictionary item can only support a single value when registered with ores like this, and NO I am not going to turn this spam off. Just register your ore dictionary entries after the GameRegistry.
TO USERS: YES this is a BUG in the mod Metallurgy 4 report it to them!
[18:39:30] [Client thread/WARN] [FML]: * at net.minecraftforge.oredict.OreDictionary.registerOreImpl(OreDictionary.java:534)
[18:39:30] [Client thread/WARN] [FML]: * at net.minecraftforge.oredict.OreDictionary.registerOre(OreDictionary.java:501)
[18:39:30] [Client thread/WARN] [FML]: * at com.teammetallurgy.metallurgy.metals.MetalSet.load(MetalSet.java:380)
[18:39:30] [Client thread/WARN] [FML]: * at com.teammetallurgy.metallurgy.BlockList.injectMetalSet(BlockList.java:201)
[18:39:30] [Client thread/WARN] [FML]: * at com.teammetallurgy.metallurgy.BlockList.initMetalSets(BlockList.java:163)
[18:39:30] [Client thread/WARN] [FML]: * at com.teammetallurgy.metallurgy.BlockList.init(BlockList.java:91)...
[18:39:30] [Client thread/WARN] [FML]: ****************************************
[18:39:30] [Client thread/WARN] [FML]: ****************************************
[18:39:30] [Client thread/WARN] [FML]: * A broken ore dictionary registration with name ingotCarmot has occurred. It adds an item (type: class com.teammetallurgy.metallurgy.metals.MetalItem) which is currently unknown to the game registry. This dictionary item can only support a single value when registered with ores like this, and NO I am not going to turn this spam off. Just register your ore dictionary entries after the GameRegistry.
TO USERS: YES this is a BUG in the mod Metallurgy 4 report it to them!
[18:39:30] [Client thread/WARN] [FML]: * at net.minecraftforge.oredict.OreDictionary.registerOreImpl(OreDictionary.java:534)
[18:39:30] [Client thread/WARN] [FML]: * at net.minecraftforge.oredict.OreDictionary.registerOre(OreDictionary.java:501)
[18:39:30] [Client thread/WARN] [FML]: * at com.teammetallurgy.metallurgy.metals.MetalSet.load(MetalSet.java:380)
[18:39:30] [Client thread/WARN] [FML]: * at com.teammetallurgy.metallurgy.BlockList.injectMetalSet(BlockList.java:201)
[18:39:30] [Client thread/WARN] [FML]: * at com.teammetallurgy.metallurgy.BlockList.initMetalSets(BlockList.java:163)
[18:39:30] [Client thread/WARN] [FML]: * at com.teammetallurgy.metallurgy.BlockList.init(BlockList.java:91)...
[18:39:30] [Client thread/WARN] [FML]: ****************************************
[18:39:30] [Client thread/WARN] [FML]: ****************************************
[18:39:30] [Client thread/WARN] [FML]: * A broken ore dictionary registration with name ingotMithril has occurred. It adds an item (type: class com.teammetallurgy.metallurgy.metals.MetalItem) which is currently unknown to the game registry. This dictionary item can only support a single value when registered with ores like this, and NO I am not going to turn this spam off. Just register your ore dictionary entries after the GameRegistry.
TO USERS: YES this is a BUG in the mod Metallurgy 4 report it to them!
[18:39:30] [Client thread/WARN] [FML]: * at net.minecraftforge.oredict.OreDictionary.registerOreImpl(OreDictionary.java:534)
[18:39:30] [Client thread/WARN] [FML]: * at net.minecraftforge.oredict.OreDictionary.registerOre(OreDictionary.java:501)
[18:39:30] [Client thread/WARN] [FML]: * at com.teammetallurgy.metallurgy.metals.MetalSet.load(MetalSet.java:380)
[18:39:30] [Client thread/WARN] [FML]: * at com.teammetallurgy.metallurgy.BlockList.injectMetalSet(BlockList.java:201)
[18:39:30] [Client thread/WARN] [FML]: * at com.teammetallurgy.metallurgy.BlockList.initMetalSets(BlockList.java:163)
[18:39:30] [Client thread/WARN] [FML]: * at com.teammetallurgy.metallurgy.BlockList.init(BlockList.java:91)...
[18:39:30] [Client thread/WARN] [FML]: ****************************************
[18:39:30] [Client thread/WARN] [FML]: ****************************************
[18:39:30] [Client thread/WARN] [FML]: * A broken ore dictionary registration with name ingotRubracium has occurred. It adds an item (type: class com.teammetallurgy.metallurgy.metals.MetalItem) which is currently unknown to the game registry. This dictionary item can only support a single value when registered with ores like this, and NO I am not going to turn this spam off. Just register your ore dictionary entries after the GameRegistry.
TO USERS: YES this is a BUG in the mod Metallurgy 4 report it to them!
[18:39:30] [Client thread/WARN] [FML]: * at net.minecraftforge.oredict.OreDictionary.registerOreImpl(OreDictionary.java:534)
[18:39:30] [Client thread/WARN] [FML]: * at net.minecraftforge.oredict.OreDictionary.registerOre(OreDictionary.java:501)
[18:39:30] [Client thread/WARN] [FML]: * at com.teammetallurgy.metallurgy.metals.MetalSet.load(MetalSet.java:380)
[18:39:30] [Client thread/WARN] [FML]: * at com.teammetallurgy.metallurgy.BlockList.injectMetalSet(BlockList.java:201)
[18:39:30] [Client thread/WARN] [FML]: * at com.teammetallurgy.metallurgy.BlockList.initMetalSets(BlockList.java:163)
[18:39:30] [Client thread/WARN] [FML]: * at com.teammetallurgy.metallurgy.BlockList.init(BlockList.java:91)...
[18:39:30] [Client thread/WARN] [FML]: ****************************************
[18:39:30] [Client thread/WARN] [FML]: ****************************************
[18:39:30] [Client thread/WARN] [FML]: * A broken ore dictionary registration with name ingotQuicksilver has occurred. It adds an item (type: class com.teammetallurgy.metallurgy.metals.MetalItem) which is currently unknown to the game registry. This dictionary item can only support a single value when registered with ores like this, and NO I am not going to turn this spam off. Just register your ore dictionary entries after the GameRegistry.
TO USERS: YES this is a BUG in the mod Metallurgy 4 report it to them!
[18:39:30] [Client thread/WARN] [FML]: * at net.minecraftforge.oredict.OreDictionary.registerOreImpl(OreDictionary.java:534)
[18:39:30] [Client thread/WARN] [FML]: * at net.minecraftforge.oredict.OreDictionary.registerOre(OreDictionary.java:501)
[18:39:30] [Client thread/WARN] [FML]: * at com.teammetallurgy.metallurgy.metals.MetalSet.load(MetalSet.java:380)
[18:39:30] [Client thread/WARN] [FML]: * at com.teammetallurgy.metallurgy.BlockList.injectMetalSet(BlockList.java:201)
[18:39:30] [Client thread/WARN] [FML]: * at com.teammetallurgy.metallurgy.BlockList.initMetalSets(BlockList.java:163)
[18:39:30] [Client thread/WARN] [FML]: * at com.teammetallurgy.metallurgy.BlockList.init(BlockList.java:91)...
[18:39:30] [Client thread/WARN] [FML]: ****************************************
[18:39:30] [Client thread/WARN] [FML]: ****************************************
[18:39:30] [Client thread/WARN] [FML]: * A broken ore dictionary registration with name ingotHaderoth has occurred. It adds an item (type: class com.teammetallurgy.metallurgy.metals.MetalItem) which is currently unknown to the game registry. This dictionary item can only support a single value when registered with ores like this, and NO I am not going to turn this spam off. Just register your ore dictionary entries after the GameRegistry.
TO USERS: YES this is a BUG in the mod Metallurgy 4 report it to them!
[18:39:30] [Client thread/WARN] [FML]: * at net.minecraftforge.oredict.OreDictionary.registerOreImpl(OreDictionary.java:534)
[18:39:30] [Client thread/WARN] [FML]: * at net.minecraftforge.oredict.OreDictionary.registerOre(OreDictionary.java:501)
[18:39:30] [Client thread/WARN] [FML]: * at com.teammetallurgy.metallurgy.metals.MetalSet.load(MetalSet.java:380)
[18:39:30] [Client thread/WARN] [FML]: * at com.teammetallurgy.metallurgy.BlockList.injectMetalSet(BlockList.java:201)
[18:39:30] [Client thread/WARN] [FML]: * at com.teammetallurgy.metallurgy.BlockList.initMetalSets(BlockList.java:163)
[18:39:30] [Client thread/WARN] [FML]: * at com.teammetallurgy.metallurgy.BlockList.init(BlockList.java:91)...
[18:39:30] [Client thread/WARN] [FML]: ****************************************
[18:39:30] [Client thread/WARN] [FML]: ****************************************
[18:39:30] [Client thread/WARN] [FML]: * A broken ore dictionary registration with name ingotOrichalcum has occurred. It adds an item (type: class com.teammetallurgy.metallurgy.metals.MetalItem) which is currently unknown to the game registry. This dictionary item can only support a single value when registered with ores like this, and NO I am not going to turn this spam off. Just register your ore dictionary entries after the GameRegistry.
TO USERS: YES this is a BUG in the mod Metallurgy 4 report it to them!
[18:39:30] [Client thread/WARN] [FML]: * at net.minecraftforge.oredict.OreDictionary.registerOreImpl(OreDictionary.java:534)
[18:39:30] [Client thread/WARN] [FML]: * at net.minecraftforge.oredict.OreDictionary.registerOre(OreDictionary.java:501)
[18:39:30] [Client thread/WARN] [FML]: * at com.teammetallurgy.metallurgy.metals.MetalSet.load(MetalSet.java:380)
[18:39:30] [Client thread/WARN] [FML]: * at com.teammetallurgy.metallurgy.BlockList.injectMetalSet(BlockList.java:201)
[18:39:30] [Client thread/WARN] [FML]: * at com.teammetallurgy.metallurgy.BlockList.initMetalSets(BlockList.java:163)
[18:39:30] [Client thread/WARN] [FML]: * at com.teammetallurgy.metallurgy.BlockList.init(BlockList.java:91)...
[18:39:30] [Client thread/WARN] [FML]: ****************************************
[18:39:30] [Client thread/WARN] [FML]: ****************************************
[18:39:30] [Client thread/WARN] [FML]: * A broken ore dictionary registration with name ingotCelenegil has occurred. It adds an item (type: class com.teammetallurgy.metallurgy.metals.MetalItem) which is currently unknown to the game registry. This dictionary item can only support a single value when registered with ores like this, and NO I am not going to turn this spam off. Just register your ore dictionary entries after the GameRegistry.
TO USERS: YES this is a BUG in the mod Metallurgy 4 report it to them!
[18:39:30] [Client thread/WARN] [FML]: * at net.minecraftforge.oredict.OreDictionary.registerOreImpl(OreDictionary.java:534)
[18:39:30] [Client thread/WARN] [FML]: * at net.minecraftforge.oredict.OreDictionary.registerOre(OreDictionary.java:501)
[18:39:30] [Client thread/WARN] [FML]: * at com.teammetallurgy.metallurgy.metals.MetalSet.load(MetalSet.java:380)
[18:39:30] [Client thread/WARN] [FML]: * at com.teammetallurgy.metallurgy.BlockList.injectMetalSet(BlockList.java:201)
[18:39:30] [Client thread/WARN] [FML]: * at com.teammetallurgy.metallurgy.BlockList.initMetalSets(BlockList.java:163)
[18:39:30] [Client thread/WARN] [FML]: * at com.teammetallurgy.metallurgy.BlockList.init(BlockList.java:91)...
[18:39:30] [Client thread/WARN] [FML]: ****************************************
[18:39:30] [Client thread/WARN] [FML]: ****************************************
[18:39:30] [Client thread/WARN] [FML]: * A broken ore dictionary registration with name ingotAdamantine has occurred. It adds an item (type: class com.teammetallurgy.metallurgy.metals.MetalItem) which is currently unknown to the game registry. This dictionary item can only support a single value when registered with ores like this, and NO I am not going to turn this spam off. Just register your ore dictionary entries after the GameRegistry.
TO USERS: YES this is a BUG in the mod Metallurgy 4 report it to them!
[18:39:30] [Client thread/WARN] [FML]: * at net.minecraftforge.oredict.OreDictionary.registerOreImpl(OreDictionary.java:534)
[18:39:30] [Client thread/WARN] [FML]: * at net.minecraftforge.oredict.OreDictionary.registerOre(OreDictionary.java:501)
[18:39:30] [Client thread/WARN] [FML]: * at com.teammetallurgy.metallurgy.metals.MetalSet.load(MetalSet.java:380)
[18:39:30] [Client thread/WARN] [FML]: * at com.teammetallurgy.metallurgy.BlockList.injectMetalSet(BlockList.java:201)
[18:39:30] [Client thread/WARN] [FML]: * at com.teammetallurgy.metallurgy.BlockList.initMetalSets(BlockList.java:163)
[18:39:30] [Client thread/WARN] [FML]: * at com.teammetallurgy.metallurgy.BlockList.init(BlockList.java:91)...
[18:39:30] [Client thread/WARN] [FML]: ****************************************
[18:39:30] [Client thread/WARN] [FML]: ****************************************
[18:39:30] [Client thread/WARN] [FML]: * A broken ore dictionary registration with name ingotAtlarus has occurred. It adds an item (type: class com.teammetallurgy.metallurgy.metals.MetalItem) which is currently unknown to the game registry. This dictionary item can only support a single value when registered with ores like this, and NO I am not going to turn this spam off. Just register your ore dictionary entries after the GameRegistry.
TO USERS: YES this is a BUG in the mod Metallurgy 4 report it to them!
[18:39:30] [Client thread/WARN] [FML]: * at net.minecraftforge.oredict.OreDictionary.registerOreImpl(OreDictionary.java:534)
[18:39:30] [Client thread/WARN] [FML]: * at net.minecraftforge.oredict.OreDictionary.registerOre(OreDictionary.java:501)
[18:39:30] [Client thread/WARN] [FML]: * at com.teammetallurgy.metallurgy.metals.MetalSet.load(MetalSet.java:380)
[18:39:30] [Client thread/WARN] [FML]: * at com.teammetallurgy.metallurgy.BlockList.injectMetalSet(BlockList.java:201)
[18:39:30] [Client thread/WARN] [FML]: * at com.teammetallurgy.metallurgy.BlockList.initMetalSets(BlockList.java:163)
[18:39:30] [Client thread/WARN] [FML]: * at com.teammetallurgy.metallurgy.BlockList.init(BlockList.java:91)...
[18:39:30] [Client thread/WARN] [FML]: ****************************************
[18:39:31] [Client thread/WARN] [FML]: ****************************************
[18:39:31] [Client thread/WARN] [FML]: * A broken ore dictionary registration with name ingotTartarite has occurred. It adds an item (type: class com.teammetallurgy.metallurgy.metals.MetalItem) which is currently unknown to the game registry. This dictionary item can only support a single value when registered with ores like this, and NO I am not going to turn this spam off. Just register your ore dictionary entries after the GameRegistry.
TO USERS: YES this is a BUG in the mod Metallurgy 4 report it to them!
[18:39:31] [Client thread/WARN] [FML]: * at net.minecraftforge.oredict.OreDictionary.registerOreImpl(OreDictionary.java:534)
[18:39:31] [Client thread/WARN] [FML]: * at net.minecraftforge.oredict.OreDictionary.registerOre(OreDictionary.java:501)
[18:39:31] [Client thread/WARN] [FML]: * at com.teammetallurgy.metallurgy.metals.MetalSet.load(MetalSet.java:380)
[18:39:31] [Client thread/WARN] [FML]: * at com.teammetallurgy.metallurgy.BlockList.injectMetalSet(BlockList.java:201)
[18:39:31] [Client thread/WARN] [FML]: * at com.teammetallurgy.metallurgy.BlockList.initMetalSets(BlockList.java:163)
[18:39:31] [Client thread/WARN] [FML]: * at com.teammetallurgy.metallurgy.BlockList.init(BlockList.java:91)...
[18:39:31] [Client thread/WARN] [FML]: ****************************************
[18:39:31] [Client thread/WARN] [FML]: ****************************************
[18:39:31] [Client thread/WARN] [FML]: * A broken ore dictionary registration with name ingotIgnatius has occurred. It adds an item (type: class com.teammetallurgy.metallurgy.metals.MetalItem) which is currently unknown to the game registry. This dictionary item can only support a single value when registered with ores like this, and NO I am not going to turn this spam off. Just register your ore dictionary entries after the GameRegistry.
TO USERS: YES this is a BUG in the mod Metallurgy 4 report it to them!
[18:39:31] [Client thread/WARN] [FML]: * at net.minecraftforge.oredict.OreDictionary.registerOreImpl(OreDictionary.java:534)
[18:39:31] [Client thread/WARN] [FML]: * at net.minecraftforge.oredict.OreDictionary.registerOre(OreDictionary.java:501)
[18:39:31] [Client thread/WARN] [FML]: * at com.teammetallurgy.metallurgy.metals.MetalSet.load(MetalSet.java:380)
[18:39:31] [Client thread/WARN] [FML]: * at com.teammetallurgy.metallurgy.BlockList.injectMetalSet(BlockList.java:201)
[18:39:31] [Client thread/WARN] [FML]: * at com.teammetallurgy.metallurgy.BlockList.initMetalSets(BlockList.java:163)
[18:39:31] [Client thread/WARN] [FML]: * at com.teammetallurgy.metallurgy.BlockList.init(BlockList.java:91)...
[18:39:31] [Client thread/WARN] [FML]: ****************************************
[18:39:31] [Client thread/WARN] [FML]: ****************************************
[18:39:31] [Client thread/WARN] [FML]: * A broken ore dictionary registration with name ingotShadowIron has occurred. It adds an item (type: class com.teammetallurgy.metallurgy.metals.MetalItem) which is currently unknown to the game registry. This dictionary item can only support a single value when registered with ores like this, and NO I am not going to turn this spam off. Just register your ore dictionary entries after the GameRegistry.
TO USERS: YES this is a BUG in the mod Metallurgy 4 report it to them!
[18:39:31] [Client thread/WARN] [FML]: * at net.minecraftforge.oredict.OreDictionary.registerOreImpl(OreDictionary.java:534)
[18:39:31] [Client thread/WARN] [FML]: * at net.minecraftforge.oredict.OreDictionary.registerOre(OreDictionary.java:501)
[18:39:31] [Client thread/WARN] [FML]: * at com.teammetallurgy.metallurgy.metals.MetalSet.load(MetalSet.java:380)
[18:39:31] [Client thread/WARN] [FML]: * at com.teammetallurgy.metallurgy.BlockList.injectMetalSet(BlockList.java:201)
[18:39:31] [Client thread/WARN] [FML]: * at com.teammetallurgy.metallurgy.BlockList.initMetalSets(BlockList.java:163)
[18:39:31] [Client thread/WARN] [FML]: * at com.teammetallurgy.metallurgy.BlockList.init(BlockList.java:91)...
[18:39:31] [Client thread/WARN] [FML]: ****************************************
[18:39:31] [Client thread/WARN] [FML]: ****************************************
[18:39:31] [Client thread/WARN] [FML]: * A broken ore dictionary registration with name ingotLemurite has occurred. It adds an item (type: class com.teammetallurgy.metallurgy.metals.MetalItem) which is currently unknown to the game registry. This dictionary item can only support a single value when registered with ores like this, and NO I am not going to turn this spam off. Just register your ore dictionary entries after the GameRegistry.
TO USERS: YES this is a BUG in the mod Metallurgy 4 report it to them!
[18:39:31] [Client thread/WARN] [FML]: * at net.minecraftforge.oredict.OreDictionary.registerOreImpl(OreDictionary.java:534)
[18:39:31] [Client thread/WARN] [FML]: * at net.minecraftforge.oredict.OreDictionary.registerOre(OreDictionary.java:501)
[18:39:31] [Client thread/WARN] [FML]: * at com.teammetallurgy.metallurgy.metals.MetalSet.load(MetalSet.java:380)
[18:39:31] [Client thread/WARN] [FML]: * at com.teammetallurgy.metallurgy.BlockList.injectMetalSet(BlockList.java:201)
[18:39:31] [Client thread/WARN] [FML]: * at com.teammetallurgy.metallurgy.BlockList.initMetalSets(BlockList.java:163)
[18:39:31] [Client thread/WARN] [FML]: * at com.teammetallurgy.metallurgy.BlockList.init(BlockList.java:91)...
[18:39:31] [Client thread/WARN] [FML]: ****************************************
[18:39:31] [Client thread/WARN] [FML]: ****************************************
[18:39:31] [Client thread/WARN] [FML]: * A broken ore dictionary registration with name ingotMidasium has occurred. It adds an item (type: class com.teammetallurgy.metallurgy.metals.MetalItem) which is currently unknown to the game registry. This dictionary item can only support a single value when registered with ores like this, and NO I am not going to turn this spam off. Just register your ore dictionary entries after the GameRegistry.
TO USERS: YES this is a BUG in the mod Metallurgy 4 report it to them!
[18:39:31] [Client thread/WARN] [FML]: * at net.minecraftforge.oredict.OreDictionary.registerOreImpl(OreDictionary.java:534)
[18:39:31] [Client thread/WARN] [FML]: * at net.minecraftforge.oredict.OreDictionary.registerOre(OreDictionary.java:501)
[18:39:31] [Client thread/WARN] [FML]: * at com.teammetallurgy.metallurgy.metals.MetalSet.load(MetalSet.java:380)
[18:39:31] [Client thread/WARN] [FML]: * at com.teammetallurgy.metallurgy.BlockList.injectMetalSet(BlockList.java:201)
[18:39:31] [Client thread/WARN] [FML]: * at com.teammetallurgy.metallurgy.BlockList.initMetalSets(BlockList.java:163)
[18:39:31] [Client thread/WARN] [FML]: * at com.teammetallurgy.metallurgy.BlockList.init(BlockList.java:91)...
[18:39:31] [Client thread/WARN] [FML]: ****************************************
[18:39:31] [Client thread/WARN] [FML]: ****************************************
[18:39:31] [Client thread/WARN] [FML]: * A broken ore dictionary registration with name ingotVyroxeres has occurred. It adds an item (type: class com.teammetallurgy.metallurgy.metals.MetalItem) which is currently unknown to the game registry. This dictionary item can only support a single value when registered with ores like this, and NO I am not going to turn this spam off. Just register your ore dictionary entries after the GameRegistry.
TO USERS: YES this is a BUG in the mod Metallurgy 4 report it to them!
[18:39:31] [Client thread/WARN] [FML]: * at net.minecraftforge.oredict.OreDictionary.registerOreImpl(OreDictionary.java:534)
[18:39:31] [Client thread/WARN] [FML]: * at net.minecraftforge.oredict.OreDictionary.registerOre(OreDictionary.java:501)
[18:39:31] [Client thread/WARN] [FML]: * at com.teammetallurgy.metallurgy.metals.MetalSet.load(MetalSet.java:380)
[18:39:31] [Client thread/WARN] [FML]: * at com.teammetallurgy.metallurgy.BlockList.injectMetalSet(BlockList.java:201)
[18:39:31] [Client thread/WARN] [FML]: * at com.teammetallurgy.metallurgy.BlockList.initMetalSets(BlockList.java:163)
[18:39:31] [Client thread/WARN] [FML]: * at com.teammetallurgy.metallurgy.BlockList.init(BlockList.java:91)...
[18:39:31] [Client thread/WARN] [FML]: ****************************************
[18:39:31] [Client thread/WARN] [FML]: ****************************************
[18:39:31] [Client thread/WARN] [FML]: * A broken ore dictionary registration with name ingotCeruclase has occurred. It adds an item (type: class com.teammetallurgy.metallurgy.metals.MetalItem) which is currently unknown to the game registry. This dictionary item can only support a single value when registered with ores like this, and NO I am not going to turn this spam off. Just register your ore dictionary entries after the GameRegistry.
TO USERS: YES this is a BUG in the mod Metallurgy 4 report it to them!
[18:39:31] [Client thread/WARN] [FML]: * at net.minecraftforge.oredict.OreDictionary.registerOreImpl(OreDictionary.java:534)
[18:39:31] [Client thread/WARN] [FML]: * at net.minecraftforge.oredict.OreDictionary.registerOre(OreDictionary.java:501)
[18:39:31] [Client thread/WARN] [FML]: * at com.teammetallurgy.metallurgy.metals.MetalSet.load(MetalSet.java:380)
[18:39:31] [Client thread/WARN] [FML]: * at com.teammetallurgy.metallurgy.BlockList.injectMetalSet(BlockList.java:201)
[18:39:31] [Client thread/WARN] [FML]: * at com.teammetallurgy.metallurgy.BlockList.initMetalSets(BlockList.java:163)
[18:39:31] [Client thread/WARN] [FML]: * at com.teammetallurgy.metallurgy.BlockList.init(BlockList.java:91)...
[18:39:31] [Client thread/WARN] [FML]: ****************************************
[18:39:31] [Client thread/WARN] [FML]: ****************************************
[18:39:31] [Client thread/WARN] [FML]: * A broken ore dictionary registration with name ingotAlduorite has occurred. It adds an item (type: class com.teammetallurgy.metallurgy.metals.MetalItem) which is currently unknown to the game registry. This dictionary item can only support a single value when registered with ores like this, and NO I am not going to turn this spam off. Just register your ore dictionary entries after the GameRegistry.
TO USERS: YES this is a BUG in the mod Metallurgy 4 report it to them!
[18:39:31] [Client thread/WARN] [FML]: * at net.minecraftforge.oredict.OreDictionary.registerOreImpl(OreDictionary.java:534)
[18:39:31] [Client thread/WARN] [FML]: * at net.minecraftforge.oredict.OreDictionary.registerOre(OreDictionary.java:501)
[18:39:31] [Client thread/WARN] [FML]: * at com.teammetallurgy.metallurgy.metals.MetalSet.load(MetalSet.java:380)
[18:39:31] [Client thread/WARN] [FML]: * at com.teammetallurgy.metallurgy.BlockList.injectMetalSet(BlockList.java:201)
[18:39:31] [Client thread/WARN] [FML]: * at com.teammetallurgy.metallurgy.BlockList.initMetalSets(BlockList.java:163)
[18:39:31] [Client thread/WARN] [FML]: * at com.teammetallurgy.metallurgy.BlockList.init(BlockList.java:91)...
[18:39:31] [Client thread/WARN] [FML]: ****************************************
[18:39:31] [Client thread/WARN] [FML]: ****************************************
[18:39:31] [Client thread/WARN] [FML]: * A broken ore dictionary registration with name ingotKalendrite has occurred. It adds an item (type: class com.teammetallurgy.metallurgy.metals.MetalItem) which is currently unknown to the game registry. This dictionary item can only support a single value when registered with ores like this, and NO I am not going to turn this spam off. Just register your ore dictionary entries after the GameRegistry.
TO USERS: YES this is a BUG in the mod Metallurgy 4 report it to them!
[18:39:31] [Client thread/WARN] [FML]: * at net.minecraftforge.oredict.OreDictionary.registerOreImpl(OreDictionary.java:534)
[18:39:31] [Client thread/WARN] [FML]: * at net.minecraftforge.oredict.OreDictionary.registerOre(OreDictionary.java:501)
[18:39:31] [Client thread/WARN] [FML]: * at com.teammetallurgy.metallurgy.metals.MetalSet.load(MetalSet.java:380)
[18:39:31] [Client thread/WARN] [FML]: * at com.teammetallurgy.metallurgy.BlockList.injectMetalSet(BlockList.java:201)
[18:39:31] [Client thread/WARN] [FML]: * at com.teammetallurgy.metallurgy.BlockList.initMetalSets(BlockList.java:163)
[18:39:31] [Client thread/WARN] [FML]: * at com.teammetallurgy.metallurgy.BlockList.init(BlockList.java:91)...
[18:39:31] [Client thread/WARN] [FML]: ****************************************
[18:39:31] [Client thread/WARN] [FML]: ****************************************
[18:39:31] [Client thread/WARN] [FML]: * A broken ore dictionary registration with name ingotVulcanite has occurred. It adds an item (type: class com.teammetallurgy.metallurgy.metals.MetalItem) which is currently unknown to the game registry. This dictionary item can only support a single value when registered with ores like this, and NO I am not going to turn this spam off. Just register your ore dictionary entries after the GameRegistry.
TO USERS: YES this is a BUG in the mod Metallurgy 4 report it to them!
[18:39:31] [Client thread/WARN] [FML]: * at net.minecraftforge.oredict.OreDictionary.registerOreImpl(OreDictionary.java:534)
[18:39:31] [Client thread/WARN] [FML]: * at net.minecraftforge.oredict.OreDictionary.registerOre(OreDictionary.java:501)
[18:39:31] [Client thread/WARN] [FML]: * at com.teammetallurgy.metallurgy.metals.MetalSet.load(MetalSet.java:380)
[18:39:31] [Client thread/WARN] [FML]: * at com.teammetallurgy.metallurgy.BlockList.injectMetalSet(BlockList.java:201)
[18:39:31] [Client thread/WARN] [FML]: * at com.teammetallurgy.metallurgy.BlockList.initMetalSets(BlockList.java:163)
[18:39:31] [Client thread/WARN] [FML]: * at com.teammetallurgy.metallurgy.BlockList.init(BlockList.java:91)...
[18:39:31] [Client thread/WARN] [FML]: ****************************************
[18:39:31] [Client thread/WARN] [FML]: ****************************************
[18:39:31] [Client thread/WARN] [FML]: * A broken ore dictionary registration with name ingotSanguinite has occurred. It adds an item (type: class com.teammetallurgy.metallurgy.metals.MetalItem) which is currently unknown to the game registry. This dictionary item can only support a single value when registered with ores like this, and NO I am not going to turn this spam off. Just register your ore dictionary entries after the GameRegistry.
TO USERS: YES this is a BUG in the mod Metallurgy 4 report it to them!
[18:39:31] [Client thread/WARN] [FML]: * at net.minecraftforge.oredict.OreDictionary.registerOreImpl(OreDictionary.java:534)
[18:39:31] [Client thread/WARN] [FML]: * at net.minecraftforge.oredict.OreDictionary.registerOre(OreDictionary.java:501)
[18:39:31] [Client thread/WARN] [FML]: * at com.teammetallurgy.metallurgy.metals.MetalSet.load(MetalSet.java:380)
[18:39:31] [Client thread/WARN] [FML]: * at com.teammetallurgy.metallurgy.BlockList.injectMetalSet(BlockList.java:201)
[18:39:31] [Client thread/WARN] [FML]: * at com.teammetallurgy.metallurgy.BlockList.initMetalSets(BlockList.java:163)
[18:39:31] [Client thread/WARN] [FML]: * at com.teammetallurgy.metallurgy.BlockList.init(BlockList.java:91)...
[18:39:31] [Client thread/WARN] [FML]: ****************************************
[18:39:31] [Client thread/WARN] [FML]: ****************************************
[18:39:31] [Client thread/WARN] [FML]: * A broken ore dictionary registration with name ingotShadowSteel has occurred. It adds an item (type: class com.teammetallurgy.metallurgy.metals.MetalItem) which is currently unknown to the game registry. This dictionary item can only support a single value when registered with ores like this, and NO I am not going to turn this spam off. Just register your ore dictionary entries after the GameRegistry.
TO USERS: YES this is a BUG in the mod Metallurgy 4 report it to them!
[18:39:31] [Client thread/WARN] [FML]: * at net.minecraftforge.oredict.OreDictionary.registerOreImpl(OreDictionary.java:534)
[18:39:31] [Client thread/WARN] [FML]: * at net.minecraftforge.oredict.OreDictionary.registerOre(OreDictionary.java:501)
[18:39:31] [Client thread/WARN] [FML]: * at com.teammetallurgy.metallurgy.metals.MetalSet.load(MetalSet.java:380)
[18:39:31] [Client thread/WARN] [FML]: * at com.teammetallurgy.metallurgy.BlockList.injectMetalSet(BlockList.java:201)
[18:39:31] [Client thread/WARN] [FML]: * at com.teammetallurgy.metallurgy.BlockList.initMetalSets(BlockList.java:163)
[18:39:31] [Client thread/WARN] [FML]: * at com.teammetallurgy.metallurgy.BlockList.init(BlockList.java:91)...
[18:39:31] [Client thread/WARN] [FML]: ****************************************
[18:39:31] [Client thread/WARN] [FML]: ****************************************
[18:39:31] [Client thread/WARN] [FML]: * A broken ore dictionary registration with name ingotInolashite has occurred. It adds an item (type: class com.teammetallurgy.metallurgy.metals.MetalItem) which is currently unknown to the game registry. This dictionary item can only support a single value when registered with ores like this, and NO I am not going to turn this spam off. Just register your ore dictionary entries after the GameRegistry.
TO USERS: YES this is a BUG in the mod Metallurgy 4 report it to them!
[18:39:31] [Client thread/WARN] [FML]: * at net.minecraftforge.oredict.OreDictionary.registerOreImpl(OreDictionary.java:534)
[18:39:31] [Client thread/WARN] [FML]: * at net.minecraftforge.oredict.OreDictionary.registerOre(OreDictionary.java:501)
[18:39:31] [Client thread/WARN] [FML]: * at com.teammetallurgy.metallurgy.metals.MetalSet.load(MetalSet.java:380)
[18:39:31] [Client thread/WARN] [FML]: * at com.teammetallurgy.metallurgy.BlockList.injectMetalSet(BlockList.java:201)
[18:39:31] [Client thread/WARN] [FML]: * at com.teammetallurgy.metallurgy.BlockList.initMetalSets(BlockList.java:163)
[18:39:31] [Client thread/WARN] [FML]: * at com.teammetallurgy.metallurgy.BlockList.init(BlockList.java:91)...
[18:39:31] [Client thread/WARN] [FML]: ****************************************
[18:39:31] [Client thread/WARN] [FML]: ****************************************
[18:39:31] [Client thread/WARN] [FML]: * A broken ore dictionary registration with name ingotAmordrine has occurred. It adds an item (type: class com.teammetallurgy.metallurgy.metals.MetalItem) which is currently unknown to the game registry. This dictionary item can only support a single value when registered with ores like this, and NO I am not going to turn this spam off. Just register your ore dictionary entries after the GameRegistry.
TO USERS: YES this is a BUG in the mod Metallurgy 4 report it to them!
[18:39:31] [Client thread/WARN] [FML]: * at net.minecraftforge.oredict.OreDictionary.registerOreImpl(OreDictionary.java:534)
[18:39:31] [Client thread/WARN] [FML]: * at net.minecraftforge.oredict.OreDictionary.registerOre(OreDictionary.java:501)
[18:39:31] [Client thread/WARN] [FML]: * at com.teammetallurgy.metallurgy.metals.MetalSet.load(MetalSet.java:380)
[18:39:31] [Client thread/WARN] [FML]: * at com.teammetallurgy.metallurgy.BlockList.injectMetalSet(BlockList.java:201)
[18:39:31] [Client thread/WARN] [FML]: * at com.teammetallurgy.metallurgy.BlockList.initMetalSets(BlockList.java:163)
[18:39:31] [Client thread/WARN] [FML]: * at com.teammetallurgy.metallurgy.BlockList.init(BlockList.java:91)...
[18:39:31] [Client thread/WARN] [FML]: ****************************************
[18:39:31] [Client thread/WARN] [FML]: ****************************************
[18:39:31] [Client thread/WARN] [FML]: * A broken ore dictionary registration with name ingotZinc has occurred. It adds an item (type: class com.teammetallurgy.metallurgy.metals.MetalItem) which is currently unknown to the game registry. This dictionary item can only support a single value when registered with ores like this, and NO I am not going to turn this spam off. Just register your ore dictionary entries after the GameRegistry.
TO USERS: YES this is a BUG in the mod Metallurgy 4 report it to them!
[18:39:31] [Client thread/WARN] [FML]: * at net.minecraftforge.oredict.OreDictionary.registerOreImpl(OreDictionary.java:534)
[18:39:31] [Client thread/WARN] [FML]: * at net.minecraftforge.oredict.OreDictionary.registerOre(OreDictionary.java:501)
[18:39:31] [Client thread/WARN] [FML]: * at com.teammetallurgy.metallurgy.metals.MetalSet.load(MetalSet.java:380)
[18:39:31] [Client thread/WARN] [FML]: * at com.teammetallurgy.metallurgy.BlockList.injectMetalSet(BlockList.java:201)
[18:39:31] [Client thread/WARN] [FML]: * at com.teammetallurgy.metallurgy.BlockList.initMetalSets(BlockList.java:163)
[18:39:31] [Client thread/WARN] [FML]: * at com.teammetallurgy.metallurgy.BlockList.init(BlockList.java:91)...
[18:39:31] [Client thread/WARN] [FML]: ****************************************
[18:39:31] [Client thread/WARN] [FML]: ****************************************
[18:39:31] [Client thread/WARN] [FML]: * A broken ore dictionary registration with name ingotSilver has occurred. It adds an item (type: class com.teammetallurgy.metallurgy.metals.MetalItem) which is currently unknown to the game registry. This dictionary item can only support a single value when registered with ores like this, and NO I am not going to turn this spam off. Just register your ore dictionary entries after the GameRegistry.
TO USERS: YES this is a BUG in the mod Metallurgy 4 report it to them!
[18:39:31] [Client thread/WARN] [FML]: * at net.minecraftforge.oredict.OreDictionary.registerOreImpl(OreDictionary.java:534)
[18:39:31] [Client thread/WARN] [FML]: * at net.minecraftforge.oredict.OreDictionary.registerOre(OreDictionary.java:501)
[18:39:31] [Client thread/WARN] [FML]: * at com.teammetallurgy.metallurgy.metals.MetalSet.load(MetalSet.java:380)
[18:39:31] [Client thread/WARN] [FML]: * at com.teammetallurgy.metallurgy.BlockList.injectMetalSet(BlockList.java:201)
[18:39:31] [Client thread/WARN] [FML]: * at com.teammetallurgy.metallurgy.BlockList.initMetalSets(BlockList.java:163)
[18:39:31] [Client thread/WARN] [FML]: * at com.teammetallurgy.metallurgy.BlockList.init(BlockList.java:91)...
[18:39:31] [Client thread/WARN] [FML]: ****************************************
[18:39:31] [Client thread/WARN] [FML]: ****************************************
[18:39:31] [Client thread/WARN] [FML]: * A broken ore dictionary registration with name ingotPlatinum has occurred. It adds an item (type: class com.teammetallurgy.metallurgy.metals.MetalItem) which is currently unknown to the game registry. This dictionary item can only support a single value when registered with ores like this, and NO I am not going to turn this spam off. Just register your ore dictionary entries after the GameRegistry.
TO USERS: YES this is a BUG in the mod Metallurgy 4 report it to them!
[18:39:31] [Client thread/WARN] [FML]: * at net.minecraftforge.oredict.OreDictionary.registerOreImpl(OreDictionary.java:534)
[18:39:31] [Client thread/WARN] [FML]: * at net.minecraftforge.oredict.OreDictionary.registerOre(OreDictionary.java:501)
[18:39:31] [Client thread/WARN] [FML]: * at com.teammetallurgy.metallurgy.metals.MetalSet.load(MetalSet.java:380)
[18:39:31] [Client thread/WARN] [FML]: * at com.teammetallurgy.metallurgy.BlockList.injectMetalSet(BlockList.java:201)
[18:39:31] [Client thread/WARN] [FML]: * at com.teammetallurgy.metallurgy.BlockList.initMetalSets(BlockList.java:163)
[18:39:31] [Client thread/WARN] [FML]: * at com.teammetallurgy.metallurgy.BlockList.init(BlockList.java:91)...
[18:39:31] [Client thread/WARN] [FML]: ****************************************
[18:39:31] [Client thread/WARN] [FML]: ****************************************
[18:39:31] [Client thread/WARN] [FML]: * A broken ore dictionary registration with name ingotBrass has occurred. It adds an item (type: class com.teammetallurgy.metallurgy.metals.MetalItem) which is currently unknown to the game registry. This dictionary item can only support a single value when registered with ores like this, and NO I am not going to turn this spam off. Just register your ore dictionary entries after the GameRegistry.
TO USERS: YES this is a BUG in the mod Metallurgy 4 report it to them!
[18:39:31] [Client thread/WARN] [FML]: * at net.minecraftforge.oredict.OreDictionary.registerOreImpl(OreDictionary.java:534)
[18:39:31] [Client thread/WARN] [FML]: * at net.minecraftforge.oredict.OreDictionary.registerOre(OreDictionary.java:501)
[18:39:31] [Client thread/WARN] [FML]: * at com.teammetallurgy.metallurgy.metals.MetalSet.load(MetalSet.java:380)
[18:39:31] [Client thread/WARN] [FML]: * at com.teammetallurgy.metallurgy.BlockList.injectMetalSet(BlockList.java:201)
[18:39:31] [Client thread/WARN] [FML]: * at com.teammetallurgy.metallurgy.BlockList.initMetalSets(BlockList.java:163)
[18:39:31] [Client thread/WARN] [FML]: * at com.teammetallurgy.metallurgy.BlockList.init(BlockList.java:91)...
[18:39:31] [Client thread/WARN] [FML]: ****************************************
[18:39:31] [Client thread/WARN] [FML]: ****************************************
[18:39:31] [Client thread/WARN] [FML]: * A broken ore dictionary registration with name ingotElectrum has occurred. It adds an item (type: class com.teammetallurgy.metallurgy.metals.MetalItem) which is currently unknown to the game registry. This dictionary item can only support a single value when registered with ores like this, and NO I am not going to turn this spam off. Just register your ore dictionary entries after the GameRegistry.
TO USERS: YES this is a BUG in the mod Metallurgy 4 report it to them!
[18:39:31] [Client thread/WARN] [FML]: * at net.minecraftforge.oredict.OreDictionary.registerOreImpl(OreDictionary.java:534)
[18:39:31] [Client thread/WARN] [FML]: * at net.minecraftforge.oredict.OreDictionary.registerOre(OreDictionary.java:501)
[18:39:31] [Client thread/WARN] [FML]: * at com.teammetallurgy.metallurgy.metals.MetalSet.load(MetalSet.java:380)
[18:39:31] [Client thread/WARN] [FML]: * at com.teammetallurgy.metallurgy.BlockList.injectMetalSet(BlockList.java:201)
[18:39:31] [Client thread/WARN] [FML]: * at com.teammetallurgy.metallurgy.BlockList.initMetalSets(BlockList.java:163)
[18:39:31] [Client thread/WARN] [FML]: * at com.teammetallurgy.metallurgy.BlockList.init(BlockList.java:91)...
[18:39:31] [Client thread/WARN] [FML]: ****************************************
[18:39:34] [Client thread/INFO] [eplus]: Initializing Configurations.
[18:39:34] [Client thread/INFO] [eplus]: Plugin loaded: TConPlugin
[18:39:34] [Client thread/INFO] [eplus]: Plugin loaded: ThaumcraftPlugin
[18:39:34] [Client thread/INFO] [eplus]: Plugin loaded: Treecapitatior
[18:39:34] [Client thread/INFO] [eplus]: Plugin initialized in PreInit... ThaumcraftPlugin
[18:39:34] [Client thread/INFO] [eplus]: Plugin initialized in PreInit... Treecapitatior
[18:39:34] [Client thread/INFO] [eplus]: Initializing Blocks.
[18:39:35] [Client thread/INFO] [eplus]: Initializing Items.
[18:39:35] [Client thread/INFO] [ExtrabiomesXL]: Initializing.
[18:39:36] [Client thread/INFO] [ExtrabiomesXL]: BLACK = DYE_BLACK
[18:39:36] [Client thread/INFO] [ExtrabiomesXL]: BLUE = DYE_BLUE
[18:39:36] [Client thread/INFO] [ExtrabiomesXL]: BROWN = DYE_BROWN
[18:39:36] [Client thread/INFO] [ExtrabiomesXL]: WHITE = DYE_WHITE
[18:39:36] [Client thread/INFO] [ExtrabiomesXL]: Module CAUTIA is enabled.
[18:39:36] [Client thread/INFO] [ExtrabiomesXL]: Module FABRICA is enabled.
[18:39:36] [Client thread/INFO] [ExtrabiomesXL]: Module AMICA is enabled.
[18:39:36] [Client thread/INFO] [ExtrabiomesXL]: Name: ExtrabiomesXL:double_woodslab
[18:39:36] [Client thread/INFO] [FML]: Applying holder lookups
[18:39:36] [Client thread/INFO] [FML]: Holder lookups applied
[18:39:36] [Client thread/INFO] [FML]: Injecting itemstacks
[18:39:36] [Client thread/INFO] [FML]: Itemstack injection complete
[OptiFine] *** Reloading textures ***
[OptiFine] Resource packs: Default
[18:39:37] [Sound Library Loader/INFO] [STDOUT]: [paulscode.sound.SoundSystemLogger:message:69]:
[18:39:37] [Sound Library Loader/INFO] [STDOUT]: [paulscode.sound.SoundSystemLogger:message:69]: Starting up SoundSystem...
[18:39:37] [Thread-8/INFO] [STDOUT]: [paulscode.sound.SoundSystemLogger:message:69]: Initializing LWJGL OpenAL
[18:39:37] [Thread-8/INFO] [STDOUT]: [paulscode.sound.SoundSystemLogger:message:69]: (The LWJGL binding of OpenAL. For more information, see http://www.lwjgl.org)
2015-11-20 18:39:37.475 java[476:17290] 18:39:37.475 WARNING: 140: This application, or a library it uses, is using the deprecated Carbon Component Manager for hosting Audio Units. Support for this will be removed in a future release. Also, this makes the host incompatible with version 3 audio units. Please transition to the API's in AudioComponent.h.
[18:39:37] [Thread-8/INFO] [STDOUT]: [paulscode.sound.SoundSystemLogger:message:69]: OpenAL initialized.
[18:39:37] [Sound Library Loader/INFO] [STDOUT]: [paulscode.sound.SoundSystemLogger:message:69]:
[18:39:37] [Sound Library Loader/INFO]: Sound engine started
[18:39:39] [Client thread/ERROR]: ########## GL ERROR ##########
[18:39:39] [Client thread/ERROR]: @ Pre startup
[18:39:39] [Client thread/ERROR]: 1281: Invalid value
[18:39:39] [Client thread/INFO] [STDOUT]: [net.minecraft.client.Minecraft:func_71377_b:349]: ---- Minecraft Crash Report ----
// Surprise! Haha. Well, this is awkward.

Time: 20/11/15 06:39 PM
Description: Initializing game

java.lang.NoSuchMethodError: net.minecraft.client.renderer.texture.TextureMap.<init>(ILjava/lang/String;Z)V
at net.minecraft.client.Minecraft.func_71384_a(Minecraft.java:540)
at net.minecraft.client.Minecraft.func_99999_d(Minecraft.java:878)
at net.minecraft.client.main.Main.main(SourceFile:148)
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:497)
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 net.minecraft.client.Minecraft.func_71384_a(Minecraft.java:540)

-- Initialization --
Details:
Stacktrace:
at net.minecraft.client.Minecraft.func_99999_d(Minecraft.java:878)
at net.minecraft.client.main.Main.main(SourceFile:148)
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:497)
at net.minecraft.launchwrapper.Launch.launch(Launch.java:135)
at net.minecraft.launchwrapper.Launch.main(Launch.java:28)

-- System Details --
Details:
Minecraft Version: 1.7.10
Operating System: Mac OS X (x86_64) version 10.11.1
Java Version: 1.8.0_66, Oracle Corporation
Java VM Version: Java HotSpot(TM) 64-Bit Server VM (mixed mode), Oracle Corporation
Memory: 115906728 bytes (110 MB) / 312078336 bytes (297 MB) up to 2134114304 bytes (2035 MB)
JVM Flags: 5 total; -Xmx2G -XX:+UseConcMarkSweepGC -XX:+CMSIncrementalMode -XX:-UseAdaptiveSizePolicy -Xmn128M
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.05 FML v7.10.99.99 Minecraft Forge 10.13.4.1566 Optifine OptiFine_1.7.10_HD_U_A3 22 mods loaded, 22 mods active
States: 'U' = Unloaded 'L' = Loaded 'C' = Constructed 'H' = Pre-initialized 'I' = Initialized 'J' = Post-initialized 'A' = Available 'D' = Disabled 'E' = Errored
UCH mcp{9.05} [Minecraft Coder Pack] (minecraft.jar)
UCH FML{7.10.99.99} [Forge Mod Loader] (forge-1.7.10-10.13.4.1566-1.7.10.jar)
UCH Forge{10.13.4.1566} [Minecraft Forge] (forge-1.7.10-10.13.4.1566-1.7.10.jar)
UCH DamageIndicatorsMod{3.2.0} [Damage Indicators] ([1.7.10]DamageIndicatorsMod-3.2.0.jar)
UCH deconstruction{2.2.5} [The Deconstruction Mod] ([MC1.7.10]deconstruction[v2.2.5].jar)
UCH abyssalcraft{1.8.9.6} [AbyssalCraft] (AbyssalCraft-1.7.10-1.8.9.6.jar)
UCH MetallurgyCore{4.0.4} [Metallurgy Core] (MetallurgyCore-1.7.10-4.0.4.18.jar)
UCH Metallurgy{4.0.6} [Metallurgy 4] (Metallurgy-1.7.10-4.0.6.80.jar)
UCH B0bGrowsOre{2.1.0} [B0bGary's Growable Ores] (B0bGary's Growable Ores-2.1.0 for 1.7.10.jar)
UCH Backpack{2.0.1} [Backpack] (backpack-2.0.1-1.7.x.jar)
UCH BiblioCraft{1.10.3} [BiblioCraft] (BiblioCraft[v1.10.3][MC1.7.10].jar)
UCH AWWayofTime{v1.3.3} [Blood Magic: Alchemical Wizardry] (BloodMagic-1.7.10-1.3.3-17.jar)
UCH chococraft{4.1.5} [Clienthax's ChocoCraft] (ChocoCraft-4.1.5.jar)
UCH CustomSpawner{3.3.0} [DrZhark's CustomSpawner] (CustomMobSpawner 3.3.0.zip)
UCH MoCreatures{6.3.1} [DrZhark's Mo'Creatures Mod] (DrZharks MoCreatures Mod v6.3.1.zip)
UCH eplus{3.0.2-d} [Enchanting Plus] (EnchantingPlus-1.7.10-3.0.2-d.jar)
UCH ExtrabiomesXL{3.16.0} [ExtrabiomesXL] (extrabiomesxl_1.7.10-3.16.0.jar)
UCH grim3212core{V0.2 - 1.7.10} [Grim3212 Core] (Grim3212 Core-V0.2 - 1.7.10.jar)
UCH GrimoireOfGaia{1.0.0} [Grimoire of Gaia 3] (GrimoireOfGaia3-1.7.10-1.0.9.jar)
UCH imc{1.6} [Improving Minecraft] (Improving Minecraft-1.6.jar)
UCH LotsOfFood{1.7.10} [Lots of Food] (Lots of Food-1.7.10 v4.jar)
UCH mexicanmod{1.2.1} [Mexican Mod] (MexicanMod_1.2.1_1.7.10.jar)
Launched Version: 1.7.10-Forge10.13.4.1566-1.7.10
LWJGL: 2.9.1
OpenGL: ATI Radeon HD 2400 XT OpenGL Engine GL version 2.1 ATI-10.0.40, ATI Technologies Inc.
GL Caps: Using GL 1.3 multitexturing.
Using framebuffer objects because ARB_framebuffer_object is supported and separate blending is supported.
Anisotropic filtering is supported and maximum anisotropy is 16.
Shaders are available because OpenGL 2.1 is supported.

Is Modded: Definitely; Client brand changed to 'fml,forge'
Type: Client (map_client.txt)
Resource Packs: []
Current Language: Español (México)
Profiler Position: N/A (disabled)
Vec3 Pool Size: 0 (0 bytes; 0 MB) allocated, 0 (0 bytes; 0 MB) used
Anisotropic Filtering: Off (1)
[18:39:39] [Client thread/INFO] [STDOUT]: [net.minecraft.client.Minecraft:func_71377_b:359]: #@[email protected]# Game crashed! Crash report saved to: #@[email protected]# /Users/carlos/Library/Application Support/minecraft/crash-reports/crash-2015-11-20_18.39.39-client.txt
AL lib: (EE) alc_cleanup: 1 device not closed