LexManos

.... Really dude... really... fix your code. you made a local constant.. why?

Do not teach people to use static constructors for initializing there items. Please change your tutorial to initialize the items in the load() function like a good mod should.

PasteBin.com is your friend for large text files.

YOur 4096 is outdated, stop using it untill it updates.

1) Tripple posting is bad 2) Your 4096 is outdated, it needs to update tot eh latest forge.

trulis, please do not provide incorrect tech support. He should follow whatever directions the clay soldiers mod tells him for installation. However, this will probably not fix your issue, as the mod has to specifically be designed to use forge's texture system instead of ModLoader's system.

https://github.com/pahimar/Equivalent-Exchange-3/blob/master/ee3_client/ee3/client/SoundHandler.java

Forge doesn't 'know' any of those registries. Those just happen to be common ones mods use. All those strings are determined by modders, not forge.

Umm no, you are using something that overwrites some of Forge's base classes, namely adl.class Most likely is you're doing something stupid and installing ModLoaderMP after forge. Don't do this.

Yes, anything 109+ Doe not need ANYTHING int eh client jar, or ANYTHING in the server jar. ModLoader and ModLoaderMP are no longer required in any case, ever.

no... As a modder, you do NOTHING related to ModContainer. ModLoader mods are loaded and every function is called appropriately.

Umm, no, you don't do anything with ModContainer. you do exactly the same thing you would with modloader.

Short answer: No Long answer: Maybe Beyond that, not going to discuss it.

https://github.com/cpw/FML/blob/master/common/cpw/mods/fml/common/modloader/ModLoaderModContainer.java#L440 Also, Dark.. there is... Please go read the ModLoder API and learn it.

Make sure the mods that rely on your API, load after you API... ModLoader has a function for this, look at getPriorities

She uses tile entities

look at the crafting handler interface.

... ya you weren't the first to report it.

Forge related bugs in non-recomended builds is probably a good thing to report on. But as with ANY bug report, make sure you check out the latest versions and make sure you understand if its been addressed and resolved or not. As for things like 4096, yes that falls under the stupid mod that isnt keeping up with forge. That one particularly just needs to update and will RARELY work with anything higher then the version it was built for. Anyways go ahead and post your portalgun issue, however, it is probably a FML issue, not a Forge issue so you need to learn how to distinguish that. But, I have see an issue with PortalGun and I think I know what it is. I'm pretty sure you can blaim it on crazyputje

Its your 4096 fix.

And Im saying that the item itself is only ever created ONCE. Every time that someone crafts the item they get a unique ItemStack not a unique Item. Look into the ItemStack, if you want to have two of the same items different.

Yes, thats how minecraft items work, there are only ever one instance of the class.

https://github.com/cpw/FML

because you're telling it that the file name is 'swoosh.1' '1' is a unknown codec, hence the error.

No, no its not. And if you use the latest forge you dont need modloader.