DaemonUmbra

You are attempting to run at least one 1.7.10 coremod with Minecraft 1.12.2.

1.7.10 is no longer supported on this forum due to its age. Please update to a modern version of Minecraft to receive support.

I don't know the nitty gritty of how these mods work. The easiest explanation is that Forge tries its hardest to be the ONLY coremod that anyone needs, people making their own coremods makes this a "too many cooks in the kitchen" situation. People making their own coremods assume things when they make their coremods, and when Forge changes something that they were making assumptions about, things go wrong. Yes the Forge change "causes" the issue. NO this is not Forge's fault, it is explicitly stated that coremods do not receive official support and this is one of the many reason why. People making coremods have to accept that when there is a change in Forge they are responsible for keeping their crap compatible. If you continue to argue that this is Forge's fault then you do not understand the regrettable arrangement between Forge and modders who insist on making coremods.

Please provide debug.log files from both the server and client in the manner described in my signature.

Obfuscate is a coremod, besides Forge plainly flagging it as such, it utilizes a library that in this case has no purpose other than coremodding. While NEI is not a coremod itself, it requires JEI as well as CodeChickenLib (which has coremod functionality) to function.

At least one version had a false positive from an Anti-Virus engine in the past. However this is usually because your browser has simply detected that you downloaded a file that is executable (i.e. a program) and it cannot verify that the program is from a commonly trusted source (i.e. a well-known corporation). If this worries you at all, remember that the source code for everything Officially-Forge-related (as far as I know) can be viewed on GitHub.

In the future please provide a full debug log, not just a snippet. Your client is missing many mods that are installed on the server, your client should have shown a screen stating this.

I believe this is because the JRE that Minecraft ships with is 1) Horrifically out of date 2) Not exactly "installed" on the user's system, it's more just extracted into Minecraft's program files, so there are no registry keys or environment variables pointing to it, a program that wants to use it has to already know where it is.

You are looking at my signature, which in this case shouldn't be required, at least not yet. Please copy paste the exact command you are using.

To quote the Wiki Page:

Update Forge, some of your mods are marked as needing a version more recent than the recommended build.

Versions of Tesla Core Lib prior to 1.0.6 require the separate Power API, do you have that installed?

User was banned for using a cracked launcher. Buy the game.

1.7.10 is no longer supported on this forum due to its age. Please update to a modern version of Minecraft to receive support.

Even if you think you "have the same issue", do not hijack a thread, make your own. I have split your reply into its own topic.

Please post logs as described in my signature below.

Please provide logs as described in my signature below.

Please provide logs as described in my signature below.

Your repo appears to be out of date, can't help you with code that's not there.

There are .gradle folders in your project workspace and your user directory, try deleting those, note that next time you run anything Gradle related everything it had cached previously will need to be re-downloaded. Also I am not 100% sure this will work. I would also delete your build folder.

Have you tried cleaning the gradle cache?

Exactly how did you start coding this project without Gradle?

Can you post your code to GitHub so I can test it on my end?

You're using an ancient version of Forge for 1.12.2 and trying to load a (presumed)1.7.10 coremod.

Decocraft2 requires PTRLib and this has not been indicated properly inside the mod so Forge doesn't catch it with a Missing Mod screen. I have been told that the next release of Decocraft2 will fix this issue, however.