OvermindDL1

I thought you needed the ModLoader entity registration.

Just remember, the more generic the better, and it must have no cost when not used, and low to no cost when it is.

They work fine in Single Player? The code for Single Player is identical for the Multi Player client in terms of rendering. You are sure that everything is registered properly? A reduced test case of code would help.

Optifine needs to update then.

Missing updated forge or an updated mod then, that works.

Or you are missing Forge altogether, one or the other.

Also be sure to update forge, the newer forges have detection for ModLoaderMP.

I have been looking for that same thing, although I want them to drop a placed block, not an item, although dropping an item that can react with the world to place itself would work.

Oh yes, was definitely thinking the same. And it is trivial to include all/parts of a page in another page automatically too.

Be careful with that, MLMP has some issues nowadays, and it would not at all be required at all for any reason. You might want to research that, it is odd... And Optifine only works with specific versions of Forge, as Forge updates, so does Optifine, but not always instantly.

Ooo, that is a good start, very cool! EDIT: I might factor it out soon into templates so each error can be on there while having its own page for discussion.

1.2.3 is pretty old, but you can still get it from the release thread at: http://minecraftforge.net/forum/index.php/topic,5.msg202.html

Good to know, thanks for report!

That means that whatever you added is a bad download, redownload whatever mods you are using, one of them is corrupt.

Just making sure. That error is always caused by either not following the installation instructions (deleting META-INF for example) or using a cracked Minecraft.

Forge does nothing to the TPS, it leaves it completely as Vanilla. Forge generally does not touch anything in the vanilla except to add hooks or to fix bugs, it does nothing to change standard operating procedures of normal Minecraft; it is purely an efficient hook-based API.

It should be compatible yes, but *only* if you order the mods in it properly, that is important. Take the following with the grain of salt as I do not use HDPatcher, I use Optifine, so this is all second-party information: RP2 is currently broken with HD textures by MCPatcher. MCPatcher does HD textures very poorly, RP2 will fix it soon. Optfine works fine however, since its method is superior. Any HD texture pack that works with MCPatcher only and not Optifine is broken, usually due to proprietary extensions by MCPatcher that should not exist. Hopefully not an issue in the future as Jeb has indicated he plans for native HD support in MC itself at some point in the future. But yes, Forge works fine with MCPatcher if you order the mods properly (ModLoader, then Forge, then your user mods).

A consistant API is good for many things, first: Forge is efficient, at times well more efficient than likely you could make things otherwise. Forge has a stable API, unlike doing base edits in Minecraft, of which you have to re-apply those base edits manually every version. Forge reduces the amount of work you have to do by quite a bit due to the hook interfaces. And of course compatibility, which is a pretty major factor, having your mod work with others that would otherwise be incompatible due to base edits is quite a boon.

That is on purpose for now, need to speak with LexManos about how he wants permissions for those handled. Remind me later. Maybe I can just link the releases to the SMF board or so...

What timezone you 'view' times in does not make sense to be in 'Look and Layout'? Not sure what sites you use, but a disproportionate amount of forums I use on other sites are indeed SMF, including some of the largest forums on the Internet (The Warhammer 40k Online forum gets close to MCF in size), so no clue where you are getting 99% from.

Usual errors, BaseModMP, class errors like the above, basic troubleshooting steps like starting completely fresh 'and' redownloading everything, how to get a stack trace, etc... Anything to reduce the 'usual' support threads.

*cough* Did you pay for Minecraft?

Anyone up for making a default set of obvious troubleshooting steps like that on the wiki that we can link to?

Without the error we cannot see. Supply the error, those are the rules in the stickied post. Do note that ModLoader as of late has been changing the camelCase of some of the function names to be more consistent, that might be your problem. If it is then this is the only time you should need to make that change.

It is a CraftGuide bug, NEI works, use NEI instead until CraftGuide updates. Closing thread.