LexManos

Reload your launcher, this is a bug that has been fixed in mojangs launcher. They add a 'libraries' to the path when there shouldnt be any.

Mojang issue not ours, there launcher is what download the libraries.

Lex, please think of the not-so-enlightened that build their own packs. If you can't type 'domain:name:version' Then you really shouldn't be making a mod pack...

This is NOT the support forum -.- And it means you dont have the libraries. The error is pretty damn straight forward... I'm gunna lock this because it seems to not being productive.

Everything shouldn't be preInit. cpw is still deciding when things should go. You should be able to load all your stuff just fine i other events...

Again, launcher issue. It only happens when Forge is installed because Forge tells the launcher it needs more files. However, the launcher needs to cache the files, and read metadata properly. it doesn't, this is nothing we can do. It's up to Mojang to update there launcher.

The strcture of the mods folder is changing I beleive right now it it /mods/{version} Eventually, we want to make it so you dont have that flat folder for mods. We want to have it like the libraries folder: /mods/cpw/mods/ironchests/1.6.1r1/ironchests-1.6.1r1.jar /mods/cpw/mods/ironchests/1.6.1r2/ironchests-1.6.1r2.jar etc.. And then we build a proper list of mods from a configuration file that modpacks, and the like ship.

u.u I dont understand how many times I have to explain this. Use the Installer You DO NOT put Forge/FML in your jar anymore. Jar modding is DEAD. Anyone who does it should stop!

If you've made a tutorial.. you should link it. Instead of advertising yourself/your server -.-

How does that relate to what I just said? The registry and stuff are client env as well.

Files should not be downloaded every time you connect. It *should* be downloaded once. This is a Mojang launcher issue, not us.

MCP related bug its know and fixed. Once MCP makes a update we'll pull.

If adfly doesnt work for you just use the direct links. We give you both so its not a problem. But yes, the issue is that they have changed it so that adblock prevents there script from running. Also, there is no point clicking the adfly link with adblock enabled as it doesnt count for the developer.

In that aspect everyone should go yell at Mojang to add 'Use latest _____' So you can select 'Use Latest Release' 'Use Latest Snapshot' 'Use Latest Forge' etc.. But untill that time we're just gunna make the time 1960 because meh

Dont add any mod to the jar, jar mods should be dead. If you're editing a 1.6.1 jar you're doing it WRONG If a mod tells you to put it int her jar yell at them to stop being stupid.

Locked to Stupidity, ALWAYS provide logs -.-

Any particular reason you used your own registry/interfaces? Could you not re-use the Command registry thats on the servers? {Havent looked yet, just a thought}

It's maven style artifact values, so: DOMAIN:NAME:VERSION gets expanded to /libraries/DOMAIN/NAME/VERSION/NAME-VERSION.jar Aside from that, cpw is working his but off on stream lining the Mod install process to both take advantage of the new structure and be simple for users. As for the json. I'll see what I can do about including a sample version.json in the universal's jar.

Ya, cpw forgot to update that. You need to call ServerLaunchWrapper cant remember the exact name right now.

Use build 762, cpw neglected to tell me about the change to the installer's manifest. I've built and tested, the installer makes a server folder just fine. It does NOT make a run script But you just need to do java -jar univeral.jar Time for sleep u.u

Humm, seems the installer isn't building the run.bat/sh files. But let me stress this point: IF YOU ARE EDTING THE VANILLA JAR IN 1.6 YOU ARE DOING IT WRONG The installer *should* of made a run.bat that contain the proper java command to launch the server. But if ti doesn't you can do it yourself. Grab all *.jar files in libraries and put them in lib {this is because they need to be in a flat directory} then run: java -cp lib\*;minecraft_server.1.6.1.jar -jar minecraft-forge-universal-{version}.jar As i said these things *should* be building the run script for you but i guess it's not. And I will be making the universal jar directly runnable {java -jar universal.jar} soon I just forgot about it. We're also still finalizing the server install {I could of sworn cpw said ti was done but w/e} So hold up. Notice how we don't have a RecomendedBuild yet? But again: IF YOU ARE EDTING THE VANILLA JAR IN 1.6 YOU ARE DOING IT WRONG

'launch code'? There should only be one argument.

Thats actually a MCP bug that I just finished fixing. I'll push a build as soon as The MCP team review it.

Actually its not a FML issue. Its a launch configuration issue. We ship those for a reason u.u You need to launch the legacylauncher.Launch class Not Start.main https://github.com/MinecraftForge/FML/blob/master/install/eclipse/.metadata/.plugins/org.eclipse.debug.core/.launches/Client.launch

Upodate.