Aw, that's a real shame to hear, because prior to 1.7.2 it was possible to use CTM with forge blocks. It worked when blocks still had IDs, but I guess it won't under the new system...
Well thank you for saving me the hassle of continuing to try. I thought it would work since there is documentation for getting MCPatcher to work with Forge in the MCPatcher wiki, but if you think it doesn't work anymore I'll defer to your better judgement.
Interesting. I was under the impression that this was broken in 1.6.x and hadn't worked since.
Don't give up hope yet! There's a possibility I'm wrong about this. Believe me, I'd love to be since I suddenly have a few really good ideas for CTM-ing mod blocks. I'll have to give it a try at some point and see what I find out. Won't be today, though.
Interesting. I was under the impression that this was broken in 1.6.x and hadn't worked since.
Don't give up hope yet! There's a possibility I'm wrong about this. Believe me, I'd love to be since I suddenly have a few really good ideas for CTM-ing mod blocks. I'll have to give it a try at some point and see what I find out. Won't be today, though.
That would be awesome. I'll work with you any way I can to see if we can't figure something out!
how do i convert a 1.7 resource pack to a 1.6 texture pack?
By doing absolutely nothing.
Any pack that works for 1.7 should also work for 1.6 just fine. Maybe one or two things that might need to be tweaked, but it'll function just fine in every technical respect.
I've made a set of full CTM for hardened and stained hardened clay. It makes them look drier towards the edges. I want all types of hardened clay to connect, which I can achieve using connect=material, but this makes it also connect with other types of stone. I tried the following without luck:
Is there a way to get all the hardened clay types (stained and not) to connect, but not with anything else?
I'm also struggling to get the new block name instead of ID changes working how I want. For example if I try and apply CTM rules to hardened clay I should be able to have a file called anything with the following inside:
Yet it still didn't work. So I've ended up naming the file hardened_clay.properties which then works, but I was under the impression you didn't have to name the block in the .properties file name. Am I doing something wrong?
You still need to use "matchBlocks" I believe. "blocks" is only for biome color maps.
Ah cheers. The new wiki confused me as it mentions "blocks=" and "textures=". I suspect it's not currently possible to have both hardened clay and stained clay connected and not with anything else as they have separate block IDs. I hit another problem which I suspect is me missing something obvious again. What is wrong with the following:
Thank you for the help so far kwerti. I have yet another problem.
I have two folders "bookshelf_connect" and "bookshelf_random". The first contains the files to make bookshelves connect horizontally and the second contains the files to make bookshelves have random textures. The idea is that anyone using my pack which likes one of these features, but not the other, can easily delete the folder they don't like. I can't get this working.
The current .properties files.
(There are also .properties files for the left, right, and middle sections)
The above works fine when both folders are included. If you delete the "bookshelf_connect" folder it obviously stops randomising as the second .properties file doesn't target the default texture (it targets "3.png" from "bookshelf_connect").
I tried adding the following that would run after all the others and randomise any remaining default bookshelf textures.
It randomises, but stops the textures from being connected. It's as if "matchTiles=bookshelf" is in fact matching the block if that texture was present originally even if previous rules have changed it. I don't understand why this is happening. I even tried having one .properties file that targets both "3.png" and the default bookshelf texture.
I hope I'm explaining myself well enough.
I believe that matchTiles will overwrite matchBlocks in a conflict. Try adding "weight=1" to the horizontal CTM. (The resolution order is weight -> matchTiles -> matchBlocks -> file name). Right now, two properties files are targeting the same textures, so matchTiles is winning.
I also personally like to use matchBlocks and weight whenever possible. I would use this for the random fallback:
He is working on the recent 1.8 snapshots, BUT he has been moving lately, so he has been busy. Everyone has a life, so you just have to wait, he will be done soon.
So, having thoroughly searched this site and googled everywhere I can think of and trying to read through some 400+ pages of information and code language I don't understand I just have a question:
Can I use mcpatcher to have the seamless glass I see in so many resource packs with the default 1.7.9 MC? Or do I have to download/make a custom pack just to get that? If so could someone point me to a good tutorial that's actually up to date? Also if this is in the wrong thread please let me know.
So, having thoroughly searched this site and googled everywhere I can think of and trying to read through some 400+ pages of information and code language I don't understand I just have a question:
Can I use mcpatcher to have the seamless glass I see in so many resource packs with the default 1.7.9 MC? Or do I have to download/make a custom pack just to get that? If so could someone point me to a good tutorial that's actually up to date? Also if this is in the wrong thread please let me know.
I just want my glass to blend together
MCPatcher isn't like Optifine. If you want to use CTM (or any of MCPatcher's features) you need to have a Resource Pack that has the CTM (or other MCPatcher features) in it. If you use MCPatcher, but you're not using a Resource Pack, then nothing will change for you.
Also MCPatcher isn't updated to 1.7.9, BUT Kahr is working on updating MCPatcher, he is just in the middle of moving & stuff like that.
Okay. Thank you, seriously. That's literally all I've been trying to find out. I hadn't even heard of optifine or "CTM" till I started researching how the glass thing was supposed to work and from what I can tell MCP is the way to go, if only for continued updating. As to the update, it should still work with 1.7.9 right? Or was that too big of an update content wise to hope for compatibility? Thus far I haven't seen any issues but like I said I'm running vanilla right now
Okay. Thank you, seriously. That's literally all I've been trying to find out. I hadn't even heard of optifine or "CTM" till I started researching how the glass thing was supposed to work and from what I can tell MCP is the way to go, if only for continued updating. As to the update, it should still work with 1.7.9 right? Or was that too big of an update content wise to hope for compatibility? Thus far I haven't seen any issues but like I said I'm running vanilla right now
Don't give up hope yet! There's a possibility I'm wrong about this. Believe me, I'd love to be since I suddenly have a few really good ideas for CTM-ing mod blocks. I'll have to give it a try at some point and see what I find out. Won't be today, though.
That would be awesome. I'll work with you any way I can to see if we can't figure something out!
Any pack that works for 1.7 should also work for 1.6 just fine. Maybe one or two things that might need to be tweaked, but it'll function just fine in every technical respect.
Is the name of any texture file different from 1.6 to 1.7.9? For example, "redstone_block" to "block_redstone".
You still need to use "matchBlocks" I believe. "blocks" is only for biome color maps.
Putting the CENDENT back in transcendent!
matchTiles is relative to /textures/blocks by default; you should not need to specify the full path. I have tested this code and it works:
Putting the CENDENT back in transcendent!
I believe that matchTiles will overwrite matchBlocks in a conflict. Try adding "weight=1" to the horizontal CTM. (The resolution order is weight -> matchTiles -> matchBlocks -> file name). Right now, two properties files are targeting the same textures, so matchTiles is winning.
I also personally like to use matchBlocks and weight whenever possible. I would use this for the random fallback:
Putting the CENDENT back in transcendent!
Kahr's MCPatcher support is much quicker than anything else i'm aware of for MC.
He supports the snapshots except for the more recent few, i.e. up to 14w11b.
• Follow Lithos on Twitter for release announcments
* Join the Lithos Discord for previews and to help
He is working on the recent 1.8 snapshots, BUT he has been moving lately, so he has been busy. Everyone has a life, so you just have to wait, he will be done soon.
Owner of the account "Piano", Ex-Player Council Member for Hypixel.
I made a tool that will repackage mcpatcher so it's easily loadable by forge, Liteloader, or as a library.
https://github.com/killjoy1221/MCPatcher-Repackager
Download's under releases.
Mods I work on and maintain:
TabbyChat | Mine Little Pony
My Blog
Can I use mcpatcher to have the seamless glass I see in so many resource packs with the default 1.7.9 MC? Or do I have to download/make a custom pack just to get that? If so could someone point me to a good tutorial that's actually up to date? Also if this is in the wrong thread please let me know.
I just want my glass to blend together
MCPatcher isn't like Optifine. If you want to use CTM (or any of MCPatcher's features) you need to have a Resource Pack that has the CTM (or other MCPatcher features) in it. If you use MCPatcher, but you're not using a Resource Pack, then nothing will change for you.
Also MCPatcher isn't updated to 1.7.9, BUT Kahr is working on updating MCPatcher, he is just in the middle of moving & stuff like that.
Okay. Thank you, seriously. That's literally all I've been trying to find out. I hadn't even heard of optifine or "CTM" till I started researching how the glass thing was supposed to work and from what I can tell MCP is the way to go, if only for continued updating. As to the update, it should still work with 1.7.9 right? Or was that too big of an update content wise to hope for compatibility? Thus far I haven't seen any issues but like I said I'm running vanilla right now
MCPatcher works perfectly with 1.7.9 and 14w11b.
Putting the CENDENT back in transcendent!