Minecraft Forums

Quote from IvoryTiger

I got it to work by not checking the Extended HD box. All the other options work fine, and the only texture pack I'm using is

http://www.curse.com...-pack-alpha-bui

with no other mods.

I have no mods installed and this worked for me.

I can see crashes have already been reported, but I would like to suggest that the thread title not say the patcher is optimized for 1.5.2, as it clearly is not

Just to clarify It is MC patcher for 1.5.2 that is causing your minecraft clients to crash. It is not your texture packs or mods as far as i have been able to determine.

For those crashing with 1.5.2, please use the beta MCPatcher version linked linked below for now. It contains fixes for 1.5.2 I mistakenly thought I had backported to the release version. EDIT: Updated the release version to support 1.5.2. The beta version is no longer required.

---

Regarding 13w18a,b,c,ad infinitum: Mojang drastically changed the texture code once again, so it will be some time before I can decipher it all and make a compatible version.

Quote from Kahr

For those crashing with 1.5.2, please use the beta MCPatcher version linked linked below for now. It contains fixes for 1.5.2 I mistakenly thought I had backported to the release version. I'll put out a proper 3.0.3_02 later.

MCPatcher 3.1.0-beta4 jar exe.

---

Regarding 13w18a,b,c,ad infinitum: Mojang drastically changed the texture code once again, so it will be some time before I can decipher it all and make a compatible version.

Thanks Kahr for all the effort you put into MCPatcher it helps allot being able to use this tool

How do I CTM the foreground frame part of the item frame? Is that "matchentity" instead of "matchblock" or something? 'Cause the number for the frame is 12, but that's also the number for sand.

I think there's a problem with doors and connected textures method=horizontal.
They seem a bit mixed up.
I'm not sure how to proceed with them.

The left door only has the correct connected texture when the right door is open.
The right door, closed or open, is always using the non-connected textures in textures\blocks.

Here are my properties... doorWood_upper.properties

matchTiles=doorWood_upper
tiles=0 1 2 3
method=horizontal

doorWood_lower.properties

matchTiles=doorWood_lower
tiles=16 17 18 19
method=horizontal

Is it a MCPatcher problem?

I'm getting a slightly different issue then what I've been seeing. After patching, Minecraft seems to think that it's 1.5.1 again. I've force-reloaded the game four times, started it up to see that it was 1.5.2, but after patching it says that it's 1.5.1 again. While this might not be that big of a deal for single-player, it has made it so that I cannot join any servers because it believes there's a version mis-match.

hey guys try this if you're having crash issues on 1.5.2
1. backup your saves/ texture packs / and if your use servers remember to right them down so you can re-add them
2. delete your .minecraft folder
3. download the new launcher from mojang
4. download mcpatcher beta
5. run the new minecraftdev launcher
6. select 1.5.2 and start up a new world
7. exit minecraft ,and launcher
8. run mcpatcher and browse for version 1.5.2 ( it will be in your new .minecraft folder inside versions folder)
9. patch
10. start the new minecraft launcher again, and inside the version list select mcpatcher 1.5.2
11. enjoy

I am currently enjoying misa's texture pack fully, I also have tmi installed as well

MCPatcher is updated to 3.0.4 to fix compatibility with 1.5.2. If you're already using the 3.1.0 beta version I linked earlier and are happy with it, then feel free to keep using it.

I had intended 3.1.0 to be the CIT (Custom Item Textures) release, but the new launcher and now a new set of big texture changes in 13w18 have derailed that plan. CIT is on hold until the new stuff stabilizes enough for me to catch up to it.

Future 3.1.0 versions may not be backward compatible with 1.5, so if any further updates to the 1.5 branch are needed, they'll be 3.0.5, etc.

---

Quote from LE_Vaughn

is there any way you could get the NPC Mod to work with your program? I know its a down right long shot but I among many others have spoken to the "Forge" mod/program owner and he's an extremely rude person (whom said many rude things about you as well hah) and is well - ban happy on his forum...

I'm not sure exactly what you're asking, but if the NPC Mod uses forge, then there's no way around needing forge to run it. That said, MCPatcher generally works fine with forge as long as you load it with MCPatcher. Start from a fresh minecraft.jar, click the Add (+) button and select the minecraftforge-universal-<version>.zip. Add any other zip-based mods (TMI, etc.) the same way.

As for the forge team's rudeness, they pretty much treat anyone who refuses to play in their sandbox that way. Frankly, I consider it a badge of honor.

Quote from Meringue

Thanks again Kahr! I'm curious, what are those drastic changes? Anything interesting (someone without much knowledge about the matter would understand)?

Nothing much of interest to players or artists, but modders might be interested to know that RenderEngine.java is basically gone. Also textures are referred to without the leading /, probably to be more consistent with the zip file format.

I'll do my best to give a brief explanation. In 1.4 and earlier, textures were loaded by a class that MCP called RenderEngine. Not the best name for it since the actual rendering code is elsewhere, but since it was one of the first deobfuscated classes, the name just stuck I guess. Anyway, in 1.4, terrain and items textures where treated like any others, which among other problems meant that animations didn't work properly with HD texture packs.

When 1.5 introduced separate files for each block/item, Mojang added a whole new set of classes to load the individual files and stitch them together to make a "virtual" terrain.png / items.png. However any non-tilesheet textures (mob skins, gui, etc.) used the old code.

In 1.6 it looks like Mojang wants to finish the job and load all textures through the new system. Not the stitching part obviously, but there's plenty of other code in the new system that would benefit unstitched textures too. So it's a reasonable thing to do, even if it means more work for me.

Quote from skittlezmb

Anyone else have a problem with still having white spiders even after patching?

NVM, seems to be a problem with my texture pack. They are fine on other packs. Not sure the problem but it isn't the patcher.

This has to do with the way mob overlay textures are rendered. Make sure the rgb values of transparent pixels in spider_eyes.png are 0 (black). Same goes for enderman_eyes.png.

I checked the .minecraft folder and went into bin. I saw a new file called minecraft-1.5.2 Whats that about??

Quote from cowmugshot

I checked the .minecraft folder and went into bin. I saw a new file called minecraft-1.5.2 Whats that about??

Its a back-up copy

Quote from mmtr1x3

For that you should change the vanilla texture to affect the item frame and after change the tile for this wood with ctm to affect all wood based Blocks, so it would revert to original texture.

I don't make that in my pack since it would broke how the game look for users that don't use MCPatcher

I can't replace it without effecting the source like I can with the fences or pressure plates? Damn

Is the latest mcpatcher version compatible with 13w18c?