LexManos

Then magic launcher is editing your jar. Stop using magic launcher. This has nothing to do with us and is solely on you, or magic launcher. The problem is simple, you're editing the jar. Stop doing that. Go speak with them. I would however simply advise you to use the normal Mojang launcher. And our normal Installer. Simple as that.

Again you're thinking that this is intended as security it is not. Forge/FML are not a security firm, we do not have the authority to designate who is secure and who is not. The end user decideds who he is going to trust by downloading and installing there mod. This has NOTHING to do with us. No, the mod author can't do anything from running the 'hacked' code, just like a random mod author can't do anything to prevent you from running your mod. A mod author CAN however handle the violation event as see that 'My god RandomMod17 says it should be signed but its signature doesnt checkout, I will not run in this untrusted environment' If every mod does that. Then the 'hacker' {God I hate using that term as that gives them to much credit} would have to modify each mod individually to remove the cross checks. 1) That'd provided by the JVM. 2) We have to trust the mod. There is no sane way for us to tell the difference between a mod with no signature and a 'hacked' mod. Anyways, we are providing the same level of 'security' that the JVM provides. Actually we are providing a bit more. By allowing a simple system of cross checking and redundancy. Again, FML/Forge signatures are not for security. Any security when it comes to things like this is a farce and shouldn't be trusted. You're offering to fix something that isn't broken. And are trying to extend our domain/liability WAY beyond what we should do. However, if you as a third party wish to do something completely unrelated to Forge. And write a utility mod that tries to govern all of this, then that is on you and we don't care.

2013-07-22 16:43:10 [sEVERE] [ForgeModLoader] There is a binary discrepency between the expected input class net.minecraft.client.settings.GameSettings (aui) and the actual class. Checksum on disk is 18272e3f, in patch 316717c8. Things are probably about to go very wrong. Did you put something into the jar file? 2013-07-22 16:43:10 [sEVERE] [ForgeModLoader] The game is going to exit, because this is a critical error, and it is very improbable that the modded game will work, please obtain clean jar files. Seems straight forward, you're editing your jars. Stop editing your jars.

In-game content is soley the responsibility of the modders. Forge does not moderate any of that. We simply provide the tools to allow modders to do what they need to do without editing any of the vanilla classes. It's up to modders to work together and create a 'coherent' gameplay experience. And a lot of modders are doing that. With differnt setups if different mod combinations are installed. But again, this is not the domain of Forge. We do not pose any restrictions or guidelines on the creativity of Modders. The only things we do is make the Engine {minecraft} suitable for modders to work WITH not ON.

We arn't writing something that is designed to execute arbitrary code from the internet. We're writing something thats designed to execute arbitrary code from the local disk. Major difference. Mainly being the fact that we do not place anything on the disk and it is SOLEY the user's responsibility what gets put there. The OS analogy works, You don't blame windows when you download and run a file called 'FreePorn.exe' you blame the user, for being stupid. If the files are on disk, then we must assume that the damage is done and not give two shits. Now, if say, Windows update were to download and install a virus during it's nightly update. THEN you blame Microsoft. But as FML/Forge has no such system, it's not on us. Anyone can sign a jar, but if there signature doesn't match the one in-code then it's rejected and as such triggers the violation event. This event is done before any of the mod code is done. The event is fired in mods that are already loaded. Anyways before you guys go all crazy about this. We will NOT be hosting a central trust server/list. We will NOT be forcing all modders to sign there code. We will NOT do anything more then we are already doing. This is NOT designed to be fort knox. Anyone who installs a mod onto there computer takes SOLE RESPONSIBILITY. Signatures in java are a joke. They should not be used for ANY form of security. And they are NOT used as security in FML. They are used as sanity checks. It is designed so that a Modder can check his own, or other's signatures and verify that he is running his own, un-tampered code.

Why are you editing base classes? Stop doing that.

1) Inactive external mods: AetherII_Alpha_v1.0.2_MC1.5.1.zip 2) Go talk to the Magic Launcher people they are launching Forge wrong. Protip: Main.main is not the way forge Launches.

Again, we're not re-writing the entirety of minecraft for something like cosmetic changes. {Mob strength is cosmetic} Yes, I do Know WoW, and I do know how it's setup. I have many years experience in it's scene. Just 'being a database' will not do what you want. You need people to actually sit down and design everything. And that's not gunna happen here. A major mod COULD do everything you want without editing base classes. But they'd be basically writing an entirely new data engine on top of minecraft. This is Not something that Forge should do.

Flush your DNS and make sure file.minecraftforge.net is pointing at 192.95.32.52 Or you can try new.files.minecraftforge.net The server is up and running just fine, and in no way connected to the CloudFlare anymore so if you're getting that message, force flush your dns.

Something has to IMPLEMENT that interface.. that's how programming works. Eclipse has tools to tell you what implements it. Go forth and do research!

Its a class in minecraft, look it up. Go try to understand whats actually happening when you register an icon -.- Now that you bring up spawn eggs. There is a perfect example of what you want. It's a multi-passs system that renders the default base on bottom. Then renders the second layer with a tint. Why arnt you using that system? 'I want to do the same thing eggs do but instead of researching how they do it I wanna change minecrafts render engine' Seems... overkill...

Do NOT edit BASECLASSES. Especially for something as retarded as that. We have events and hooks in place to satisfy your vanity. Look into them. We are not helping anyone who edits base classes be it Minecraft's or ours, especially for something as stupid as branding.

What do you even mean by that? Interesting, and what strength of Respiration do you have equipped?Screen shots of your equipment would be nice. As you say that you are giving yourself beyond vanilla max enchants.. this still doesn't sound like a Forge issue.

No, we're not re-writing Minecraft's engine to the sole benefit of cosmetic blocks. It is already ungodly simple to create new blocks. No need to make it simpler for some and more of a pain for others.

You can register your own AtlastTextures and do w/e you want in it. However, for The texture packer's sake. I advise either generating your images at release time once, or making a standard format to allow the texture pack artists to design them.

You shouldn't get that file. Why are you editing Forge files? For normal modders, Unless you write the class, you shouldn't be editing it.

Logs logs logs logs logs logs logs logs

You're editing the jar file, Stop editing the jar file. Nothing should go into the jar file anymore. If you're using Optifine follow it's instructions on how to install it along side Forge.

We dont update older versions. But this looks more like the entity isnt registered or something. And looking at those files, I'd say Forge is not the only jar mod you have intalled.. May wanna look into that.

Try without Optifine. That doesn't look like the standard launcher either... And the log im referring to is the client log in the .minecraft folder created by FML. The one you posted is useless as it doesn't tell me how you're launching it, or what mods are loading, or anything. Humm didn't pay attention to the new enchantmnets. So.. what you're saying, is that if you create a unnatural enchantment that goes beyond Resperation's max level, it screws up the fog.. That kind seems right considering it probably does some basic math to generate how 'clear' the water should be anything above what it takes to make 100% would probable fuck things up.

This isn't caused by the installer. Note the Obfusicated class names. That DOESN'T happen in a setup installed by the installer. Hence why AI asked how he installed things.

How are you installing forge? However you're doing it you're doing it wrong. You should use the installer that is provided.

Fog in water is normal... Anyways what else do you have installed? Forge my itself doesn't throw these GL errors. Post a full client log.

Copy %appdata%/.minecraft/versions/1.5.2 to: %appdata%/.minecraft/versions/1.5.2-Forge Inside this folder: Rename from '1.5.2.jar' to '1.5.2-Forge.jar' Rename from '1.5.2.json' to '1.5.2-Forge.json' Install forge into 1.5.2-Forge.jar like you always would for 1.5 Edit 1.5.2-Forge.json to change the 'id' value from "1.5.2" to "1.5.2-Forge" Create a new profile in the launcher, and change it's game directory to %appdata%/.minecraft/versions/1.5.2-Forge Now this is hard and complicated but i'm pretty sure it'll work. Forge for 1.5.2 came out before the new launcher existed so the install is kind a pain. If you can't figure it out, then go try installing MultiMC it should be able to setup everything for you it's just a different launcher.

Interesting, it seems that somehow you've derped up your version information. If you used our installer then this shouldn't happen. But if you installed a version manually then things could derp up. What you need to do is go in to the versions folder, delete them all {vanilla ones will re-download when you use them} and re-run the Forge installer.