LexManos

Provide exact versions, and all hashes listed on the site are valid for the files they reference. It's all generated through maven on our end. So if the file you're getting doesn't match the hash on our site http://files.minecraftforge.net/ then you've got a corrupt/invalid download. So, da39a3ee5e6b4b0d3255bfef95601890afd80709 is the sha1 of a 0-length input. Which means you're probably hashing 0 bytes. Which means you're using firefox and it is blocking the download.

1) There is always a log post them if you want support 2) Update to a modern version of Minecraft is you want support on this forum.

1.13.2 has been "ready" for quite some time. It's solely waiting on modders to provide feedback and testing. I've stated this MANY TIMES. 1.13.2 WILL NOT be getting a recommended build. I blame this mostly on lack of modder feedback, but also on the fact that we knew 1.13 was going to be a complete rewrite of everything, so we're doing what the community has been asking for for years. Essentially 'skipping' a version. But ya. Any other 1.14 speculation posts are gunna get deleted. Yes I know it's coming out, I'll start the update when it officially exists. Hold your horses.

Mod for a modern version of Minecraft.

Use Java 8.

Post the installer logs, and the exact path of your AppData

Use JarFix to fix your jar file association. You have it associated with your web browser for some reason: https://johann.loefflmann.net/en/software/jarfix/

The answer is still the same, update to a modern version of Minecraft if you want us to activity support you. If not, then you're on your own to fix your issues.

Yes, it does. Please stop being difficult and do what they said. Open a console. Navigate to the directory your server is in with: cd TheDirectoryPath Then run: java -jar forge-1.12.2-14.23.4.2759-universal.jar The console will output SOMETHING. So tell us what it says.

A lot of things dont use the Registry event, because they aren't Registries in the implementation sense. And we're not in the position to do vast rewrites of vanilla code to make them.

delete the files listed and rerun the installer.

nope, I could change it at any moment. Our installer supports that. There should however be no reason for you to need this file. So it shouldn't matter.

You're trying to install 1.10 mods on 1.8... This will not work. You should update to 1.12 and play modern mods.

Provide your datapacks/world for testing.

Provide your datapacks/world for testing. And before you say ANY data pack does this, no it's not any datapack. So please provide your specific data pack.

We need logs: 62 is: https://github.com/MinecraftForge/MinecraftForge/commit/cb70702ab59ea22d783818773de358991b06c7c5 63 is: https://github.com/MinecraftForge/MinecraftForge/commit/58494f88788b9a298ffe3b5112875c873ebc2150 Both are commits related to the network handshake. But without access to a realm server, and just reading the code. It should be fine.

The universal json was there for metadata. Nobody ever used it correctly so I removed it. The version json in the launcher is because I figured it was stupid to have a json extracted from another json, instead of just extracted as a file.

Use the updated launcher.

Entities are tied to the chunk. So if the chunk it's in is culled there is nothing you can do to make the entity render. You need to split your entity into multiple parts.

Congrats, by providing more detailed information, we were able to reprodue the crash and found that it was something dumb in vanilla code. Much like most issues like this. Anyways I fixed it. Point is you should always provide as much information as possible. Also this isn't "Any mod" it is only mods that register their custom tile entity renderers super early.

Unable to reproduce, provide world.

Update

Sort then via maven structure and load them using the modlist file.

Then report it to the 60 mods. This is a major issue that modders need to stop doing: https://www.reddit.com/r/feedthebeast/comments/5x0twz/investigating_extreme_worldgen_lag/

Read the log it tells you what to do. You should also report it to the specific mods that are causing it.