Where is the Amazing 3D textures. Looks like that the link is bronken D:
It would appear that the person who hosted (and created) those textures has pulled the download for an unknown reason. Unfortunately, there's no way to obtain them at this time.
I'm trying to use this mod (3.1.1) with Tekkit, but I got some ID conflicts.
When I changed the block ID's in Metallurgy from (for example) 901:6 to 4901:6, I get an array index out of bounds error
Does changing the ID's not work?
---- Minecraft Crash Report ----
// You should try our sister game, Minceraft!
Time: 20.07.13 17:27
Description: Failed to start game
java.lang.ArrayIndexOutOfBoundsException: 4901
at rebelkeithy.mods.metablock.SubBlock.<init>(SubBlock.java:44)
at rebelkeithy.mods.metallurgy.core.metalsets.OreInfo.init(OreInfo.java:303)
at rebelkeithy.mods.metallurgy.core.metalsets.MetalSet.init(MetalSet.java:70)
at rebelkeithy.mods.metallurgy.core.metalsets.MetalSet.<init>(MetalSet.java:35)
at rebelkeithy.mods.metallurgy.metals.MetallurgyMetals.preInit(MetallurgyMetals.java:160)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
at java.lang.reflect.Method.invoke(Unknown Source)
at cpw.mods.fml.common.FMLModContainer.handleModStateEvent(FMLModContainer.java:494)
at sun.reflect.GeneratedMethodAccessor5.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
at java.lang.reflect.Method.invoke(Unknown Source)
at com.google.common.eventbus.EventHandler.handleEvent(EventHandler.java:74)
at com.google.common.eventbus.SynchronizedEventHandler.handleEvent(SynchronizedEventHandler.java:45)
at com.google.common.eventbus.EventBus.dispatch(EventBus.java:314)
at com.google.common.eventbus.EventBus.dispatchQueuedEvents(EventBus.java:296)
at com.google.common.eventbus.EventBus.post(EventBus.java:267)
at cpw.mods.fml.common.LoadController.propogateStateMessage(LoadController.java:165)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
at java.lang.reflect.Method.invoke(Unknown Source)
at com.google.common.eventbus.EventHandler.handleEvent(EventHandler.java:74)
at com.google.common.eventbus.SynchronizedEventHandler.handleEvent(SynchronizedEventHandler.java:45)
at com.google.common.eventbus.EventBus.dispatch(EventBus.java:314)
at com.google.common.eventbus.EventBus.dispatchQueuedEvents(EventBus.java:296)
at com.google.common.eventbus.EventBus.post(EventBus.java:267)
at cpw.mods.fml.common.LoadController.distributeStateMessage(LoadController.java:98)
at cpw.mods.fml.common.Loader.loadMods(Loader.java:514)
at cpw.mods.fml.client.FMLClientHandler.beginMinecraftLoading(FMLClientHandler.java:160)
at net.minecraft.client.Minecraft.func_71384_a(Minecraft.java:410)
at net.minecraft.client.MinecraftAppletImpl.func_71384_a(SourceFile:56)
at net.minecraft.client.Minecraft.run(Minecraft.java:732)
at java.lang.Thread.run(Unknown Source)
A detailed walkthrough of the error, its code path and all known details is as follows:
---------------------------------------------------------------------------------------
Changing the IDs does work, but you're choosing a number that doesn't allow enough space. Block IDs can't go past 4096, and IDs more often than not get shifted by 256. 4901 is effectively 5157, in this case, though both numbers are outside the allowed range for Block IDs. It's worth noting that Block IDs are different than Item IDs, which have a much larger range available to them.
Put simply, choose a much lower number to change your IDs to, and things should be fine.
Okay, thanks, that fixed that.
However, I still have an ID conflict. Apparently there is one or multiple items which have a fixed itemID that I can not change in the config
---- Minecraft Crash Report ----
// I let you down. Sorry
Time: 20.07.13 20:57
Description: Failed to start game
java.lang.IllegalArgumentException: Slot 920 is already occupied by thermalexpansion.block.device.BlockLamp@17ac5d when adding rebelkeithy.mods.metallurgy.metals.utilityItems.tnt.BlockLargeTNT@354729
at net.minecraft.block.Block.<init>(Block.java:340)
at net.minecraft.block.BlockTNT.<init>(SourceFile:24)
at rebelkeithy.mods.metallurgy.metals.utilityItems.tnt.BlockLargeTNT.<init>(BlockLargeTNT.java:21)
at rebelkeithy.mods.metallurgy.metals.MetallurgyMetals.createUtilityItems(MetallurgyMetals.java:287)
at rebelkeithy.mods.metallurgy.metals.MetallurgyMetals.Init(MetallurgyMetals.java:212)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
at java.lang.reflect.Method.invoke(Unknown Source)
at cpw.mods.fml.common.FMLModContainer.handleModStateEvent(FMLModContainer.java:494)
at sun.reflect.GeneratedMethodAccessor5.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
at java.lang.reflect.Method.invoke(Unknown Source)
at com.google.common.eventbus.EventHandler.handleEvent(EventHandler.java:74)
at com.google.common.eventbus.SynchronizedEventHandler.handleEvent(SynchronizedEventHandler.java:45)
at com.google.common.eventbus.EventBus.dispatch(EventBus.java:314)
at com.google.common.eventbus.EventBus.dispatchQueuedEvents(EventBus.java:296)
at com.google.common.eventbus.EventBus.post(EventBus.java:267)
at cpw.mods.fml.common.LoadController.propogateStateMessage(LoadController.java:165)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
at java.lang.reflect.Method.invoke(Unknown Source)
at com.google.common.eventbus.EventHandler.handleEvent(EventHandler.java:74)
at com.google.common.eventbus.SynchronizedEventHandler.handleEvent(SynchronizedEventHandler.java:45)
at com.google.common.eventbus.EventBus.dispatch(EventBus.java:314)
at com.google.common.eventbus.EventBus.dispatchQueuedEvents(EventBus.java:296)
at com.google.common.eventbus.EventBus.post(EventBus.java:267)
at cpw.mods.fml.common.LoadController.distributeStateMessage(LoadController.java:98)
at cpw.mods.fml.common.Loader.initializeMods(Loader.java:690)
at cpw.mods.fml.client.FMLClientHandler.finishMinecraftLoading(FMLClientHandler.java:206)
at net.minecraft.client.Minecraft.func_71384_a(Minecraft.java:447)
at net.minecraft.client.MinecraftAppletImpl.func_71384_a(SourceFile:56)
at net.minecraft.client.Minecraft.run(Minecraft.java:732)
at java.lang.Thread.run(Unknown Source)
A detailed walkthrough of the error, its code path and all known details is as follows:
---------------------------------------------------------------------------------------
BlockLargeTNT is for HE TNT, using block ID 920. You should be able to change it, but if changing it doesn't make any difference, you can change the ID on Applied Energistics' side.
Actually, they're not. The default textures are named differently in 1.6. Instead of "bootsDiamond", for example, they're now named "diamond_boots". So, I'm actually right on this. Same things goes for the in-game armor that you see on your character, as well.
Actually, they're not. The default textures are named differently in 1.6. Instead of "bootsDiamond", for example, they're now named "diamond_boots". So, I'm actually right on this. Same things goes for the in-game armor that you see on your character, as well.
Except for the fact that those textures are for 1.5.2.
Except for the fact that those textures are for 1.5.2.
Which means that whoever wanted to use these textures would have to rename each and every texture to work with 1.6. That seems like a lot of work to me.
Which means that whoever wanted to use these textures would have to rename each and every texture to work with 1.6. That seems like a lot of work to me.
The 1.6 version of Metallurgy already retextures vanilla items. If you want retextured vanilla items in 1.6, just enable it via config.
1.5.2 has no option, that's the reason this pack was made.
Hey I have a small question: Is there any way to disable the chests added by Metallurgy? I recall that the config files had an option to change the values to "false" in M2, but I can't seem to find those values anymore.
Yes! a great idea! however...
If it burns infinitely, could you still set the stairs and slabs on fire? if not (which i guess) what is the use?
also an idea, you could put it in the crafting table to get some sort of furnace fuel. life blaze powder, or fire charge, or even a new thing.
The Meaning of Life, the Universe, and Everything.
Join Date:
7/3/2013
Posts:
54
Minecraft:
Gak2321
Member Details
Another suggestion: Galvorn (meteoric iron)
Anyway awesome mod, keep up the good work.
Rollback Post to RevisionRollBack
The Road goes ever on and on, down from the the door where it began. Now far ahead the Road has gone, and I must follow if I can, pursuing it with eager feet, until it joins some larger way, where many paths and errands meet. And whither then? I cannot say.
If Facebook, Myspace, and Twitter were all destroyed, 99% of teens would go insane. If you're one of the 1% that would be laughing at them, copy this into your signature and hope it happens (I'm one of them... can you figure out which?)
-
View User Profile
-
View Posts
-
Send Message
Curse PremiumIt would appear that the person who hosted (and created) those textures has pulled the download for an unknown reason. Unfortunately, there's no way to obtain them at this time.
-
View User Profile
-
View Posts
-
Send Message
Curse PremiumChanging the IDs does work, but you're choosing a number that doesn't allow enough space. Block IDs can't go past 4096, and IDs more often than not get shifted by 256. 4901 is effectively 5157, in this case, though both numbers are outside the allowed range for Block IDs. It's worth noting that Block IDs are different than Item IDs, which have a much larger range available to them.
Put simply, choose a much lower number to change your IDs to, and things should be fine.
-
View User Profile
-
View Posts
-
Send Message
Curse PremiumIn this specific case, the config you'll need to look in is MetallurgyUtility.cfg. You're looking for this section:
#################### # "item ids" #################### ""item ids"" { I:Bitumen=29015 I:Fertilizer=29009 I:"HE TNT"=920 I:"LE TNT"=921 I:Magnesium=29014 I:"Magnesium Igniter"=29007 I:Match=29008 I:Phosphorus=29011 I:Potash=29016 I:Saltpeter=29013 I:Sulfur=29012 I:Tar=29010 }BlockLargeTNT is for HE TNT, using block ID 920. You should be able to change it, but if changing it doesn't make any difference, you can change the ID on Applied Energistics' side.
You need to rename the textures to work with the new Metallurgy mod.
-
View User Profile
-
View Posts
-
Send Message
Curse PremiumThe textures in that pack are correctly named.
Right you are. I think they just stopped to forwarding that in the code.
Actually, they're not. The default textures are named differently in 1.6. Instead of "bootsDiamond", for example, they're now named "diamond_boots". So, I'm actually right on this. Same things goes for the in-game armor that you see on your character, as well.
-
View User Profile
-
View Posts
-
Send Message
Curse PremiumExcept for the fact that those textures are for 1.5.2.
Which means that whoever wanted to use these textures would have to rename each and every texture to work with 1.6. That seems like a lot of work to me.
-
View User Profile
-
View Posts
-
Send Message
Curse PremiumThe 1.6 version of Metallurgy already retextures vanilla items. If you want retextured vanilla items in 1.6, just enable it via config.
1.5.2 has no option, that's the reason this pack was made.
Oh, okay. I didn't know that. Thanks for telling me.
[url="http://www.minecraftforum.net/topic/365357-"][IMG]http://i.imgur.com/XQNnk.png[/IMG][/url]
You meant Century Ago
Anyway awesome mod, keep up the good work.
If Facebook, Myspace, and Twitter were all destroyed, 99% of teens would go insane. If you're one of the 1% that would be laughing at them, copy this into your signature and hope it happens (I'm one of them... can you figure out which?)