LexManos

As I've said before, BungeeCord works fine with Forge. There was a previous issue that was fixed 3 weeks ago. If the Hive servers haven't upgraded yet that's there issue. If it is another problem then we'll have to speak with md-5 and see if we can track it down. However we would need to know more about there server configuration exact setup details, server logs of forge connections, etc.. There's not much we can do on our end without communication with THEM not with random user X. For note, I just logged in using the latest Forge and it worked wonderfully.

That's because Millenaire v5.1.3 is for MC 1.5.2 TextureStitched doesn't exist in 1.6.2 Update your mods -.-

its generated from vanilla's jar, and files on our github. This particular situation in my opinion is best handled by checking if the requested version is downloaded. If it is use the included jar to run the download processes. If not download the universal jar once and then install/go that route.

It's impossible to catch those cast exceptions. And it's impossible for us to know what item overwrites should or should not be crashed on. There is simply no way to do this. As a user you need to apply some logic. If it says ItemX can't be cast to ItemY then you can safely assume it's a ID conflict and should search for those in your log. I'm gunna assume you're not a programmer, but trust me it's not a 'replace this line with that' Thats impssible to do how you want.

Then you probably messed up the install. This is where you should be posting your logs.

No, we can't because various modders are lazy and rely on this non-crashing behavior instead of clearning there slots or checking they they are free. However, item conflicts ARE logged. So you should be able to find them

The answer to this is a resounding 'No, its pointless' Modders should use it for whatever they need. They should NOT abuse it though. It's a simple String -> ItemStack[] dictionary. Nothing more, it doesn't care what those strings or stacks are.

However you're launching the game is not supplying the username and session into. Use the mojang launcher or talk to whomever write your launcher.

Dont install a 1.5.2 mod on 1.6 ... That doesn't work. http://www.minecraftforum.net/topic/964897-152-spmplan-clay-soldiers-mod-v-911/

Your first post says you're trying to do 1.6.2 but your error log tells another story: Minecraft Version: 1.4.6 Anyways the issue is straight forward, no matter what version you're using you're running out of memory, Give your game more then the gig it has. However, as themineblader says, we don't support that old of version. Upgrade. There is no reason not to.

Update Forge 790 was bugged.

Your user account screws up a lot of things because it's non-standard ascii and can't be decoded by utf-8. So, move all things out of your user directory.

1) kill any MCP you have and only use the one Forge downloads during install 2) What version of astyle do you have? I can't remember off the top of my head but we need a fairly specific range

No, the Ore dictionary is a general dictionary for String -> ItemStack[] The 'Ore' is just legacy name and there is no real reason to change it. What would we call it? 'GeneralDictionairy' 'ItemDictionary', 'Dictionary'? Why break code for something as stupid as a cosmetic name change?

Why do you need this info without having the full download?

If you've fucked up your jst assosciation, you should go fix them {google is your friend} As a temporary solution you could run it manually by opening cmd prompt and running: java -jar {forgeinstallername}.jar

Yup.

His answer was correct. Running a jar isn't hard.

That is where you get instructions. We do not support Bukkit here. And there entire point is to port things to bukkit. You're better off there.

https://github.com/MinecraftForge/MinecraftForge/blob/master/client/net/minecraftforge/client/event/RenderGameOverlayEvent.java

https://github.com/MinecraftForge/MinecraftForge/commit/ee70b214600d48848af79b90a1d3a43985df8eb0 I'll need to do some updating of the python on the src side but this should fix any further runtime env.

Install optifine AFTER forge.

Yes, 1.5.2 Forge was developed before they started putting the version name in the jar file, so you can either run it as: java -cp minecraft_server.1.5.2.jar -jar forge.jar nogui Or rename it to 'minecraft_server.jar' and just run it as: java -jar forge.jar nogui

Not us* It's caused by 'mekanism', Not us

Simple, don't edit base classes {Mojang's or ours} And use the events provided. it can do what you want.