DaemonUmbra

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

I doubt Forge will officially support it, however as you say it is open source so a mod will probably be able to do the job. Note: I am not part of the dev team so if one of them contradicts me, listen to them over me.

I'm not sure what you mean by this, what launcher are you using?

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'm not 100% certain but the issue may be OneDrive being funky with file permissions. Try making another folder outside of OneDrive and telling Twitch to use that folder instead.

The log gets re-generated whenever you run the launcher, so it's a log of whatever version you launched last, provided you're looking at the correct launcher. You're playing Continuum using Twitch, right? I believe the launcher_log.txt for the launcher that Twitch hooks into is at /Documents/Curse/Minecraft/Install/

I need the log from a time when you tried to start continuum... this shows you running 1.13.1

Ok...and the link?

Just use one of the sites linked in my signature and post the link.

It's below each of my posts.

Can you provide your launcher_log.txt using one of the sites linked in my signature?

Is this in the launcher or Minecraft itself?

From the looks of the log, are you are registering armor models inside the armor item's constructor?

Bug was already fixed, update the mod.

Just use any other version and it should work.

I don't see Forge or any other mod in the stacktrace and that usually indicates the issue is a coremod. However, @quadraxis brings up a good point that it could be any mod screwing up their entity spawn registration.

As far as I know a mod is not required to have an mcmod.info, it's just a file that has extra information for Forge to serve to the player in the mod listing screen.

Curse doesn’t fetch Forge from Forge’s servers, they use their own CDN which has the bad version saved.

Everything, I tried testing with the files you provided and was unable to replicate your issue.

1.7.10 is no longer supported on this forum (nor in the AW community). Please update to a modern version of Minecraft to receive support in either place.

Make a backup of the world and start going through the mods Forge has listed as Coremods. Remove them one by one.

Can I ask what URL you got the installer from? It shouldn't be asking for you to "add the forge launcher manually" as far as I know...

You say this as if 1.7.10 is unique in this regard.

I don't have an answer for that currently. Worst case you can still use launcher profiles to target standalone Java installations.

It's not as simple as you think. Forge uses a lot of Java backend/internal stuff and most, if not all, of it has changed between Java versions 8 and 9/10. All of that has to be rewritten to work in Java 9+ It's being worked on though, Forge 1.13 will run on Java 9+