Since my first impressions of MCPatcher, I’ve avoided it like a bad tooth ache. The bad memories still haunt me.<\/p>\n
It was back in \/infdev\/ (or was it Alpha?) I tried out MCPatcher. Even then, I was leary about anything “patching” my game that wasn’t an official patch from Notch. I remember trying to install a 32x texture pack. Can’t remember the name.
\nI patch, get in, and the game is running really slow (I think I still had a shit computer compared to now). So I tried to remove this “patch”, and it didn’t, forcing me to do a clean install.<\/p>\n
Since then, I said FUCK YOU to it. But the Painterly pack is starting to be more for MCPatcher, turning a few things I like into MCPatcher-only options.
\nToday, I decided to give it another chance. Seeing how it’s been a few years, maybe they got the bugs from the past squished.
\nMCPatcher is supposed to take the stress out of adding mods (after just adding them due to one mod that refuses to work right ever again). That’s one reason why I decided to give it another go.<\/p>\n
I started by doing a full backup of my entire .minecraft folder, then running MCPatcher.
\nUnfortunately, this thing seems “incompatible” with TortoiseSVN. First it tells me that minecraft.jar has been modded (no shit). So I tell Tortoise to fall back to Revision 1 which was when I got 1.1.0 back, and now it can’t find the .jar at all. From its POV, it’s not there. But Windows Explorer says it IS there.<\/p>\n
I asked what the fuck is going on, and hopefully I’ll have a response by tomorrow. I fear they’ll tell me that I’m going to have to use that thing again to downgrade to 1.1.0 from 1.2.3, just to get MCPatcher to recognize the file structure.<\/p>\n","protected":false},"excerpt":{"rendered":"
Since my first impressions of MCPatcher, I’ve avoided it like a bad tooth ache. The bad memories still haunt me. It was back in \/infdev\/ (or was it Alpha?) I tried out MCPatcher. Even then, I was leary about anything … Continue reading