Register New Block Texture Without Registering A New Block

[LRFLEW]

I want to update a forge mod I made to work with MC 1.5+, but I'm having trouble with the new texture system.  My mod changes how a vanilla block is rendered on the client (in this case, it changes the standard rail blocks).  I used to be able to just register a multi-texture file in the mod initializer method and set the block's render id and texture file to my own.  All the tutorials I've seen for MC 1.5+ are added in the block class.  I really don't want to override the vanilla class for this mod as it complicates the installation process.  Is there a way to register a texture file outside of a block class?

[LRFLEW]

I want to update a forge mod I made to work with MC 1.5+, but I'm having trouble with the new texture system.  My mod changes how a vanilla block is rendered on the client (in this case, it changes the standard rail blocks).  I used to be able to just register a multi-texture file in the mod initializer method and set the block's render id and texture file to my own.  All the tutorials I've seen for MC 1.5+ are added in the block class.  I really don't want to override the vanilla class for this mod as it complicates the installation process.  Is there a way to register a texture file outside of a block class?

[RANKSHANK]

sounds like you may need to either reflect to get access to the block's icon and replace it with your own, or reflect to replace the block instance with one of your own which will bind your custom texture

[RANKSHANK]

sounds like you may need to either reflect to get access to the block's icon and replace it with your own, or reflect to replace the block instance with one of your own which will bind your custom texture

[LRFLEW]

sounds like you may need to either reflect to get access to the block's icon and replace it with your own, or reflect to replace the block instance with one of your own which will bind your custom texture

 

I'm not sure what you mean by "reflect to get access", and I can't seem to replace the instance of the block easily. 

[LRFLEW]

sounds like you may need to either reflect to get access to the block's icon and replace it with your own, or reflect to replace the block instance with one of your own which will bind your custom texture

 

I'm not sure what you mean by "reflect to get access", and I can't seem to replace the instance of the block easily. 

[LRFLEW]

I think I may have answered my own question.  I was surfing the code when I found the TextureStitchEvent.  It seems that the pre texture stitch even happens at just the right time to register the textures.  However, the textures aren't appearing correctly.  All I'm seeing is diamond block, gold block, and emerald block textures.  Any reason why that might be?

 

Edit: never mind.  I was having problems with how many times registerIcon() actually gets called.

[LRFLEW]

I think I may have answered my own question.  I was surfing the code when I found the TextureStitchEvent.  It seems that the pre texture stitch even happens at just the right time to register the textures.  However, the textures aren't appearing correctly.  All I'm seeing is diamond block, gold block, and emerald block textures.  Any reason why that might be?

 

Edit: never mind.  I was having problems with how many times registerIcon() actually gets called.

[RANKSHANK]

check the debug texture that's outputted in the /jars directory to see if it's there, some code will need to be shown

[RANKSHANK]

check the debug texture that's outputted in the /jars directory to see if it's there, some code will need to be shown