LexManos

It's the other way around we would need to know what you're planning to tell you the benifits. However simple answer is Forge registries do all the hard work of saving/loading/syncing/substitutes/aliases/networking for you. So if you use any of those features it's probably best to use ours. But if you're working internally and don't need numerical ids for networking or dynamic substitutions then a normal map would work.

fixed that for you

Why?

you've yet to explain what is hard or how it could possibly be made easier. The entire point of this system is that it is literally the easiest it can be. Any easier would involve us writing your mod for you. The thread shows a lack of effort and just complaining on your end and that's not welcome here. Either provide ideas for solutions or shush.

OR you could use anything past 1.5~ and let forge take care of it all automatically for you.

Because it is a self-contained easy to use system that runs on the JVM which is the language/platform required for developing Forge mods so it does not add any extra dependencies and allows for standardized development with many projects. It's an industry standard outside of Minecraft for many reasons. Short answer: Yes, but it is so complicated and annoying that it is not worth the effort, and beyond that most methods are illegal and would piss off Microsoft's lawyers which everyone would agree is a bad idea. Running literally ONE command is a 'pain'? Seriously how do you expect us to make it easier? Write the mod for you when you look at your screen? Actually it works on all computers that are capable of running the J8 JVM. Which, considering my toaster can do it I think makes this point invalid. This is actually a valid complaint but this is not a fault of Forge or Gradle. This wouldn't be solved by moving to a different system. This is a issue with your network setups. It integrates rather well with all popular IDEs, the main problem is that the tasks needed to setup a Forge project are NOWHERE near standard java practices due to legal issues. So you're just going to have to deal with some lack of IDE integration here. However that being said, again all popular IDEs are are supported by gradle, and by ForgeGradle. Run the proper command and it will create a eclipse project for you that has all the proper libraries, run configs, debug flags, and is useable by a simple 'File -> Import -> Import Existing Project' Again, this is not done for legal reasons, blame Mojang. However gradle can do all of this for you with 1 command 'gradlew setupDecompWorkspace eclipse' In conclusion your points are invalid and you're just bitching, stop.

Because we don't know they will 403 and we don't want to speciacase Mojang a servers for no real reason

https://github.com/MinecraftForge/MinecraftForge/commit/45097fed0c054407dedcf4cb9bab0e54b977d7e7

This has nothing to do with your server or anything like that. The log shows you installed the client. Hence why optional files weren't downloaded, the Mojang launcher downloads those files. As for the 403s that's intentional because we try the compressed form of the library first which the Mojang servers don't have. Just tested on windows, works just fine as it's my main dev env.

Looks like a successful install to me, what 'issue' are you having? Just run the client using the normal launcher and it'll download the files it skipped. This is why it skipped those files.

Again why are you making you life harder? Just install forge and put liteloader in the mods folder. Not the other way around

Blame vapors I'll have him look at his upload script when he can. He just recently added the forge mirror as he was having issues with his server. So it may take some time to iron out the kinks

Your computer needs to be connected to the internet, or disable the optional mod Mercurius.

Whatever that is, it's fradulent. We get people stealing our name for the appstore all the time. There is jack shit we can do about it tho.

... They should be unless some mod goes in and screws with the internals of our registries, which has been known to happen. If using JUST forge, then your worlds should stay compatible with vanilla. Once you add mod items/blocks tho, you're probably screwed.

IIRC with Forge installed, LiteLoader is just a Mods folder mod... so... just stick it in the mods folder...

What? Why?

It's almost like different mod packs have different system requirements and do different things! 1) It';s not forge's fault it's the mods/your computers 2) You're only allocating 3G of ram, and you're pegging that out before the coremods scan finishes, so you're slowing yourself down. 3) You have a lot of JVM args that futz with the GC which will cause it to be a lot slower then it should be. So ya, nuke your JVM args, and give the process more RAM. Nothing on our end.

It functions, as with all older versions. We just don't actively provide tech support. Forge does not retroactively disable anything.

The version you want for your version of Minecraft Forge is not OS dependent.

You can not change the logo.

Forge doesn't do anything to break the skin system of Minecraft. As long as you have a legit account, and you change your skin on the Minecraft site then you will get the new skin in game. Note, it takes a while for your skin to propagate

You have several coremods installed, one of them is screwing up the crops class badly. Nothing we can do to tell you what one besides just stop using coremods.

There is no crash here, but as a random guess, try disabling the loading screen as described in the eaqs

Post the installer logs, they are in a file in the same folder as your installer. Also, make sure you have a valid unblocked internet connection. It has to be able to access our servers to download the libraries.