LexManos

Because it looks good where it is, and it'd have the same 'issue' as this one where long server names wouldn't display 'properly' You can fix it on your end by lowering the width of your banner, pretty sure MOTD's rendering supports \n

Someone poke fry and tell him to just disable this shir on osx by default the level of dumb is getting annoying.

Let me make this perfectly clear. There are NO "commanf line arguments" that you should care about. If forge needs your input on something it will ask and tell you how to use it.

Going to assume you mean ENVIRONMENT VARIABLES not command line arguments. Forge does not add any command line arguments. So yes looking at the main class for MC or whatever wiki you can find for the arguments is your best bet for those. Its not a joke, this is how minecraft modding works. You have to be at least a little competent on your end and do research. But no, there isn't any documentation on the EnvVars that FML/Forge checks as most of them are purely for debugging purposes. You could ask nicely on IRC if someone would work on documenting them in our RTD repo.

Yes FML lowers the width of the MOTD to make the vast majority of them fit correctly with the server mod info. Not sure I particularly care to 'fix' this. The MOTD isn't 'broken' its just rendered in a smaller width to make room for the check mark.

It wont let you select it because you're already on the 1.8 page... If you'll notice the downloads all have 1.8 in the name.... Just download the files.. Also how the hell is this a suggestion...

You dont.

Forge doesnt add any startup paramters, Mineraft does. And thats been documented many places. YOu could also look at the Main class to see them all.

Remove whatever other coremods you have installed.

Missing Mods: Already in if they are required Extra Mods: Nothing you can do. This is intentinal, also even if it wasnt theres nothing you can do because you can't trust the client.

[15:18:12] [Client thread/INFO] [sTDERR]: [java.lang.Throwable$WrappedPrintStream:println:748]: java.lang.UnsupportedOperationException: This LP version isn't compatible with the installed BC version.

Why? What are you trying to accomplish?

UE numina{1.0} [numina] (numina-0.3.0.78.jar) UE powersuits{0.11.0.7-QMX} [MachineMuse's Modular Powersuits] (ModularPowersuits-0.11.0.7-QMX.jar) UE powersuitaddons{0.11.0.7-QMX} [Modular Powersuit Addons] (ModularPowersuitsAddons-0.11.0.7-QMX.jar) Try taking those guys out. You've installed a non 1.7.10 mod on 1.7.10

Doesnt seem like an error, just seems like it finished what it was doing.

It doesn't. None of the files are corrupt. Which is why I asked for md5s so we could compare it against our versions.

This is what we have been trying to tell him but hes a fucking moron. Updating to the newest version will have the error happen once, and then Forge itself will disable it. Talking about other installers that steal modders content and rehost/package them without permissions is not gunna garner any sympathy. {Note the website im referring to has been removed from his post because I dont want him advertising for bad things} The Forge installer works fine because if it didnt you wouldn't get to the stage where you're having this issue. SIMPLE FACTS. The reason using that 'installer' 'worked' is because IT LIED TO YOU ABOUT WHAT VERSION IT WAS INSTALLING. Probably installing a modified/old version of Forge before the loading screen existed. If you can't edit a simple text file, and refuse to update to the latest version, then we can not help you.

Make sure to delete the file that errored somehow it is a invalid zip

Don't make coremods, or before you do actually fkin understand what is going on. This is not a bug this is intended behavior of Forge.

If you ever decide you want to sell your old laptop I would love to grab it, so i can deal with this bug in a test bed that actually reproduces it. But glad that this fixed it.

Did i stutter? Update forge. Something in your graphics drivers are shit and doesnt allow multithreaded rendering. This is a detected issue in latest versions causing forge to automatically disable the loading screen for the next run. So again update Forge DONT question me -.-

Update forge

Post your graphics card info (forge logs this is the logs folder) you're probably on that one damp driver that doesn't like multithreading on macs -.- but yes disabling the new splash screen will fix it.

Dont use 1.7.2 there is literally no sane reason to. Use 1.7.10

If you havent noticed fromt my plethora of posts and tweets, i'm traveling right now so irc and the like dont work. However most of your comments and suggestioms cpuld probably be answered with "I know, but thats not how minecraft or the community works" Keep in mind ive been developing systems like this for 15 years, i know what im doing and there are reasons why the methods ive choses are what they are.

Because throwing buzzwords around has nothing to do with functional code. The parts that forge addss on top of minecraft are dictated by minecrafts style, compatibility with other mods, and just the samity of having to deal with mc/modders. Forges goal is to be a small later on top of mc and to have modders work with mc directly. And the designs that forge and fml employ are what are needed to do this. Trying to restrict modders is just a futile effort due to the environment.