LexManos

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.

The files pages use a very simple system where it defaults to that message, and it's replaced by the ads that are shown. This works on some computers, and with some of the ads, but apparently not all of them. It's a best guess system. If you get it and ads, sorry... we're doing the best we can.

The advertiser that was caught doing that has been banned from the entire Adfocus network. We do not take those things lightly. But back on to point, All ad services have risk. Ads always have risk. Adfocus is used by Forge as it is the most responsive and responsible about any issues that arise. It contains the least malicious things as far as we can tell. Obviously you'll still get ads with download buttons for "Software managers" that's just the nature of the beast. If you don't like Adfocus on Forge. Consider supporting us on Patron. Until then, bills need to be paid.

Mod developers can start playing with 1.13.2. The only way we can fix bugs is if people use it an report the ones they find.

Except, they would. And it's a bit more of a overhead then we would want to put on to the server. As it's designed to be a very light weight server that does nothing but serve raw files. There is metadata available. If you're spend a bit of time to actually do you research you can figure out how to do it correctly. But most people don't. And we're not going to sit here and support the people who don't support us.

Then talk to the mod pack maker as they have released a broken pack. My advise on removing coremods still stands tho.

1) Dont spam the forum, this is not a chat room it may take a while for people to respond. 2) You have a crapload of coremods installed, it's almost impossible to tell.you which one is breaking things. I'd advise removing the coremods.

No, just run the setup. The files that the process makes/edits are illegal to redistribute {they are owned by Mojang} so there is no legitimate way to transfer them anywhere else. There is a reason why we go through the complicated setup.

Yay a For profit server manager bypassing our source of income. These is an example of exactly what we don't want happening.

You can't. This is basic server client logic. Act like the server doesnt exist on the physical client. You need to send an appropriate message tot eh server to tell it to do what you want.

Your automation is probably a bade use case. There are ways to get the information you need. However we are not publicly exposing/documenting this API as it would do nothing but harm us {both financially, and support wise} IF you have a proper usecase beside 'I'm just lazy' we might be able to point you in the right direction. But you're saying you want it for older MC versions, which honestly, Should be dead. I doubt you're installing older versions so often that you need automation for it.

Yes, it worked in the version of Forge from before you posted. Please be sure you're on the latest version before posting.

Many systems exist, the fat json file has long been the wrong way to get this information. You should make your usecase better known. If it's actually good then we can advise you how to do it now. But yes, Don't auto-download Forge. Don't use the giant json file.

Re download the installer, jenkins fucked up, I re-ran the build.

Re download the installer, Jenkins fucked up,I re-ran the build.