OvermindDL1

Inficraft does it, look at its source, it is public on github.

That is for ModLoader, quit saying stupid things. For Forge it should work in the mod jar in the proper place.

Actually it should be in your own mods jar in the armor folder.

PlayerAPI edits can be made dynamically in forge now using the asm library most likely.

But it is still not updated to work with Forge though last I saw. Does it say that it is now?

Optifine is not yet updated last I checked though?

Should be fixed since 204, update your Forge: http://jenkins.minecraftforge.net:7070/job/forge/lastBuild/ (that will always link to latest) Reference: http://jenkins.minecraftforge.net:7070/job/forge/207/

MCP comes with an eclipse workspace you should know?

Well around forge, never recommend addOverride as it is horribly designed with massive limitations.

First, how well do you know Java? You need to know it quite well to make most mods else the struggle will be very very high.

Not home right now so cannot check, but it is there, just look through them, you will find lots of interesting things too. Look in ForgeHooks for hooks, and look at all subclasses of the Forge Event class for possible Events.

MultiMC > MCPatcher

That might require editing the player renderer...

I had always considered a world that was raised by about 64 blocks, still bedrock at the bottom, but some adamantium ore veins running through it or so, with hell underneath, kind of like DF. This is a good start to such a thing.

There is a hook/event for that.

What part?

Yeah it is far easier for Forge. Just put the texture in your mod jar. To reference the texture and attach it to an item or block instance, just do: myItemOrBlockInstance.setTextureFile("/myTexture.png"); Change the "/myTexture.png" part to be where it is in your mod jar file, such as if you have it in a subfolder of "my/mod/and/whatever/myTexture.png", then in the setTextureFile call just do: "/my/mod/and/whatever/myTexture.png" Please do not be showing ModLoader stuff here if possible, those ways are generally broken and more difficult to use. In the case of ModLoader.addOverride, that is horribly broken. There are a very limited number of sprite indices and they get used in in just a couple of blocks, thus *never* recommend addOverride, it is horrid. For note, in MCP when developing I have it in my "MCP/src/minecraft/where-ever" and it is equivalent, it is part of my normal code tree.

There is already a ForgeHook for that.

The launcher is broken, but he knows of it and is fixing his launcher.

Since been fixed.

Has since been fixed.

Has since been fixed for note.

Heh, no problem. But I do hope the search works well on this forum.

It is how IronChests does it, should learn it, it is actually quite clear.

Do not use the ModLoader methods, use the FML methods. Look at how IronChests2 does it.