LexManos

If it says that the server or client is modified, then its modified, there is no other way around it. Make sure you delete both your jars and the backups of the jars And try agian.

There are variations of setBlock that do less stuff, as well as the ability to edit things directly in the chunks. You'd have to look into what the best code path for you would be.

Ah that is a item id configuration error between your server and yourself. However, I've added NPE protection for that into build #265

God will you guys all read the fucking question? Dont download the source file download the universal file. And to install it just stick all the files from that zip into your minecraft.jar.

Not forge, some other mod you have.

Caught exception from YourName_ModName java.lang.ClassNotFoundException: tutorial.generic.Generic Seems fairly straight forward: You have a class named YourName_ModName which references tutorial.generic.Generic which is not in the class path.; So you need to install tutorial.generic.Generic into your class path.

Get a better texture reader when it comes to the line breaks. We are not going to CRLF. As for forge not working in different versions of windows, the only space it tries to access is the folder that MC is in, which needs write access by minecraft anyways {which is why its in appdata} so there is no reason why it shouldn't work. So you're gunna have to be more specific then 'chokes'.

You screwed up installing and didnt install all the classes, try again.

Almost never does multiple threads in the same program have a different memory space beyond the thread itself. And yes, MC shares the same instance among all threads, and this isn't gunna change, we are not gunna initialize your mod twice. The code will be consistent, if you've done it right. And all of your code should not care what thread it run on, as long as you do not start accessing things you should {like the client world from the server thread} you're fine. Thats how all of MC is designed, single instances shared amung threads.

Wow thats horrible, you should just get the minecraft directory like a sane person. Aside from that, you're expecting the MC api within a year, you're kidding yourself. Also looking into your mod, switching to forge would provide quite a bit of a benefit for your end users and the installation process. As well as probably clean up a lot of your code. And get all your classes out of the default namespace which is horrible, and should never of been in the first place.

Umm no are you high? How exactly do you expect a variable to hold two values? The reason you're getting both of the lines in your log is because both functions are being executed ON THE SAME INSTANCE OF THE CLASS. Thats how inheritance works...

Read The Fucking License

By running the AT, the facilities are there, go look.

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.