LexManos

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.

Mojang EXPLICITLY states not to do capes. Bye.

You should be able to just do java -cp {netty} -jar {forge} --nogui If not Forge's server main class is net.minecraftforge.fml.relauncher.ServerLaunchWrapper But you'll need to add every other library to the classpath. The server's MANIFEST file specifies all this.

User was suspended for 7 days for being an ass twards someone who was trying to help him.

We do not support jar modding in any way on these forums. If you're wanting to work with the guy to make things open source, Then move him to a proper mod before doing so.

There is a space after "-jar"

The issue is if IPB has a hook to allow for that kind of injection, I haven't seen one.

Remove the coremods, One of them is screwing up something. And because it is a coremod there is no way to tell what.

Don't hijack other people threads, make your own. And follow the other rules lined out int her EAQs.

Remove all that shit and try again. ESPECIALLY 'NotEnoughIDs' as it is KNOWN to screw up handshakes as well as corrupt worlds.

Thaumcraft. at thaumcraft.client.fx.ParticleEngine.updateParticles(ParticleEngine.java:296)

They use this internal method is a half-baked anti-cheat system. It was doomed to fail from the beginning as it requires the server to trust the client. Not to mention it bypassed all the other ways mods are loaded. But ya its internal API that isn't garenteed to work.