Minecraft Forums

To a point it does, but it's not perfect yet. 64x and up have glitches with Spider and Endermen textures, and for all resolutions, custom water/lava/portal doesn't work.

You say it works with Pre 1.8 no updated needed, but when I used this with the pre 1.8 Minecraft stops loading.

Also I dunno if this is normal, but I in 1.8 I tried using an HD texturepack with out your patcher (since its not working in 1.8) and the texturepack loaded and worked, but there was a tiny fire animation playing in every tile.

Quote from EmoKnight

MCPatcher do not work right with zombe mod for MC1.8

Quote from Ghost P.

Tested and true...

Could either of you be more specific...?

Probably a class conflict between the patcher and Zombe's Modpack. There always was, from memory. There was a certain mod in the pack that didn't agree with the patcher.

HOWEVER, I recall being able to fix it by patching first and THEN manually installing Zombe's modpack...

EDIT: Just remembered the problem. Ignore that first bit. The problem is, Kahr, Zombe's Modpack adds an extra .class file that apparently matches the patcher's definition (or whatever it uses) for one of the base classes (I think it matches EntityRenderer.java somehow). It must be due to how the patcher identifies classes. Because ofthis, it refuses to patch. I think it's the ZMod.class that causes it. Not entirely sure, I haven't used Zombe's modpack for a while.

I can't patch my minecraft pre 1.8 =( Log:

When will this be updated to fix the Spider and Endermen bugs?
Will we have to wait until 1.8 is officially out?

Quote from vexx32

EDIT: Just remembered the problem. Ignore that first bit. The problem is, Kahr, Zombe's Modpack adds an extra .class file that apparently matches the patcher's definition (or whatever it uses) for one of the base classes (I think it matches EntityRenderer.java somehow). It must be due to how the patcher identifies classes. Because ofthis, it refuses to patch. I think it's the ZMod.class that causes it. Not entirely sure, I haven't used Zombe's modpack for a while.

That sounds familiar, but I think I fixed that bug a while back. I remember tightening that class signature specifically, and, to be extra sure, restricting the matching algorithm to class files with all lowercase names.

Quote from EmoKnight

they do not work with each other

facepalm

The reason I ask for specifics is because I tried installing zombe's mod myself using the patcher and didn't notice any obvious problems. Does it fail to patch? Does it patch but the game fails to launch? Does the game launch but some of the mod's features don't work? Do hordes of carnivorous pink bunnies burst forth from your PC and devour your pets?

Quote from se7enthcell

I can't patch my minecraft pre 1.8 =( Log:

MCPatcher version is 2.1.0_02
OS: Windows 7 6.1 x86
JVM: Sun Microsystems Inc. 1.6.0_26 (32 bit)
Classpath: C:\Users\Craig Hoffman\AppData\Roaming\.minecraft\mcpatcher-2.1.0_02.exe
Exception in thread "main" java.lang.NullPointerException
at com.pclewis.mcpatcher.MinecraftJar.getOrigMD5(MinecraftJar.java:144)
at com.pclewis.mcpatcher.MinecraftJar.<init>(MinecraftJar.java:58)
at com.pclewis.mcpatcher.MCPatcher.setMinecraft(MCPatcher.java:172)
at com.pclewis.mcpatcher.UserInterface.go(UserInterface.java:50)
at com.pclewis.mcpatcher.MCPatcher.main(MCPatcher.java:145)

This is a bug that will be fixed in the next release. In the meantime, deleting the file called "md5s" in the .minecraft/bin folder should fix the problem. This may cause the launcher to redownload the game next time, so copy back the 1.8 minecraft.jar if it does.

Quote from PhantomGamers

When will this be updated to fix the Spider and Endermen bugs?
Will we have to wait until 1.8 is officially out?

Hopefully this evening. I considered including idshift's patch for the furnace crash, but Jeb said on Twitter that the bug will be fixed in an updated pre-release tomorrow anyway.

Quote from Kahr

This is a bug that will be fixed in the next release. In the meantime, deleting the file called "md5s" in the .minecraft/bin folder should fix the problem. This may cause the launcher to redownload the game next time, so copy back the 1.8 minecraft.jar if it does.

Thanks bro worked like a charm

Quote from Kahr

Hopefully this evening. I considered including idshift's patch for the furnace crash, but Jeb said on Twitter that the bug will be fixed in an updated pre-release tomorrow anyway.

I suppose, but if it's not that much trouble it may be better off adding it in anyway.
I really don't know how much work would go into that though, if it is too much I agree that it's fine to just wait for tomorrow when Jeb fixes it.

Looking forward to the other fix though!
Makes it hard to use texture packs when Enderman are white...

Patcher updated to 2.1.1. See OP for details. I decided against including the furnace fix because of the potential for unpredictable behavior when Jeb fixes the bug for real tomorrow. I've left the code there in case it is needed later though.

wow looks awesome I hope I have a great time with it. Oh but umm is there like any possible of blank or useless file generating or like just like it taking up any more room than its supposed to or anything like that like say after you remove a mod or texturepack. LOl sry I ain the best modder but after my first experience being bad with modding trying to be safe here ^.^

I'm having an issue with boxes. When I load an HD pack, the box is the default texture. Everything else is fine, and it's only with HD packs. I'm playing pre-1.8, HD packs are still broken for me without Patcher. Is there a fix for this yet? I've found some awesome HD packs that I'd like to use!

ever think of including files that would allow for texture pack creators to rename items based on a .txt or something?
or allow for redstone recoloring if they wanted to change it to copper or something?
just some ideas, im not sure if it has been brought up before or if it is more effort than its worth.

Quote from Kahr

That sounds familiar, but I think I fixed that bug a while back. I remember tightening that class signature specifically, and, to be extra sure, restricting the matching algorithm to class files with all lowercase names.

Ah OK. As I said, i haven't used Zombe's modpack for a while, so I hadn't noticed you'd fixed it :smile.gif:

Quote from Kahr

facepalm

The reason I ask for specifics is because I tried installing zombe's mod myself using the patcher and didn't notice any obvious problems. Does it fail to patch? Does it patch but the game fails to launch? Does the game launch but some of the mod's features don't work? Do hordes of carnivorous pink bunnies burst forth from your PC and devour your pets?

Now that would be an awesome bug... even if it killed you. Win!

Quote from Kahr

This is a bug that will be fixed in the next release. In the meantime, deleting the file called "md5s" in the .minecraft/bin folder should fix the problem. This may cause the launcher to redownload the game next time, so copy back the 1.8 minecraft.jar if it does.



Hopefully this evening. I considered including idshift's patch for the furnace crash, but Jeb said on Twitter that the bug will be fixed in an updated pre-release tomorrow anyway.

Cool. I thought you might have done something for the furnace, but just so you know, the furnace still causes a crash in a particular circumstance:
1. If the fuel runs out just as it finishes smelting an item, it will crash if there are no more items to be smelted in the input box. (i.e. if you smelt 8 items with 1 piece of coal, it will crash after the 8th has been smelted).
This appears to follow on to another bug, whereby it will crash as soon as you put something in the furnace's top slot while there is fuel in the bottom slot already AND the furnace is unlit, it will crash... but ONLY if the 1st bug has occurred for that particular furnace.

After a successful smelt or two without a crash, the second bug disappears until the 1st bug happens again.

This took a bit of figuring out, and it makes no sense either, since I read about that troublesome bit of code and it doesn't fit in with that...

A heads up for anyone using the second 1.8 preview that Jeb just released. Both are version 1.8 as far as the patcher is concerned, so there's a extra step you need to do. If you don't do these steps the furnace crash or other bugs may mysteriously reappear.

1. Open the .minecraft/bin folder.
2. Delete or rename minecraft-1.8.jar.
3. Download the second 1.8 preview from Jeb's link.
4. Run the patcher. A new minecraft-1.8.jar will be created. Double-check that it is 1897780 bytes.
5. Patch and start the game. Confirm that the title screen says "Minecraft 1.8 Preview 2 ; )" and not simply "Minecraft 1.8 Preview".

You'll need to do this for any future "1.8" release (preview or final).

EDIT: Clarified

The patcher for the first 1.8 pre-release does not work with the 2nd pre release anytime you patch the 2nd it downgrades it back to the 1st one hence why one guy is still getting the furnace glitch. If your MC doesn't have Pre-release 2 :smile.gif: at the bottom left hand (on menu) and top left hand (in game) it means you MCPatcher rolled the game back to the first pre release.

Never-mind another poster showed us how to fix that.

Quote from Rexaton

Never-mind another poster showed us how to fix that.

Another poster? It's the guy who made the tool that showed us how to fix it.
Although I think(hope) most people would have figured that out on there own.

alternative way of installing mods without using the patcher:
1. patch mc with no mods or so and test.
2. press windows key and r and write the following in it: "%appdata%/.minecraft/bin" with no quotes.
3. open the minecraft.jar not the one with a version number with a preferred archiver.
4. drag and drop your mods like you useually would DELETE META-INF and save it.
5. test minecraft if it runs and shows your hd texture pack with no glitches you've done it right.

Can't get it to work with OS X Lion, any help would be appreciated [::