Hello,
I've been compiling my own custom texture pack and in it, I have connected textures for use with MCPatcher, but I've run into a problem with the connected textures for my End Stone. They don't work at all, it still uses just the default End Stone texture. I know the problem has something to do with the .properties files in my End Stone folder in the ctm folder within my texture pack, but I don't know how to change them to get them to work with the .png files for my End Stone.
Hoping that this isn't confusing, I would really appreciate some guidance and help from someone who knows how to fix this.
Alright, I understand your problem, to help you I may need some screenshots, but I'll see what I can do,
first off, you can look at almost any texture pack to see some examples. Sphax for instance there is a folder called "ctm"
if you then go deeper into the second "ctm" folder within it you will find a lot of textures, only pay attention to the textures that look like glass, and the "glass" properties file.
Now once inside it is easy to see what to do. inside the "glass" properties file, you find some numbers
Try downloading this sphax folder as an example. then get back to me, of course, change the size of eazh texture from 128 pixels, to whatever you are working with, also, you should be able to rename the properties file to the block id of the block you are texturing.
you can download the example here: download
Hey swvn9Gaming,
before I get started, thank you for taking the time to help me.
Ok, here are some screenshots of the ctm folder for my End Stone:
There's 250 individual textures, and I've noticed some of them are the same. I got this from a texture pack that included extra textures to use to change out some of the other ones. I've changed the .properties file to the according End Stone Block ID which is 121 (found on both the Minecraft Wiki http://www.minecraft.../wiki/End_Stone, and also by using Too Many Items by Marglyph).
Now here's a look inside the .properties files:
I've learned that the lines after # have no effect what so ever on how ctm works, and I did not find anything that referred to them on the MCPatcher forum post in the section about CTM. All the other ctm textures that I have for any block are working fine.
And this is what it looks like in-game after a successful patch with MCPatcher:
"#" = a comment, not actual code. On the other hand, make sure that end stone is actually named end stone in 1.6, there's been issues with stone bricks and cobblestone.
Well, Let me have a think. First of all, it depends what version you're using. Next, if you could upload the pack you're working on to dropbox and give me a link, I'll see what the problem is.
"#" = a comment, not actual code. On the other hand, make sure that end stone is actually named end stone in 1.6, there's been issues with stone bricks and cobblestone.
Thank you macadamia238 for your help, but I knew beforehand that "#" lines were just comments/notes, but your reminder to check to see if End Stone was properly written within the .properties files made me wonder if the ID value for End Stone had changed and I went to go check but it's remained the same from Minecraft version 1.5.2.
Just to be clear to anyone reading this post I am using the new 1.6.1 version and I realized I've been calling it a texturepack (if that caused any belief I was using an older version) and I should have called it a resourcepack from the get go.
Rollback Post to RevisionRollBack
To post a comment, please login or register a new account.
I've been compiling my own custom texture pack and in it, I have connected textures for use with MCPatcher, but I've run into a problem with the connected textures for my End Stone. They don't work at all, it still uses just the default End Stone texture. I know the problem has something to do with the .properties files in my End Stone folder in the ctm folder within my texture pack, but I don't know how to change them to get them to work with the .png files for my End Stone.
Hoping that this isn't confusing, I would really appreciate some guidance and help from someone who knows how to fix this.
first off, you can look at almost any texture pack to see some examples. Sphax for instance there is a folder called "ctm"
if you then go deeper into the second "ctm" folder within it you will find a lot of textures, only pay attention to the textures that look like glass, and the "glass" properties file.
Now once inside it is easy to see what to do. inside the "glass" properties file, you find some numbers
Try downloading this sphax folder as an example. then get back to me, of course, change the size of eazh texture from 128 pixels, to whatever you are working with, also, you should be able to rename the properties file to the block id of the block you are texturing.
you can download the example here: download
before I get started, thank you for taking the time to help me.
Ok, here are some screenshots of the ctm folder for my End Stone:
There's 250 individual textures, and I've noticed some of them are the same. I got this from a texture pack that included extra textures to use to change out some of the other ones. I've changed the .properties file to the according End Stone Block ID which is 121 (found on both the Minecraft Wiki http://www.minecraft.../wiki/End_Stone, and also by using Too Many Items by Marglyph).
Now here's a look inside the .properties files:
I've learned that the lines after # have no effect what so ever on how ctm works, and I did not find anything that referred to them on the MCPatcher forum post in the section about CTM. All the other ctm textures that I have for any block are working fine.
And this is what it looks like in-game after a successful patch with MCPatcher:
Servers Rules|Support Forum Rules|Show Your Creation Rules|Off Topic Rules
Thank you macadamia238 for your help, but I knew beforehand that "#" lines were just comments/notes, but your reminder to check to see if End Stone was properly written within the .properties files made me wonder if the ID value for End Stone had changed and I went to go check but it's remained the same from Minecraft version 1.5.2.
Just to be clear to anyone reading this post I am using the new 1.6.1 version and I realized I've been calling it a texturepack (if that caused any belief I was using an older version) and I should have called it a resourcepack from the get go.