LexManos

You don't change the title screen, its explicitly disallowed. Let Mojang have their credits.

Post the exact command you are running because if you ran the one given to you in the EAQ you wouldnt get that error.

As Minecraft is still targeting J8 it is recommended that you use the J8 JDK to dev with. However, the re-write of the loading system is to support running on J8+, that includes 9, and 10. But again, as Minecraft still targets J8 we have to support it, which means no hard deps on J9/10 features. Hence why developing with JDK8 is recommended.

Multicraft issue, if they are charging you money to use our free software, it is on them to deal with whatever interop/changes happens. Never come to us for these types of things.

Post the new log then. The error you're getting: Is caused by a messed up JRE. See here for more info: https://confluence.atlassian.com/kb/unable-to-connect-to-ssl-services-due-to-pkix-path-building-failed-779355358.html The other option you have is to manually download the server jar yourself and place it named correctly into the folder you're installing to. The installer will then skip the download and *should* bypass that part of what you've got that broken.

The installer will work on any java version. The issue is that is installation is corrupt and somehow hes screwed up his security tokens. He needs to uninstall java, and reinstall it.

include the .jar extension and dont run the universal run the installer.

Run the installer not the universal.

You don't. These types of advertising/client takeovers are not good. Just have them join your server normally.

Never gunna happen, welcome too the world of Minecraft Modding.

java.lang.ClassCastException: it.unimi.dsi.fastutil.ints.Int2ObjectOpenHashMap cannot be cast to gnu.trove.map.hash.TIntObjectHashMap at team.chisel.ctm.client.model.ModelUtil.lambda$getMesh$0(ModelUtil.java:51) at team.chisel.ctm.client.model.ModelUtil$$Lambda$1195/1768680984.apply(Unknown Source) at java.util.Optional.map(Optional.java:215) at team.chisel.ctm.client.model.ModelUtil.getMesh(ModelUtil.java:51) at team.chisel.ctm.client.model.AbstractCTMBakedModel$Overrides.handleItemState(AbstractCTMBakedModel.java:84) Chisel is hacking into internals of Forge, it needs to stop doing that. Either update chisel, or if there isnt a update yell at the author to stoop doing bad things.

There arnt, ONLY ever use MinecraftForge.net Any other website is stealing from us, and most likely installing viruses/malware on your computer.

Post the debug.log file, not the crash report. It will have more information. However, you have WAY to many coremods.. should think about killing off those.

This is why you should always post and read your log files. Your server is returning 403 for that url when using a java client.

Post the client one, the server seems fine.

Do not make launchers, It has been requested by Mojang that launching the game and any user auth goes through them for security purposes. So, ya, don't do it. Esp considering you have obviously not spent any time trying to figure out how any of this works.

No.

Running vanilla first should not be required if you are using the vanilla launcher and a modern forge installer.

You're pointing the installer at the GameDir, you need to point it at the launcher's directory. If you just run the normal MC launcher then leave the installer at it's default value. If you run the normal installer with the --workDir argument, then you need to point it to that directory.

Spaces should be fine, it's the ! that is used by java to denote files inside of archives. Which is what we're working with. Soo it was looking for a archive named "Ding" with files inside it. Removing the ! *should* fix it, if not then its most likely a poorly made mod. Either way we'd need the log to know.

Dont have ! in your path.

you need to include the extensions when running jar files. installer-win.exe And you can skip the second universal argument.

You should never extract a mod, just take the file that you download and put it into the mods folder. If there is a mod that tells you to extract it, this is wrong and they need to update their instructions. There should only be one folder in the mods folder named 1.12.2, Anything else needs to be deleted.

If its giving you the same error then SOMETHING is broken with your JVM. Or your trust chains. See https://stackoverflow.com/questions/6784463/error-trustanchors-parameter-must-be-non-empty for more info. This isn't a Forge or installer issue. Its something wrong with your server. As for Forge not working on J9, the installer will work fine on it. However LaunchWrapper, the core loading system assumes some things about the classpath that J9 breaks. It'll just error when you try and actually run the server. As I said, the installer will work fine. As for where this is told yo you, in the error, and in our EAQs

I would advise going through a few basic programming courses. Stanford has a nice one. https://www.youtube.com/view_play_list?p=84A56BC7F4A1F852 Getting a basic understanding of how objects work, and the basic layout of java would be highly beneficial for modding.