DaemonUmbra

You have a 1.7.10 coremod in there screwing things up. See my signature for the most helpful log

Do you have any other files? If possible post then to github and link the repo.

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.

Please provide logs as described in the EAQ and my signature below.

Pretty sure it's in the splash.properties... anyway try separating the gif into an animation strip png with each successive frame below the previous. The timing may be off but that's how the modern Forge animation handles it.

I see these (spoiler because images are big): And again I must mention that these are case-sensitive, so far I haven't seen a before and after with the correct capitalization used.

The thing is a lot of the tags are nested and case sensitive, for instance I see you using enginetype but elsewhere in the original data I see engineType, and I also see some other stats that are in the NBT that may or may not change when you change the engine using this method.

When the entity data changes successfully it vomits all of the entity's NBT data into chat. I assume that's what's happened here but that link is a 404.

The square brackets immediately following the @e are filters, separated by commas. Adding the type filter to your existing command would look like this: /entitydata @e[r=2,type=<whatever the entity type is>] {engineType:4}

@e selects entities, you are an entity. r= tells the command the radius in which to search for entities, again you are included in this search You have no filter in there to tell the command to look specifically for the vehicle, so it's just going to use every entity it finds. You can use/summon (requires cheats) to look up the actual entity type of the vehicle using the tab completions, once you have that you can use the type= filter for @e.

I'm afraid that seems likely.

Yeah I think the issue is Twitch has their own CDN deliver the files and they appear to have broken/corrupted versions of some of them that they are then pushing to clients. I had Twitch refresh all the libraries that worked and now it crashes again.

Well I just copied my libraries folder from my Mojang launcher installation and launched it with my own bat file to target Twitch's installation directory... it works...

I looked closer and saw that what I thought was gone was actually moved somewhere else in the file. Looking further...

Ok so I was unable to replicate the issue with Forge on the Mojang launcher but I was able to replicate it with Twitch... ergo Twitch is screwing things up as usual. Note: With the way the Mojang Launcher works you have to close EVERYTHING to get a new instance of it. I'm assuming a bit here but if you tested with Twitch and closed the launcher but not the log, starting the launcher again would not bring up the regular launcher, it would bring up Twitch's version (i.e. the broken one) again.

From the top going by the root "Caused By" of each error: This is impossible unless something is modifying Forge, or the file is corrupted. More of the same. This suggests you are missing a Library, or it is corrupted. Try the following to force Twitch to fetch fresh versions of everything(this should fix the issue if it is indeed corruption): Go into /Documents/Curse/Minecraft/ and delete the Install folder, then relaunch the pack with Twitch. To install a clean version of Forge with Mojang's launcher go to %AppData%\.minecraft\libraries\net\minecraftforge\forge\ and delete the appropriate [MC Version]-[Forge Version] folder, then re-run the Forge installer.

Does it work if you DON'T select your modpack's directory?

Have you tried it in a normal launcher without Twitch's middleman shenanigans?

Does this happen without any mods installed? If so please post a log with no mods installed.

Recipes+ is broken for servers.

Post a debug.log from Forge for 1.12.2

Try a more modern version of Minecraft.

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

Forge's incompatibility with Java 9+ is known and is not new, you need to use Java 8 as the installer outright tells you when you try to install Forge with any other version of Java.

Please make your own thread, it helps keep things straight when there is only one person needing help in each thread.