Whenever I try to patch minecraft.jar, the first time, with a 32x32 texture pack it always stops at around 75% on the terrain.png
I'm not using custom water/lava.
However it always works the second time. The only difference seems to be the fix creating and overwriting the old backup on the first run. the minecraft.original.jar
I use the same texture.zip for both runs.
Rollback Post to RevisionRollBack
Website & Forums for our public SMP server TerraCubic
Server IP: 109.169.60.140
I eventually figured this out. I was using the items.png from Misa's HD pack, which is 64 pixels, so the patcher was upsizing it to 128 pixels, which should have worked fine but for some reason was causing bugs with the compass and dial.png. Swapping to Aegeon's items.png with Misa's armor and weapons spliced on solved the problem entirely.
Yes, it's best to have all your graphics files at the target resolution, at this point, the patcher modifies pointers (it doesn't actually modify the graphics files themselves, that's up to the user) for the main terrain.png, items.png and maybe dial.png for the watch, though I think you can use a standard size for that one, though it will look jaggy on a high texture pack. Also note that the patcher expects these files to be in the main minecraft.jar file, so you will have to have the correct files there, not in your texture pack. If you have multiple texture packs, the graphics will be used from the main JAR file, not your texture pack file(s). Since I think the only things affected are the watch and compass, this shouldn't be a big deal. Animated water and lava are also affected, now that I think of it, that would probably be the most noticeable, when changing texture packs.
Quote from MikeC2103 »
Whenever I try to patch minecraft.jar, the first time, with a 32x32 texture pack it always stops at around 75% on the terrain.png
I'm not using custom water/lava.
However it always works the second time. The only difference seems to be the fix creating and overwriting the old backup on the first run. the minecraft.original.jar
I use the same texture.zip for both runs.
It's always best to start fresh from a new minecraft download. I always delete everything in the /bin folder, let minecraft update and then apply patches. That way you know the patch is being applied to the correct JAR file, and no old backups are getting in the way.
Rollback Post to RevisionRollBack
D_B
To tell them how to live is to prevent them living.
When I try to use it it just re-downloads minecraft to purge your program and I don't get my fix. I didn't pick a texture pack in the patcher screen, but I assumed you had it working in tandem with the new textue pack selection screen in the game itself.
I tried it selecting the file on my desktop and it also purges the HD patch.I don't think it likes me deleting the minecraft. original and version file. Either way It just selects the texture pack from its own texture pack folder. Might want to explain how to get around this, I am stumped.
This patch is not compatible with the new texture pack selector, it only works if you install the packs the old way
Not true! I always ( and just did ) patch without selecting a texture pack in the patcher, and then place the texturepack.zip in the texturepacks folder.
This combination of client and patche will not work if custom water or lava are ticked as said many times, but I don't see any issue installing the texture packs the new way.
It works here on minecraft client 1.2.5 with 1.1.9_02 patcher. And before for as many versions as I have used it for. Since 1.1.2 I think.
When I try to use it it just re-downloads minecraft to purge your program and I don't get my fix. I didn't pick a texture pack in the patcher screen, but I assumed you had it working in tandem with the new textue pack selection screen in the game itself.
I tried it selecting the file on my desktop and it also purges the HD patch.I don't think it likes me deleting the minecraft. original and version file. Either way It just selects the texture pack from its own texture pack folder. Might want to explain how to get around this, I am stumped.
This patch is not compatible with the new texture pack selector, it only works if you install the packs the old way
Not true! I always ( and just did ) patch without selecting a texture pack in the patcher, and then place the texturepack.zip in the texturepacks folder.
This combination of client and patche will not work if custom water or lava are ticked as said many times, but I don't see any issue installing the texture packs the new way.
Actually it is true, the in game texture tool is fine on packs that don't have anything extra, but if you have different biome colors or water these won't work, that's pretty significant for some texture packs.... so to say that you don't see any issues, is false sorry. I say stick with the patcher until notch realizes he's going to need to support at least 32x.
Have this mod been abandon? I`d like an update soon ô.ô
I really hope not. Fortunately it still works just without custom water and lava and with Misa's 64x64 Realistic Overhaul the default water and lava goes well with the rest of the textures.
Two days is a little early to be wondering if something is abandoned! I have some stuff in the works that should make custom water/lava as resilient to updates as everything else, but I don't have a lot of time to work on it right now.
LATEST UPDATE:
1.1.9_03 - Fixed custom water/lava for 1.2.5.
Updating Minecraft
To use with the latest Minecraft update:
0. Download the latest patcher
1. Run the patcher
2. Click "Minecraft Folder"
3. Close the patcher
4. In the minecraft folder, delete minecraft.original.jar and the file called "version"
5. Run Minecraft with the launcher and log in to make sure the latest version is downloaded
6. Close Minecraft
7. Run the patcher
8. If Minecraft version is higher than 1.2.5, uncheck custom water and lava.
9. Click Patch
Problems
As always, if you had a problem before this post and it doesn't go away with this update, please post it again.
Hey, I'm still having problems with my watch and compass. This latest patch fixed my portals though (thanks for that) so I don't know what the problem is. I'll try to post a screen of what's going on.
Is anyone else get a weird problem where the foliage like reeds, flowers, etc. have the white around where the plant texture is. So when I have a flower it is inside a white square so a white square with the plant on top is basically what they look like.
Is anyone else get a weird problem where the foliage like reeds, flowers, etc. have the white around where the plant texture is. So when I have a flower it is inside a white square so a white square with the plant on top is basically what they look like.
Have you previousely edited the terrain.png using MS Paint? If so, download Gimp 2 or Paint.net and use that to edit textures. Also delete the MS Paint edited terrain.png because it's corrupt!
things seemed smooth at first. Patched alright, but I hit run minecraft and nothing happened. I tried to open the client itself, but it just loads the mojang icon and goes black screen. I will assume you don't have it up for the about 3rd time Notch decided to re-update the code. For the sake of people like you, I wish he would just take a 2 day run through the world doing everything so he can fine tune the updates because I am sick of waiting days for people like you having to play catch up like this, it isn't fair.
Rollback Post to RevisionRollBack
Quote from Destrozo »
So you say 1.4 is fail because you don't know how to update your server? WTF
Thats like saying all cars fail because you don't know how to put gas in them.
Hey, I'm still having problems with my watch and compass.
Please post the texture pack you are using and the log from the patcher in code tags.
Quote from Giroro44 »
Is anyone else get a weird problem where the foliage like reeds, flowers, etc. have the white around where the plant texture is. So when I have a flower it is inside a white square so a white square with the plant on top is basically what they look like.
Sounds like transparency problem with your terrain.png. Please post the texture pack you are using.
Quote from PhoenixBrave »
EDIT: Fixed it!
When this happens (to anyone), please post what was wrong and how you fixed it, even if it is something silly like "my computer wasn't plugged in." It might help someone else and lets me know what to fix or clarify.
Quote from zoram »
Patched alright, but I hit run minecraft and nothing happened. I tried to open the client itself, but it just loads the mojang icon and goes black screen. I will assume you don't have it up for the about 3rd time Notch decided to re-update the code.
There hasn't been a Minecraft update since the last patcher update. When you use the Run Minecraft button a log window should pop up. The information there most likely indicates what is wrong. You should probably post it if you want help.
Quote from zoram »
For the sake of people like you, I wish he would just take a 2 day run through the world doing everything so he can fine tune the updates because I am sick of waiting days for people like you having to play catch up like this, it isn't fair.
Notch purposefully uses a tool to obfuscate the code and hinder modders. I don't mind; it's what makes it interesting to me. Consider this: if he didn't do it, I wouldn't have made this fix! (Then realize that someone else would have probably made it even earlier anyway.)
As I said before, I am working on some things to make the patcher work across updates without it's own update. 90% of it already does.
I'm not using custom water/lava.
However it always works the second time. The only difference seems to be the fix creating and overwriting the old backup on the first run. the minecraft.original.jar
I use the same texture.zip for both runs.
Server IP: 109.169.60.140
Yes, it's best to have all your graphics files at the target resolution, at this point, the patcher modifies pointers (it doesn't actually modify the graphics files themselves, that's up to the user) for the main terrain.png, items.png and maybe dial.png for the watch, though I think you can use a standard size for that one, though it will look jaggy on a high texture pack. Also note that the patcher expects these files to be in the main minecraft.jar file, so you will have to have the correct files there, not in your texture pack. If you have multiple texture packs, the graphics will be used from the main JAR file, not your texture pack file(s). Since I think the only things affected are the watch and compass, this shouldn't be a big deal. Animated water and lava are also affected, now that I think of it, that would probably be the most noticeable, when changing texture packs.
It's always best to start fresh from a new minecraft download. I always delete everything in the /bin folder, let minecraft update and then apply patches. That way you know the patch is being applied to the correct JAR file, and no old backups are getting in the way.
D_B
To tell them how to live is to prevent them living.
Not true! I always ( and just did ) patch without selecting a texture pack in the patcher, and then place the texturepack.zip in the texturepacks folder.
This combination of client and patche will not work if custom water or lava are ticked as said many times, but I don't see any issue installing the texture packs the new way.
It works here on minecraft client 1.2.5 with 1.1.9_02 patcher. And before for as many versions as I have used it for. Since 1.1.2 I think.
Any advice?
Not true! I always ( and just did ) patch without selecting a texture pack in the patcher, and then place the texturepack.zip in the texturepacks folder.
This combination of client and patche will not work if custom water or lava are ticked as said many times, but I don't see any issue installing the texture packs the new way.
Actually it is true, the in game texture tool is fine on packs that don't have anything extra, but if you have different biome colors or water these won't work, that's pretty significant for some texture packs.... so to say that you don't see any issues, is false sorry. I say stick with the patcher until notch realizes he's going to need to support at least 32x.
I really hope not. Fortunately it still works just without custom water and lava and with Misa's 64x64 Realistic Overhaul the default water and lava goes well with the rest of the textures.
LATEST UPDATE:
1.1.9_03 - Fixed custom water/lava for 1.2.5.
LATEST DOWNLOAD:
WINDOWS: http://github.com/downloads/pclewis/mcp ... 1.9_03.exe
MAC: http://github.com/downloads/pclewis/mcp ... 1.9_03.dmg
EVERYBODY ELSE: http://github.com/downloads/pclewis/mcp ... 1.9_03.jar
Updating Minecraft
To use with the latest Minecraft update:
0. Download the latest patcher
1. Run the patcher
2. Click "Minecraft Folder"
3. Close the patcher
4. In the minecraft folder, delete minecraft.original.jar and the file called "version"
5. Run Minecraft with the launcher and log in to make sure the latest version is downloaded
6. Close Minecraft
7. Run the patcher
8. If Minecraft version is higher than 1.2.5, uncheck custom water and lava.
9. Click Patch
Problems
As always, if you had a problem before this post and it doesn't go away with this update, please post it again.
post attempt 6
Hmm, I can't attach a pic so here's a link to it instead
http://img17.mediafire.com/052579bfe08d97a738169aa1619f5b3d718400027db518fe22be928467b10d2b4g.jpg
I really don't like not having a watch/compass so any help would be much appreciated.
Sorry that we are such an impatient bunch. Now you know how Notch must feel sometimes.
Thank you very much for the update.
Have you previousely edited the terrain.png using MS Paint? If so, download Gimp 2 or Paint.net and use that to edit textures. Also delete the MS Paint edited terrain.png because it's corrupt!
I used to have toes
EDIT: Fixed it!
I freakin love this....
"We who are about to patch salute you!"
Thanks again, keep up the good work and have fun,
Heftig
[simg]http://img826.imageshack.us/img826/709/sigimagea.png[/simg]
Please post the texture pack you are using and the log from the patcher in code tags.
Sounds like transparency problem with your terrain.png. Please post the texture pack you are using.
When this happens (to anyone), please post what was wrong and how you fixed it, even if it is something silly like "my computer wasn't plugged in." It might help someone else and lets me know what to fix or clarify.
There hasn't been a Minecraft update since the last patcher update. When you use the Run Minecraft button a log window should pop up. The information there most likely indicates what is wrong. You should probably post it if you want help.
Notch purposefully uses a tool to obfuscate the code and hinder modders. I don't mind; it's what makes it interesting to me. Consider this: if he didn't do it, I wouldn't have made this fix! (Then realize that someone else would have probably made it even earlier anyway.)
As I said before, I am working on some things to make the patcher work across updates without it's own update. 90% of it already does.
Hey I got it fixed, I used a larger items.png instead of 16x16 its now 32x32.
Credit goes to Tlos for the resized defaults and to the resized items I'm using(below)
here's a link to the post where I found them http://www.minecraftforum.net/viewtopic.php?f=25&t=16966