I remember posting on a thread where someone mentioned one a while back, but I don't want to sift through my 54 pages of posts to find it... The thread was about connecting textures and someone suggested a library of some sort.
Rollback Post to RevisionRollBack
Click this banner for a list of illegal mod distributors -- only download from legal sites!
if you are working with 1.8+ than it's pretty much impossible (if you want to keep your mental health) because of the json models. There would be way to much model variants. You need like 32 variants for each face of the block for each block.
if you are working with 1.8+ than it's pretty much impossible (if you want to keep your mental health) because of the json models. There would be way to much model variants. You need like 32 variants for each face of the block for each block.
CTMLib is made by the Chisel team(Drullkus and co, not Cricket or whoever else has a fork), they seem to have built a very nice CTM system for 1.9. Hopefully they'll release it as a separate library for others to use.
Rollback Post to RevisionRollBack
Please don't PM me asking for help, I will just redirect you to the appropriate forum, where there are others who are far more skilled than me.
Once Chisel gets into a stable state for 1.9, they plan to rip out all the fancy CTM code and move it into CTMLib again. Just need to work out the kinks.
CTMLib is made by the Chisel team(Drullkus and co, not Cricket or whoever else has a fork), they seem to have built a very nice CTM system for 1.9. Hopefully they'll release it as a separate library for others to use.
Technically we have a separate mod thats you relocate block models from the vanilla/forge json handler to the chisel json handler. You can find the proof-of-concept here. It's not stable and requires Chisel in 1.9.0 to run.
All you need to do is to go to the regular blockstate.json, and put ctm: in front of the model name. I.E. "ctm:minecraft:oak_log". For anything that happens after that, you can refer to the Chisel json assets until we make proper documentation.
Anyone know of a good connected textures api which I could use in my mod?
Is there an api for that? Also it is pretty crucial to specify the version of mc you are working with.
Not doing mc modding that much anymore because I am making a full blown game that does not have limitations that mc has. (rip Magiology for now)
I may come back if MC fixes it's rendering pipeline.
I remember posting on a thread where someone mentioned one a while back, but I don't want to sift through my 54 pages of posts to find it... The thread was about connecting textures and someone suggested a library of some sort.
CTMLib is a library for connected textures, though it's currently only available for 1.7.10. Though I see you already found that.
if you are working with 1.8+ than it's pretty much impossible (if you want to keep your mental health) because of the json models. There would be way to much model variants. You need like 32 variants for each face of the block for each block.
Not doing mc modding that much anymore because I am making a full blown game that does not have limitations that mc has. (rip Magiology for now)
I may come back if MC fixes it's rendering pipeline.
CTMLib is made by the Chisel team(Drullkus and co, not Cricket or whoever else has a fork), they seem to have built a very nice CTM system for 1.9. Hopefully they'll release it as a separate library for others to use.
Please don't PM me asking for help, I will just redirect you to the appropriate forum, where there are others who are far more skilled than me.
This is not the signature you are looking for.
Banners and such things
Once Chisel gets into a stable state for 1.9, they plan to rip out all the fancy CTM code and move it into CTMLib again. Just need to work out the kinks.
Yeah I'm using CTMLib now. Works great!
Technically we have a separate mod thats you relocate block models from the vanilla/forge json handler to the chisel json handler. You can find the proof-of-concept here. It's not stable and requires Chisel in 1.9.0 to run.
All you need to do is to go to the regular blockstate.json, and put ctm: in front of the model name. I.E. "ctm:minecraft:oak_log". For anything that happens after that, you can refer to the Chisel json assets until we make proper documentation.