LexManos

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.

1) Update to a modern MC if you want support 2) Read your crash it tells you what mod is crashing, you should ask them not us.

Full system time and date: date is redundant IMO, but it's already there: [11Mar2019 16:36:24.841] [main/INFO] [cpw.mods.modlauncher.Launcher/MODLAUNCHER]: ModLauncher starting: java version 9.0.1 Folder paths: [11Mar2019 16:36:25.169] [main/DEBUG] [net.minecraftforge.fml.loading.FMLPaths/CORE]: Path GAMEDIR is Z:\Projects\Forge\Forge_113\projects\forge\run [11Mar2019 16:36:25.170] [main/DEBUG] [net.minecraftforge.fml.loading.FMLPaths/CORE]: Path MODSDIR is Z:\Projects\Forge\Forge_113\projects\forge\run\mods [11Mar2019 16:36:25.171] [main/DEBUG] [net.minecraftforge.fml.loading.FMLPaths/CORE]: Path CONFIGDIR is Z:\Projects\Forge\Forge_113\projects\forge\run\config All the information is there if you look.

"You shouldn't do that as that is now what the system is designed for" "I still wanna do the thing even tho you just told me that it is the wrong way to do it because... I'm special..." Seriously? No. Don't 'circumvent it' just use the system the way it was designed.

"the vanilla item didn't have any variants and my override item does" That is your problem. When replacing a registry item, do not add variants. You must replace the item exactly as is. if you need more then add an extra registry entry and translate them as needed.

Stop spamming our forum with your sob story. I already told you on github that the issue should not be present as everything we do caches the files and tasks after they are first run. So internet should not be strictly necessary unless something in your cache is corrupt. IF you have a real reproducible issue submit a PR to fix it. That's what open source/github is for. Until then we don't want to hear your sob story.

Again your issue is that you're being stupid and using a constant when a standard item/tag would do: { "name": "strangetrees:super_infusion_emerald", "item": "strangetrees:super_infusion_emerald" }, else if (json.has("item")) tmp.put(name, new StackList(Lists.newArrayList(getItemStack(JsonUtils.getJsonObject(json, "item"), true)))); Follow the correct spec for _constants if you're gunna use them. Basically, _constants was created as a precursor to tags. If you're just using ONE item use the item directly. If you have basic list items that have no meta/nbt. Then use a tag. ONLY use _constants if you're using custom ingredients/nbt.

Protip: All of your 'constants' are bad. The point of the constants json was to prevent massive duplication. If you're just redirecting to a single line for a tag. Then you're just wasting load time by making it a constant. You should convert your 'emerald's to tags and skip _constants.json entirely.

The "symbol you're referring to is a "bug" it's used to mark builds that are not the main branch for their version. Stars are rec builds, half stars are latest builds. No idea where you got said "virus". If you're downloading through ad links be sure you're not downloading the advertized software if you don't want it.

Read the error... run the installer..

This has been fixed.

you don't, but we can.