Minecraft Forums

Quote from Gavenom

I like the program, but It will be a pain on getting the animations to work for 1.5.

Actually, I wouldn't be surprised if you could take existing (image strip) animations and rename them to the file of the block they're supposed to animate and them just working. Well, that is just a plain animation, not sure if they have implemented changing the duration of frames, or even for the entire animation, that may be the biggest pain....

Quote from Gavenom

I like the program, but It will be a pain on getting the animations to work for 1.5.

Quote from insomniac_lemon

Actually, I wouldn't be surprised if you could take existing (image strip) animations and rename them to the file of the block they're supposed to animate and them just working. Well, that is just a plain animation, not sure if they have implemented changing the duration of frames, or even for the entire animation, that may be the biggest pain....

If anything we can be pretty sure that they will make it easier at some point if not right away. Mojang consistently surprises me with how much they change things to make things easier for modders/texture designers to stick with their opensource mind frame.

A lot of games talk the talk but don't walk the walk heh

Quote from XSSheep

Well first off, open the jar file with java, it should bring up a menu telling you to select a texture pack to convert and it will allow you to browse to where your texture pack is if it's not in minecraft's texture pack folder, which it opens by default. If you've done that and it you can't find your pack, make sure your pack is zipped (in the .zip format) because that's what format the unstitcher requires as far as I can tell.

Also, I think it should be noted that the unstitcher.jar might need to be located in your /.minecraft/bin folder (along side your minecraft.jar) in order for it to work. I tried it from my downloads and texturepacks folder and it didn't work, but then it worked correctly when I put it in my bin folder.

Quote from insomniac_lemon

Also, I think it should be noted that the unstitcher.jar might need to be located in your /.minecraft/bin folder (along side your minecraft.jar) in order for it to work. I tried it from my downloads and texturepacks folder and it didn't work, but then it worked correctly when I put it in my bin folder.

I have a dedicated Minecraft folder (separate from .minecraft) and it ran just fine from there. Thought you'd like to know.

I'm seriously hoping that there's a long term benefit to this change, because having each image as its own file is a serious pain in the rear, imo. Don't fail me now Dinnerbone!

Quote from Alvoria

I have a dedicated Minecraft folder (separate from .minecraft) and it ran just fine from there. Thought you'd like to know.

I'm seriously hoping that there's a long term benefit to this change, because having each image as its own file is a serious pain in the rear, imo. Don't fail me now Dinnerbone!

I can honestly see nothing but good from this as it removed a large majority of limitations that the old design created opening up way more things we can do along with modders to expand things even farther. It also makes things run smoother as the files themselves will only be loaded if needed which will clear up resources for things that in the past would have been impossible due to memory issues.

Quote from XSSheep

One bad thing is that it makes comparing textures side by side very difficult so it's a lot harder to keep your textures consistent with each other. It's also going to break all of our CTM property files which is gonna take a fair while to fix for those who have plenty of CTM in their texture packs...

I can see the CTM thing I haven't gotten to far into that. I also don't understand the other part because I do every texture in a single file in Illustrator 1024x1024 then import them into a terrain file that is sized for the size texture pack I need in Photoshop then exported as a png. I just never thought of the comparing textures outside of the game would be convenient but that's probably just the way I do it and am used to only working on single files where you guys are used to working in the terrain file.

Although if there is one thing watching and speaking with you guys is you all are really smart and effective so I am sure as a community everyone will adapt and find new effective ways of accomplishing what you need.

Quote from XSSheep

What I mean is that it's hard to keep your style consistent and make sure that the colours of each texture work well together if you can't see them all on one sheet and you just work on them individually. That might just be a personal thing though.

A palette for the entire terrain will now be harder to do (well, unless you decide before hand and index a file with those colors and use that for every image), although as a side effect is does mean that you will be able to per-block palettes much easier, and also you will more easily be able to index those to make the files to make them smaller while not needing to reduce the colors (like how default has way too many un-needed colors), or worry about the indexing while working on new blocks.

Also, maybe someone can make a restitcher.jar with Dinnerbone's unstitcher.jar so pack makers could travel back and forth freely (to an extent) relatively easily, so they can work with textures together like we can now.

Quote from XSSheep

What I mean is that it's hard to keep your style consistent and make sure that the colours of each texture work well together if you can't see them all on one sheet and you just work on them individually. That might just be a personal thing though.

Quote from insomniac_lemon

A palette for the entire terrain will now be harder to do (well, unless you decide before hand and index a file with those colors and use that for every image), although as a side effect is does mean that you will be able to per-block palettes much easier, and also you will more easily be able to index those to make the files to make them smaller while not needing to reduce the colors (like how default has way too many un-needed colors), or worry about the indexing while working on new blocks.

Also, maybe someone can make a restitcher.jar with Dinnerbone's unstitcher.jar so pack makers could travel back and forth freely (to an extent) relatively easily, so they can work with textures together like we can now.

I'm not sure about paint.net or gimp, since a lot of people use those but with photoshop you can set slices for a files and name them. So you can ultimately work on one file and split them in the program. Not sure if the other programs used have a similar feature. I will check into it.
edit:

In gimp it's called "Guillotine (Image > Transform > Guillotine)." it slices by guide or “Slice” filter (Filters > Web > Slice)

In Paint.net it's called Slicing

Well this wont effect me much, I already do each texture in it's own file then copy it into the terrain.png,

But will only the terrain be effected? Or items as well?

I just attempted working on some blocks for my Definitance pack with the new 1.5 layout, and has anyone considered the problem with all textures for the same large block tiling? If a block occupies more than one space, it has multiple images, but all images must tile together perfectly. Having them in one spot made that easier as the textures were together anyway. Although, I can't think of a way of putting more than one texture in an image without losing the vanilla HD texture compatibility.


Edit: It also occurs to me that with HD textures compatible with vanilla Minecraft, much fewer people who download texture packs will download a patcher, so any features that, by patching there client, they would get automatically, they won't get anymore. If things like CTM, animated textures, custom colours and other features are compatible with a patcher, a lot less people would get those features.