Advertisement
Tsyklop

A broken ore dictionary registration WaterPower

Nov 16th, 2015
150
0
Never
Not a member of Pastebin yet? Sign Up, it unlocks many cool features!
text 23.06 KB | None | 0 0
  1. [15:47:46] [Client thread/WARN] [FML]: ****************************************
  2. [15:47:46] [Client thread/WARN] [FML]: * A broken ore dictionary registration with name blockZinc has occurred. It adds an item (type: class org.jackhuang.watercraft.common.block.ore.ItemBlockMaterial) 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.
  3. TO USERS: YES this is a BUG in the mod WaterPower report it to them!
  4. [15:47:46] [Client thread/WARN] [FML]: * at net.minecraftforge.oredict.OreDictionary.registerOreImpl(OreDictionary.java:534)
  5. [15:47:46] [Client thread/WARN] [FML]: * at net.minecraftforge.oredict.OreDictionary.registerOre(OreDictionary.java:501)
  6. [15:47:46] [Client thread/WARN] [FML]: * at org.jackhuang.watercraft.common.recipe.IRecipeRegistrar.registerOreDict(IRecipeRegistrar.java:482)
  7. [15:47:46] [Client thread/WARN] [FML]: * at org.jackhuang.watercraft.common.block.ore.ItemBlockMaterial.registerOreDict(ItemBlockMaterial.java:42)
  8. [15:47:46] [Client thread/WARN] [FML]: * at org.jackhuang.watercraft.common.block.ore.ItemBlockMaterial.<init>(ItemBlockMaterial.java:17)
  9. [15:47:46] [Client thread/WARN] [FML]: * at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)...
  10. [15:47:46] [Client thread/WARN] [FML]: ****************************************
  11. [15:47:46] [Client thread/WARN] [FML]: ****************************************
  12. [15:47:46] [Client thread/WARN] [FML]: * A broken ore dictionary registration with name blockZincAlloy has occurred. It adds an item (type: class org.jackhuang.watercraft.common.block.ore.ItemBlockMaterial) 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.
  13. TO USERS: YES this is a BUG in the mod WaterPower report it to them!
  14. [15:47:46] [Client thread/WARN] [FML]: * at net.minecraftforge.oredict.OreDictionary.registerOreImpl(OreDictionary.java:534)
  15. [15:47:46] [Client thread/WARN] [FML]: * at net.minecraftforge.oredict.OreDictionary.registerOre(OreDictionary.java:501)
  16. [15:47:46] [Client thread/WARN] [FML]: * at org.jackhuang.watercraft.common.recipe.IRecipeRegistrar.registerOreDict(IRecipeRegistrar.java:482)
  17. [15:47:46] [Client thread/WARN] [FML]: * at org.jackhuang.watercraft.common.block.ore.ItemBlockMaterial.registerOreDict(ItemBlockMaterial.java:42)
  18. [15:47:46] [Client thread/WARN] [FML]: * at org.jackhuang.watercraft.common.block.ore.ItemBlockMaterial.<init>(ItemBlockMaterial.java:17)
  19. [15:47:46] [Client thread/WARN] [FML]: * at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)...
  20. [15:47:46] [Client thread/WARN] [FML]: ****************************************
  21. [15:47:46] [Client thread/WARN] [FML]: ****************************************
  22. [15:47:46] [Client thread/WARN] [FML]: * A broken ore dictionary registration with name blockNeodymium has occurred. It adds an item (type: class org.jackhuang.watercraft.common.block.ore.ItemBlockMaterial) 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.
  23. TO USERS: YES this is a BUG in the mod WaterPower report it to them!
  24. [15:47:46] [Client thread/WARN] [FML]: * at net.minecraftforge.oredict.OreDictionary.registerOreImpl(OreDictionary.java:534)
  25. [15:47:46] [Client thread/WARN] [FML]: * at net.minecraftforge.oredict.OreDictionary.registerOre(OreDictionary.java:501)
  26. [15:47:46] [Client thread/WARN] [FML]: * at org.jackhuang.watercraft.common.recipe.IRecipeRegistrar.registerOreDict(IRecipeRegistrar.java:482)
  27. [15:47:46] [Client thread/WARN] [FML]: * at org.jackhuang.watercraft.common.block.ore.ItemBlockMaterial.registerOreDict(ItemBlockMaterial.java:42)
  28. [15:47:46] [Client thread/WARN] [FML]: * at org.jackhuang.watercraft.common.block.ore.ItemBlockMaterial.<init>(ItemBlockMaterial.java:17)
  29. [15:47:46] [Client thread/WARN] [FML]: * at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)...
  30. [15:47:46] [Client thread/WARN] [FML]: ****************************************
  31. [15:47:46] [Client thread/WARN] [FML]: ****************************************
  32. [15:47:46] [Client thread/WARN] [FML]: * A broken ore dictionary registration with name blockNeodymiumMagnet has occurred. It adds an item (type: class org.jackhuang.watercraft.common.block.ore.ItemBlockMaterial) 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.
  33. TO USERS: YES this is a BUG in the mod WaterPower report it to them!
  34. [15:47:46] [Client thread/WARN] [FML]: * at net.minecraftforge.oredict.OreDictionary.registerOreImpl(OreDictionary.java:534)
  35. [15:47:46] [Client thread/WARN] [FML]: * at net.minecraftforge.oredict.OreDictionary.registerOre(OreDictionary.java:501)
  36. [15:47:46] [Client thread/WARN] [FML]: * at org.jackhuang.watercraft.common.recipe.IRecipeRegistrar.registerOreDict(IRecipeRegistrar.java:482)
  37. [15:47:46] [Client thread/WARN] [FML]: * at org.jackhuang.watercraft.common.block.ore.ItemBlockMaterial.registerOreDict(ItemBlockMaterial.java:42)
  38. [15:47:46] [Client thread/WARN] [FML]: * at org.jackhuang.watercraft.common.block.ore.ItemBlockMaterial.<init>(ItemBlockMaterial.java:17)
  39. [15:47:46] [Client thread/WARN] [FML]: * at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)...
  40. [15:47:46] [Client thread/WARN] [FML]: ****************************************
  41. [15:47:46] [Client thread/WARN] [FML]: ****************************************
  42. [15:47:46] [Client thread/WARN] [FML]: * A broken ore dictionary registration with name blockIndustrialSteel has occurred. It adds an item (type: class org.jackhuang.watercraft.common.block.ore.ItemBlockMaterial) 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.
  43. TO USERS: YES this is a BUG in the mod WaterPower report it to them!
  44. [15:47:46] [Client thread/WARN] [FML]: * at net.minecraftforge.oredict.OreDictionary.registerOreImpl(OreDictionary.java:534)
  45. [15:47:46] [Client thread/WARN] [FML]: * at net.minecraftforge.oredict.OreDictionary.registerOre(OreDictionary.java:501)
  46. [15:47:46] [Client thread/WARN] [FML]: * at org.jackhuang.watercraft.common.recipe.IRecipeRegistrar.registerOreDict(IRecipeRegistrar.java:482)
  47. [15:47:46] [Client thread/WARN] [FML]: * at org.jackhuang.watercraft.common.block.ore.ItemBlockMaterial.registerOreDict(ItemBlockMaterial.java:42)
  48. [15:47:46] [Client thread/WARN] [FML]: * at org.jackhuang.watercraft.common.block.ore.ItemBlockMaterial.<init>(ItemBlockMaterial.java:17)
  49. [15:47:46] [Client thread/WARN] [FML]: * at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)...
  50. [15:47:46] [Client thread/WARN] [FML]: ****************************************
  51. [15:47:46] [Client thread/WARN] [FML]: ****************************************
  52. [15:47:46] [Client thread/WARN] [FML]: * A broken ore dictionary registration with name blockMagnetite has occurred. It adds an item (type: class org.jackhuang.watercraft.common.block.ore.ItemBlockMaterial) 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.
  53. TO USERS: YES this is a BUG in the mod WaterPower report it to them!
  54. [15:47:46] [Client thread/WARN] [FML]: * at net.minecraftforge.oredict.OreDictionary.registerOreImpl(OreDictionary.java:534)
  55. [15:47:46] [Client thread/WARN] [FML]: * at net.minecraftforge.oredict.OreDictionary.registerOre(OreDictionary.java:501)
  56. [15:47:46] [Client thread/WARN] [FML]: * at org.jackhuang.watercraft.common.recipe.IRecipeRegistrar.registerOreDict(IRecipeRegistrar.java:482)
  57. [15:47:46] [Client thread/WARN] [FML]: * at org.jackhuang.watercraft.common.block.ore.ItemBlockMaterial.registerOreDict(ItemBlockMaterial.java:42)
  58. [15:47:46] [Client thread/WARN] [FML]: * at org.jackhuang.watercraft.common.block.ore.ItemBlockMaterial.<init>(ItemBlockMaterial.java:17)
  59. [15:47:46] [Client thread/WARN] [FML]: * at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)...
  60. [15:47:46] [Client thread/WARN] [FML]: ****************************************
  61. [15:47:46] [Client thread/WARN] [FML]: ****************************************
  62. [15:47:46] [Client thread/WARN] [FML]: * A broken ore dictionary registration with name blockVanadium has occurred. It adds an item (type: class org.jackhuang.watercraft.common.block.ore.ItemBlockMaterial) 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.
  63. TO USERS: YES this is a BUG in the mod WaterPower report it to them!
  64. [15:47:46] [Client thread/WARN] [FML]: * at net.minecraftforge.oredict.OreDictionary.registerOreImpl(OreDictionary.java:534)
  65. [15:47:46] [Client thread/WARN] [FML]: * at net.minecraftforge.oredict.OreDictionary.registerOre(OreDictionary.java:501)
  66. [15:47:46] [Client thread/WARN] [FML]: * at org.jackhuang.watercraft.common.recipe.IRecipeRegistrar.registerOreDict(IRecipeRegistrar.java:482)
  67. [15:47:46] [Client thread/WARN] [FML]: * at org.jackhuang.watercraft.common.block.ore.ItemBlockMaterial.registerOreDict(ItemBlockMaterial.java:42)
  68. [15:47:46] [Client thread/WARN] [FML]: * at org.jackhuang.watercraft.common.block.ore.ItemBlockMaterial.<init>(ItemBlockMaterial.java:17)
  69. [15:47:46] [Client thread/WARN] [FML]: * at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)...
  70. [15:47:46] [Client thread/WARN] [FML]: ****************************************
  71. [15:47:46] [Client thread/WARN] [FML]: ****************************************
  72. [15:47:46] [Client thread/WARN] [FML]: * A broken ore dictionary registration with name blockVanadiumSteel has occurred. It adds an item (type: class org.jackhuang.watercraft.common.block.ore.ItemBlockMaterial) 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.
  73. TO USERS: YES this is a BUG in the mod WaterPower report it to them!
  74. [15:47:46] [Client thread/WARN] [FML]: * at net.minecraftforge.oredict.OreDictionary.registerOreImpl(OreDictionary.java:534)
  75. [15:47:46] [Client thread/WARN] [FML]: * at net.minecraftforge.oredict.OreDictionary.registerOre(OreDictionary.java:501)
  76. [15:47:46] [Client thread/WARN] [FML]: * at org.jackhuang.watercraft.common.recipe.IRecipeRegistrar.registerOreDict(IRecipeRegistrar.java:482)
  77. [15:47:46] [Client thread/WARN] [FML]: * at org.jackhuang.watercraft.common.block.ore.ItemBlockMaterial.registerOreDict(ItemBlockMaterial.java:42)
  78. [15:47:46] [Client thread/WARN] [FML]: * at org.jackhuang.watercraft.common.block.ore.ItemBlockMaterial.<init>(ItemBlockMaterial.java:17)
  79. [15:47:46] [Client thread/WARN] [FML]: * at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)...
  80. [15:47:46] [Client thread/WARN] [FML]: ****************************************
  81. [15:47:46] [Client thread/WARN] [FML]: ****************************************
  82. [15:47:46] [Client thread/WARN] [FML]: * A broken ore dictionary registration with name blockManganese has occurred. It adds an item (type: class org.jackhuang.watercraft.common.block.ore.ItemBlockMaterial) 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.
  83. TO USERS: YES this is a BUG in the mod WaterPower report it to them!
  84. [15:47:46] [Client thread/WARN] [FML]: * at net.minecraftforge.oredict.OreDictionary.registerOreImpl(OreDictionary.java:534)
  85. [15:47:46] [Client thread/WARN] [FML]: * at net.minecraftforge.oredict.OreDictionary.registerOre(OreDictionary.java:501)
  86. [15:47:46] [Client thread/WARN] [FML]: * at org.jackhuang.watercraft.common.recipe.IRecipeRegistrar.registerOreDict(IRecipeRegistrar.java:482)
  87. [15:47:46] [Client thread/WARN] [FML]: * at org.jackhuang.watercraft.common.block.ore.ItemBlockMaterial.registerOreDict(ItemBlockMaterial.java:42)
  88. [15:47:46] [Client thread/WARN] [FML]: * at org.jackhuang.watercraft.common.block.ore.ItemBlockMaterial.<init>(ItemBlockMaterial.java:17)
  89. [15:47:46] [Client thread/WARN] [FML]: * at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)...
  90. [15:47:46] [Client thread/WARN] [FML]: ****************************************
  91. [15:47:46] [Client thread/WARN] [FML]: ****************************************
  92. [15:47:46] [Client thread/WARN] [FML]: * A broken ore dictionary registration with name blockManganeseSteel has occurred. It adds an item (type: class org.jackhuang.watercraft.common.block.ore.ItemBlockMaterial) 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.
  93. TO USERS: YES this is a BUG in the mod WaterPower report it to them!
  94. [15:47:46] [Client thread/WARN] [FML]: * at net.minecraftforge.oredict.OreDictionary.registerOreImpl(OreDictionary.java:534)
  95. [15:47:46] [Client thread/WARN] [FML]: * at net.minecraftforge.oredict.OreDictionary.registerOre(OreDictionary.java:501)
  96. [15:47:46] [Client thread/WARN] [FML]: * at org.jackhuang.watercraft.common.recipe.IRecipeRegistrar.registerOreDict(IRecipeRegistrar.java:482)
  97. [15:47:46] [Client thread/WARN] [FML]: * at org.jackhuang.watercraft.common.block.ore.ItemBlockMaterial.registerOreDict(ItemBlockMaterial.java:42)
  98. [15:47:46] [Client thread/WARN] [FML]: * at org.jackhuang.watercraft.common.block.ore.ItemBlockMaterial.<init>(ItemBlockMaterial.java:17)
  99. [15:47:46] [Client thread/WARN] [FML]: * at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)...
  100. [15:47:46] [Client thread/WARN] [FML]: ****************************************
  101. [15:47:46] [Client thread/WARN] [FML]: ****************************************
  102. [15:47:46] [Client thread/WARN] [FML]: * A broken ore dictionary registration with name blockSteel has occurred. It adds an item (type: class org.jackhuang.watercraft.common.block.ore.ItemBlockMaterial) 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.
  103. TO USERS: YES this is a BUG in the mod WaterPower report it to them!
  104. [15:47:46] [Client thread/WARN] [FML]: * at net.minecraftforge.oredict.OreDictionary.registerOreImpl(OreDictionary.java:534)
  105. [15:47:46] [Client thread/WARN] [FML]: * at net.minecraftforge.oredict.OreDictionary.registerOre(OreDictionary.java:501)
  106. [15:47:46] [Client thread/WARN] [FML]: * at org.jackhuang.watercraft.common.recipe.IRecipeRegistrar.registerOreDict(IRecipeRegistrar.java:482)
  107. [15:47:46] [Client thread/WARN] [FML]: * at org.jackhuang.watercraft.common.block.ore.ItemBlockMaterial.registerOreDict(ItemBlockMaterial.java:42)
  108. [15:47:46] [Client thread/WARN] [FML]: * at org.jackhuang.watercraft.common.block.ore.ItemBlockMaterial.<init>(ItemBlockMaterial.java:17)
  109. [15:47:46] [Client thread/WARN] [FML]: * at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)...
  110. [15:47:46] [Client thread/WARN] [FML]: ****************************************
  111. [15:47:46] [Client thread/WARN] [FML]: ****************************************
  112. [15:47:46] [Client thread/WARN] [FML]: * A broken ore dictionary registration with name Monazite has occurred. It adds an item (type: class org.jackhuang.watercraft.common.block.ore.ItemOre) 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.
  113. TO USERS: YES this is a BUG in the mod WaterPower report it to them!
  114. [15:47:46] [Client thread/WARN] [FML]: * at net.minecraftforge.oredict.OreDictionary.registerOreImpl(OreDictionary.java:534)
  115. [15:47:46] [Client thread/WARN] [FML]: * at net.minecraftforge.oredict.OreDictionary.registerOre(OreDictionary.java:501)
  116. [15:47:46] [Client thread/WARN] [FML]: * at org.jackhuang.watercraft.common.recipe.IRecipeRegistrar.registerOreDict(IRecipeRegistrar.java:482)
  117. [15:47:46] [Client thread/WARN] [FML]: * at org.jackhuang.watercraft.common.block.ore.ItemOre.registerOreDict(ItemOre.java:40)
  118. [15:47:46] [Client thread/WARN] [FML]: * at org.jackhuang.watercraft.common.block.ore.ItemOre.<init>(ItemOre.java:15)
  119. [15:47:46] [Client thread/WARN] [FML]: * at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)...
  120. [15:47:46] [Client thread/WARN] [FML]: ****************************************
  121. [15:47:46] [Client thread/WARN] [FML]: ****************************************
  122. [15:47:46] [Client thread/WARN] [FML]: * A broken ore dictionary registration with name Vanadium has occurred. It adds an item (type: class org.jackhuang.watercraft.common.block.ore.ItemOre) 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.
  123. TO USERS: YES this is a BUG in the mod WaterPower report it to them!
  124. [15:47:46] [Client thread/WARN] [FML]: * at net.minecraftforge.oredict.OreDictionary.registerOreImpl(OreDictionary.java:534)
  125. [15:47:46] [Client thread/WARN] [FML]: * at net.minecraftforge.oredict.OreDictionary.registerOre(OreDictionary.java:501)
  126. [15:47:46] [Client thread/WARN] [FML]: * at org.jackhuang.watercraft.common.recipe.IRecipeRegistrar.registerOreDict(IRecipeRegistrar.java:482)
  127. [15:47:46] [Client thread/WARN] [FML]: * at org.jackhuang.watercraft.common.block.ore.ItemOre.registerOreDict(ItemOre.java:40)
  128. [15:47:46] [Client thread/WARN] [FML]: * at org.jackhuang.watercraft.common.block.ore.ItemOre.<init>(ItemOre.java:15)
  129. [15:47:46] [Client thread/WARN] [FML]: * at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)...
  130. [15:47:46] [Client thread/WARN] [FML]: ****************************************
  131. [15:47:46] [Client thread/WARN] [FML]: ****************************************
  132. [15:47:46] [Client thread/WARN] [FML]: * A broken ore dictionary registration with name Manganese has occurred. It adds an item (type: class org.jackhuang.watercraft.common.block.ore.ItemOre) 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.
  133. TO USERS: YES this is a BUG in the mod WaterPower report it to them!
  134. [15:47:46] [Client thread/WARN] [FML]: * at net.minecraftforge.oredict.OreDictionary.registerOreImpl(OreDictionary.java:534)
  135. [15:47:46] [Client thread/WARN] [FML]: * at net.minecraftforge.oredict.OreDictionary.registerOre(OreDictionary.java:501)
  136. [15:47:46] [Client thread/WARN] [FML]: * at org.jackhuang.watercraft.common.recipe.IRecipeRegistrar.registerOreDict(IRecipeRegistrar.java:482)
  137. [15:47:46] [Client thread/WARN] [FML]: * at org.jackhuang.watercraft.common.block.ore.ItemOre.registerOreDict(ItemOre.java:40)
  138. [15:47:46] [Client thread/WARN] [FML]: * at org.jackhuang.watercraft.common.block.ore.ItemOre.<init>(ItemOre.java:15)
  139. [15:47:46] [Client thread/WARN] [FML]: * at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)...
  140. [15:47:46] [Client thread/WARN] [FML]: ****************************************
  141. [15:47:46] [Client thread/WARN] [FML]: ****************************************
  142. [15:47:46] [Client thread/WARN] [FML]: * A broken ore dictionary registration with name Magnet has occurred. It adds an item (type: class org.jackhuang.watercraft.common.block.ore.ItemOre) 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.
  143. TO USERS: YES this is a BUG in the mod WaterPower report it to them!
  144. [15:47:46] [Client thread/WARN] [FML]: * at net.minecraftforge.oredict.OreDictionary.registerOreImpl(OreDictionary.java:534)
  145. [15:47:46] [Client thread/WARN] [FML]: * at net.minecraftforge.oredict.OreDictionary.registerOre(OreDictionary.java:501)
  146. [15:47:46] [Client thread/WARN] [FML]: * at org.jackhuang.watercraft.common.recipe.IRecipeRegistrar.registerOreDict(IRecipeRegistrar.java:482)
  147. [15:47:46] [Client thread/WARN] [FML]: * at org.jackhuang.watercraft.common.block.ore.ItemOre.registerOreDict(ItemOre.java:40)
  148. [15:47:46] [Client thread/WARN] [FML]: * at org.jackhuang.watercraft.common.block.ore.ItemOre.<init>(ItemOre.java:15)
  149. [15:47:46] [Client thread/WARN] [FML]: * at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)...
  150. [15:47:46] [Client thread/WARN] [FML]: ****************************************
  151. [15:47:46] [Client thread/WARN] [FML]: ****************************************
  152. [15:47:46] [Client thread/WARN] [FML]: * A broken ore dictionary registration with name Zinc has occurred. It adds an item (type: class org.jackhuang.watercraft.common.block.ore.ItemOre) 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.
  153. TO USERS: YES this is a BUG in the mod WaterPower report it to them!
  154. [15:47:46] [Client thread/WARN] [FML]: * at net.minecraftforge.oredict.OreDictionary.registerOreImpl(OreDictionary.java:534)
  155. [15:47:46] [Client thread/WARN] [FML]: * at net.minecraftforge.oredict.OreDictionary.registerOre(OreDictionary.java:501)
  156. [15:47:46] [Client thread/WARN] [FML]: * at org.jackhuang.watercraft.common.recipe.IRecipeRegistrar.registerOreDict(IRecipeRegistrar.java:482)
  157. [15:47:46] [Client thread/WARN] [FML]: * at org.jackhuang.watercraft.common.block.ore.ItemOre.registerOreDict(ItemOre.java:40)
  158. [15:47:46] [Client thread/WARN] [FML]: * at org.jackhuang.watercraft.common.block.ore.ItemOre.<init>(ItemOre.java:15)
  159. [15:47:46] [Client thread/WARN] [FML]: * at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)...
  160. [15:47:46] [Client thread/WARN] [FML]: ****************************************
Advertisement
Add Comment
Please, Sign In to add comment
Advertisement