Ugdhar

Please post full logs as described in the EAQ, there is not enough information in your post to help.

1.12 is no longer supported on these forums due to age. Please update to a modern version to receive support here. More information on supported versions can be found in the LTS link at the top of every page.

Please be more specific about what you are trying to achieve, details from the players point of view would help

1.12 is no longer supported on this forum due to age. Please update to a modern version to receive support here. More information on supported versions can be found in the LTS link at the top of every page.

1.12 is no longer supported on this forum due to age. Please update to a modern version to receive support here. More information on supported versions can be found in the LTS link at the top of every page.

Unfortunately, not something I've messed with yet, so I can't help you. I was just explaining how (I'm guessing) the other person was figuring it was server side..

Not sure if this is 100% correct, but unless something is graphics, sound, or input, I would pretty much guess that it's server-side, otherwise the client could corrupt/hack stuff.

First, I'm pretty sure you are not supposed to rehost mods like you are doing on your google drive. Second, 1.7 is no longer supported on these forums due to being so old. Please update to a modern version to receive support here. More information on supported versions can be found in the LTS link at the top of every page.

Whats Line? Not sure if that's the line number or not where it says "SourceFile:62", but again, probably would want to look at the debug log, not just the crashlog (I know this is old, but if it were new that's what you'd want to do) for more info, as it may be crashing in that method in AgeableModel, but it's more than likely not CAUSED by the AgeableModel.

So this is how I am reading that log you linked: 1. I notice it's a Null Pointer Exception (NPE), so something that's null is being accessed 2. Not much more information at the top here, just a list of classes where it errored out, but I don't believe that it was the actual AgeableModel that is crashing us, so I continue scrolling/scanning the log 3. Further down, we see some stuff about a unicorn, so to me, that's where I'd be looking. Of course, you only posted the crash log, no debug, so info is limited, and no code to go with the crash. But basically, scan through it (you have to be patient, and actually LOOK at everything, at least a little) and look for stuff that is: A) understandable, i.e. looking for "exception caused by" or something like that; B) any class/package names that are from your project, as these are most likely to cause the issues. Honestly, it's really just programming experience and practice that make a programmer able to debug their stuff. The more you are exposed to it, the more you will understand. Something confusing now, if you keep with it, and continue to learn/grow, in a month you'll look at the same confusing thing and find it much easier to understand. If you find something too hard, back off a bit, work with something a little easier, then come back to it later with a clear mind and maybe a little more knowledge.

1.7 is no longer supported on these forums due to age. Please update to a modern version to receive support. See the LTS link at the top of every page for more information on supported versions.

It's one of the gradle tasks

What happens when you try to run the installer for newer versions? Be as detailed as possible.

If you read the error report, it tells you exactly what is wrong: You have 1.14.4 mods trying to load in 1.15.2

1.7 is no longer supported on these forums due to age. Please update to a modern version to receive support. See the LTS link at the top of every page for more information on supported versions.

1.12 is no longer supported on these forums due to age, this thread is over a year old. If you are having an issue with a modern/supported version, please start your own thread with relevant information on your issue, including code/logs.

1.5 is no longer supported on these forums due to age. Please update to a modern version if you wish to receive support. See the LTS link at the top of every page for more information on supported versions.

Optifine's website, the download page, there's a changelog link next to every version download, and the changelog will tell you which version of forge that version of optifine will work with.

In theory you should already have run configurations setup after ruinning genEclipseRuns or genIntellijRuns If I had to choose one, I would probably choose Main from net.minecraft.client.main

Since you downloaded mods from a sketchy website, it could be any of them. You should delete all of the mods you downloaded, and then only download mods from curseforge.com

For example, looking on curseforge, the double doors mod has a filename of doubledoors_1.14-1.2.jar, but your filename is Double-Doors-Mod-1.14.4.jar, and this format is consistent with illegal mod repost sites. If you redownload all the mods from curseforge and still have a problem, post new logs for us to look at.

Where did you download your mods from? Some of the filenames look like you downloaded them from bad websites (i.e. 9 minecraft is BAD, never download from there). Only download mods from curseforge.com or directly from the mod developer. Other websites illegally distributing mods may have outdated versions, hacked jar files containing malware/viruses, or worse. I would delete all mods you downloaded elsewhere, and go redownload them from curseforge, and try again.

Try deleting your config folder and trying again

Please post logs as described in the EAQ, there is no information available without them.

From what I can tell, it looks like a coremod is blowing up, and I also see errors with simplefarming I think. I think more information would be needed, such as a list of mods in use when this crash happens, along with their version #s, and where you downloaded them from. My gut feeling is (if the mod(s) aren't just broken) that there's likely some sort of mismatch with the mod version being used vs the forge version being used. But I don't think there's enough info to tell.