API tools faq
paste
Advertisement
Guest User

Chrashlog MC

a guest
Jan 6th, 2016
142
0
Never
Add comment
Not a member of Pastebin yet? Sign Up, it unlocks many cool features!
text 129.88 KB | None | 0 0
raw download clone embed print report
  1. [16:20:56] [Client thread/INFO] [ESM]: Loading ESM Global Config
  2. [16:20:57] [Client thread/INFO] [FastCraft]: FastCraft 1.21 loaded.
  3. [16:20:57] [Thread-18/INFO] [FastCraft]: You are using the latest suitable version.
  4. [16:20:57] [Client thread/INFO] [STDOUT]: [com.inventorypets.InventoryPets:syncConfig:1493]: Custom Pet config synced.
  5. [16:20:57] [Client thread/INFO] [FML]: InvTweaks: invtweaks.InvTweaksObfuscation
  6. [16:20:57] [Client thread/INFO] [STDOUT]: [lycanite.lycanitesmobs.LycanitesMobs:printInfo:377]: [LycanitesMobs] [Info] Config lycanitesmobs-version created successfully.
  7. [16:20:57] [Client thread/INFO] [STDOUT]: [lycanite.lycanitesmobs.LycanitesMobs:printInfo:377]: [LycanitesMobs] [Info] Config lycanitesmobs-general created successfully.
  8. [16:20:57] [Client thread/INFO] [STDOUT]: [lycanite.lycanitesmobs.LycanitesMobs:printInfo:377]: [LycanitesMobs] [Info] Config lycanitesmobs-spawning created successfully.
  9. [16:20:57] [Client thread/INFO] [STDOUT]: [lycanite.lycanitesmobs.LycanitesMobs:printInfo:377]: [LycanitesMobs] [Info] Config lycanitesmobs-mobevents created successfully.
  10. [16:20:57] [Client thread/INFO] [STDOUT]: [lycanite.lycanitesmobs.LycanitesMobs:printInfo:377]: [LycanitesMobs] [Info] Config lycanitesmobs-itemlists created successfully.
  11. [16:20:57] [Client thread/INFO] [STDOUT]: [lycanite.lycanitesmobs.LycanitesMobs:printInfo:377]: [LycanitesMobs] [Info] Config arcticmobs-spawning created successfully.
  12. [16:20:57] [Client thread/INFO] [STDOUT]: [lycanite.lycanitesmobs.LycanitesMobs:printInfo:377]: [LycanitesMobs] [Info] Config arcticmobs-general created successfully.
  13. [16:20:58] [Client thread/INFO] [STDOUT]: [lycanite.lycanitesmobs.LycanitesMobs:printInfo:377]: [LycanitesMobs] [Info] Config demonmobs-spawning created successfully.
  14. [16:20:58] [Client thread/INFO] [STDOUT]: [lycanite.lycanitesmobs.LycanitesMobs:printInfo:377]: [LycanitesMobs] [Info] Config demonmobs-general created successfully.
  15. [16:20:58] [Client thread/INFO] [STDOUT]: [lycanite.lycanitesmobs.LycanitesMobs:printInfo:377]: [LycanitesMobs] [Info] Config desertmobs-spawning created successfully.
  16. [16:20:58] [Client thread/INFO] [STDOUT]: [lycanite.lycanitesmobs.LycanitesMobs:printInfo:377]: [LycanitesMobs] [Info] Config desertmobs-general created successfully.
  17. [16:20:58] [Client thread/INFO] [STDOUT]: [lycanite.lycanitesmobs.LycanitesMobs:printInfo:377]: [LycanitesMobs] [Info] Config forestmobs-spawning created successfully.
  18. [16:20:58] [Client thread/INFO] [STDOUT]: [lycanite.lycanitesmobs.LycanitesMobs:printInfo:377]: [LycanitesMobs] [Info] Config forestmobs-general created successfully.
  19. [16:20:58] [Client thread/INFO] [STDOUT]: [lycanite.lycanitesmobs.LycanitesMobs:printInfo:377]: [LycanitesMobs] [Info] Config freshwatermobs-spawning created successfully.
  20. [16:20:58] [Client thread/INFO] [STDOUT]: [lycanite.lycanitesmobs.LycanitesMobs:printInfo:377]: [LycanitesMobs] [Info] Config freshwatermobs-general created successfully.
  21. [16:20:58] [Client thread/INFO] [STDOUT]: [lycanite.lycanitesmobs.LycanitesMobs:printInfo:377]: [LycanitesMobs] [Info] Config infernomobs-spawning created successfully.
  22. [16:20:58] [Client thread/INFO] [STDOUT]: [lycanite.lycanitesmobs.LycanitesMobs:printInfo:377]: [LycanitesMobs] [Info] Config infernomobs-general created successfully.
  23. [16:20:58] [Client thread/INFO] [STDOUT]: [lycanite.lycanitesmobs.LycanitesMobs:printInfo:377]: [LycanitesMobs] [Info] Config junglemobs-spawning created successfully.
  24. [16:20:58] [Client thread/INFO] [STDOUT]: [lycanite.lycanitesmobs.LycanitesMobs:printInfo:377]: [LycanitesMobs] [Info] Config junglemobs-general created successfully.
  25. [16:20:58] [Client thread/INFO] [STDOUT]: [lycanite.lycanitesmobs.LycanitesMobs:printInfo:377]: [LycanitesMobs] [Info] Config mountainmobs-spawning created successfully.
  26. [16:20:58] [Client thread/INFO] [STDOUT]: [lycanite.lycanitesmobs.LycanitesMobs:printInfo:377]: [LycanitesMobs] [Info] Config mountainmobs-general created successfully.
  27. [16:20:58] [Client thread/INFO] [STDOUT]: [lycanite.lycanitesmobs.LycanitesMobs:printInfo:377]: [LycanitesMobs] [Info] Config plainsmobs-spawning created successfully.
  28. [16:20:58] [Client thread/INFO] [STDOUT]: [lycanite.lycanitesmobs.LycanitesMobs:printInfo:377]: [LycanitesMobs] [Info] Config plainsmobs-general created successfully.
  29. [16:20:58] [Client thread/INFO] [STDOUT]: [lycanite.lycanitesmobs.LycanitesMobs:printInfo:377]: [LycanitesMobs] [Info] Config saltwatermobs-spawning created successfully.
  30. [16:20:58] [Client thread/INFO] [STDOUT]: [lycanite.lycanitesmobs.LycanitesMobs:printInfo:377]: [LycanitesMobs] [Info] Config saltwatermobs-general created successfully.
  31. [16:20:58] [Client thread/INFO] [STDOUT]: [lycanite.lycanitesmobs.LycanitesMobs:printInfo:377]: [LycanitesMobs] [Info] Config shadowmobs-spawning created successfully.
  32. [16:20:58] [Client thread/INFO] [STDOUT]: [lycanite.lycanitesmobs.LycanitesMobs:printInfo:377]: [LycanitesMobs] [Info] Config shadowmobs-general created successfully.
  33. [16:20:58] [Client thread/INFO] [STDOUT]: [lycanite.lycanitesmobs.LycanitesMobs:printInfo:377]: [LycanitesMobs] [Info] Config swampmobs-spawning created successfully.
  34. [16:20:58] [Client thread/INFO] [STDOUT]: [lycanite.lycanitesmobs.LycanitesMobs:printInfo:377]: [LycanitesMobs] [Info] Config swampmobs-general created successfully.
  35. [16:20:58] [Client thread/INFO] [Mantle]: Mantle (1.7.10-0.3.2.jenkins184) -- Preparing for launch.
  36. [16:20:58] [Client thread/INFO] [Mantle]: Entering preinitialization phase.
  37. [16:20:58] [Client thread/INFO] [Mantle]: Loading configuration from disk.
  38. [16:20:58] [Client thread/INFO] [Mantle]: Configuration load completed.
  39. [16:20:58] [Client thread/INFO] [RadixCore]: Loaded language en_US for mca.
  40. [16:20:58] [Client thread/WARN] [FML]: ****************************************
  41. [16:20:58] [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.
  42. TO USERS: YES this is a BUG in the mod Metallurgy 4 report it to them!
  43. [16:20:58] [Client thread/WARN] [FML]: * at net.minecraftforge.oredict.OreDictionary.registerOreImpl(OreDictionary.java:534)
  44. [16:20:58] [Client thread/WARN] [FML]: * at net.minecraftforge.oredict.OreDictionary.registerOre(OreDictionary.java:501)
  45. [16:20:58] [Client thread/WARN] [FML]: * at com.teammetallurgy.metallurgy.metals.MetalSet.load(MetalSet.java:380)
  46. [16:20:58] [Client thread/WARN] [FML]: * at com.teammetallurgy.metallurgy.BlockList.injectMetalSet(BlockList.java:201)
  47. [16:20:58] [Client thread/WARN] [FML]: * at com.teammetallurgy.metallurgy.BlockList.initMetalSets(BlockList.java:163)
  48. [16:20:58] [Client thread/WARN] [FML]: * at com.teammetallurgy.metallurgy.BlockList.init(BlockList.java:91)...
  49. [16:20:58] [Client thread/WARN] [FML]: ****************************************
  50. [16:20:58] [Client thread/WARN] [FML]: ****************************************
  51. [16:20:58] [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.
  52. TO USERS: YES this is a BUG in the mod Metallurgy 4 report it to them!
  53. [16:20:58] [Client thread/WARN] [FML]: * at net.minecraftforge.oredict.OreDictionary.registerOreImpl(OreDictionary.java:534)
  54. [16:20:58] [Client thread/WARN] [FML]: * at net.minecraftforge.oredict.OreDictionary.registerOre(OreDictionary.java:501)
  55. [16:20:58] [Client thread/WARN] [FML]: * at com.teammetallurgy.metallurgy.metals.MetalSet.load(MetalSet.java:380)
  56. [16:20:58] [Client thread/WARN] [FML]: * at com.teammetallurgy.metallurgy.BlockList.injectMetalSet(BlockList.java:201)
  57. [16:20:58] [Client thread/WARN] [FML]: * at com.teammetallurgy.metallurgy.BlockList.initMetalSets(BlockList.java:163)
  58. [16:20:58] [Client thread/WARN] [FML]: * at com.teammetallurgy.metallurgy.BlockList.init(BlockList.java:91)...
  59. [16:20:58] [Client thread/WARN] [FML]: ****************************************
  60. [16:20:58] [Client thread/WARN] [FML]: ****************************************
  61. [16:20:58] [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.
  62. TO USERS: YES this is a BUG in the mod Metallurgy 4 report it to them!
  63. [16:20:58] [Client thread/WARN] [FML]: * at net.minecraftforge.oredict.OreDictionary.registerOreImpl(OreDictionary.java:534)
  64. [16:20:58] [Client thread/WARN] [FML]: * at net.minecraftforge.oredict.OreDictionary.registerOre(OreDictionary.java:501)
  65. [16:20:58] [Client thread/WARN] [FML]: * at com.teammetallurgy.metallurgy.metals.MetalSet.load(MetalSet.java:380)
  66. [16:20:58] [Client thread/WARN] [FML]: * at com.teammetallurgy.metallurgy.BlockList.injectMetalSet(BlockList.java:201)
  67. [16:20:58] [Client thread/WARN] [FML]: * at com.teammetallurgy.metallurgy.BlockList.initMetalSets(BlockList.java:163)
  68. [16:20:58] [Client thread/WARN] [FML]: * at com.teammetallurgy.metallurgy.BlockList.init(BlockList.java:91)...
  69. [16:20:58] [Client thread/WARN] [FML]: ****************************************
  70. [16:20:58] [Client thread/WARN] [FML]: ****************************************
  71. [16:20:58] [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.
  72. TO USERS: YES this is a BUG in the mod Metallurgy 4 report it to them!
  73. [16:20:58] [Client thread/WARN] [FML]: * at net.minecraftforge.oredict.OreDictionary.registerOreImpl(OreDictionary.java:534)
  74. [16:20:58] [Client thread/WARN] [FML]: * at net.minecraftforge.oredict.OreDictionary.registerOre(OreDictionary.java:501)
  75. [16:20:58] [Client thread/WARN] [FML]: * at com.teammetallurgy.metallurgy.metals.MetalSet.load(MetalSet.java:380)
  76. [16:20:58] [Client thread/WARN] [FML]: * at com.teammetallurgy.metallurgy.BlockList.injectMetalSet(BlockList.java:201)
  77. [16:20:58] [Client thread/WARN] [FML]: * at com.teammetallurgy.metallurgy.BlockList.initMetalSets(BlockList.java:163)
  78. [16:20:58] [Client thread/WARN] [FML]: * at com.teammetallurgy.metallurgy.BlockList.init(BlockList.java:91)...
  79. [16:20:58] [Client thread/WARN] [FML]: ****************************************
  80. [16:20:58] [Client thread/WARN] [FML]: ****************************************
  81. [16:20:58] [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.
  82. TO USERS: YES this is a BUG in the mod Metallurgy 4 report it to them!
  83. [16:20:58] [Client thread/WARN] [FML]: * at net.minecraftforge.oredict.OreDictionary.registerOreImpl(OreDictionary.java:534)
  84. [16:20:58] [Client thread/WARN] [FML]: * at net.minecraftforge.oredict.OreDictionary.registerOre(OreDictionary.java:501)
  85. [16:20:58] [Client thread/WARN] [FML]: * at com.teammetallurgy.metallurgy.metals.MetalSet.load(MetalSet.java:380)
  86. [16:20:58] [Client thread/WARN] [FML]: * at com.teammetallurgy.metallurgy.BlockList.injectMetalSet(BlockList.java:201)
  87. [16:20:58] [Client thread/WARN] [FML]: * at com.teammetallurgy.metallurgy.BlockList.initMetalSets(BlockList.java:163)
  88. [16:20:58] [Client thread/WARN] [FML]: * at com.teammetallurgy.metallurgy.BlockList.init(BlockList.java:91)...
  89. [16:20:58] [Client thread/WARN] [FML]: ****************************************
  90. [16:20:58] [Client thread/WARN] [FML]: ****************************************
  91. [16:20:58] [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.
  92. TO USERS: YES this is a BUG in the mod Metallurgy 4 report it to them!
  93. [16:20:58] [Client thread/WARN] [FML]: * at net.minecraftforge.oredict.OreDictionary.registerOreImpl(OreDictionary.java:534)
  94. [16:20:58] [Client thread/WARN] [FML]: * at net.minecraftforge.oredict.OreDictionary.registerOre(OreDictionary.java:501)
  95. [16:20:58] [Client thread/WARN] [FML]: * at com.teammetallurgy.metallurgy.metals.MetalSet.load(MetalSet.java:380)
  96. [16:20:58] [Client thread/WARN] [FML]: * at com.teammetallurgy.metallurgy.BlockList.injectMetalSet(BlockList.java:201)
  97. [16:20:58] [Client thread/WARN] [FML]: * at com.teammetallurgy.metallurgy.BlockList.initMetalSets(BlockList.java:163)
  98. [16:20:58] [Client thread/WARN] [FML]: * at com.teammetallurgy.metallurgy.BlockList.init(BlockList.java:91)...
  99. [16:20:58] [Client thread/WARN] [FML]: ****************************************
  100. [16:20:58] [Client thread/WARN] [FML]: ****************************************
  101. [16:20:58] [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.
  102. TO USERS: YES this is a BUG in the mod Metallurgy 4 report it to them!
  103. [16:20:58] [Client thread/WARN] [FML]: * at net.minecraftforge.oredict.OreDictionary.registerOreImpl(OreDictionary.java:534)
  104. [16:20:58] [Client thread/WARN] [FML]: * at net.minecraftforge.oredict.OreDictionary.registerOre(OreDictionary.java:501)
  105. [16:20:58] [Client thread/WARN] [FML]: * at com.teammetallurgy.metallurgy.metals.MetalSet.load(MetalSet.java:380)
  106. [16:20:58] [Client thread/WARN] [FML]: * at com.teammetallurgy.metallurgy.BlockList.injectMetalSet(BlockList.java:201)
  107. [16:20:58] [Client thread/WARN] [FML]: * at com.teammetallurgy.metallurgy.BlockList.initMetalSets(BlockList.java:163)
  108. [16:20:58] [Client thread/WARN] [FML]: * at com.teammetallurgy.metallurgy.BlockList.init(BlockList.java:91)...
  109. [16:20:58] [Client thread/WARN] [FML]: ****************************************
  110. [16:20:58] [Client thread/WARN] [FML]: ****************************************
  111. [16:20:58] [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.
  112. TO USERS: YES this is a BUG in the mod Metallurgy 4 report it to them!
  113. [16:20:58] [Client thread/WARN] [FML]: * at net.minecraftforge.oredict.OreDictionary.registerOreImpl(OreDictionary.java:534)
  114. [16:20:58] [Client thread/WARN] [FML]: * at net.minecraftforge.oredict.OreDictionary.registerOre(OreDictionary.java:501)
  115. [16:20:58] [Client thread/WARN] [FML]: * at com.teammetallurgy.metallurgy.metals.MetalSet.load(MetalSet.java:380)
  116. [16:20:58] [Client thread/WARN] [FML]: * at com.teammetallurgy.metallurgy.BlockList.injectMetalSet(BlockList.java:201)
  117. [16:20:58] [Client thread/WARN] [FML]: * at com.teammetallurgy.metallurgy.BlockList.initMetalSets(BlockList.java:163)
  118. [16:20:58] [Client thread/WARN] [FML]: * at com.teammetallurgy.metallurgy.BlockList.init(BlockList.java:91)...
  119. [16:20:58] [Client thread/WARN] [FML]: ****************************************
  120. [16:20:58] [Client thread/WARN] [FML]: ****************************************
  121. [16:20:58] [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.
  122. TO USERS: YES this is a BUG in the mod Metallurgy 4 report it to them!
  123. [16:20:58] [Client thread/WARN] [FML]: * at net.minecraftforge.oredict.OreDictionary.registerOreImpl(OreDictionary.java:534)
  124. [16:20:58] [Client thread/WARN] [FML]: * at net.minecraftforge.oredict.OreDictionary.registerOre(OreDictionary.java:501)
  125. [16:20:58] [Client thread/WARN] [FML]: * at com.teammetallurgy.metallurgy.metals.MetalSet.load(MetalSet.java:380)
  126. [16:20:58] [Client thread/WARN] [FML]: * at com.teammetallurgy.metallurgy.BlockList.injectMetalSet(BlockList.java:201)
  127. [16:20:58] [Client thread/WARN] [FML]: * at com.teammetallurgy.metallurgy.BlockList.initMetalSets(BlockList.java:163)
  128. [16:20:58] [Client thread/WARN] [FML]: * at com.teammetallurgy.metallurgy.BlockList.init(BlockList.java:91)...
  129. [16:20:58] [Client thread/WARN] [FML]: ****************************************
  130. [16:20:58] [Client thread/WARN] [FML]: ****************************************
  131. [16:20:58] [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.
  132. TO USERS: YES this is a BUG in the mod Metallurgy 4 report it to them!
  133. [16:20:58] [Client thread/WARN] [FML]: * at net.minecraftforge.oredict.OreDictionary.registerOreImpl(OreDictionary.java:534)
  134. [16:20:58] [Client thread/WARN] [FML]: * at net.minecraftforge.oredict.OreDictionary.registerOre(OreDictionary.java:501)
  135. [16:20:58] [Client thread/WARN] [FML]: * at com.teammetallurgy.metallurgy.metals.MetalSet.load(MetalSet.java:380)
  136. [16:20:58] [Client thread/WARN] [FML]: * at com.teammetallurgy.metallurgy.BlockList.injectMetalSet(BlockList.java:201)
  137. [16:20:58] [Client thread/WARN] [FML]: * at com.teammetallurgy.metallurgy.BlockList.initMetalSets(BlockList.java:163)
  138. [16:20:58] [Client thread/WARN] [FML]: * at com.teammetallurgy.metallurgy.BlockList.init(BlockList.java:91)...
  139. [16:20:58] [Client thread/WARN] [FML]: ****************************************
  140. [16:20:58] [Client thread/WARN] [FML]: ****************************************
  141. [16:20:58] [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.
  142. TO USERS: YES this is a BUG in the mod Metallurgy 4 report it to them!
  143. [16:20:58] [Client thread/WARN] [FML]: * at net.minecraftforge.oredict.OreDictionary.registerOreImpl(OreDictionary.java:534)
  144. [16:20:58] [Client thread/WARN] [FML]: * at net.minecraftforge.oredict.OreDictionary.registerOre(OreDictionary.java:501)
  145. [16:20:58] [Client thread/WARN] [FML]: * at com.teammetallurgy.metallurgy.metals.MetalSet.load(MetalSet.java:380)
  146. [16:20:58] [Client thread/WARN] [FML]: * at com.teammetallurgy.metallurgy.BlockList.injectMetalSet(BlockList.java:201)
  147. [16:20:58] [Client thread/WARN] [FML]: * at com.teammetallurgy.metallurgy.BlockList.initMetalSets(BlockList.java:163)
  148. [16:20:58] [Client thread/WARN] [FML]: * at com.teammetallurgy.metallurgy.BlockList.init(BlockList.java:91)...
  149. [16:20:58] [Client thread/WARN] [FML]: ****************************************
  150. [16:20:58] [Client thread/WARN] [FML]: ****************************************
  151. [16:20:58] [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.
  152. TO USERS: YES this is a BUG in the mod Metallurgy 4 report it to them!
  153. [16:20:58] [Client thread/WARN] [FML]: * at net.minecraftforge.oredict.OreDictionary.registerOreImpl(OreDictionary.java:534)
  154. [16:20:58] [Client thread/WARN] [FML]: * at net.minecraftforge.oredict.OreDictionary.registerOre(OreDictionary.java:501)
  155. [16:20:58] [Client thread/WARN] [FML]: * at com.teammetallurgy.metallurgy.metals.MetalSet.load(MetalSet.java:380)
  156. [16:20:58] [Client thread/WARN] [FML]: * at com.teammetallurgy.metallurgy.BlockList.injectMetalSet(BlockList.java:201)
  157. [16:20:58] [Client thread/WARN] [FML]: * at com.teammetallurgy.metallurgy.BlockList.initMetalSets(BlockList.java:163)
  158. [16:20:58] [Client thread/WARN] [FML]: * at com.teammetallurgy.metallurgy.BlockList.init(BlockList.java:91)...
  159. [16:20:58] [Client thread/WARN] [FML]: ****************************************
  160. [16:20:58] [Client thread/WARN] [FML]: ****************************************
  161. [16:20:58] [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.
  162. TO USERS: YES this is a BUG in the mod Metallurgy 4 report it to them!
  163. [16:20:58] [Client thread/WARN] [FML]: * at net.minecraftforge.oredict.OreDictionary.registerOreImpl(OreDictionary.java:534)
  164. [16:20:58] [Client thread/WARN] [FML]: * at net.minecraftforge.oredict.OreDictionary.registerOre(OreDictionary.java:501)
  165. [16:20:58] [Client thread/WARN] [FML]: * at com.teammetallurgy.metallurgy.metals.MetalSet.load(MetalSet.java:380)
  166. [16:20:58] [Client thread/WARN] [FML]: * at com.teammetallurgy.metallurgy.BlockList.injectMetalSet(BlockList.java:201)
  167. [16:20:58] [Client thread/WARN] [FML]: * at com.teammetallurgy.metallurgy.BlockList.initMetalSets(BlockList.java:163)
  168. [16:20:58] [Client thread/WARN] [FML]: * at com.teammetallurgy.metallurgy.BlockList.init(BlockList.java:91)...
  169. [16:20:58] [Client thread/WARN] [FML]: ****************************************
  170. [16:20:58] [Client thread/WARN] [FML]: ****************************************
  171. [16:20:58] [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.
  172. TO USERS: YES this is a BUG in the mod Metallurgy 4 report it to them!
  173. [16:20:58] [Client thread/WARN] [FML]: * at net.minecraftforge.oredict.OreDictionary.registerOreImpl(OreDictionary.java:534)
  174. [16:20:58] [Client thread/WARN] [FML]: * at net.minecraftforge.oredict.OreDictionary.registerOre(OreDictionary.java:501)
  175. [16:20:58] [Client thread/WARN] [FML]: * at com.teammetallurgy.metallurgy.metals.MetalSet.load(MetalSet.java:380)
  176. [16:20:58] [Client thread/WARN] [FML]: * at com.teammetallurgy.metallurgy.BlockList.injectMetalSet(BlockList.java:201)
  177. [16:20:58] [Client thread/WARN] [FML]: * at com.teammetallurgy.metallurgy.BlockList.initMetalSets(BlockList.java:163)
  178. [16:20:58] [Client thread/WARN] [FML]: * at com.teammetallurgy.metallurgy.BlockList.init(BlockList.java:91)...
  179. [16:20:58] [Client thread/WARN] [FML]: ****************************************
  180. [16:20:58] [Client thread/WARN] [FML]: ****************************************
  181. [16:20:58] [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.
  182. TO USERS: YES this is a BUG in the mod Metallurgy 4 report it to them!
  183. [16:20:58] [Client thread/WARN] [FML]: * at net.minecraftforge.oredict.OreDictionary.registerOreImpl(OreDictionary.java:534)
  184. [16:20:58] [Client thread/WARN] [FML]: * at net.minecraftforge.oredict.OreDictionary.registerOre(OreDictionary.java:501)
  185. [16:20:58] [Client thread/WARN] [FML]: * at com.teammetallurgy.metallurgy.metals.MetalSet.load(MetalSet.java:380)
  186. [16:20:58] [Client thread/WARN] [FML]: * at com.teammetallurgy.metallurgy.BlockList.injectMetalSet(BlockList.java:201)
  187. [16:20:58] [Client thread/WARN] [FML]: * at com.teammetallurgy.metallurgy.BlockList.initMetalSets(BlockList.java:163)
  188. [16:20:58] [Client thread/WARN] [FML]: * at com.teammetallurgy.metallurgy.BlockList.init(BlockList.java:91)...
  189. [16:20:58] [Client thread/WARN] [FML]: ****************************************
  190. [16:20:58] [Client thread/WARN] [FML]: ****************************************
  191. [16:20:58] [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.
  192. TO USERS: YES this is a BUG in the mod Metallurgy 4 report it to them!
  193. [16:20:58] [Client thread/WARN] [FML]: * at net.minecraftforge.oredict.OreDictionary.registerOreImpl(OreDictionary.java:534)
  194. [16:20:58] [Client thread/WARN] [FML]: * at net.minecraftforge.oredict.OreDictionary.registerOre(OreDictionary.java:501)
  195. [16:20:58] [Client thread/WARN] [FML]: * at com.teammetallurgy.metallurgy.metals.MetalSet.load(MetalSet.java:380)
  196. [16:20:58] [Client thread/WARN] [FML]: * at com.teammetallurgy.metallurgy.BlockList.injectMetalSet(BlockList.java:201)
  197. [16:20:58] [Client thread/WARN] [FML]: * at com.teammetallurgy.metallurgy.BlockList.initMetalSets(BlockList.java:163)
  198. [16:20:58] [Client thread/WARN] [FML]: * at com.teammetallurgy.metallurgy.BlockList.init(BlockList.java:91)...
  199. [16:20:58] [Client thread/WARN] [FML]: ****************************************
  200. [16:20:58] [Client thread/WARN] [FML]: ****************************************
  201. [16:20:58] [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.
  202. TO USERS: YES this is a BUG in the mod Metallurgy 4 report it to them!
  203. [16:20:58] [Client thread/WARN] [FML]: * at net.minecraftforge.oredict.OreDictionary.registerOreImpl(OreDictionary.java:534)
  204. [16:20:58] [Client thread/WARN] [FML]: * at net.minecraftforge.oredict.OreDictionary.registerOre(OreDictionary.java:501)
  205. [16:20:58] [Client thread/WARN] [FML]: * at com.teammetallurgy.metallurgy.metals.MetalSet.load(MetalSet.java:380)
  206. [16:20:58] [Client thread/WARN] [FML]: * at com.teammetallurgy.metallurgy.BlockList.injectMetalSet(BlockList.java:201)
  207. [16:20:58] [Client thread/WARN] [FML]: * at com.teammetallurgy.metallurgy.BlockList.initMetalSets(BlockList.java:163)
  208. [16:20:58] [Client thread/WARN] [FML]: * at com.teammetallurgy.metallurgy.BlockList.init(BlockList.java:91)...
  209. [16:20:58] [Client thread/WARN] [FML]: ****************************************
  210. [16:20:58] [Client thread/WARN] [FML]: ****************************************
  211. [16:20:58] [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.
  212. TO USERS: YES this is a BUG in the mod Metallurgy 4 report it to them!
  213. [16:20:58] [Client thread/WARN] [FML]: * at net.minecraftforge.oredict.OreDictionary.registerOreImpl(OreDictionary.java:534)
  214. [16:20:58] [Client thread/WARN] [FML]: * at net.minecraftforge.oredict.OreDictionary.registerOre(OreDictionary.java:501)
  215. [16:20:58] [Client thread/WARN] [FML]: * at com.teammetallurgy.metallurgy.metals.MetalSet.load(MetalSet.java:380)
  216. [16:20:58] [Client thread/WARN] [FML]: * at com.teammetallurgy.metallurgy.BlockList.injectMetalSet(BlockList.java:201)
  217. [16:20:58] [Client thread/WARN] [FML]: * at com.teammetallurgy.metallurgy.BlockList.initMetalSets(BlockList.java:163)
  218. [16:20:58] [Client thread/WARN] [FML]: * at com.teammetallurgy.metallurgy.BlockList.init(BlockList.java:91)...
  219. [16:20:58] [Client thread/WARN] [FML]: ****************************************
  220. [16:20:58] [Client thread/WARN] [FML]: ****************************************
  221. [16:20:58] [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.
  222. TO USERS: YES this is a BUG in the mod Metallurgy 4 report it to them!
  223. [16:20:58] [Client thread/WARN] [FML]: * at net.minecraftforge.oredict.OreDictionary.registerOreImpl(OreDictionary.java:534)
  224. [16:20:58] [Client thread/WARN] [FML]: * at net.minecraftforge.oredict.OreDictionary.registerOre(OreDictionary.java:501)
  225. [16:20:58] [Client thread/WARN] [FML]: * at com.teammetallurgy.metallurgy.metals.MetalSet.load(MetalSet.java:380)
  226. [16:20:58] [Client thread/WARN] [FML]: * at com.teammetallurgy.metallurgy.BlockList.injectMetalSet(BlockList.java:201)
  227. [16:20:58] [Client thread/WARN] [FML]: * at com.teammetallurgy.metallurgy.BlockList.initMetalSets(BlockList.java:163)
  228. [16:20:58] [Client thread/WARN] [FML]: * at com.teammetallurgy.metallurgy.BlockList.init(BlockList.java:91)...
  229. [16:20:58] [Client thread/WARN] [FML]: ****************************************
  230. [16:20:58] [Client thread/WARN] [FML]: ****************************************
  231. [16:20:58] [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.
  232. TO USERS: YES this is a BUG in the mod Metallurgy 4 report it to them!
  233. [16:20:58] [Client thread/WARN] [FML]: * at net.minecraftforge.oredict.OreDictionary.registerOreImpl(OreDictionary.java:534)
  234. [16:20:58] [Client thread/WARN] [FML]: * at net.minecraftforge.oredict.OreDictionary.registerOre(OreDictionary.java:501)
  235. [16:20:58] [Client thread/WARN] [FML]: * at com.teammetallurgy.metallurgy.metals.MetalSet.load(MetalSet.java:380)
  236. [16:20:58] [Client thread/WARN] [FML]: * at com.teammetallurgy.metallurgy.BlockList.injectMetalSet(BlockList.java:201)
  237. [16:20:58] [Client thread/WARN] [FML]: * at com.teammetallurgy.metallurgy.BlockList.initMetalSets(BlockList.java:163)
  238. [16:20:58] [Client thread/WARN] [FML]: * at com.teammetallurgy.metallurgy.BlockList.init(BlockList.java:91)...
  239. [16:20:58] [Client thread/WARN] [FML]: ****************************************
  240. [16:20:58] [Client thread/WARN] [FML]: ****************************************
  241. [16:20:58] [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.
  242. TO USERS: YES this is a BUG in the mod Metallurgy 4 report it to them!
  243. [16:20:58] [Client thread/WARN] [FML]: * at net.minecraftforge.oredict.OreDictionary.registerOreImpl(OreDictionary.java:534)
  244. [16:20:58] [Client thread/WARN] [FML]: * at net.minecraftforge.oredict.OreDictionary.registerOre(OreDictionary.java:501)
  245. [16:20:58] [Client thread/WARN] [FML]: * at com.teammetallurgy.metallurgy.metals.MetalSet.load(MetalSet.java:380)
  246. [16:20:58] [Client thread/WARN] [FML]: * at com.teammetallurgy.metallurgy.BlockList.injectMetalSet(BlockList.java:201)
  247. [16:20:58] [Client thread/WARN] [FML]: * at com.teammetallurgy.metallurgy.BlockList.initMetalSets(BlockList.java:163)
  248. [16:20:58] [Client thread/WARN] [FML]: * at com.teammetallurgy.metallurgy.BlockList.init(BlockList.java:91)...
  249. [16:20:58] [Client thread/WARN] [FML]: ****************************************
  250. [16:20:58] [Client thread/WARN] [FML]: ****************************************
  251. [16:20:58] [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.
  252. TO USERS: YES this is a BUG in the mod Metallurgy 4 report it to them!
  253. [16:20:58] [Client thread/WARN] [FML]: * at net.minecraftforge.oredict.OreDictionary.registerOreImpl(OreDictionary.java:534)
  254. [16:20:58] [Client thread/WARN] [FML]: * at net.minecraftforge.oredict.OreDictionary.registerOre(OreDictionary.java:501)
  255. [16:20:58] [Client thread/WARN] [FML]: * at com.teammetallurgy.metallurgy.metals.MetalSet.load(MetalSet.java:380)
  256. [16:20:58] [Client thread/WARN] [FML]: * at com.teammetallurgy.metallurgy.BlockList.injectMetalSet(BlockList.java:201)
  257. [16:20:58] [Client thread/WARN] [FML]: * at com.teammetallurgy.metallurgy.BlockList.initMetalSets(BlockList.java:163)
  258. [16:20:58] [Client thread/WARN] [FML]: * at com.teammetallurgy.metallurgy.BlockList.init(BlockList.java:91)...
  259. [16:20:58] [Client thread/WARN] [FML]: ****************************************
  260. [16:20:58] [Client thread/WARN] [FML]: ****************************************
  261. [16:20:58] [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.
  262. TO USERS: YES this is a BUG in the mod Metallurgy 4 report it to them!
  263. [16:20:58] [Client thread/WARN] [FML]: * at net.minecraftforge.oredict.OreDictionary.registerOreImpl(OreDictionary.java:534)
  264. [16:20:58] [Client thread/WARN] [FML]: * at net.minecraftforge.oredict.OreDictionary.registerOre(OreDictionary.java:501)
  265. [16:20:58] [Client thread/WARN] [FML]: * at com.teammetallurgy.metallurgy.metals.MetalSet.load(MetalSet.java:380)
  266. [16:20:58] [Client thread/WARN] [FML]: * at com.teammetallurgy.metallurgy.BlockList.injectMetalSet(BlockList.java:201)
  267. [16:20:58] [Client thread/WARN] [FML]: * at com.teammetallurgy.metallurgy.BlockList.initMetalSets(BlockList.java:163)
  268. [16:20:58] [Client thread/WARN] [FML]: * at com.teammetallurgy.metallurgy.BlockList.init(BlockList.java:91)...
  269. [16:20:58] [Client thread/WARN] [FML]: ****************************************
  270. [16:20:58] [Client thread/WARN] [FML]: ****************************************
  271. [16:20:58] [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.
  272. TO USERS: YES this is a BUG in the mod Metallurgy 4 report it to them!
  273. [16:20:58] [Client thread/WARN] [FML]: * at net.minecraftforge.oredict.OreDictionary.registerOreImpl(OreDictionary.java:534)
  274. [16:20:58] [Client thread/WARN] [FML]: * at net.minecraftforge.oredict.OreDictionary.registerOre(OreDictionary.java:501)
  275. [16:20:58] [Client thread/WARN] [FML]: * at com.teammetallurgy.metallurgy.metals.MetalSet.load(MetalSet.java:380)
  276. [16:20:58] [Client thread/WARN] [FML]: * at com.teammetallurgy.metallurgy.BlockList.injectMetalSet(BlockList.java:201)
  277. [16:20:58] [Client thread/WARN] [FML]: * at com.teammetallurgy.metallurgy.BlockList.initMetalSets(BlockList.java:163)
  278. [16:20:58] [Client thread/WARN] [FML]: * at com.teammetallurgy.metallurgy.BlockList.init(BlockList.java:91)...
  279. [16:20:58] [Client thread/WARN] [FML]: ****************************************
  280. [16:20:58] [Client thread/WARN] [FML]: ****************************************
  281. [16:20:58] [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.
  282. TO USERS: YES this is a BUG in the mod Metallurgy 4 report it to them!
  283. [16:20:58] [Client thread/WARN] [FML]: * at net.minecraftforge.oredict.OreDictionary.registerOreImpl(OreDictionary.java:534)
  284. [16:20:58] [Client thread/WARN] [FML]: * at net.minecraftforge.oredict.OreDictionary.registerOre(OreDictionary.java:501)
  285. [16:20:58] [Client thread/WARN] [FML]: * at com.teammetallurgy.metallurgy.metals.MetalSet.load(MetalSet.java:380)
  286. [16:20:58] [Client thread/WARN] [FML]: * at com.teammetallurgy.metallurgy.BlockList.injectMetalSet(BlockList.java:201)
  287. [16:20:58] [Client thread/WARN] [FML]: * at com.teammetallurgy.metallurgy.BlockList.initMetalSets(BlockList.java:163)
  288. [16:20:58] [Client thread/WARN] [FML]: * at com.teammetallurgy.metallurgy.BlockList.init(BlockList.java:91)...
  289. [16:20:58] [Client thread/WARN] [FML]: ****************************************
  290. [16:20:58] [Client thread/WARN] [FML]: ****************************************
  291. [16:20:58] [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.
  292. TO USERS: YES this is a BUG in the mod Metallurgy 4 report it to them!
  293. [16:20:58] [Client thread/WARN] [FML]: * at net.minecraftforge.oredict.OreDictionary.registerOreImpl(OreDictionary.java:534)
  294. [16:20:58] [Client thread/WARN] [FML]: * at net.minecraftforge.oredict.OreDictionary.registerOre(OreDictionary.java:501)
  295. [16:20:58] [Client thread/WARN] [FML]: * at com.teammetallurgy.metallurgy.metals.MetalSet.load(MetalSet.java:380)
  296. [16:20:58] [Client thread/WARN] [FML]: * at com.teammetallurgy.metallurgy.BlockList.injectMetalSet(BlockList.java:201)
  297. [16:20:58] [Client thread/WARN] [FML]: * at com.teammetallurgy.metallurgy.BlockList.initMetalSets(BlockList.java:163)
  298. [16:20:58] [Client thread/WARN] [FML]: * at com.teammetallurgy.metallurgy.BlockList.init(BlockList.java:91)...
  299. [16:20:58] [Client thread/WARN] [FML]: ****************************************
  300. [16:20:58] [Client thread/WARN] [FML]: ****************************************
  301. [16:20:58] [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.
  302. TO USERS: YES this is a BUG in the mod Metallurgy 4 report it to them!
  303. [16:20:58] [Client thread/WARN] [FML]: * at net.minecraftforge.oredict.OreDictionary.registerOreImpl(OreDictionary.java:534)
  304. [16:20:58] [Client thread/WARN] [FML]: * at net.minecraftforge.oredict.OreDictionary.registerOre(OreDictionary.java:501)
  305. [16:20:58] [Client thread/WARN] [FML]: * at com.teammetallurgy.metallurgy.metals.MetalSet.load(MetalSet.java:380)
  306. [16:20:58] [Client thread/WARN] [FML]: * at com.teammetallurgy.metallurgy.BlockList.injectMetalSet(BlockList.java:201)
  307. [16:20:58] [Client thread/WARN] [FML]: * at com.teammetallurgy.metallurgy.BlockList.initMetalSets(BlockList.java:163)
  308. [16:20:58] [Client thread/WARN] [FML]: * at com.teammetallurgy.metallurgy.BlockList.init(BlockList.java:91)...
  309. [16:20:58] [Client thread/WARN] [FML]: ****************************************
  310. [16:20:58] [Client thread/WARN] [FML]: ****************************************
  311. [16:20:58] [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.
  312. TO USERS: YES this is a BUG in the mod Metallurgy 4 report it to them!
  313. [16:20:58] [Client thread/WARN] [FML]: * at net.minecraftforge.oredict.OreDictionary.registerOreImpl(OreDictionary.java:534)
  314. [16:20:58] [Client thread/WARN] [FML]: * at net.minecraftforge.oredict.OreDictionary.registerOre(OreDictionary.java:501)
  315. [16:20:58] [Client thread/WARN] [FML]: * at com.teammetallurgy.metallurgy.metals.MetalSet.load(MetalSet.java:380)
  316. [16:20:58] [Client thread/WARN] [FML]: * at com.teammetallurgy.metallurgy.BlockList.injectMetalSet(BlockList.java:201)
  317. [16:20:58] [Client thread/WARN] [FML]: * at com.teammetallurgy.metallurgy.BlockList.initMetalSets(BlockList.java:163)
  318. [16:20:58] [Client thread/WARN] [FML]: * at com.teammetallurgy.metallurgy.BlockList.init(BlockList.java:91)...
  319. [16:20:58] [Client thread/WARN] [FML]: ****************************************
  320. [16:20:58] [Client thread/WARN] [FML]: ****************************************
  321. [16:20:58] [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.
  322. TO USERS: YES this is a BUG in the mod Metallurgy 4 report it to them!
  323. [16:20:58] [Client thread/WARN] [FML]: * at net.minecraftforge.oredict.OreDictionary.registerOreImpl(OreDictionary.java:534)
  324. [16:20:58] [Client thread/WARN] [FML]: * at net.minecraftforge.oredict.OreDictionary.registerOre(OreDictionary.java:501)
  325. [16:20:58] [Client thread/WARN] [FML]: * at com.teammetallurgy.metallurgy.metals.MetalSet.load(MetalSet.java:380)
  326. [16:20:58] [Client thread/WARN] [FML]: * at com.teammetallurgy.metallurgy.BlockList.injectMetalSet(BlockList.java:201)
  327. [16:20:58] [Client thread/WARN] [FML]: * at com.teammetallurgy.metallurgy.BlockList.initMetalSets(BlockList.java:163)
  328. [16:20:58] [Client thread/WARN] [FML]: * at com.teammetallurgy.metallurgy.BlockList.init(BlockList.java:91)...
  329. [16:20:58] [Client thread/WARN] [FML]: ****************************************
  330. [16:20:58] [Client thread/WARN] [FML]: ****************************************
  331. [16:20:58] [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.
  332. TO USERS: YES this is a BUG in the mod Metallurgy 4 report it to them!
  333. [16:20:58] [Client thread/WARN] [FML]: * at net.minecraftforge.oredict.OreDictionary.registerOreImpl(OreDictionary.java:534)
  334. [16:20:58] [Client thread/WARN] [FML]: * at net.minecraftforge.oredict.OreDictionary.registerOre(OreDictionary.java:501)
  335. [16:20:58] [Client thread/WARN] [FML]: * at com.teammetallurgy.metallurgy.metals.MetalSet.load(MetalSet.java:380)
  336. [16:20:58] [Client thread/WARN] [FML]: * at com.teammetallurgy.metallurgy.BlockList.injectMetalSet(BlockList.java:201)
  337. [16:20:58] [Client thread/WARN] [FML]: * at com.teammetallurgy.metallurgy.BlockList.initMetalSets(BlockList.java:163)
  338. [16:20:58] [Client thread/WARN] [FML]: * at com.teammetallurgy.metallurgy.BlockList.init(BlockList.java:91)...
  339. [16:20:58] [Client thread/WARN] [FML]: ****************************************
  340. [16:20:58] [Client thread/WARN] [FML]: ****************************************
  341. [16:20:58] [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.
  342. TO USERS: YES this is a BUG in the mod Metallurgy 4 report it to them!
  343. [16:20:58] [Client thread/WARN] [FML]: * at net.minecraftforge.oredict.OreDictionary.registerOreImpl(OreDictionary.java:534)
  344. [16:20:58] [Client thread/WARN] [FML]: * at net.minecraftforge.oredict.OreDictionary.registerOre(OreDictionary.java:501)
  345. [16:20:58] [Client thread/WARN] [FML]: * at com.teammetallurgy.metallurgy.metals.MetalSet.load(MetalSet.java:380)
  346. [16:20:58] [Client thread/WARN] [FML]: * at com.teammetallurgy.metallurgy.BlockList.injectMetalSet(BlockList.java:201)
  347. [16:20:58] [Client thread/WARN] [FML]: * at com.teammetallurgy.metallurgy.BlockList.initMetalSets(BlockList.java:163)
  348. [16:20:58] [Client thread/WARN] [FML]: * at com.teammetallurgy.metallurgy.BlockList.init(BlockList.java:91)...
  349. [16:20:58] [Client thread/WARN] [FML]: ****************************************
  350. [16:20:58] [Client thread/WARN] [FML]: ****************************************
  351. [16:20:58] [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.
  352. TO USERS: YES this is a BUG in the mod Metallurgy 4 report it to them!
  353. [16:20:58] [Client thread/WARN] [FML]: * at net.minecraftforge.oredict.OreDictionary.registerOreImpl(OreDictionary.java:534)
  354. [16:20:58] [Client thread/WARN] [FML]: * at net.minecraftforge.oredict.OreDictionary.registerOre(OreDictionary.java:501)
  355. [16:20:58] [Client thread/WARN] [FML]: * at com.teammetallurgy.metallurgy.metals.MetalSet.load(MetalSet.java:380)
  356. [16:20:58] [Client thread/WARN] [FML]: * at com.teammetallurgy.metallurgy.BlockList.injectMetalSet(BlockList.java:201)
  357. [16:20:58] [Client thread/WARN] [FML]: * at com.teammetallurgy.metallurgy.BlockList.initMetalSets(BlockList.java:163)
  358. [16:20:58] [Client thread/WARN] [FML]: * at com.teammetallurgy.metallurgy.BlockList.init(BlockList.java:91)...
  359. [16:20:58] [Client thread/WARN] [FML]: ****************************************
  360. [16:20:58] [Client thread/WARN] [FML]: ****************************************
  361. [16:20:58] [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.
  362. TO USERS: YES this is a BUG in the mod Metallurgy 4 report it to them!
  363. [16:20:58] [Client thread/WARN] [FML]: * at net.minecraftforge.oredict.OreDictionary.registerOreImpl(OreDictionary.java:534)
  364. [16:20:58] [Client thread/WARN] [FML]: * at net.minecraftforge.oredict.OreDictionary.registerOre(OreDictionary.java:501)
  365. [16:20:58] [Client thread/WARN] [FML]: * at com.teammetallurgy.metallurgy.metals.MetalSet.load(MetalSet.java:380)
  366. [16:20:58] [Client thread/WARN] [FML]: * at com.teammetallurgy.metallurgy.BlockList.injectMetalSet(BlockList.java:201)
  367. [16:20:58] [Client thread/WARN] [FML]: * at com.teammetallurgy.metallurgy.BlockList.initMetalSets(BlockList.java:163)
  368. [16:20:58] [Client thread/WARN] [FML]: * at com.teammetallurgy.metallurgy.BlockList.init(BlockList.java:91)...
  369. [16:20:58] [Client thread/WARN] [FML]: ****************************************
  370. [16:20:58] [Client thread/WARN] [FML]: ****************************************
  371. [16:20:58] [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.
  372. TO USERS: YES this is a BUG in the mod Metallurgy 4 report it to them!
  373. [16:20:58] [Client thread/WARN] [FML]: * at net.minecraftforge.oredict.OreDictionary.registerOreImpl(OreDictionary.java:534)
  374. [16:20:58] [Client thread/WARN] [FML]: * at net.minecraftforge.oredict.OreDictionary.registerOre(OreDictionary.java:501)
  375. [16:20:58] [Client thread/WARN] [FML]: * at com.teammetallurgy.metallurgy.metals.MetalSet.load(MetalSet.java:380)
  376. [16:20:58] [Client thread/WARN] [FML]: * at com.teammetallurgy.metallurgy.BlockList.injectMetalSet(BlockList.java:201)
  377. [16:20:58] [Client thread/WARN] [FML]: * at com.teammetallurgy.metallurgy.BlockList.initMetalSets(BlockList.java:163)
  378. [16:20:58] [Client thread/WARN] [FML]: * at com.teammetallurgy.metallurgy.BlockList.init(BlockList.java:91)...
  379. [16:20:58] [Client thread/WARN] [FML]: ****************************************
  380. [16:20:58] [Client thread/WARN] [FML]: ****************************************
  381. [16:20:58] [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.
  382. TO USERS: YES this is a BUG in the mod Metallurgy 4 report it to them!
  383. [16:20:58] [Client thread/WARN] [FML]: * at net.minecraftforge.oredict.OreDictionary.registerOreImpl(OreDictionary.java:534)
  384. [16:20:58] [Client thread/WARN] [FML]: * at net.minecraftforge.oredict.OreDictionary.registerOre(OreDictionary.java:501)
  385. [16:20:58] [Client thread/WARN] [FML]: * at com.teammetallurgy.metallurgy.metals.MetalSet.load(MetalSet.java:380)
  386. [16:20:58] [Client thread/WARN] [FML]: * at com.teammetallurgy.metallurgy.BlockList.injectMetalSet(BlockList.java:201)
  387. [16:20:58] [Client thread/WARN] [FML]: * at com.teammetallurgy.metallurgy.BlockList.initMetalSets(BlockList.java:163)
  388. [16:20:58] [Client thread/WARN] [FML]: * at com.teammetallurgy.metallurgy.BlockList.init(BlockList.java:91)...
  389. [16:20:58] [Client thread/WARN] [FML]: ****************************************
  390. [16:20:58] [Client thread/WARN] [FML]: ****************************************
  391. [16:20:58] [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.
  392. TO USERS: YES this is a BUG in the mod Metallurgy 4 report it to them!
  393. [16:20:58] [Client thread/WARN] [FML]: * at net.minecraftforge.oredict.OreDictionary.registerOreImpl(OreDictionary.java:534)
  394. [16:20:58] [Client thread/WARN] [FML]: * at net.minecraftforge.oredict.OreDictionary.registerOre(OreDictionary.java:501)
  395. [16:20:58] [Client thread/WARN] [FML]: * at com.teammetallurgy.metallurgy.metals.MetalSet.load(MetalSet.java:380)
  396. [16:20:58] [Client thread/WARN] [FML]: * at com.teammetallurgy.metallurgy.BlockList.injectMetalSet(BlockList.java:201)
  397. [16:20:58] [Client thread/WARN] [FML]: * at com.teammetallurgy.metallurgy.BlockList.initMetalSets(BlockList.java:163)
  398. [16:20:58] [Client thread/WARN] [FML]: * at com.teammetallurgy.metallurgy.BlockList.init(BlockList.java:91)...
  399. [16:20:58] [Client thread/WARN] [FML]: ****************************************
  400. [16:20:58] [Client thread/WARN] [FML]: ****************************************
  401. [16:20:58] [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.
  402. TO USERS: YES this is a BUG in the mod Metallurgy 4 report it to them!
  403. [16:20:58] [Client thread/WARN] [FML]: * at net.minecraftforge.oredict.OreDictionary.registerOreImpl(OreDictionary.java:534)
  404. [16:20:58] [Client thread/WARN] [FML]: * at net.minecraftforge.oredict.OreDictionary.registerOre(OreDictionary.java:501)
  405. [16:20:58] [Client thread/WARN] [FML]: * at com.teammetallurgy.metallurgy.metals.MetalSet.load(MetalSet.java:380)
  406. [16:20:58] [Client thread/WARN] [FML]: * at com.teammetallurgy.metallurgy.BlockList.injectMetalSet(BlockList.java:201)
  407. [16:20:58] [Client thread/WARN] [FML]: * at com.teammetallurgy.metallurgy.BlockList.initMetalSets(BlockList.java:163)
  408. [16:20:58] [Client thread/WARN] [FML]: * at com.teammetallurgy.metallurgy.BlockList.init(BlockList.java:91)...
  409. [16:20:58] [Client thread/WARN] [FML]: ****************************************
  410. [16:20:58] [Client thread/WARN] [FML]: ****************************************
  411. [16:20:58] [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.
  412. TO USERS: YES this is a BUG in the mod Metallurgy 4 report it to them!
  413. [16:20:58] [Client thread/WARN] [FML]: * at net.minecraftforge.oredict.OreDictionary.registerOreImpl(OreDictionary.java:534)
  414. [16:20:58] [Client thread/WARN] [FML]: * at net.minecraftforge.oredict.OreDictionary.registerOre(OreDictionary.java:501)
  415. [16:20:58] [Client thread/WARN] [FML]: * at com.teammetallurgy.metallurgy.metals.MetalSet.load(MetalSet.java:380)
  416. [16:20:58] [Client thread/WARN] [FML]: * at com.teammetallurgy.metallurgy.BlockList.injectMetalSet(BlockList.java:201)
  417. [16:20:58] [Client thread/WARN] [FML]: * at com.teammetallurgy.metallurgy.BlockList.initMetalSets(BlockList.java:163)
  418. [16:20:58] [Client thread/WARN] [FML]: * at com.teammetallurgy.metallurgy.BlockList.init(BlockList.java:91)...
  419. [16:20:58] [Client thread/WARN] [FML]: ****************************************
  420. [16:20:58] [Client thread/WARN] [FML]: ****************************************
  421. [16:20:58] [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.
  422. TO USERS: YES this is a BUG in the mod Metallurgy 4 report it to them!
  423. [16:20:58] [Client thread/WARN] [FML]: * at net.minecraftforge.oredict.OreDictionary.registerOreImpl(OreDictionary.java:534)
  424. [16:20:58] [Client thread/WARN] [FML]: * at net.minecraftforge.oredict.OreDictionary.registerOre(OreDictionary.java:501)
  425. [16:20:58] [Client thread/WARN] [FML]: * at com.teammetallurgy.metallurgy.metals.MetalSet.load(MetalSet.java:380)
  426. [16:20:58] [Client thread/WARN] [FML]: * at com.teammetallurgy.metallurgy.BlockList.injectMetalSet(BlockList.java:201)
  427. [16:20:58] [Client thread/WARN] [FML]: * at com.teammetallurgy.metallurgy.BlockList.initMetalSets(BlockList.java:163)
  428. [16:20:58] [Client thread/WARN] [FML]: * at com.teammetallurgy.metallurgy.BlockList.init(BlockList.java:91)...
  429. [16:20:58] [Client thread/WARN] [FML]: ****************************************
  430. [16:20:58] [Client thread/WARN] [FML]: ****************************************
  431. [16:20:58] [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.
  432. TO USERS: YES this is a BUG in the mod Metallurgy 4 report it to them!
  433. [16:20:58] [Client thread/WARN] [FML]: * at net.minecraftforge.oredict.OreDictionary.registerOreImpl(OreDictionary.java:534)
  434. [16:20:58] [Client thread/WARN] [FML]: * at net.minecraftforge.oredict.OreDictionary.registerOre(OreDictionary.java:501)
  435. [16:20:58] [Client thread/WARN] [FML]: * at com.teammetallurgy.metallurgy.metals.MetalSet.load(MetalSet.java:380)
  436. [16:20:58] [Client thread/WARN] [FML]: * at com.teammetallurgy.metallurgy.BlockList.injectMetalSet(BlockList.java:201)
  437. [16:20:58] [Client thread/WARN] [FML]: * at com.teammetallurgy.metallurgy.BlockList.initMetalSets(BlockList.java:163)
  438. [16:20:58] [Client thread/WARN] [FML]: * at com.teammetallurgy.metallurgy.BlockList.init(BlockList.java:91)...
  439. [16:20:58] [Client thread/WARN] [FML]: ****************************************
  440. [16:20:58] [Client thread/WARN] [FML]: ****************************************
  441. [16:20:58] [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.
  442. TO USERS: YES this is a BUG in the mod Metallurgy 4 report it to them!
  443. [16:20:58] [Client thread/WARN] [FML]: * at net.minecraftforge.oredict.OreDictionary.registerOreImpl(OreDictionary.java:534)
  444. [16:20:58] [Client thread/WARN] [FML]: * at net.minecraftforge.oredict.OreDictionary.registerOre(OreDictionary.java:501)
  445. [16:20:58] [Client thread/WARN] [FML]: * at com.teammetallurgy.metallurgy.metals.MetalSet.load(MetalSet.java:380)
  446. [16:20:58] [Client thread/WARN] [FML]: * at com.teammetallurgy.metallurgy.BlockList.injectMetalSet(BlockList.java:201)
  447. [16:20:58] [Client thread/WARN] [FML]: * at com.teammetallurgy.metallurgy.BlockList.initMetalSets(BlockList.java:163)
  448. [16:20:58] [Client thread/WARN] [FML]: * at com.teammetallurgy.metallurgy.BlockList.init(BlockList.java:91)...
  449. [16:20:58] [Client thread/WARN] [FML]: ****************************************
  450. [16:20:58] [Client thread/WARN] [FML]: ****************************************
  451. [16:20:58] [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.
  452. TO USERS: YES this is a BUG in the mod Metallurgy 4 report it to them!
  453. [16:20:58] [Client thread/WARN] [FML]: * at net.minecraftforge.oredict.OreDictionary.registerOreImpl(OreDictionary.java:534)
  454. [16:20:58] [Client thread/WARN] [FML]: * at net.minecraftforge.oredict.OreDictionary.registerOre(OreDictionary.java:501)
  455. [16:20:58] [Client thread/WARN] [FML]: * at com.teammetallurgy.metallurgy.metals.MetalSet.load(MetalSet.java:380)
  456. [16:20:58] [Client thread/WARN] [FML]: * at com.teammetallurgy.metallurgy.BlockList.injectMetalSet(BlockList.java:201)
  457. [16:20:58] [Client thread/WARN] [FML]: * at com.teammetallurgy.metallurgy.BlockList.initMetalSets(BlockList.java:163)
  458. [16:20:58] [Client thread/WARN] [FML]: * at com.teammetallurgy.metallurgy.BlockList.init(BlockList.java:91)...
  459. [16:20:58] [Client thread/WARN] [FML]: ****************************************
  460. [16:20:58] [Client thread/WARN] [FML]: ****************************************
  461. [16:20:58] [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.
  462. TO USERS: YES this is a BUG in the mod Metallurgy 4 report it to them!
  463. [16:20:58] [Client thread/WARN] [FML]: * at net.minecraftforge.oredict.OreDictionary.registerOreImpl(OreDictionary.java:534)
  464. [16:20:58] [Client thread/WARN] [FML]: * at net.minecraftforge.oredict.OreDictionary.registerOre(OreDictionary.java:501)
  465. [16:20:58] [Client thread/WARN] [FML]: * at com.teammetallurgy.metallurgy.metals.MetalSet.load(MetalSet.java:380)
  466. [16:20:58] [Client thread/WARN] [FML]: * at com.teammetallurgy.metallurgy.BlockList.injectMetalSet(BlockList.java:201)
  467. [16:20:58] [Client thread/WARN] [FML]: * at com.teammetallurgy.metallurgy.BlockList.initMetalSets(BlockList.java:163)
  468. [16:20:58] [Client thread/WARN] [FML]: * at com.teammetallurgy.metallurgy.BlockList.init(BlockList.java:91)...
  469. [16:20:58] [Client thread/WARN] [FML]: ****************************************
  470. [16:20:58] [Client thread/WARN] [FML]: ****************************************
  471. [16:20:58] [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.
  472. TO USERS: YES this is a BUG in the mod Metallurgy 4 report it to them!
  473. [16:20:58] [Client thread/WARN] [FML]: * at net.minecraftforge.oredict.OreDictionary.registerOreImpl(OreDictionary.java:534)
  474. [16:20:58] [Client thread/WARN] [FML]: * at net.minecraftforge.oredict.OreDictionary.registerOre(OreDictionary.java:501)
  475. [16:20:58] [Client thread/WARN] [FML]: * at com.teammetallurgy.metallurgy.metals.MetalSet.load(MetalSet.java:380)
  476. [16:20:58] [Client thread/WARN] [FML]: * at com.teammetallurgy.metallurgy.BlockList.injectMetalSet(BlockList.java:201)
  477. [16:20:58] [Client thread/WARN] [FML]: * at com.teammetallurgy.metallurgy.BlockList.initMetalSets(BlockList.java:163)
  478. [16:20:58] [Client thread/WARN] [FML]: * at com.teammetallurgy.metallurgy.BlockList.init(BlockList.java:91)...
  479. [16:20:58] [Client thread/WARN] [FML]: ****************************************
  480. [16:20:58] [Client thread/WARN] [FML]: ****************************************
  481. [16:20:58] [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.
  482. TO USERS: YES this is a BUG in the mod Metallurgy 4 report it to them!
  483. [16:20:58] [Client thread/WARN] [FML]: * at net.minecraftforge.oredict.OreDictionary.registerOreImpl(OreDictionary.java:534)
  484. [16:20:58] [Client thread/WARN] [FML]: * at net.minecraftforge.oredict.OreDictionary.registerOre(OreDictionary.java:501)
  485. [16:20:58] [Client thread/WARN] [FML]: * at com.teammetallurgy.metallurgy.metals.MetalSet.load(MetalSet.java:380)
  486. [16:20:58] [Client thread/WARN] [FML]: * at com.teammetallurgy.metallurgy.BlockList.injectMetalSet(BlockList.java:201)
  487. [16:20:58] [Client thread/WARN] [FML]: * at com.teammetallurgy.metallurgy.BlockList.initMetalSets(BlockList.java:163)
  488. [16:20:58] [Client thread/WARN] [FML]: * at com.teammetallurgy.metallurgy.BlockList.init(BlockList.java:91)...
  489. [16:20:58] [Client thread/WARN] [FML]: ****************************************
  490. [16:20:59] [Client thread/INFO] [PulseManager-Natura]: Skipping Pulse Natura TE4 Compatibility; missing dependency: ThermalExpansion
  491. [16:20:59] [Client thread/INFO] [PulseManager-Natura]: Skipping Pulse Natura BuildCraft Compatibility; missing dependency: BuildCraft|Transport
  492. [16:20:59] [Client thread/INFO] [PulseManager-Natura]: Skipping Pulse Natura Forestry Compatibility; missing dependency: Forestry
  493. [16:20:59] [Client thread/INFO] [FastLeafDecay]: Patching leaves.
  494. [16:20:59] [Client thread/INFO] [FastLeafDecay]: Found leaf Class: mods/natura/blocks/trees/NLeaves
  495. [16:20:59] [Client thread/INFO] [PulseManager-Natura]: Skipping Pulse Natura TreeCapitator Compatibility; missing dependency: Treecapitator
  496. [16:20:59] [Client thread/INFO] [PulseManager-Natura]: Skipping Pulse Natura Thaumcraft Compatibility; missing dependency: Thaumcraft
  497. [16:20:59] [Client thread/INFO] [PulseManager-Natura]: Skipping Pulse Natura FMP Compatibility; missing dependency: ForgeMultipart
  498. [16:20:59] [Client thread/INFO] [PulseManager-Natura]: Skipping Pulse Natura MFR Compatibility; missing dependency: MineFactoryReloaded
  499. [16:20:59] [Client thread/INFO] [STDERR]: [com.sirolf2009.necromancy.Necromancy:preInit:108]: not connected to the internet, special scythes are de-activated
  500. [16:21:00] [Client thread/INFO] [neresources]: Loading configs..
  501. [16:21:00] [Client thread/INFO] [neresources]: Updating ModMetaData...
  502. [16:21:00] [Client thread/INFO] [neresources]: Registering Network Messages...
  503. [16:21:00] [Client thread/INFO] [neresources]: Requesting Sync...
  504. [16:21:00] [Client thread/INFO] [neresources]: Registering Events...
  505. Jan 06, 2016 4:21:00 PM com.stek101.projectzulu.common.core.ProjectZuluLog log
  506. Information: Detected ProjectZulu|Block module.
  507. Jan 06, 2016 4:21:00 PM com.stek101.projectzulu.common.core.ProjectZuluLog log
  508. Information: Detected ProjectZulu|Mob module.
  509. Jan 06, 2016 4:21:00 PM com.stek101.projectzulu.common.core.ProjectZuluLog log
  510. Information: Detected ProjectZulu|Dungeon module.
  511. Jan 06, 2016 4:21:00 PM com.stek101.projectzulu.common.core.ProjectZuluLog log
  512. Information: Detected ProjectZulu|World module.
  513. Jan 06, 2016 4:21:00 PM com.stek101.projectzulu.common.core.ProjectZuluLog log
  514. Information: Module [ProjectZulu|Block] settings read and will be loaded.
  515. Jan 06, 2016 4:21:00 PM com.stek101.projectzulu.common.core.ProjectZuluLog log
  516. Information: Module [ProjectZulu|Mob] settings read and will be loaded.
  517. Jan 06, 2016 4:21:00 PM com.stek101.projectzulu.common.core.ProjectZuluLog log
  518. Information: Module [ProjectZulu|Dungeon] settings read and will be loaded.
  519. Jan 06, 2016 4:21:00 PM com.stek101.projectzulu.common.core.ProjectZuluLog log
  520. Information: Module [ProjectZulu|World] settings read and will be loaded.
  521. Jan 06, 2016 4:21:00 PM com.stek101.projectzulu.common.core.ProjectZuluLog log
  522. Information: Registering Events
  523. Jan 06, 2016 4:21:00 PM com.stek101.projectzulu.common.core.ProjectZuluLog log
  524. Information: Starting Potion Init
  525. Jan 06, 2016 4:21:00 PM com.stek101.projectzulu.common.core.ProjectZuluLog log
  526. Information: Finished Potion Init
  527. Jan 06, 2016 4:21:01 PM com.stek101.projectzulu.common.core.ProjectZuluLog log
  528. Information: Load Entity Moxdels and Render
  529. Jan 06, 2016 4:21:01 PM com.stek101.projectzulu.common.core.ProjectZuluLog log
  530. Information: Load Entity Properties
  531. Jan 06, 2016 4:21:01 PM com.stek101.projectzulu.common.core.ProjectZuluLog log
  532. Information: Starting ItemBlock Setup
  533. Jan 06, 2016 4:21:01 PM com.stek101.projectzulu.common.core.ProjectZuluLog log
  534. Information: Starting ItemBlock Registration
  535. Jan 06, 2016 4:21:01 PM com.stek101.projectzulu.common.core.ProjectZuluLog log
  536. Information: Spike Render ID Registed to 57
  537. Jan 06, 2016 4:21:01 PM com.stek101.projectzulu.common.core.ProjectZuluLog log
  538. Information: Campfire Render ID Registed to 58
  539. Jan 06, 2016 4:21:01 PM com.stek101.projectzulu.common.core.ProjectZuluLog log
  540. Information: Universal Flower Pot Render ID Registed to 59
  541. Jan 06, 2016 4:21:01 PM com.stek101.projectzulu.common.core.ProjectZuluLog log
  542. Information: Brewing Stand Single Render ID Registed to 60
  543. Jan 06, 2016 4:21:01 PM com.stek101.projectzulu.common.core.ProjectZuluLog log
  544. Information: Brewing Stand Triple Render ID Registed to 61
  545. Jan 06, 2016 4:21:01 PM com.stek101.projectzulu.common.core.ProjectZuluLog log
  546. Information: Spike Render ID Registed to 62
  547. Jan 06, 2016 4:21:01 PM com.stek101.projectzulu.common.core.ProjectZuluLog log
  548. Information: Spike Render ID Registed to 63
  549. Jan 06, 2016 4:21:01 PM com.stek101.projectzulu.common.core.ProjectZuluLog log
  550. Information: Spike Render ID Registed to 64
  551. [16:21:01] [Client thread/WARN] [FML]: ****************************************
  552. [16:21:01] [Client thread/WARN] [FML]: * A broken ore dictionary registration with name foodSalt has occurred. It adds an item (type: class com.stek101.projectzulu.common.core.ItemGenerics) 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.
  553. TO USERS: YES this is a BUG in the mod Project Zulu report it to them!
  554. [16:21:01] [Client thread/WARN] [FML]: * at net.minecraftforge.oredict.OreDictionary.registerOreImpl(OreDictionary.java:534)
  555. [16:21:01] [Client thread/WARN] [FML]: * at net.minecraftforge.oredict.OreDictionary.registerOre(OreDictionary.java:501)
  556. [16:21:01] [Client thread/WARN] [FML]: * at com.stek101.projectzulu.common.blocks.itemblockdeclarations.GenericCraftingItemsDeclaration.registerItem(GenericCraftingItemsDeclaration.java:32)
  557. [16:21:01] [Client thread/WARN] [FML]: * at com.stek101.projectzulu.common.core.itemblockdeclaration.ItemDeclaration.register(ItemDeclaration.java:59)
  558. [16:21:01] [Client thread/WARN] [FML]: * at com.stek101.projectzulu.common.core.ItemBlockManager.registerBlocks(ItemBlockManager.java:49)
  559. [16:21:01] [Client thread/WARN] [FML]: * at com.stek101.projectzulu.common.ProjectZulu_Core.preInit(ProjectZulu_Core.java:184)...
  560. [16:21:01] [Client thread/WARN] [FML]: ****************************************
  561. Jan 06, 2016 4:21:01 PM com.stek101.projectzulu.common.core.ProjectZuluLog log
  562. Information: Completed ItemBlock Registration
  563. Jan 06, 2016 4:21:01 PM com.stek101.projectzulu.common.core.ProjectZuluLog log
  564. Information: Registering Entites
  565. [16:21:02] [Client thread/INFO] [ZombieInfection]: Pre-Init Complete
  566. [16:21:02] [Client thread/INFO] [FML]: Applying holder lookups
  567. [16:21:02] [Client thread/INFO] [FML]: Holder lookups applied
  568. [16:21:02] [Client thread/INFO] [FML]: Injecting itemstacks
  569. [16:21:02] [Client thread/INFO] [FML]: Itemstack injection complete
  570. [16:21:02] [Sound Library Loader/INFO] [STDOUT]: [paulscode.sound.SoundSystemLogger:message:69]:
  571. [16:21:02] [Sound Library Loader/INFO] [STDOUT]: [paulscode.sound.SoundSystemLogger:message:69]: Starting up SoundSystem...
  572. [16:21:02] [Thread-19/INFO] [STDOUT]: [paulscode.sound.SoundSystemLogger:message:69]: Initializing LWJGL OpenAL
  573. [16:21:02] [Thread-19/INFO] [STDOUT]: [paulscode.sound.SoundSystemLogger:message:69]: (The LWJGL binding of OpenAL. For more information, see http://www.lwjgl.org)
  574. [16:21:02] [Thread-19/INFO] [STDOUT]: [paulscode.sound.SoundSystemLogger:message:69]: OpenAL initialized.
  575. [16:21:03] [Sound Library Loader/INFO] [STDOUT]: [paulscode.sound.SoundSystemLogger:message:69]:
  576. [16:21:03] [Sound Library Loader/INFO]: Sound engine started
  577. [16:21:03] [Client thread/INFO]: Created: 16x16 textures/blocks-atlas
  578. [16:21:03] [Client thread/INFO]: Created: 16x16 textures/items-atlas
  579. [16:21:03] [Client thread/ERROR] [CodeChickenCore]: Unable to do mod description scrolling due to lack of stencil buffer
  580. [16:21:03] [Client thread/ERROR] [CodeChickenCore]: Unable to do mod description scrolling due to lack of stencil buffer
  581. [16:21:03] [Client thread/INFO] [bspkrsCore]: Initializing ModVersionChecker for mod bspkrsCore
  582. Jan 06, 2016 4:21:03 PM java.util.prefs.WindowsPreferences <init>
  583. Warnung: Could not open/create prefs root node Software\JavaSoft\Prefs at root 0x80000002. Windows RegCreateKeyEx(...) returned error code 5.
  584. [16:21:03] [Client thread/INFO] [bspkrsCore]: Initializing ModVersionChecker for mod ArmorStatusHUD
  585. [16:21:04] [Client thread/INFO] [FML]: Mortar and Pestle Mod has initiated Init()
  586. [16:21:04] [Client thread/INFO] [FML]: Mortar and Pestle Mod has finished Init()
  587. [16:21:04] [Client thread/INFO] [bspkrsCore]: Initializing ModVersionChecker for mod StatusEffectHUD
  588. [16:21:04] [Back Tools Resource download thread/INFO] [STDERR]: [java.lang.Throwable$WrappedPrintStream:println:-1]: java.io.FileNotFoundException: http://new.creeperrepo.net/ichun/static/backtools.xml
  589. [16:21:04] [Back Tools Resource download thread/INFO] [STDERR]: [java.lang.Throwable$WrappedPrintStream:println:-1]: at sun.net.www.protocol.http.HttpURLConnection.getInputStream(Unknown Source)
  590. [16:21:04] [Back Tools Resource download thread/INFO] [STDERR]: [java.lang.Throwable$WrappedPrintStream:println:-1]: at backtools.client.thread.ThreadCheckModSupport.run(ThreadCheckModSupport.java:40)
  591. [16:21:05] [Client thread/INFO] [cannibalism]: [Cannibalism] Initializating Recipes and Events
  592. [16:21:05] [Client thread/INFO] [STDOUT]: [toast.deadlyWorld._DeadlyWorld:console:101]: [Deadly World] Loaded 16 features!
  593. [16:21:05] [Client thread/INFO] [STDOUT]: [atomicstryker.infernalmobs.common.InfernalMobsCore:load:163]: InfernalMobsCore load() completed! Modifiers ready: 27
  594. [16:21:05] [Client thread/INFO] [STDOUT]: [atomicstryker.multimine.common.fmlmagic.MMTransformer:handlePlayerControllerMP:76]: **************** Multi Mine transform running on PlayerControllerMP, obfuscated: true ***********************
  595. [16:21:05] [Client thread/INFO] [STDOUT]: [atomicstryker.multimine.common.fmlmagic.MMTransformer:handlePlayerControllerMP:89]: In target method! Patching!
  596. [16:21:05] [Client thread/INFO] [STDOUT]: [atomicstryker.multimine.common.fmlmagic.MMTransformer:handlePlayerControllerMP:106]: Found IFLT Node at 170
  597. [16:21:05] [Client thread/INFO] [STDOUT]: [atomicstryker.multimine.common.fmlmagic.MMTransformer:handlePlayerControllerMP:114]: Found ALOAD Node at offset -4 from IFLT Node
  598. [16:21:05] [Client thread/INFO] [STDOUT]: [atomicstryker.multimine.common.fmlmagic.MMTransformer:handlePlayerControllerMP:192]: Patching Complete! Writing class bytes now.
  599. [16:21:06] [Client thread/INFO] [inventorytweaks]: InvTweaks: Configuration loaded.
  600. [16:21:06] [Client thread/INFO] [inventorytweaks]: Mod initialized
  601. [16:21:06] [Client thread/INFO] [journeymap]: JourneyMap log initialized.
  602. [16:21:06] [Client thread/INFO] [journeymap]: ensureCurrent ENTER
  603. [16:21:06] [Client thread/INFO] [journeymap]: Loaded CoreProperties from C:\Users\User\AppData\Roaming\.minecraft\journeymap\config\5.1\journeymap.core.config
  604. [16:21:06] [Client thread/INFO] [journeymap]: Loaded FullMapProperties from C:\Users\User\AppData\Roaming\.minecraft\journeymap\config\5.1\journeymap.fullmap.config
  605. [16:21:06] [Client thread/INFO] [journeymap]: Loaded MiniMapProperties from C:\Users\User\AppData\Roaming\.minecraft\journeymap\config\5.1\journeymap.minimap.config
  606. [16:21:06] [Client thread/INFO] [journeymap]: Loaded MiniMapProperties2 from C:\Users\User\AppData\Roaming\.minecraft\journeymap\config\5.1\journeymap.minimap2.config
  607. [16:21:06] [Client thread/INFO] [journeymap]: Loaded WebMapProperties from C:\Users\User\AppData\Roaming\.minecraft\journeymap\config\5.1\journeymap.webmap.config
  608. [16:21:06] [Client thread/INFO] [journeymap]: Loaded WaypointProperties from C:\Users\User\AppData\Roaming\.minecraft\journeymap\config\5.1\journeymap.waypoint.config
  609. [16:21:06] [Client thread/INFO] [journeymap]: ensureCurrent EXIT, elapsed§8 count §r1§8 avg §r204.7§8ms§r
  610. [16:21:06] [Client thread/INFO] [STDOUT]: [lycanite.lycanitesmobs.LycanitesMobs:printInfo:377]: [LycanitesMobs] [Info] Config mountainmobs-stats created successfully.
  611. [16:21:06] [Client thread/INFO] [STDOUT]: [lycanite.lycanitesmobs.LycanitesMobs:printInfo:377]: [LycanitesMobs] [Info] Config swampmobs-stats created successfully.
  612. [16:21:06] [Client thread/INFO] [STDOUT]: [lycanite.lycanitesmobs.LycanitesMobs:printInfo:377]: [LycanitesMobs] [Info] Config arcticmobs-stats created successfully.
  613. [16:21:06] [Client thread/INFO] [STDOUT]: [lycanite.lycanitesmobs.LycanitesMobs:printInfo:377]: [LycanitesMobs] [Info] Config demonmobs-stats created successfully.
  614. [16:21:06] [Client thread/INFO] [STDOUT]: [lycanite.lycanitesmobs.LycanitesMobs:printInfo:377]: [LycanitesMobs] [Info] Config shadowmobs-stats created successfully.
  615. [16:21:06] [Client thread/INFO] [STDOUT]: [lycanite.lycanitesmobs.LycanitesMobs:printInfo:377]: [LycanitesMobs] [Info] Config desertmobs-stats created successfully.
  616. [16:21:06] [Client thread/INFO] [STDOUT]: [lycanite.lycanitesmobs.LycanitesMobs:printInfo:377]: [LycanitesMobs] [Info] Config forestmobs-stats created successfully.
  617. [16:21:06] [Client thread/INFO] [STDOUT]: [lycanite.lycanitesmobs.LycanitesMobs:printInfo:377]: [LycanitesMobs] [Info] Config junglemobs-stats created successfully.
  618. [16:21:06] [Client thread/INFO] [STDOUT]: [lycanite.lycanitesmobs.LycanitesMobs:printInfo:377]: [LycanitesMobs] [Info] Config saltwatermobs-stats created successfully.
  619. [16:21:06] [Client thread/INFO] [STDOUT]: [lycanite.lycanitesmobs.LycanitesMobs:printInfo:377]: [LycanitesMobs] [Info] Config infernomobs-stats created successfully.
  620. [16:21:06] [Client thread/INFO] [STDOUT]: [lycanite.lycanitesmobs.LycanitesMobs:printInfo:377]: [LycanitesMobs] [Info] Config freshwatermobs-stats created successfully.
  621. [16:21:06] [Client thread/INFO] [STDOUT]: [lycanite.lycanitesmobs.LycanitesMobs:printInfo:377]: [LycanitesMobs] [Info] Config plainsmobs-stats created successfully.
  622. [16:21:06] [Client thread/INFO] [Mantle]: Entering initialization phase.
  623. [16:21:06] [Client thread/INFO] [Natura]: Waila detected.
  624. [16:21:06] [Client thread/INFO] [STDOUT]: [com.thedespite.noshelter.NoShelterMain:init:170]: Number of biomes: 40
  625. Jan 06, 2016 4:21:06 PM com.stek101.projectzulu.common.core.ProjectZuluLog log
  626. Information: Load Entity Biomes
  627. Jan 06, 2016 4:21:07 PM com.stek101.projectzulu.common.core.ProjectZuluLog log
  628. Information: Register Entity Spawns
  629. [16:21:07] [Client thread/WARN] [FML]: The mod TotemDefender tried to register the entity class class ru.kordum.totemDefender.common.entities.EntityProjectile which was already registered - if you wish to override default naming for FML mod entities, register it here first
  630. [16:21:07] [Client thread/INFO] [FML]: InvTweaks: net.minecraft.inventory.ContainerWorkbench
  631. [16:21:07] [Client thread/INFO] [FML]: InvTweaks: net.minecraft.inventory.ContainerRepair
  632. [16:21:07] [Client thread/INFO] [ZombieInfection]: Init Complete
  633. [16:21:07] [Client thread/INFO] [denseores]: Ph'nglui mglw'nafh, y'uln Dense Ores shugg ch'agl
  634. [16:21:07] [Client thread/INFO] [Waila]: Receiving registration request from [ mod_Invasion ] for method invmod.common.util.IMWailaProvider.callbackRegister
  635. [16:21:07] [Client thread/INFO] [Waila]: Receiving registration request from [ JABBA ] for method mcp.mobius.betterbarrels.BBWailaProvider.callbackRegister
  636. [16:21:07] [Client thread/INFO] [Waila]: Receiving registration request from [ Natura ] for method mods.natura.plugins.waila.WailaRegistrar.wailaCallback
  637. [16:21:07] [Client thread/INFO] [Waila]: Receiving registration request from [ WailaHarvestability ] for method squeek.wailaharvestability.WailaHandler.callbackRegister
  638. [16:21:07] [Client thread/INFO] [FML]: Injecting itemstacks
  639. [16:21:07] [Client thread/INFO] [FML]: Itemstack injection complete
  640. [16:21:07] [Client thread/INFO] [FML]: Mortar and Pestle Mod has been successfully loaded.
  641. [16:21:07] [Client thread/INFO] [ambiotic]: Setting normal channels to 22, streaming channels to 10
  642. [16:21:07] [Client thread/INFO] [Backpack]: [Backpacks] NEI Support enabled
  643. [16:21:07] [Client thread/INFO] [STDOUT]: [atomicstryker.battletowers.common.TowerStageItemManager:<init>:67]: Battletowers parsed Item/Block/ChestGenHook net.minecraft.item.Item@d0578df
  644. [16:21:07] [Client thread/INFO] [STDOUT]: [atomicstryker.battletowers.common.TowerStageItemManager:<init>:67]: Battletowers parsed Item/Block/ChestGenHook net.minecraft.item.ItemSeeds@212771de
  645. [16:21:07] [Client thread/INFO] [STDOUT]: [atomicstryker.battletowers.common.TowerStageItemManager:<init>:67]: Battletowers parsed Item/Block/ChestGenHook net.minecraft.item.ItemMultiTexture@76f073b3
  646. [16:21:07] [Client thread/INFO] [STDOUT]: [atomicstryker.battletowers.common.TowerStageItemManager:<init>:67]: Battletowers parsed Item/Block/ChestGenHook net.minecraft.item.ItemReed@58f03ef7
  647. [16:21:07] [Client thread/INFO] [STDOUT]: [atomicstryker.battletowers.common.TowerStageItemManager:<init>:67]: Battletowers parsed Item/Block/ChestGenHook net.minecraft.item.ItemPickaxe@33f5ce07
  648. [16:21:07] [Client thread/INFO] [STDOUT]: [atomicstryker.battletowers.common.TowerStageItemManager:<init>:67]: Battletowers parsed Item/Block/ChestGenHook net.minecraft.item.ItemAxe@4ea94837
  649. [16:21:07] [Client thread/INFO] [STDOUT]: [atomicstryker.battletowers.common.TowerStageItemManager:<init>:67]: Battletowers parsed Item/Block/ChestGenHook net.minecraft.item.ItemBlock@725fe50e
  650. [16:21:07] [Client thread/INFO] [STDOUT]: [atomicstryker.battletowers.common.TowerStageItemManager:<init>:67]: Battletowers parsed Item/Block/ChestGenHook net.minecraft.item.ItemBlock@460d5f9
  651. [16:21:07] [Client thread/INFO] [STDOUT]: [atomicstryker.battletowers.common.TowerStageItemManager:<init>:67]: Battletowers parsed Item/Block/ChestGenHook net.minecraft.item.Item@62427f26
  652. [16:21:07] [Client thread/INFO] [STDOUT]: [atomicstryker.battletowers.common.TowerStageItemManager:<init>:67]: Battletowers parsed Item/Block/ChestGenHook net.minecraft.item.ItemCoal@56fc3f0b
  653. [16:21:07] [Client thread/INFO] [STDOUT]: [atomicstryker.battletowers.common.TowerStageItemManager:<init>:67]: Battletowers parsed Item/Block/ChestGenHook net.minecraft.item.ItemReed@4b52c7e9
  654. [16:21:07] [Client thread/INFO] [STDOUT]: [atomicstryker.battletowers.common.TowerStageItemManager:<init>:67]: Battletowers parsed Item/Block/ChestGenHook net.minecraft.item.ItemCloth@1ff19bf0
  655. [16:21:07] [Client thread/INFO] [STDOUT]: [atomicstryker.battletowers.common.TowerStageItemManager:<init>:67]: Battletowers parsed Item/Block/ChestGenHook net.minecraft.item.ItemBlock@2bacd397
  656. [16:21:07] [Client thread/INFO] [STDOUT]: [atomicstryker.battletowers.common.TowerStageItemManager:<init>:67]: Battletowers parsed Item/Block/ChestGenHook net.minecraft.item.Item@27c2b8a1
  657. [16:21:07] [Client thread/INFO] [STDOUT]: [atomicstryker.battletowers.common.TowerStageItemManager:<init>:67]: Battletowers parsed Item/Block/ChestGenHook net.minecraft.item.ItemFood@39dee970
  658. [16:21:07] [Client thread/INFO] [STDOUT]: [atomicstryker.battletowers.common.TowerStageItemManager:<init>:67]: Battletowers parsed Item/Block/ChestGenHook net.minecraft.item.ItemFood@77e71427
  659. [16:21:07] [Client thread/INFO] [STDOUT]: [atomicstryker.battletowers.common.TowerStageItemManager:<init>:67]: Battletowers parsed Item/Block/ChestGenHook net.minecraft.item.ItemBlock@5729dc5
  660. [16:21:07] [Client thread/INFO] [STDOUT]: [atomicstryker.battletowers.common.TowerStageItemManager:<init>:67]: Battletowers parsed Item/Block/ChestGenHook net.minecraft.item.ItemBlock@2b16aba6
  661. [16:21:07] [Client thread/INFO] [STDOUT]: [atomicstryker.battletowers.common.TowerStageItemManager:<init>:67]: Battletowers parsed Item/Block/ChestGenHook net.minecraft.item.ItemMultiTexture@15c148b3
  662. [16:21:07] [Client thread/INFO] [STDOUT]: [atomicstryker.battletowers.common.TowerStageItemManager:<init>:67]: Battletowers parsed Item/Block/ChestGenHook net.minecraft.item.Item@24a4b6d3
  663. [16:21:07] [Client thread/INFO] [STDOUT]: [atomicstryker.battletowers.common.TowerStageItemManager:<init>:67]: Battletowers parsed Item/Block/ChestGenHook net.minecraft.item.ItemSign@160d74d5
  664. [16:21:07] [Client thread/INFO] [STDOUT]: [atomicstryker.battletowers.common.TowerStageItemManager:<init>:67]: Battletowers parsed Item/Block/ChestGenHook net.minecraft.item.ItemFishingRod@1f7718be
  665. [16:21:07] [Client thread/INFO] [STDOUT]: [atomicstryker.battletowers.common.TowerStageItemManager:<init>:67]: Battletowers parsed Item/Block/ChestGenHook net.minecraft.item.ItemSeeds@7e33df34
  666. [16:21:07] [Client thread/INFO] [STDOUT]: [atomicstryker.battletowers.common.TowerStageItemManager:<init>:67]: Battletowers parsed Item/Block/ChestGenHook net.minecraft.item.ItemSeeds@7f830fa6
  667. [16:21:07] [Client thread/INFO] [STDOUT]: [atomicstryker.battletowers.common.TowerStageItemManager:<init>:67]: Battletowers parsed Item/Block/ChestGenHook net.minecraft.item.ItemSword@d0a0086
  668. [16:21:07] [Client thread/INFO] [STDOUT]: [atomicstryker.battletowers.common.TowerStageItemManager:<init>:67]: Battletowers parsed Item/Block/ChestGenHook net.minecraft.item.Item@71391d27
  669. [16:21:07] [Client thread/INFO] [STDOUT]: [atomicstryker.battletowers.common.TowerStageItemManager:<init>:67]: Battletowers parsed Item/Block/ChestGenHook net.minecraft.item.Item@57fd4753
  670. [16:21:07] [Client thread/INFO] [STDOUT]: [atomicstryker.battletowers.common.TowerStageItemManager:<init>:67]: Battletowers parsed Item/Block/ChestGenHook net.minecraft.item.ItemFishFood@2bdc93e2
  671. [16:21:07] [Client thread/INFO] [STDOUT]: [atomicstryker.battletowers.common.TowerStageItemManager:<init>:67]: Battletowers parsed Item/Block/ChestGenHook net.minecraft.item.ItemDye@1278aad8
  672. [16:21:07] [Client thread/INFO] [STDOUT]: [atomicstryker.battletowers.common.TowerStageItemManager:<init>:67]: Battletowers parsed Item/Block/ChestGenHook net.minecraft.item.ItemArmor@273c59de
  673. [16:21:07] [Client thread/INFO] [STDOUT]: [atomicstryker.battletowers.common.TowerStageItemManager:<init>:67]: Battletowers parsed Item/Block/ChestGenHook net.minecraft.item.ItemArmor@6b3011f1
  674. [16:21:07] [Client thread/INFO] [STDOUT]: [atomicstryker.battletowers.common.TowerStageItemManager:<init>:67]: Battletowers parsed Item/Block/ChestGenHook net.minecraft.item.ItemArmor@20ea1c31
  675. [16:21:07] [Client thread/INFO] [STDOUT]: [atomicstryker.battletowers.common.TowerStageItemManager:<init>:67]: Battletowers parsed Item/Block/ChestGenHook net.minecraft.item.ItemArmor@69e0e5d8
  676. [16:21:07] [Client thread/INFO] [STDOUT]: [atomicstryker.battletowers.common.TowerStageItemManager:<init>:67]: Battletowers parsed Item/Block/ChestGenHook ChestGenHook:dungeonChest:3
  677. [16:21:07] [Client thread/INFO] [STDOUT]: [atomicstryker.battletowers.common.TowerStageItemManager:<init>:67]: Battletowers parsed Item/Block/ChestGenHook net.minecraft.item.ItemBlock@2c12c572
  678. [16:21:07] [Client thread/INFO] [STDOUT]: [atomicstryker.battletowers.common.TowerStageItemManager:<init>:67]: Battletowers parsed Item/Block/ChestGenHook net.minecraft.item.ItemBlock@7e5d4811
  679. [16:21:07] [Client thread/INFO] [STDOUT]: [atomicstryker.battletowers.common.TowerStageItemManager:<init>:67]: Battletowers parsed Item/Block/ChestGenHook net.minecraft.item.ItemLilyPad@7c7d3eb3
  680. [16:21:07] [Client thread/INFO] [STDOUT]: [atomicstryker.battletowers.common.TowerStageItemManager:<init>:67]: Battletowers parsed Item/Block/ChestGenHook net.minecraft.item.ItemReed@1ab1b70e
  681. [16:21:07] [Client thread/INFO] [STDOUT]: [atomicstryker.battletowers.common.TowerStageItemManager:<init>:67]: Battletowers parsed Item/Block/ChestGenHook ChestGenHook:dungeonChest:5
  682. [16:21:07] [Client thread/INFO] [STDOUT]: [atomicstryker.battletowers.common.TowerStageItemManager:<init>:67]: Battletowers parsed Item/Block/ChestGenHook net.minecraft.item.ItemEnderPearl@573e48d4
  683. [16:21:07] [Client thread/INFO] [STDOUT]: [atomicstryker.battletowers.common.TowerStageItemManager:<init>:67]: Battletowers parsed Item/Block/ChestGenHook net.minecraft.item.Item@4a8f17ca
  684. [16:21:07] [Client thread/INFO] [STDOUT]: [atomicstryker.battletowers.common.TowerStageItemManager:<init>:67]: Battletowers parsed Item/Block/ChestGenHook net.minecraft.item.ItemRedstone@2debe4d1
  685. [16:21:07] [Client thread/INFO] [STDOUT]: [atomicstryker.battletowers.common.TowerStageItemManager:<init>:67]: Battletowers parsed Item/Block/ChestGenHook net.minecraft.item.Item@28c3d5b4
  686. [16:21:07] [Client thread/INFO] [STDOUT]: [atomicstryker.battletowers.common.TowerStageItemManager:<init>:67]: Battletowers parsed Item/Block/ChestGenHook ChestGenHook:dungeonChest:7
  687. [16:21:07] [Client thread/INFO] [BetterFoliage]: Registering renderers
  688. [16:21:07] [Client thread/INFO] [BetterFoliage]: Registering texture generators
  689. [16:21:07] [Client thread/INFO] [cannibalism]: [Cannibalism] Reading JSON
  690. [16:21:07] [Client thread/INFO] [cannibalism]: [Cannibalism] Mod Locked and Loaded
  691. [16:21:07] [Client thread/INFO] [STDOUT]: [jaredbgreat.dldungeons.themes.ThemeReader:readThemes:94]: [DLDUNGEONS] Found 12 themes.
  692. [16:21:07] [Client thread/INFO] [STDOUT]: [jaredbgreat.dldungeons.themes.ThemeReader:readLoot:119]: [DLDUNGEONS] Loading chest loot file (chests.cfg)
  693.  
  694. [16:21:07] [Client thread/INFO] [STDOUT]: [jaredbgreat.dldungeons.DoomlikeDungeons:postInit:68]: OUTPUT OF MOBS BY THEME:
  695. [16:21:08] [Client thread/INFO] [STDOUT]: [mcp.mobius.waila.gui.truetyper.TrueTypeFont:<init>:98]: TrueTypeFont loaded: java.awt.Font[family=Minecraftia,name=Minecraftia Regular,style=plain,size=14] - AntiAlias = true
  696. [16:21:08] [Client thread/INFO] [journeymap]: postInitialize ENTER
  697. [16:21:08] [Client thread/INFO] [journeymap]: Registered channel: world_info
  698. [16:21:08] [Client thread/INFO] [journeymap]: Initializing icon sets...
  699. [16:21:08] [Client thread/INFO] [journeymap]: postInitialize EXIT, elapsed§8 count §r1§8 avg §r333.82§8ms§r
  700. [16:21:08] [Client thread/INFO] [STDOUT]: [lycanite.lycanitesmobs.LycanitesMobs:printInfo:377]: [LycanitesMobs] [Info] Config arcticmobs-worldgen created successfully.
  701. [16:21:08] [Client thread/INFO] [STDOUT]: [lycanite.lycanitesmobs.LycanitesMobs:printInfo:377]: [LycanitesMobs] [Info] Config infernomobs-worldgen created successfully.
  702. [16:21:08] [Client thread/INFO] [Mantle]: Entering postinitialization phase.
  703. [16:21:08] [Client thread/INFO] [Mantle]: Loading Manual XML from: /assets/mantle/manuals/test.xml
  704. Jan 06, 2016 4:21:08 PM com.stek101.projectzulu.common.core.ProjectZuluLog log
  705. Information: Initializing TerrainFeatures
  706. Jan 06, 2016 4:21:08 PM com.stek101.projectzulu.common.core.ProjectZuluLog log
  707. Information: Starting Potion Setup
  708. Jan 06, 2016 4:21:08 PM com.stek101.projectzulu.common.core.ProjectZuluLog log
  709. Information: Finished Potion Setup
  710. [16:21:09] [Client thread/INFO] [ZombieInfection]: Post-Init Complete
  711. [16:21:09] [Client thread/INFO] [denseores]: Dense Ores is fully loaded but sadly it cannot tell you the unlocalized name for dirt.
  712. [16:21:09] [Client thread/INFO] [FML]: Unknown recipe class! jds.bibliocraft.BiblioSpecialRecipes Modder please refer to net.minecraftforge.oredict.RecipeSorter
  713. [16:21:09] [Client thread/INFO] [FML]: Unknown recipe class! toast.utilityMobs.RecipeSavePermissions Modder please refer to net.minecraftforge.oredict.RecipeSorter
  714. [16:21:09] [Client thread/WARN] [Waila]: [BC] Class not found. java.lang.ClassNotFoundException: buildcraft.factory.TileTank
  715. [16:21:09] [Client thread/WARN] [Waila]: [IndustrialCraft 2] Error while loading generator hooks.java.lang.ClassNotFoundException: ic2.core.block.generator.tileentity.TileEntityBaseGenerator
  716. [16:21:09] [Client thread/WARN] [Waila]: [Thaumcraft] Class not found. java.lang.ClassNotFoundException: thaumcraft.common.Thaumcraft
  717. [16:21:09] [Client thread/INFO] [Waila]: [EnderStorage] EnderStorage mod not found.
  718. [16:21:09] [Client thread/INFO] [Waila]: [GraveStone] GraveStone mod not found.
  719. [16:21:09] [Client thread/INFO] [Waila]: [TwilightForestMod] TwilightForestMod mod not found.
  720. [16:21:09] [Client thread/WARN] [Waila]: [Thermal Expansion] Error while loading Energy hooks.java.lang.ClassNotFoundException: cofh.api.energy.IEnergyProvider
  721. [16:21:09] [Client thread/WARN] [Waila]: [Thermal Expansion] Error while loading Energy Cell hooks.java.lang.ClassNotFoundException: cofh.thermalexpansion.block.cell.TileCell
  722. [16:21:09] [Client thread/WARN] [Waila]: [Thermal Expansion] Error while loading Tank hooks.java.lang.ClassNotFoundException: cofh.thermalexpansion.block.tank.TileTank
  723. [16:21:09] [Client thread/WARN] [Waila]: [Thermal Expansion] Error while loading Tesseract hooks.java.lang.ClassNotFoundException: cofh.thermalexpansion.block.ender.TileTesseract
  724. [16:21:09] [Client thread/WARN] [Waila]: [Thermal Expansion] Error while loading ISecureTile hooks.java.lang.ClassNotFoundException: cofh.api.tileentity.ISecurable
  725. [16:21:09] [Client thread/WARN] [Waila]: [Thermal Expansion] Error while loading Tesseract hooks.java.lang.ClassNotFoundException: cofh.thermalexpansion.block.cache.TileCache
  726. [16:21:09] [Client thread/WARN] [Waila]: [Thermal Dynamics] Error while loading FluidDuct hooks.java.lang.ClassNotFoundException: cofh.thermaldynamics.ducts.fluid.TileFluidDuct
  727. [16:21:09] [Client thread/INFO] [Waila]: [Engineer Toolbox] Engineer Toolbox mod not found.
  728. [16:21:09] [Client thread/INFO] [Waila]: [ProjectRed] ProjectRed|Integration mod not found.
  729. [16:21:09] [Client thread/INFO] [Waila]: [ExtraUtilities] ExtraUtilities mod not found.
  730. [16:21:09] [Client thread/INFO] [Waila]: [OpenBlocks] OpenBlocks mod not found.
  731. [16:21:09] [Client thread/INFO] [Waila]: [Railcraft] Railcraft mod not found.
  732. [16:21:09] [Client thread/INFO] [Waila]: [PamHarvestCraft] PamHarvestCraft mod not found.
  733. [16:21:09] [Client thread/INFO] [Waila]: [MagicalCrops] MagicalCrops mod not found.
  734. [16:21:09] [Client thread/INFO] [Waila]: [Statues] Statues mod not found.
  735. [16:21:09] [Client thread/INFO] [Waila]: [Agriculture] Agriculture mod not found.
  736. [16:21:09] [Client thread/INFO] [Waila]: Trying to reflect invmod.common.util.IMWailaProvider callbackRegister
  737. [16:21:09] [Client thread/WARN] [Waila]: Could not find class invmod.common.util.IMWailaProvider
  738. [16:21:09] [Client thread/INFO] [Waila]: Trying to reflect mcp.mobius.betterbarrels.BBWailaProvider callbackRegister
  739. [16:21:09] [Client thread/INFO] [Waila]: Success in registering JABBA
  740. [16:21:09] [Client thread/INFO] [Waila]: Trying to reflect mods.natura.plugins.waila.WailaRegistrar wailaCallback
  741. [16:21:09] [Client thread/INFO] [Waila]: Success in registering Natura
  742. [16:21:09] [Client thread/INFO] [Waila]: Trying to reflect squeek.wailaharvestability.WailaHandler callbackRegister
  743. [16:21:09] [Client thread/INFO] [Waila]: Success in registering WailaHarvestability
  744. [16:21:09] [Client thread/INFO] [streams.StreamsMod$]: Welcome to Farseek/Streams. Please visit http://www.minecraftforum.net/forums/mapping-and-modding/minecraft-mods/2346379-streams-real-flowing-rivers for information and updates.
  745. [16:21:09] [Client thread/INFO] [streams.StreamsMod$]: Shader configuration: if you wish to use shaders with custom water blocks including Streams river blocks, edit your shader's gbuffers_wqater.wsh file to replace the line:
  746. if (mc_Entity.x == 8 || mc_Entity.x == 9) {
  747. with the following line:
  748. if (mc_Entity.x == 8 || mc_Entity.x == 9 || mc_Entity.x == 227 || mc_Entity.x == 228 || mc_Entity.x == 250 || mc_Entity.x == 617 || mc_Entity.x == 833 || mc_Entity.x == 834 || mc_Entity.x == 835 || mc_Entity.x == 836 || mc_Entity.x == 837 || mc_Entity.x == 838 || mc_Entity.x == 839 || mc_Entity.x == 840 || mc_Entity.x == 841 || mc_Entity.x == 842 || mc_Entity.x == 843 || mc_Entity.x == 844 || mc_Entity.x == 845 || mc_Entity.x == 846 || mc_Entity.x == 847 || mc_Entity.x == 848 || mc_Entity.x == 849) {
  749. Note that these ids will change with every new combination of loaded mods.
  750. [16:21:09] [Client thread/INFO] [FML]: Forge Mod Loader has successfully loaded 109 mods
  751. [16:21:09] [Client thread/INFO]: Reloading ResourceManager: Default, FMLFileResourcePack:Forge Mod Loader, FMLFileResourcePack:Minecraft Forge, FMLFileResourcePack:Not Enough Items, FMLFileResourcePack:OpenEye, FMLFileResourcePack:ArmorStatusHUD, FMLFileResourcePack:Mortar and Pestle Mod, FMLFileResourcePack:StatusEffectHUD, FMLFileResourcePack:Air Overhaul, FMLFileResourcePack:Ambiotic, FMLFileResourcePack:AnimationAPI, FMLFileResourcePack:AppleCore, FMLFileResourcePack:Backpack, FMLFileResourcePack:BackTools, FMLFileResourcePack:Battle Towers, FMLFileResourcePack:Better Achievements, FMLFileResourcePack:Better Foliage, FMLFileResourcePack:Better Title Screen, FMLFileResourcePack:BiblioCraft, FMLFileResourcePack:Revenge of the Blocks, FMLFileResourcePack:Cannibalism, FMLFileResourcePack:Castle Defender, FMLFileResourcePack:Build Mod, FMLFileResourcePack:CoroPets, FMLFileResourcePack:CoroAI, FMLFileResourcePack:Extended Renderer, FMLFileResourcePack:Extended Mod Config, FMLFileResourcePack:CraftHeraldry, FMLFileResourcePack:DrCyano's Lootable Bodies, FMLFileResourcePack:Deadly World, FMLFileResourcePack:DeathCounter, FMLFileResourcePack:debug, FMLFileResourcePack:Dense Ores, FMLFileResourcePack:Ding, FMLFileResourcePack:Diversity, FMLFileResourcePack:Doomlike Dungeons, FMLFileResourcePack:Dynamic Lights, FMLFileResourcePack:Dynamic Lights Burning Entity Module, FMLFileResourcePack:Dynamic Lights Creeper Module, FMLFileResourcePack:Dynamic Lights EntityItem Module, FMLFileResourcePack:Dynamic Lights Entity Light Module, FMLFileResourcePack:Dynamic Lights Mob Equipment Light Module, FMLFileResourcePack:Dynamic Lights Fiery Arrows Light Module, FMLFileResourcePack:Dynamic Lights Flood Light, FMLFileResourcePack:Dynamic Lights OtherPlayers Light Module, FMLFileResourcePack:Dynamic Lights Player Light Module, FMLFileResourcePack:Elemental Creepers, FMLFileResourcePack:EnchantView, FMLFileResourcePack:Epic Siege Mod, FMLFileResourcePack:The Farlanders, FMLFileResourcePack:Farseek, FMLFileResourcePack:FastCraft, FMLFileResourcePack:Fast Leaf Decay, FMLFileResourcePack:Gollum Core Lib, FMLFileResourcePack:Heart Crystal Mod, FMLFileResourcePack:iChunUtil, FMLFileResourcePack:Infernal Mobs, FMLFileResourcePack:Invasion, FMLFileResourcePack:Inventory Pets, FMLFileResourcePack:Inventory Tweaks, FMLFileResourcePack:Iron Chest, FMLFileResourcePack:JABBA, FMLFileResourcePack:JourneyMap, FMLFileResourcePack:Lava Monsters, FMLFileResourcePack:Lycanites Mobs, FMLFileResourcePack:Lycanites Arctic Mobs, FMLFileResourcePack:Lycanites Demon Mobs, FMLFileResourcePack:Lycanites Desert Mobs, FMLFileResourcePack:Lycanites Forest Mobs, FMLFileResourcePack:Lycanites Freshwater Mobs, FMLFileResourcePack:Lycanites Inferno Mobs, FMLFileResourcePack:Lycanites Jungle Mobs, FMLFileResourcePack:Lycanites Mountain Mobs, FMLFileResourcePack:Lycanites Plains Mobs, FMLFileResourcePack:Lycanites Saltwater Mobs, FMLFileResourcePack:Lycanites Shadow Mobs, FMLFileResourcePack:Lycanites Swamp Mobs, FMLFileResourcePack:Magical Crops: Core, FMLFileResourcePack:Mantle, FMLFileResourcePack:Minecraft Comes Alive, FMLFileResourcePack:Metallurgy 4, FMLFileResourcePack:Metallurgy Core, FMLFileResourcePack:Mob Rebirth, FMLFileResourcePack:Multi Mine, FMLFileResourcePack:Mutant Creatures, FMLFileResourcePack:Natura, FMLFileResourcePack:Natural Absorption, FMLFileResourcePack:Necromancy, FMLFileResourcePack:noshelter, FMLFileResourcePack:NotEnoughKeys, FMLFileResourcePack:Not Enough Resources, FMLFileResourcePack:Pam's HarvestCraft, FMLFileResourcePack:Placeable Gunpowder, FMLFileResourcePack:Project Zulu, FMLFileResourcePack:RadixCore, FMLFileResourcePack:Realistic Terrain Generation, FMLFileResourcePack:Streams, FMLFileResourcePack:ThebombzenAPI, FMLFileResourcePack:Totem Defender, FMLFileResourcePack:AtomicStryker Update Check Mod, FMLFileResourcePack:Utility Mobs, FMLFileResourcePack:Waila, FMLFileResourcePack:Waila Harvestability, FMLFileResourcePack:Localized Weather & Storms, FMLFileResourcePack:Wild Caves 3, FMLFileResourcePack:Zombie Infection, FMLFileResourcePack:Zombie Awareness, FMLFileResourcePack:bspkrsCore
  752. [16:21:09] [Client thread/WARN]: ResourcePack: ignored non-lowercase namespace: RTG in C:\Users\User\AppData\Roaming\.minecraft\mods\RTG-1.7.10-0.4.0.jar
  753. [16:21:09] [Client thread/WARN]: ResourcePack: ignored non-lowercase namespace: RTG in C:\Users\User\AppData\Roaming\.minecraft\mods\RTG-1.7.10-0.4.0.jar
  754. [16:21:09] [Client thread/WARN]: ResourcePack: ignored non-lowercase namespace: RTG in C:\Users\User\AppData\Roaming\.minecraft\mods\RTG-1.7.10-0.4.0.jar
  755. [16:21:09] [Client thread/WARN]: ResourcePack: ignored non-lowercase namespace: RTG in C:\Users\User\AppData\Roaming\.minecraft\mods\RTG-1.7.10-0.4.0.jar
  756. [16:21:09] [Client thread/WARN]: ResourcePack: ignored non-lowercase namespace: RTG in C:\Users\User\AppData\Roaming\.minecraft\mods\RTG-1.7.10-0.4.0.jar
  757. [16:21:09] [Client thread/WARN]: ResourcePack: ignored non-lowercase namespace: RTG in C:\Users\User\AppData\Roaming\.minecraft\mods\RTG-1.7.10-0.4.0.jar
  758. [16:21:09] [Client thread/WARN]: ResourcePack: ignored non-lowercase namespace: RTG in C:\Users\User\AppData\Roaming\.minecraft\mods\RTG-1.7.10-0.4.0.jar
  759. [16:21:09] [Client thread/WARN]: ResourcePack: ignored non-lowercase namespace: RTG in C:\Users\User\AppData\Roaming\.minecraft\mods\RTG-1.7.10-0.4.0.jar
  760. [16:21:09] [Client thread/WARN]: ResourcePack: ignored non-lowercase namespace: RTG in C:\Users\User\AppData\Roaming\.minecraft\mods\RTG-1.7.10-0.4.0.jar
  761. [16:21:09] [Client thread/WARN]: ResourcePack: ignored non-lowercase namespace: RTG in C:\Users\User\AppData\Roaming\.minecraft\mods\RTG-1.7.10-0.4.0.jar
  762. [16:21:09] [Client thread/WARN]: ResourcePack: ignored non-lowercase namespace: RTG in C:\Users\User\AppData\Roaming\.minecraft\mods\RTG-1.7.10-0.4.0.jar
  763. [16:21:09] [Client thread/WARN]: ResourcePack: ignored non-lowercase namespace: RTG in C:\Users\User\AppData\Roaming\.minecraft\mods\RTG-1.7.10-0.4.0.jar
  764. [16:21:09] [Client thread/WARN]: ResourcePack: ignored non-lowercase namespace: RTG in C:\Users\User\AppData\Roaming\.minecraft\mods\RTG-1.7.10-0.4.0.jar
  765. [16:21:10] [Client thread/INFO]: Created: 1024x1024 textures/items-atlas
  766. [16:21:10] [Client thread/INFO] [BetterFoliage]: Found 2 cactus arm textures
  767. [16:21:10] [Client thread/INFO] [BetterFoliage]: Found 3 netherrack vine textures
  768. [16:21:10] [Client thread/INFO] [BetterFoliage]: Found 2 lilypad flower textures
  769. [16:21:10] [Client thread/INFO] [BetterFoliage]: Found 3 lilypad root textures
  770. [16:21:10] [Client thread/INFO] [BetterFoliage]: Found 4 mycelium textures
  771. [16:21:10] [Client thread/INFO] [BetterFoliage]: Found 3 snowed leaves textures
  772. [16:21:10] [Client thread/INFO] [BetterFoliage]: Found 5 short grass textures
  773. [16:21:10] [Client thread/INFO] [BetterFoliage]: Found 2 snowy grass textures
  774. [16:21:10] [Client thread/INFO] [BetterFoliage]: Found 2 hanging grass textures
  775. [16:21:10] [Client thread/INFO] [BetterFoliage]: Found 4 reed textures
  776. [16:21:10] [Client thread/INFO] [BetterFoliage]: Found 4 algae textures
  777. [16:21:10] [Client thread/INFO] [BetterFoliage]: Found 4 coral crust textures
  778. [16:21:10] [Client thread/INFO] [BetterFoliage]: Found 6 coral textures
  779. [16:21:10] [Client thread/INFO] [BetterFoliage]: Reloading leaf textures
  780. [16:21:11] [Client thread/INFO] [denseores]: Dense Ores: Succesfully generated dense ore texture for 'redstone_ore' with background 'stone'. Place redstone_ore_dense.png in the assets folder to override.
  781. [16:21:11] [Client thread/INFO] [denseores]: Dense Ores: Succesfully generated dense ore texture for 'gold_ore' with background 'stone'. Place gold_ore_dense.png in the assets folder to override.
  782. [16:21:11] [Client thread/INFO] [denseores]: Dense Ores: Succesfully generated dense ore texture for 'coal_ore' with background 'stone'. Place coal_ore_dense.png in the assets folder to override.
  783. [16:21:11] [Client thread/INFO] [denseores]: Dense Ores: Succesfully generated dense ore texture for 'diamond_ore' with background 'stone'. Place diamond_ore_dense.png in the assets folder to override.
  784. [16:21:11] [Client thread/INFO] [denseores]: Dense Ores: Succesfully generated dense ore texture for 'iron_ore' with background 'stone'. Place iron_ore_dense.png in the assets folder to override.
  785. [16:21:11] [Client thread/INFO] [denseores]: Dense Ores: Succesfully generated dense ore texture for 'lapis_ore' with background 'stone'. Place lapis_ore_dense.png in the assets folder to override.
  786. [16:21:11] [Client thread/INFO] [denseores]: Dense Ores: Succesfully generated dense ore texture for 'quartz_ore' with background 'netherrack'. Place quartz_ore_dense.png in the assets folder to override.
  787. [16:21:11] [Client thread/INFO] [denseores]: Dense Ores: Succesfully generated dense ore texture for 'emerald_ore' with background 'stone'. Place emerald_ore_dense.png in the assets folder to override.
  788. [16:21:11] [Client thread/WARN] [FastCraft-core]: The sprite bettergrassandleaves:soul_track caused the mipmap level to drop from 4 to 3 because it's too small (8x8 px).
  789. [16:21:11] [Client thread/INFO]: Created: 1024x1024 textures/blocks-atlas
  790. [16:21:12] [Client thread/INFO] [BetterFoliage]: Found 2 soul particle textures
  791. [16:21:12] [Client thread/INFO] [BetterFoliage]: Loaded leaf textures: 90 generated, 0 pre-drawn
  792. [16:21:12] [Client thread/INFO] [BetterFoliage]: Loaded 4 leaf particle sets
  793. [16:21:12] [Client thread/INFO] [STDOUT]: [paulscode.sound.SoundSystemLogger:message:69]:
  794. [16:21:12] [Client thread/INFO] [STDOUT]: [paulscode.sound.SoundSystemLogger:message:69]: SoundSystem shutting down...
  795. [16:21:12] [Client thread/INFO] [STDOUT]: [paulscode.sound.SoundSystemLogger:importantMessage:90]: Author: Paul Lamb, www.paulscode.com
  796. [16:21:12] [Client thread/INFO] [STDOUT]: [paulscode.sound.SoundSystemLogger:message:69]:
  797. [16:21:12] [Sound Library Loader/INFO] [STDOUT]: [paulscode.sound.SoundSystemLogger:message:69]:
  798. [16:21:12] [Sound Library Loader/INFO] [STDOUT]: [paulscode.sound.SoundSystemLogger:message:69]: Starting up SoundSystem...
  799. [16:21:12] [Thread-26/INFO] [STDOUT]: [paulscode.sound.SoundSystemLogger:message:69]: Initializing LWJGL OpenAL
  800. [16:21:12] [Thread-26/INFO] [STDOUT]: [paulscode.sound.SoundSystemLogger:message:69]: (The LWJGL binding of OpenAL. For more information, see http://www.lwjgl.org)
  801. [16:21:12] [Thread-26/INFO] [STDOUT]: [paulscode.sound.SoundSystemLogger:message:69]: OpenAL initialized.
  802. [16:21:13] [Client thread/INFO] [ambiotic]: Loading engine.json
  803. [16:21:13] [Sound Library Loader/INFO] [STDOUT]: [paulscode.sound.SoundSystemLogger:message:69]:
  804. [16:21:13] [Client thread/INFO] [ambiotic]: Loading scanner definitions
  805. [16:21:13] [Sound Library Loader/INFO]: Sound engine started
  806. [16:21:13] [Client thread/INFO] [ambiotic]: Loading variable definitions
  807. [16:21:13] [Client thread/INFO] [ambiotic]: Loading default variable definitions
  808. [16:21:13] [Client thread/INFO] [ambiotic]: Loading macro definitions
  809. [16:21:13] [Client thread/INFO] [ambiotic]: Loading emitter list
  810. [16:21:13] [Client thread/INFO] [ambiotic]: Loading emitter definition 'ambiotic:emitters/background.json'
  811. [16:21:13] [Client thread/INFO] [ambiotic]: Loading emitter definition 'ambiotic:emitters/swamp.json'
  812. [16:21:13] [Client thread/INFO] [ambiotic]: Loading emitter definition 'ambiotic:emitters/beach.json'
  813. [16:21:13] [Client thread/INFO] [ambiotic]: Loading emitter definition 'ambiotic:emitters/water.json'
  814. [16:21:13] [Client thread/INFO] [ambiotic]: Loading emitter definition 'ambiotic:emitters/forest.json'
  815. [16:21:13] [Client thread/INFO] [ambiotic]: Loading emitter definition 'ambiotic:emitters/savanna.json'
  816. [16:21:13] [Client thread/INFO] [ambiotic]: Loading emitter definition 'ambiotic:emitters/plains.json'
  817. [16:21:13] [Client thread/INFO] [ambiotic]: Loading emitter definition 'ambiotic:emitters/jungle.json'
  818. [16:21:13] [Client thread/INFO] [ambiotic]: Loading emitter definition 'ambiotic:emitters/coldforest.json'
  819. [16:21:13] [Client thread/INFO] [ambiotic]: Expanding emitter macros
  820. [16:21:13] [Client thread/INFO] [ambiotic]: Evaluating javascript helper file
  821. [16:21:13] [Client thread/INFO] [bspkrsCore]: Enabling Main Menu Mob render ticker
  822. [16:21:13] [Client thread/ERROR] [TEXTURE ERRORS]: +=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=
  823. [16:21:13] [Client thread/ERROR] [TEXTURE ERRORS]: The following texture errors were found.
  824. [16:21:13] [Client thread/ERROR] [TEXTURE ERRORS]: ==================================================
  825. [16:21:13] [Client thread/ERROR] [TEXTURE ERRORS]: DOMAIN minecraft
  826. [16:21:13] [Client thread/ERROR] [TEXTURE ERRORS]: --------------------------------------------------
  827. [16:21:13] [Client thread/ERROR] [TEXTURE ERRORS]: domain minecraft is missing 8 textures
  828. [16:21:13] [Client thread/ERROR] [TEXTURE ERRORS]: domain minecraft has 5 locations:
  829. [16:21:13] [Client thread/ERROR] [TEXTURE ERRORS]: unknown resourcepack type net.minecraft.client.resources.DefaultResourcePack : Default
  830. [16:21:13] [Client thread/ERROR] [TEXTURE ERRORS]: mod ambiotic resources at C:\Users\User\AppData\Roaming\.minecraft\mods\ambiotic-1.2.0.jar
  831. [16:21:13] [Client thread/ERROR] [TEXTURE ERRORS]: mod journeymap resources at C:\Users\User\AppData\Roaming\.minecraft\mods\journeymap-1.7.10-5.1.3-unlimited.jar
  832. [16:21:13] [Client thread/ERROR] [TEXTURE ERRORS]: mod magicalcrops resources at C:\Users\User\AppData\Roaming\.minecraft\mods\magicalcrops-4.0.0_PUBLIC_BETA_5.jar
  833. [16:21:13] [Client thread/ERROR] [TEXTURE ERRORS]: mod necromancy resources at C:\Users\User\AppData\Roaming\.minecraft\mods\Necromancy-1.7.10.jar
  834. [16:21:13] [Client thread/ERROR] [TEXTURE ERRORS]: -------------------------
  835. [16:21:13] [Client thread/ERROR] [TEXTURE ERRORS]: The missing resources for domain minecraft are:
  836. [16:21:13] [Client thread/ERROR] [TEXTURE ERRORS]: textures/items/MISSING_ICON_ITEM_4889_Necronomicon.png
  837. [16:21:13] [Client thread/ERROR] [TEXTURE ERRORS]: textures/blocks/MISSING_ICON_BLOCK_617_FlowingBlood.png
  838. [16:21:13] [Client thread/ERROR] [TEXTURE ERRORS]: textures/blocks/MISSING_ICON_BLOCK_543_bookshelf.png
  839. [16:21:13] [Client thread/ERROR] [TEXTURE ERRORS]: textures/blocks/MISSING_ICON_BLOCK_615_Altar Building Block.png
  840. [16:21:13] [Client thread/ERROR] [TEXTURE ERRORS]: textures/items/MISSING_ICON_ITEM_4890_ItemScythe.png
  841. [16:21:13] [Client thread/ERROR] [TEXTURE ERRORS]: textures/blocks/MISSING_ICON_BLOCK_614_Summoning Altar.png
  842. [16:21:13] [Client thread/ERROR] [TEXTURE ERRORS]: textures/blocks/MISSING_ICON_BLOCK_616_Sewing Machine.png
  843. [16:21:13] [Client thread/ERROR] [TEXTURE ERRORS]: textures/items/MISSING_ICON_ITEM_4891_ItemScytheBone.png
  844. [16:21:13] [Client thread/ERROR] [TEXTURE ERRORS]: -------------------------
  845. [16:21:13] [Client thread/ERROR] [TEXTURE ERRORS]: No other errors exist for domain minecraft
  846. [16:21:13] [Client thread/ERROR] [TEXTURE ERRORS]: ==================================================
  847. [16:21:13] [Client thread/ERROR] [TEXTURE ERRORS]: ==================================================
  848. [16:21:13] [Client thread/ERROR] [TEXTURE ERRORS]: DOMAIN magicalcrops
  849. [16:21:13] [Client thread/ERROR] [TEXTURE ERRORS]: --------------------------------------------------
  850. [16:21:13] [Client thread/ERROR] [TEXTURE ERRORS]: domain magicalcrops is missing 2 textures
  851. [16:21:13] [Client thread/ERROR] [TEXTURE ERRORS]: domain magicalcrops has 1 location:
  852. [16:21:13] [Client thread/ERROR] [TEXTURE ERRORS]: mod magicalcrops resources at C:\Users\User\AppData\Roaming\.minecraft\mods\magicalcrops-4.0.0_PUBLIC_BETA_5.jar
  853. [16:21:13] [Client thread/ERROR] [TEXTURE ERRORS]: -------------------------
  854. [16:21:13] [Client thread/ERROR] [TEXTURE ERRORS]: The missing resources for domain magicalcrops are:
  855. [16:21:13] [Client thread/ERROR] [TEXTURE ERRORS]: textures/blocks/Crop_S3.png
  856. [16:21:13] [Client thread/ERROR] [TEXTURE ERRORS]: textures/blocks/Crop_3.png
  857. [16:21:13] [Client thread/ERROR] [TEXTURE ERRORS]: -------------------------
  858. [16:21:13] [Client thread/ERROR] [TEXTURE ERRORS]: No other errors exist for domain magicalcrops
  859. [16:21:13] [Client thread/ERROR] [TEXTURE ERRORS]: ==================================================
  860. [16:21:13] [Client thread/ERROR] [TEXTURE ERRORS]: ==================================================
  861. [16:21:13] [Client thread/ERROR] [TEXTURE ERRORS]: DOMAIN harvestcraft
  862. [16:21:13] [Client thread/ERROR] [TEXTURE ERRORS]: --------------------------------------------------
  863. [16:21:13] [Client thread/ERROR] [TEXTURE ERRORS]: domain harvestcraft is missing 1 texture
  864. [16:21:13] [Client thread/ERROR] [TEXTURE ERRORS]: domain harvestcraft has 1 location:
  865. [16:21:13] [Client thread/ERROR] [TEXTURE ERRORS]: mod harvestcraft resources at C:\Users\User\AppData\Roaming\.minecraft\mods\Pam's HarvestCraft 1.7.10Lb.jar
  866. [16:21:13] [Client thread/ERROR] [TEXTURE ERRORS]: -------------------------
  867. [16:21:13] [Client thread/ERROR] [TEXTURE ERRORS]: The missing resources for domain harvestcraft are:
  868. [16:21:13] [Client thread/ERROR] [TEXTURE ERRORS]: textures/items/chocolaterollItem.png
  869. [16:21:13] [Client thread/ERROR] [TEXTURE ERRORS]: -------------------------
  870. [16:21:13] [Client thread/ERROR] [TEXTURE ERRORS]: No other errors exist for domain harvestcraft
  871. [16:21:13] [Client thread/ERROR] [TEXTURE ERRORS]: ==================================================
  872. [16:21:13] [Client thread/ERROR] [TEXTURE ERRORS]: ==================================================
  873. [16:21:13] [Client thread/ERROR] [TEXTURE ERRORS]: DOMAIN weather2
  874. [16:21:13] [Client thread/ERROR] [TEXTURE ERRORS]: --------------------------------------------------
  875. [16:21:13] [Client thread/ERROR] [TEXTURE ERRORS]: domain weather2 is missing 2 textures
  876. [16:21:13] [Client thread/ERROR] [TEXTURE ERRORS]: domain weather2 has 1 location:
  877. [16:21:13] [Client thread/ERROR] [TEXTURE ERRORS]: mod weather2 resources at C:\Users\User\AppData\Roaming\.minecraft\mods\weather2-2.3.10 for MC v1.7.10.jar
  878. [16:21:13] [Client thread/ERROR] [TEXTURE ERRORS]: -------------------------
  879. [16:21:13] [Client thread/ERROR] [TEXTURE ERRORS]: The missing resources for domain weather2 are:
  880. [16:21:13] [Client thread/ERROR] [TEXTURE ERRORS]: textures/blocks/Anemometer.png
  881. [16:21:13] [Client thread/ERROR] [TEXTURE ERRORS]: textures/blocks/WindVane.png
  882. [16:21:13] [Client thread/ERROR] [TEXTURE ERRORS]: -------------------------
  883. [16:21:13] [Client thread/ERROR] [TEXTURE ERRORS]: No other errors exist for domain weather2
  884. [16:21:13] [Client thread/ERROR] [TEXTURE ERRORS]: ==================================================
  885. [16:21:13] [Client thread/ERROR] [TEXTURE ERRORS]: ==================================================
  886. [16:21:13] [Client thread/ERROR] [TEXTURE ERRORS]: DOMAIN projectzulublock
  887. [16:21:13] [Client thread/ERROR] [TEXTURE ERRORS]: --------------------------------------------------
  888. [16:21:13] [Client thread/ERROR] [TEXTURE ERRORS]: domain projectzulublock is missing 1 texture
  889. [16:21:13] [Client thread/ERROR] [TEXTURE ERRORS]: domain projectzulublock has 1 location:
  890. [16:21:13] [Client thread/ERROR] [TEXTURE ERRORS]: mod ProjectZulu|Core resources at C:\Users\User\AppData\Roaming\.minecraft\mods\ProjectZulu-1.7.10-1.4c2.jar
  891. [16:21:13] [Client thread/ERROR] [TEXTURE ERRORS]: -------------------------
  892. [16:21:13] [Client thread/ERROR] [TEXTURE ERRORS]: The missing resources for domain projectzulublock are:
  893. [16:21:13] [Client thread/ERROR] [TEXTURE ERRORS]: textures/blocks/potion.png
  894. [16:21:13] [Client thread/ERROR] [TEXTURE ERRORS]: -------------------------
  895. [16:21:13] [Client thread/ERROR] [TEXTURE ERRORS]: No other errors exist for domain projectzulublock
  896. [16:21:13] [Client thread/ERROR] [TEXTURE ERRORS]: ==================================================
  897. [16:21:13] [Client thread/ERROR] [TEXTURE ERRORS]: +=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=
  898. [16:21:13] [Client thread/INFO] [FML]: InvTweaks: net.minecraft.inventory.ContainerPlayer
  899. [16:21:14] [Client thread/INFO] [journeymap]: Loading blocks and textures...
  900. [16:21:14] [Client thread/INFO] [journeymap]: Built BlockMD cache (1474) : BlockMD.reset count 1 avg 45.13ms
  901. [16:21:14] [Client thread/INFO] [journeymap]: initBlocksTexture: 1024x1024 loaded in 21.75886ms
  902. [16:21:14] [Client thread/INFO] [journeymap]: Existing color palette's resource packs and mod names match current loadout.
  903. [16:21:14] [Client thread/INFO] [journeymap]: Loaded 1471 block colors from color palette file in 4ms: C:\Users\User\AppData\Roaming\.minecraft\journeymap\colorpalette.json
  904. [16:21:14] [Client thread/INFO] [journeymap]: Initialized 3 block colors from mods and resource packs in 2ms
  905. [16:21:15] [Client thread/INFO] [journeymap]: Color palette file generated with 1471 colors in 97ms for: C:\Users\User\AppData\Roaming\.minecraft\journeymap\colorpalette.json
  906. [16:21:15] [Client thread/INFO] [journeymap]: Updated color palette file: C:\Users\User\AppData\Roaming\.minecraft\journeymap\colorpalette.json
  907. [16:21:16] [Client thread/INFO] [bspkrsCore]: Disabling Main Menu Mob render ticker
  908. [16:21:17] [Client thread/INFO] [FML]: InvTweaks: net.minecraft.client.gui.GuiTextField
  909. [16:21:17] [Client thread/INFO] [FML]: InvTweaks: successfully transformed setFocused/func_146195_b
  910. [16:21:32] [Client thread/INFO] [bspkrsCore]: Enabling Main Menu Mob render ticker
  911. [16:21:33] [Server thread/INFO]: Starting integrated minecraft server version 1.7.10
  912. [16:21:33] [Server thread/INFO]: Generating keypair
  913. [16:21:33] [Server thread/INFO]: Converting map!
  914. [16:21:33] [Server thread/INFO]: Scanning folders...
  915. [16:21:33] [Server thread/INFO]: Total conversion count is 0
  916. [16:21:33] [Server thread/INFO] [FML]: Injecting existing block and item data into this server instance
  917. [16:21:33] [Server thread/INFO] [FML]: Applying holder lookups
  918. [16:21:33] [Server thread/INFO] [FML]: Holder lookups applied
  919. [16:21:33] [Server thread/INFO] [OpenEye]: openeye.asm.SingleClassTransformer.visitMethod(SingleClassTransformer.java:26): Applying method transformer chunk_write for method a((Lapx;Lahb;Ldh;)V)
  920. [16:21:33] [Server thread/INFO] [OpenEye]: openeye.asm.injectors.ExceptionHandlerInjector.addHandler(ExceptionHandlerInjector.java:63): Adding handler for 'entity_write'
  921. [16:21:33] [Server thread/INFO] [OpenEye]: openeye.asm.injectors.ExceptionHandlerInjector.addHandler(ExceptionHandlerInjector.java:63): Adding handler for 'tile_entity_write'
  922. [16:21:33] [Server thread/WARN]: Unable to find spawn biome
  923. [16:21:34] [Server thread/INFO] [streams.world]: River at tp 23 64 95
  924. [16:21:35] [Server thread/INFO] [STDOUT]: [atomicstryker.battletowers.common.WorldGenHandler:loadPosFile:311]: Battletower Positions reloaded. Lines 1, entries 0
  925. [16:21:35] [Server thread/INFO] [FML]: Loading dimension 0 (New World) (net.minecraft.server.integrated.IntegratedServer@2b9a909c)
  926. [16:21:35] [Server thread/INFO] [FML]: Loading dimension 1 (New World) (net.minecraft.server.integrated.IntegratedServer@2b9a909c)
  927. Jan 06, 2016 4:21:35 PM com.stek101.projectzulu.common.core.ProjectZuluLog log
  928. Information: Project Zulu : Death Rules are ENABLED.
  929. [16:21:35] [Server thread/INFO] [STDOUT]: [atomicstryker.battletowers.common.WorldGenHandler:loadPosFile:311]: Battletower Positions reloaded. Lines 1, entries 0
  930. [16:21:35] [Server thread/INFO] [STDOUT]: [atomicstryker.battletowers.common.WorldGenHandler:loadPosFile:311]: Battletower Positions reloaded. Lines 1, entries 0
  931. [16:21:35] [Server thread/INFO] [FML]: Loading dimension -1 (New World) (net.minecraft.server.integrated.IntegratedServer@2b9a909c)
  932. Jan 06, 2016 4:21:35 PM com.stek101.projectzulu.common.core.ProjectZuluLog log
  933. Information: Project Zulu : Death Rules are ENABLED.
  934. [16:21:35] [Server thread/INFO] [STDOUT]: [atomicstryker.battletowers.common.WorldGenHandler:loadPosFile:311]: Battletower Positions reloaded. Lines 1, entries 0
  935. [16:21:35] [Server thread/INFO] [STDOUT]: [atomicstryker.battletowers.common.WorldGenHandler:loadPosFile:311]: Battletower Positions reloaded. Lines 1, entries 0
  936. Attemping to load JABBA data.
  937. Jan 06, 2016 4:21:35 PM com.stek101.projectzulu.common.core.ProjectZuluLog log
  938. Information: Project Zulu : Death Rules are ENABLED.
  939. [16:21:35] [Server thread/INFO] [STDOUT]: [atomicstryker.battletowers.common.WorldGenHandler:loadPosFile:311]: Battletower Positions reloaded. Lines 1, entries 0
  940. [16:21:35] [Server thread/INFO] [STDOUT]: [atomicstryker.battletowers.common.WorldGenHandler:loadPosFile:311]: Battletower Positions reloaded. Lines 1, entries 0
  941. [16:21:35] [Server thread/INFO]: Preparing start region for level 0
  942. Logged 0 towers so far, accepted new site coords [-240,-144], mindist 9999.000000
  943. [16:21:36] [Server thread/INFO] [STDOUT]: [atomicstryker.battletowers.common.AS_WorldGenTower:generate:474]: Battle Tower type SandStone spawned at [ -240 | -144 ], underground: false
  944. [16:21:36] [Server thread/INFO]: Preparing spawn area: 9%
  945. [16:21:37] [Server thread/INFO]: Preparing spawn area: 29%
  946. [16:21:38] [Server thread/INFO]: Preparing spawn area: 52%
  947. Jan 06, 2016 4:21:39 PM com.stek101.projectzulu.common.core.ProjectZuluLog log
  948. Information: construct
  949. [16:21:39] [Server thread/INFO]: Preparing spawn area: 67%
  950. [16:21:40] [Server thread/INFO]: Preparing spawn area: 83%
  951. Jan 06, 2016 4:21:41 PM com.stek101.projectzulu.common.core.ProjectZuluLog log
  952. Information: construct
  953. [16:21:41] [Server thread/INFO] [neresources]: Loading compatibility for minecraft
  954. [16:21:41] [Server thread/INFO] [neresources]: CoFHCore not loaded - skipping
  955. [16:21:41] [Server thread/INFO] [neresources]: Loading compatibility for Metallurgy
  956. [16:21:41] [Server thread/INFO] [neresources]: NetherOres not loaded - skipping
  957. [16:21:41] [Server thread/INFO] [neresources]: BigReactors not loaded - skipping
  958. [16:21:41] [Server thread/INFO] [neresources]: appliedenergistics2 not loaded - skipping
  959. [16:21:41] [Server thread/INFO] [neresources]: Thaumcraft not loaded - skipping
  960. [16:21:41] [Server thread/INFO] [neresources]: ElectriCraft not loaded - skipping
  961. [16:21:41] [Server thread/INFO] [neresources]: ReactorCraft not loaded - skipping
  962. [16:21:41] [Server thread/INFO] [neresources]: Forestry not loaded - skipping
  963. [16:21:41] [Server thread/INFO] [neresources]: TConstruct not loaded - skipping
  964. [16:21:41] [Server thread/INFO] [neresources]: IC2 not loaded - skipping
  965. [16:21:41] [Server thread/INFO] [neresources]: MobProperties not loaded - skipping
  966. [16:21:41] [Server thread/INFO] [neresources]: xreliquary not loaded - skipping
  967. [16:21:41] [Server thread/INFO] [neresources]: bluepower not loaded - skipping
  968. [16:21:41] [Client thread/INFO] [bspkrsCore]: Disabling Main Menu Mob render ticker
  969. [16:21:41] [Server thread/INFO] [STDOUT]: [CoroUtil.forge.CoroAI:initTry:91]: CoroUtil being reinitialized
  970. [16:21:41] [Server thread/INFO] [FML]: InvTweaks: net.minecraft.inventory.ContainerHopper
  971. [16:21:41] [Server thread/INFO] [FML]: InvTweaks: net.minecraft.inventory.ContainerChest
  972. [16:21:41] [Server thread/INFO] [FML]: InvTweaks: net.minecraft.inventory.ContainerBrewingStand
  973. [16:21:41] [Server thread/INFO] [FML]: InvTweaks: net.minecraft.inventory.ContainerBeacon
  974. [16:21:41] [Server thread/INFO] [FML]: InvTweaks: net.minecraft.inventory.ContainerDispenser
  975. [16:21:41] [Server thread/INFO] [FML]: InvTweaks: net.minecraft.inventory.ContainerFurnace
  976. [16:21:41] [Server thread/INFO] [FML]: InvTweaks: net.minecraft.inventory.ContainerMerchant
  977. [16:21:42] [Server thread/INFO]: Changing view distance to 12, from 10
  978. [16:21:42] [Netty Client IO #0/INFO] [FML]: Server protocol version 2
  979. [16:21:42] [Netty IO #1/INFO] [FML]: Client protocol version 2
  980. [16:21:42] [Netty IO #1/INFO] [FML]: Client attempting to join with 109 mods : hearts@1.1.1,iChunUtil@4.2.2,AS_UpdateCheck@1.1.7,ExtendedRenderer@v1.0,DynamicLights_flameArrows@1.0.0,BiblioCraft@1.11.4,dldungeonsjdg@1.8.7,GollumCoreLib@2.0.0,airoverhaul@1.7.10_1.0,magicalcrops@4.0.0_PUBLIC_BETA_4b,WailaHarvestability@1.1.6,Backpack@2.0.1,DynamicLights_otherPlayers@1.0.8,ConfigMod@v1.0,FastCraft@1.21,Ding@MC1.7.10,shadowmobs@1.13.0.5 - MC 1.7.10,IronChest@6.0.62.742,AS_MultiMine@1.4.4,CodeChickenCore@1.0.7.47,notenoughkeys@@MOD_VERSION@,Natura@2.2.0,mountainmobs@1.13.0.5 - MC 1.7.10,ProjectZulu|Core@1.7.10-1.4c2,desertmobs@1.13.0.5 - MC 1.7.10,thebombzenapi@2.4.2,cannibalism@1.1.1,necromancy@1.7.2,journeymap@5.1.3,lycanitesmobs@1.13.0.5 - MC 1.7.10,fastleafdecay@1.4,UtilityMobs@3.1.1,farseek@1.0.10,BuildMod@v1.0,neresources@0.1.0.ManuallyBuilt,inventorytweaks@1.58-147-645ca10,DynamicLights_onFire@1.0.5,CastleDefenders@3.0.0 [Build Smeagol],debug@1.0,saltwatermobs@1.13.0.5 - MC 1.7.10,InventoryPets@1.3.8,DynamicLights_mobEquipment@1.0.8,demonmobs@1.13.0.5 - MC 1.7.10,junglemobs@1.13.0.5 - MC 1.7.10,enchantview@4.1.0,FML@7.10.99.99,JABBA@1.2.1,denseores@1.0,NaturalAbsorption@1.2.1,diversity@ALPHA 1.6.1,DynamicLights_thePlayer@1.1.4,BetterTitleScreen@1.7.10-1.1,MutantCreatures@1.4.9,bspkrsCore@6.16,arcticmobs@1.13.0.5 - MC 1.7.10,OpenEye@0.6,BetterFoliage@1.0.15,weather2@v2.3.10,AppleCore@1.1.0,ESM@10.0.146,DynamicLights_dropItems@1.0.8,lootablebodies@1.3.6,ZAMod@v1.9.5,BattleTowers@1.5.2,wildcaves3@1.7.10,mcp@9.05,AnimationAPI@1.2.4,blockrevenge@1.0,plainsmobs@1.13.0.5 - MC 1.7.10,TotemDefender@1.1.7,BackTools@4.0.0,DeathCounter@4.0.0,CoroPets@v1.0,MetallurgyCore@4.0.4,ambiotic@1.2.0,ZombieInfection@@VERSION@,DynamicLights_entityClasses@1.0.1,DynamicLights@1.3.9,Waila@1.5.10,swampmobs@1.13.0.5 - MC 1.7.10,streams@0.1.6,MCA@1.7.10-5.1.1.1,CraftHeraldry@1.1.3,Metallurgy@4.0.6,gunpowder@1.1,ArmorStatusHUD@1.28,LavaMonsters@2.2.1,freshwatermobs@1.13.0.5 - MC 1.7.10,DeadlyWorld@1.0.2,RTG@0.4.0,mobrebirth@bp1.7.10(2.3.1.0),NotEnoughItems@1.0.5.120,InfernalMobs@1.6.6,harvestcraft@1.7.10j,RadixCore@2.1.1,BetterAchievements@0.1.0,Mantle@1.7.10-0.3.2.jenkins184,mod_Invasion@1.1.5,DynamicLights_creepers@1.0.4,farlanders@1.2b,DynamicLights_floodLights@1.0.2,feudalrox_mortarandpestle@v1.1,Forge@10.13.4.1558,elementalcreepers@4.3.0,noshelter@2.1,forestmobs@1.13.0.5 - MC 1.7.10,StatusEffectHUD@1.27,CoroAI@v1.0,infernomobs@1.13.0.5 - MC 1.7.10
  981. [16:21:42] [Netty IO #1/INFO] [FML]: Attempting connection with missing mods [] at CLIENT
  982. [16:21:42] [Netty Client IO #0/INFO] [FML]: Attempting connection with missing mods [] at SERVER
  983. [16:21:42] [Server thread/INFO] [FML]: [Server thread] Server side modded connection established
  984. [16:21:42] [Server thread/INFO]: Tinte1[local:E:ef6ee6a1] logged in with entity id 158 at (-46.5, 65.0, 54.5)
  985. [16:21:42] [Server thread/INFO]: Tinte1 joined the game
  986. [16:21:42] [Client thread/INFO] [FML]: [Client thread] Client side modded connection established
  987. [16:21:42] [Client thread/INFO] [STDOUT]: [atomicstryker.battletowers.common.AS_BattleTowersCore:onClientConnected:71]: CLIENT registered ClientConnectedToServerEvent, sending packet to server
  988. Jan 06, 2016 4:21:42 PM com.stek101.projectzulu.common.core.ProjectZuluLog log
  989. Information: Project Zulu : Death Rules are ENABLED.
  990. [16:21:42] [Client thread/INFO]: [CHAT] -------------------------------
  991. [16:21:42] [Client thread/INFO]: [CHAT] Thank you use the mod Gollum Core Lib. The mod is up to date. Visit http://smeagol-mods.com/ for more informations.
  992. [16:21:42] [Client thread/INFO]: [CHAT] -------------------------------
  993. [16:21:42] [Client thread/INFO]: [CHAT] -------------------------------
  994. [16:21:42] [Client thread/INFO]: [CHAT] Thank you use the mod Castle Defender. The mod is up to date. Visit http://smeagol-mods.com/ for more informations.
  995. [16:21:42] [Client thread/INFO]: [CHAT] -------------------------------
  996. [16:21:42] [Client thread/INFO] [MCA]: Received and applied server-side configuration.
  997. [16:21:43] [Client thread/ERROR] [NotEnoughItems]: Failed to find identifier for: mods.natura.items.BerryMedley@59658f9f
  998. [16:21:50] [Thread-30/INFO] [STDOUT]: [atomicstryker.updatecheck.common.UpdateCheckMod$UpdateCheckThread:run:76]: Now reading data segment for mismatching mcversion: Minecraft 1.6.4
  999. Exception in thread "Thread-29" Exception in thread "Thread-31" Exception in thread "Thread-30" Exception in thread "Thread-32" [16:22:13] [Server thread/INFO]: Stopping server
  1000. Exception in thread "Server thread"
Advertisement
Add Comment
Please, Sign In to add comment
Advertisement
Public Pastes
Advertisement
We use cookies for various purposes including analytics. By continuing to use Pastebin, you agree to our use of cookies as described in the Cookies Policy.  OK, I Understand
Not a member of Pastebin yet?
Sign Up, it unlocks many cool features!