LexManos

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.

Only thing google tells me is your JRE is not installed correctly. Run using a different JRE or re-install your java.

Odd, something on your end is screwy. It's stopping before reaching the end of the AT file. It Stops here: https://github.com/MinecraftForge/MinecraftForge/blob/bea02348e2845ef6b1f49b0692f79dbc097d2706/src/main/resources/forge_at.cfg#L313 Only thing I can say is delete the libraries/net/minecraftforge/ folder and re-install.

Remove any mod that was made using mcreator. It is a horrible program that does nothing but cause problems. Your current error is from: at mod.mcreator.arcanelamps.<init>(arcanelamps.java:37) ~[arcanelamps.class:?] So im gunna assume the mod is called 'Arcane Lamps'

Re-run with the JVM argument -Dfml.debugAccessTransformer=true And post a new log. This shouldn't be happening.

Yes, Register them. You need to send them from the client side and thats where the check is. It doesn't care whats on the server. Or as dies saiid, you can move away from SimpleImpl if its not the standard format.

1.12.2

Yes, 1.13 will run on J9

First off JournyMap is broken, you should tell them about it. And you have quite a few coremods installed so those could cause it. However, thats the server log, most likely the issue is on thee client. So we need the client log.

Install it using the official Forge installer. https://files.minecraftforge.net/

Dont do this. First off modders need to know the basics, and if they cant download a zip, and extract it they shouldn't be modding. Secondly, automated downloads of Forge is discouraged because the main source of revinue for Forge to pay our server costs and the like is the ads on the download page.

I think I see where he screwed up. The cookies laws are just dumb, not even the EU's site regarding guidelines for cookies can be entered without storing at least one cookie. How ever, I've changed the wording slightly, and made the theam code use the normal accept/decline methods. https://github.com/MinecraftForge/Web/commit/53e2919f90a43326e74e25deb3da49ab6d370936 This should be a good stop-gap until paleo can take a look at it.

Or, you can answer the prompt from the command line, even on a headless server. We have quite a few options including the command line command processor. As well as the environment variables. And a launch argument IIRC. There are options you can use.

It'll bee fixed in the next version, just a DNS issue. As always you can see all the changes here: https://github.com/MinecraftForge/MinecraftForge/commits/1.12.x

Interesting i'll look into it, however from all of our tests that is not the case. Can you provide what exact version of your browser, you are using. And any possible addons you may have that are interfering with basic java-script functionality. As for the wording, we've had it vetted and it seems to be fine to most reasonable people. I'll see if Paleo can think of even more explicit terms.