LexManos

You are confusing things that are in vanilla minecraft, and not part of Forge with things that we should be responsible for. That is just stupid, We are not Mojang, we are not providing generic support for all random stuff you want to do with MC. 99% of everything you want to do is not our domain. The parts that are are documented well enough in code and have logical names that with a small amount of effort on the modder's end it can be understood. A Full blow javadocs or something like that is Mojang's domain not ours. We provide enough information on what Forge does that it is sufficient. If you want documentation what Minecraft does, go bitch at Mojang. As for tutorials and other things, that is not my job, I suck at writing them, the community has full access to this forum and the wiki and a plethora of other places to create them. It is just that nobody cares enough to do things properly so people just regurgitate the same stuff they have been fed. If you need the highlevel descripotion of Minecraft functionality, write it. Also, banned for 7 days for being a fucking thread necro over, and over, and over, and over. ALL of your posts have necroed threads that are over a month old.

Thats for bumping a month of thread just to have me yell at you to update your forge cuz this particular issue has already been fixed .. a month ago.. If you are using the updated version and still getting those items then its the mod makers issue, not ours. Also, dont bump month old threads -.-

So.. you're trying to run a vanilla mod on a bukkit server, the hell makes you think that'll work?

Thats cuz you have to set it up properly. If you can't figure it out, you shouldn't be doing it.

Or, you know.. you could use it as is. Its fairly expandable and designed to work with other textures.

I'll be doing a 3.4 final release when I start work on 1.3 shit.

That isnt necessarily, it gets used heavily so it gets JITed quite quickly.

This has nothing to do with EE, you just fucked up installing forge. Try harder, do better.

Interesting, it may be that you screwed soemthing up while installing, do those classes exist? You're using the official jdk?

How the hell are you running the install? And there should be no reason that your install is failing if you have everything installed correctly.

We will NOT be releasing for the pre-releases. However, cpw has been doing a lot of hard work to design FML for 1.3. He already has FML running on the w27 snapshot. However, 1.3's release is kinda really bad timing. cpw is going on a trip sometime this week so he will be gone for a while. Then I will have to be out of my house the 2nd-5th. So what I plan to do is if cpw gets a FML stable for the snapshots, I will start working on 1.3 Forge, however a note to Mod devs this will be a RADICAL change. I will be introducing a new event system that should make things a lot easier. But that will mean it will take some time. As well as almost every mod having to re-write themselves for the new Local SMP, this are gunna be hectic. So ya.... this update is gunna be fun, keep an eye on the github for more details. I will work as well as I can, but I garentee that 1.3 will be a bitch, for everyone.

!! Modified jar detected. Unpredictable results !! Thars your problem.

Actually I don't have a normal job cuz its a bitch to find one. But no, Mojang won't hire us, Thats what they hired the Bukkit team for. So just shush.

-.- all the crap that comes up when you run install.bat.. thats the log, post it here.

What OS/JVM are you on?

Full log, not just the last few lines.

I could, but meh

It is https://github.com/MinecraftForge/MinecraftForge/blob/master/forge/update_patches.bat The bat just adds the bin folder to the path, where you know.. the diff.exe is...

Well thats a lie. Consideirng if you use optifine, with A texturepack that has custom lava/flames it will not have any issue. And honestly, if you're saying that you MUST use a 2x2 to play MC, then well, you shouldnt be playing MC.

ASparently from the looks of our code, if the dimensions for the texture is set properly before the update function is called it will work fine. BUT Honestly its YOUR problem. Stop using a texturepack thats < 16x.

Aparently not, and as you are using Optifine this is his territory not ours.

From the sounds of what Over and True are getting, rewriting it to use Math would actually be detrimental as after JIT kicks in everything outperforms in MathHelper. Interesting, JIT is quite annoying in some cases

Use a texturepack of sufficient size.

use update_patches.bat not .py

Had to drag that out of the trash, but that kiddies, is how you bend over and ask for the ban paddle.