LexManos

I would go find the 'A critical server error' line and make it print its exception.

There is nothing that has changed related to this, so you'd have to find out whats causing it.

Ya I know about it, its a non-priority, so I don't really care about fixing it. There are a few things in mcp that we break by merging things together, but none of them are of any importance. This isn't a MCP issue its a FML/Forge issue as we are the ones merging the codebase. {We patch MCP}

Can you read the logs it has nothing to do with optifine: Caused by: java.lang.LinkageError: loader (instance of net/minecraft/GameUpdater$2): attempted duplicate class definition for name: "Item762x51mm0" Your launcher is fucked up, whatever launcher you're using Aside from that the mod is trying to define the same class twice, so thats your issue, go speak with the mod author, not us.

MM this is a mod issue not a forge issue. You need to track ti down by removing mods untill the crash stops. And then go speak with the mod author, not us.

Thats a NPE on his end and therefor requires him to take a look, not us.

Well quick glance at it shows that the packet does not support canceling it. You may want to write a PR for FML to add support for returning null from the handler. Best bet for getting a new feature into FML is a pull request on github. {If you dont know how to do it, get someone who does, or learn}

Probably he best place to look is ModLoader.registerKey as it points to the FML functions that deal with it.

Update, this was fixed like 40 builds ago. If you're still having issues on the latest build provide your mod code so I can test.

There is, it may just be hidden, get a differnt archiving tool that lets you see it.

If a modloader mod does not work with Forge, do as the big red letters at the top of the forum say, and post god damn logs and links to the mod. We cant debug 'omg lyke it no workz', that gives us no info to work with and annoys me a lot. Anyways, closed.

The issue starts with: ColorizerGrass.setGrassBiomeColorizer(this.renderEngine.getTextureContents("/misc/grasscolor.png")); Which means that somehow your /misc/grasscolor.png is not a valid 255x255 image. Figure out why it isnt. This isnt a forge issue.

Its a really simple fix there are mechanics in there to fix it. So its up to sk89q to do it, probably be 10 mins worth of work once he is made aware of it.

Lucas, I am the only on who is allowed to be rude on this forum, esp I am the only one who is allowed to swear. Beyond that, yes this is LBM's issue, not ours. Tell them to become compatible. There is no logical reason they should still be using ML/MLMP. So goodby.

Dont care guesses are useless, he should go to the mod author not us, this has nothing to do with us.

She uses tile entities to store extra data.

When it come to specific render types, you have to fall under the restrictions of those types, or render the block yourself. So it appears the height is not taken from the bounds for rendering crops. So you're gunna have to do it yourself.

Access transformers are for Core Mods only. There is generally less support for making core mods as they are reserved for people who know what they are doing. In general, you don't need to do these things.

Ugh this is getting out of hand he has done nothing but bitch while and moan, refuse to follow directions, refuse to post proper logs, and bitch at me about my work. Banned, fuck it.

Why would I do that? Optifine is the good one, MCPatcher is the shit one. But yes, FML detects optifine and sticks a fake mod container in there so people can detect it as a mod.

Damn macs doing it wrong again -.- delete the __macosx folder from the jar.

IIRC cpw has fixed cjb issues in recent versions.

what launcher are you using?

Once again I cant tell you what is wrong unless you tell me what is on that line.

Do me a favor 1) Update, you're really fucking old 2) Try loading without any mods