LexManos

How about.. setTextureFile... no.. thats to freakin obvious.

Look at IArrowNock/LooseHandlers

Alright just to shut up people You cant I want to add a hook for this but its very low on my priorities list right now. People who are saying reflection, please stop being a dick and only say reflection when you are right.

Have you even freakin looked at the class? You already can.

Don't use MCPatcher to install mods esp if you're installing the yogsbox it comes with a installer...

So.... you're creating instances of items.. that are vanilla classes, never telling them you want them to use a custom texture.. and expecting them to use a custom texture... Also, you're edting base classes.. awesome...

Update your JDK.

Post a log of recompile

Meh

Actually no, it has something to do with Forestry, its trying to access something called stump. There isnt anything named that in Minecraft. Bug or install problem with Forestry.

MLMP has been unneeded and incompatible for quite some time.

Do a search for Colorizer, even when you disable everything that crap gets injected. And please don't even assume you know anything about how MCPatcher works or bytecode injection, else you wouldn't be so high and mighty. Bytecode injection is good for SMALL things, I actually have a project for 1.3 that i've been working on that will massivly simplify things. However, its is not a valid solution for large scale things like Optifine or Forge. Yes the functionality of 'put all mods here and click button poof installed' is nice. And can be done quite easily with a lot of other tools. As for the whole issue of communicating with TexturePack authors, thats Mojangs/Optifines/MCPatchers jobs not forge. I see no legitimate reason to take over there functionality. From every usage case I have found Optifine works perfectly fine. Does everything a TexturePack author needs, and hes open to speaking with people about improvements. Hes not the fastest person on the block but he gets the job done. As I said, the FML HD texture modifications were BUG FIXES. Nothing more. They fixed the BUGS in Vanilla MC that made the game CRASH and massive visual artifacts while playing. We never intended to be the one stop shop for all texture related needs, as I said it already exists in Optifine, there is no reason for us to do it. So I ask this, give me a VALID reason that we should absorb MCPatcher. Bytecode injection is not a valid reason. Texturepack authors are not valid reason, they already have there solutions. The ONLY valid reason is for simpler installation for the end user, and there are discussions going on directly for that that have nothing to do with MCPatcher.

Thread locked cuz you're a moron.

Of optifine, any of the C series should work, but try the latest C.

Reinstall optifine and make sure you're using a compatible version

I repeat, what are you needing done that can not be done with the CURRENT HOOKS that are in place in that exact spot.

I dont like the fact that its poorly coded, and injects itself when it is not needed and you can't disable it. its the cause of so many issues because people think that it is just a 'mod installer' and then bitch when it crashes cuz its doing stuff its told not to do. Back in the day I really liked it I even created a few mods that were pure bytecode injection using it. However, I dont intend to ingest it, there are already things in place for a lot of its bytecode related functionality to be supported. We will be shipping ASM with 1.3's Forge. As for the ease of use for the installer, I am waiting on someone to create a simple open source system that doesn't do the complexities of bytecode patching because its unneeded. A simple installer similar to the yogsbox from last I saw is all thats needed. If MCPatcher worked like it was supposed to, I would have no issues recommending it along with Optifine But it doesn't And it causes a lot of stupid issues So I dont

Post your code. This usually happens when you only have one achivement on the page, but it looks like you have more then one.

Humm it appears that EE needs to update its Soundhandler, and that my wrapper to hopefully prevent this error has failed. Awesome, i'll fix that later, but ya, EE needs to update.

Code

Highly doubt its a FML issue. However link me to the offending plugin and I'll take a look.

-jar not -cp -.-

What are you needing done that can not be done buy the current hooks that are in place in that exact spot?

You can fallow directions and give a fucking proper error log. Its not like we dont tell you exactly how to do it http://minecraftforge.net/forum/index.php/topic,20.0.html http://www.minecraftwiki.net/wiki/Crash#How_to_Get_a_Crash_Report

You have to many mods that are not forge mods. They are all using addOverride which is mkaing it run out of open slots. Talk to whoever makes some of your mods and tell them to update to forge so they dont have to take up override space anymore.