Minecraft Forums

Quote from Kahr

I'm stretched pretty thin right now rewriting MCPatcher's UI and configuration system to better fit the new launcher

I feel bad for mod makers, what with all the hardcore changes going on with minecraft, particularly with this massive 1.6.x situation. It must be hard to keep on top of things. I don't think I'd have the patience.

Grateful for all your work.

Quote from Alvoria

Will this provide a fix for the compatibility issues with Forge? I really don't want to have to choose between texture packs and mods, you see.

That's a doozy of a question. I'll post a fuller response later.

Quote from Chaos2341

I've some errors on start up in the new client useing MCPatcher for MISA. Please checkout the following link and look at the errors.
In the #minecrafthelp (IRC) I asked also but they told me that it's caused by MCPatcher:

http://pastebin.com/VaYgD4DJ

This is fixed in MCPatcher 4.1.0_04. You'll probably need to redo your MCPatcher settings (Better Grass, mipmapping, etc.).

Quote from SilvoDev

the report file content :/ .. same stuff as in the laucher crash report. Agh,.. frustrating. No hd fonts and diverse creatures for a while I guess

Sorry, I just scanned through the original Crash Report you sent, & expected it to be more bulky(I thought it would be a big crash report), & did go through & ACTUALLY look for the problem. I forgot that crash reports can be small too at times.
Sorry about that.
But Kahr helped you out so you should be good.

Quote from Kahr

That's a strange one. It appears to be a looking for a class I never created. Java has a mind of its own sometimes.

I'm stretched pretty thin right now rewriting MCPatcher's UI and configuration system to better fit the new launcher, so could you try a workaround for me and let me know if it works?

Make sure both Minecraft and MCPatcher are closed. Open up both jar files in an archiver like Winzip:

• mcpatcher-4.1.0_04.jar and
• versions/1.6.2-mcpatcher.jar/1.6.2-mcpatcher.jar

The second file is the patched minecraft.jar. Copy the file com/prupe/mcpatcher/cit/EnchantmentList$1.class from mcpatcher to the same location inside the minecraft jar. Normally this wouldn't work, but since the class in question is completely empty (no fields or methods) it might in this case. I'll incorporate a proper fix in the next release.

That's odd. How could Java just create a path to a file that doesn't exist(without it being told to do so)? Or in that case create a file on its own(also, without it being told to do so)?
Is MCPatcher slowly being coming Self-Aware now too? Because if it is, that would be a great update & a technological break through.
(I mean self-aware as in thinking on its own in the same exact sense as a human being)

BUT Jokes aside, I plan on learning Java to help you with the making/coding/updating(Especially Updating)of MCPatcher, I would like to help you out in making this. You work so hard to keep this project working for ALL versions of Minecraft,(well, almost all versions ... Dang Evil Minecraft Bugs), & you seem to look like you're being pushed to hard & to much. So I want to help you out & make it easier for you. I would like to help in anyway. But first need to learn java. Do I need to learn anything else for MCPatcher? or just Java?

I realize Forge is a somewhat of a competitor what with the mod loading, but is there ANYWAY I can use this to patch the profile I have Forge on? The texture pack I'm wanting to use has textures that won't work unless I use MCPatcher for some reason, which makes no sense since I can use a larger res texture pack with absolutely no problems. Just as well, MCpatcher isn't wanting to work in-game for me, even when using the default profile that is using 1.6.2-mcpatcher. None of the mods that are supposed to be there (Better Grass being the most obvious) just aren't there.

Regarding forge support. For those who are unaware, forge's latest update is essentially an ultimatum to modders: Either be incompatible with us or be incompatible with everything else. As one of MCPatcher's core design principles is to be as compatible as possible, this is completely unacceptable. Making MCPatcher forge-compliant would represent an enormous effort for an inferior result. Among other things it would mean no snapshot support, leaving texture pack artists with no way to work on new features between major Minecraft releases.

There is no technical reason for this "no jar edits" requirement. With a few hours work I was able to bypass it and get a proof-of-concept MCPatcher+forge modified jar up and running with only minor incompatibilities. The result is essentially the same as the old way of adding a forge zip to MCPatcher and clicking Patch.

I am led to conclude that this change is more about promoting an ideology than a technology, and recent public behavior by Lex and cpw only confirms that. They repeatedly insist that any modder not doing things their way is "doing it wrong", as if there were only One True Way to create Minecraft mods. The condescension is especially rich considering forge's crude binary diffs method for base class edits is light years behind what MCPatcher has been doing for over two years now.

So while perhaps I could cobble together something that will work both with and without forge, having to bend over backward to accommodate a group with so little regard for others is extremely frustrating. I would much rather work on new features for artists than constantly jump through forge's ever-changing and utterly unnecessary hoops.

I'm not sure if I'm doing something wrong or its a bug but my spider skins and spider eyes are not syncing up like they used to it just seems to be choosing the eye texture at random.

ASSIMILATE INTO THE FORGE...

RESISTANCE IS... ESSENTIAL..

Speaking as a guy who's become increasingly fed up with the guys, I'm applauding you for standing to your values. They're basically the main reason I have given up on modding for this game due to their technique of grouping everybody together into their ideal view of the modding community...

Which is the forge being the sole overlord of the modding community, being the dictators of what does and doesn't go.

What? They're not working for the benefit of the modders anymore? Oh noooo...

Mc Patcher doesn't work for Minecraft 1.6.2. I Downloaded the new McPatcher (4.1.0_04)
I patch and get this error as i launch the game

---- Minecraft Crash Report ----
// Don't do that.
Time: 13-07-11 23:31
Description: Initializing game
java.lang.NullPointerException
at bka.b(SourceFile:76)
at ats.O(SourceFile:332)
at ats.d(SourceFile:599)
at net.minecraft.client.main.Main.main(SourceFile:101)

A detailed walkthrough of the error, its code path and all known details is as follows:
---------------------------------------------------------------------------------------
-- Head --
Stacktrace:
at bka.b(SourceFile:76)
at ats.O(SourceFile:332)
-- Initialization --
Details:
Stacktrace:
at ats.d(SourceFile:599)
at net.minecraft.client.main.Main.main(SourceFile:101)
-- System Details --
Details:
Minecraft Version: 1.6.2
Operating System: Windows XP (x86) version 5.1
Java Version: 1.7.0_25, Oracle Corporation
Java VM Version: Java HotSpot(TM) Client VM (mixed mode), Oracle Corporation
Memory: 45161552 bytes (43 MB) / 141885440 bytes (135 MB) up to 1037959168 bytes (989 MB)
JVM Flags: 1 total; -Xmx1G
AABB Pool Size: 0 (0 bytes; 0 MB) allocated, 0 (0 bytes; 0 MB) used
Suspicious classes: ~~ERROR~~ NoClassDefFoundError: com/prupe/mcpatcher/cit/EnchantmentList$1
IntCache: cache: 0, tcache: 0, allocated: 0, tallocated: 0
Launched Version: 1.6.2-mcpatcher
LWJGL: 2.9.0
OpenGL: GeForce GT 430/PCIe/SSE2 GL version 4.3.0, NVIDIA Corporation
Is Modded: Very likely; Jar signature invalidated
Type: Client (map_client.txt)
Resource Pack: Misa.zip
Current Language: ~~ERROR~~ NullPointerException: null
Profiler Position: N/A (disabled)
Vec3 Pool Size: ~~ERROR~~ NullPointerException: null

I need Mcpatcher for Connected Textures... My game is based on the connected textures of the Crafting Table and Chiseled Bricks.

Kahr, you have shown by your actions in the past that you will always go well out of your way to assist your fellow mod authors in as selfless a manner as I have ever seen. Your stand on this issue is an inspiration and I thank you for going public with it. No matter how heavy the storm gets, you are not alone.

Hey Kahr. I just wanted to say that I know you might get a lot of backlash for the stance your're taking but I want you to know that there are many people who support your decision including me.

Quote from Kahr

-snip-

It's a shame I can't +1 this more times. It's about time more people realize that forge isn't the beautiful godsend of minecraft modding it's cracked up to be

Alright, I was just wondering if there was a way. I totally understand your point of view on the matter (most of which is indeed made up of fact instead of pretty words, unlike a lot of people I would see online who are just too lazy to do something and would rather hide it). Thank y very much for educating me on the matter. Keep up the good work.

Quote from Kahr

~snip~

Well put Kahr. Stick to your guns. The "our way or the highway" attitude is uncalled for.

*Applause*