LexManos

congrats, you necroed a 4 year old thread.... Don't do that.

Try jarfix You're running the installed incorrectly. You could also run it manually by: java -jar forge-1.14.2-26.0.35-installer.jar

Then post a new log, both the installer, and the launcher.

Congrats, you downloaded and installed Forge from a malicious website. ONLY ever download Forge from our site: https://files.minecraftforge.net/ Run a virus scanner, delete whatever installer you used. And download a real one.

It means that something you're doing is producing a wrong output. However, your input hashes are correct in the log. So something else is wrong. What version of java are you running?

Why are you installing 26.0.0? That's 33 versions out of date...

It tried to, but there is a known bug cpw is working on, where it doesnt properly crash/show our error screens. Basically, if you see a really screwed up world like in that intal screens hot. It's a mod crash that didnt properly crash.

Known issue with the realms library. Waiting on Mojang to fix their end. If they havent by the time we get other more important things squashed I'll write something up to fix it.

Main Page? Anyways, 'Recommended' is a manual promotion. It's to mark a build as 'stable'. Meaning people have tested it and all known major issues have been resolved. This process requires modders/users to actually test and give feedback. So go forth and test!

No, MCP is the core and it will continue to be the core. I create MCP and thus I can trust in it's stability and availability. If modders want to make a translation tool between the two so that Fabric can load on SRG names. Then go for it. I have spoken many times about how a system should be designed. But the people who have said they wanted to help haven't followed through. Anyways, getting tired of answering this. Forge will never use Fabric. Fabric's core design of "screw it everyone's a coremod!" is NOT feasible for a large compatible modding ecosystem. Forge's major rewrite is done, which means updates should be back to our normal same day target. Sorry for being 'slow' because we decided to cleanup 8 years of technical debt and plan for the next 10 years. Anyways, don't bump old threads.

1.8.0_211 should have LetsEncrypt. However, try installing again, as you may of been in the window where our server was having issues.

Alright, im able to reproduce, and this seems to be a bug in the Mojang Realms library. They are *supposed* to only be accessing the Minecraft codebase through purely the deobfusicated API. Due to us doing the deobfusication of Minecraft at install time. Those classes it's referencing does not exist at all. We will look into fixing this, but it may require a fix on Mojang's end. We'll see.

Slight derp in the cert renewal. Fixed: https://github.com/MinecraftForge/MinecraftForge/issues/5807

Try again, the server went through some updates. If it still does not work post updated logs.

Post your logs.

That is not a log file. But I was able to track it down to a vanilla bug. That we expose instead of letting it fail silently. Fixed in https://github.com/MinecraftForge/MinecraftForge/commit/c509cac02b8ca2f73c50acba60ef067e490d1af8

No idea what you're saying, but as a temporary fix for 1.13 until we remove it in 1.14 I added the vanilla entry to the seed list.

Depends on what change you're doing. Provide the full logs.

dataserializes seems to be a registry added in 1.13, which would lead me to think your world was upgrade, or the server is running 1.13. Which for obvious reasons wont work on 1.12. So... try 1.13.

Interesting, seems to of slipped through the cracks. With 1.13.2 being a transitional version and 1.14 right around the corner im not gunna spend to much time on this as it should be moot with 1.14's changes. May be worth just nuking our patches related to this in 1.13.2 to keep vanilla compatibility.

There is nothing causing the problem, our downloads ARE safe. Google is just paranoid and has taken it upon themselves to be the police of the internet claiming ANYTHING that isn't made by them is a threat.

obf does not change line numbers

What if the server has a different config then you? you should allow for changing whatever those values are at runtime/server start/server connect. so that you can seamlessly connect to multiple servers.

When you say "latest version" understand that that number changes as versions are released. When people ask about it, specify what EXACT version number you're using. The errors you have been experiancing have been fixed in 205+ So.. Update