LexManos

If you've broken your jar file associations, fix them: http://stackoverflow.com/questions/354664/executing-a-jar-on-vista-with-a-double-click

Seems HaddonBridgeModLoader, Or ReiMinimap is broken, not a forge issue. Make sure you're using the correct version for the MC you're targeting.

Its really really fucking simple. The same place as 1.5 except 'mods' is 'assets' now. mcp/src/minecraft/assets/{domain}/textures/{blocks|items}/{name}.png Simple as shit. And you should ALWAYS use your own domain not 'minecraft', you don't own Minecraft so stay out of it's packages/domains.

Minecraft Version: 1.5.2 Forge{7.8.1.737} [Minecraft Forge] (coremods) Unloaded->Constructed->Pre-initialized->Initialized DamageIndicatorsMod{2.8.3.0} [Damage Indicators] (1) Unloaded->Constructed->Pre-initialized->Errored Looks to me like your mod isnt 1.5.2 compatible, its looking for 1.6 classes. Please read your mods instructions before thinking it's Forge.

The files are downloaded from Maven central not our servers. And it's a Launcher issue on Mojangs end. They need to support standard maven repo urls in addition to special AWS servers {that they use}

As a note a fairly SMALL use case. And we assumed server admins were smart enough to know how to manage libraries. Either way a headless version fo the installer has been added: https://github.com/MinecraftForge/Installer/commit/8f76329abac29a4c51ee83f5b5ec154c848d6cd5 The majority of users are client users. And we do not ship libraries to the client. These libraries are download by the launcher. We add lzma, scala, legacylauncher. LZMA and LegacyLauncher are not to large, but Scala is pretty damn big. Also, we don't want to ship LegacyLauncher because that would be shipping Mojangs code. Which breaks the entire point of this new launching system. We went after the best use case for the VAST majority of our users. And this is it. The conversation between cpw and I was quite simple. We assumed that server admins, specifically ones who we doing things on dedicated environments such as yours. Would know how to so dimple library management. Either way, your situation is handled, have fun.

However you installed Forge you did it wrong. As there is one one of those arguments in our install. Please speak with whomever gave you the json file to install.

Actually this is a bug in MCP and will be addressed in our update to 1.6.2. This only happened when using startclient correct? Temporarily you can fix it by going to your conf folder and editng mcp.cfg Find the line 'ClassPathClient = ' and make it 'ClassPathClient = conf' Or just using eclipse to test for the time being. As I said, small bug with MCP's adding things tot he classpath it shouldn't. Will be fixed shortly.

No it doesn't DO NOT FOLLOW SHITTY 3rd party websites. The installer is all you need.

1) That's 1.6.2 2) Looks to me like you installed something in your client jar that you shouldn't of. 3) If you want to install forge, Install it using the Installer. Not random websites that have no real idea how to do it.

Typically read timeouts are caused by the server side running bungeecord that had a small issue recently. If they update things should be fine.

You don't have the minecraft_server.1.6.1.jar in the folder... Seriously if you can't figure it. Download the installer Run Install Server Copy the ENTIRE FOLDER to your server. And run it.

Noo, your log clearly states that you have other things in your mods folder: 2013-07-05 13:47:20 [iNFO] [ForgeModLoader] Searching C:\Users\Heather\AppData\Roaming\.minecraft\mods for mods 2013-07-05 13:47:20 [FINE] [ForgeModLoader] Found a candidate mod directory Durability101 2013-07-05 13:47:20 [FINE] [ForgeModLoader] Found a candidate mod directory macros 2013-07-05 13:47:20 [FINE] [ForgeModLoader] Found a candidate zip or jar file mca v3.3.0.zip 2013-07-05 13:47:20 [FINE] [ForgeModLoader] Found a candidate mod directory rei_minimap 2013-07-05 13:47:20 [FINE] [ForgeModLoader] Found a candidate mod directory spc ... You really think... Forge... ships....MCA.... No.. that's just retarded..

The java runtime environment. Same java that you need for Minecraft. The launcher you use for Minecraft is a jar file Just wrapped in a small exe that does 'java -jar Minecraft.exe' Seriously, how do you not know how to run jar files? They are used in thousands of moden applications. Either way this is nothing to do with Forge.

All programs need to be loaded by SOMETHING to be run. Executables are loaded by windows. Jars are loaded by java. They are in essence, the same thing. A book is still a book even if one is written in English and the other is in Sweedish.

You should know how to do it, they are java's equivalent of exe. http://lmgtfy.com/?q=how+do+you+execute+a+.jar+file%3F

http://www.minecraftforge.net/forum/index.php?action=files After downloading it, you run it. If you can't figure out what to do once its ran.. then I feel sorry for you... Its one of the simplest things you will ever see.

This has NOTHING to do with Forge. Forge DOES NOT download anything. This is PURELY a Mojang Launcher issue. One that Should of already been fixed. Update your launcher...

No, if you load a mod save and click the yes button then you're taking responsibility for whatever the fuck happens to the same. As for that error, it would make it seem that you have two versions of minecraft trying to load the same world. If thats not the case then some other program on your computer is doing it. Try restarting.

Files is up, as for the links on that page, forgot to update them for the 1.6 changes. {Installer and jars instead of zips} Should be good now.

Again, Mojang launcher issue not outs. They do not yet support standard maven md5 caching. There issue.

Whatever launcher you're using needs to update to the new system. We do not support things that don't exist anymore.

Talk to the MagicLauncher people not us.

You need to fix your .jar file associations. The installer works fine. http://stackoverflow.com/questions/354664/executing-a-jar-on-vista-with-a-double-click

Nothing to do with Forge, you';ve installed it wrong by following shitty tutorials instead of using the supported install method.