Ran into the same issue, couldn't find a fix after spending a couple of days troubleshooting and looking at the logs. I eventually gave up and just used another launcher app to manage my modpack installs.
Been trying to figure this one out myself. It seems that the forge 1.16.1 packs are not populating the correct forge jar files if the pack runs forge version 32.0.108. I found this by going to "Settings" on the Minecraft Launcher and checking the box for "Open output log when games start". I'm not sure where the best place to report this is, because it happens with EVERY 1.16.1 pack
Failed to find Minecraft resource version 1.16.1-20200625.160719 at C:\Program Files (x86)\Minecraft\Install\libraries\net\minecraftforge\forge\1.16.1-32.0.108\forge-1.16.1-32.0.108-client.jar
0
In reply to djromrell:
Yeah, I just gave up troubleshooting and starting using a different modpack launcher.
0
Ran into the same issue, couldn't find a fix after spending a couple of days troubleshooting and looking at the logs. I eventually gave up and just used another launcher app to manage my modpack installs.
2.87310672054075
Been trying to figure this one out myself. It seems that the forge 1.16.1 packs are not populating the correct forge jar files if the pack runs forge version 32.0.108. I found this by going to "Settings" on the Minecraft Launcher and checking the box for "Open output log when games start". I'm not sure where the best place to report this is, because it happens with EVERY 1.16.1 pack
Failed to find Minecraft resource version 1.16.1-20200625.160719 at C:\Program Files (x86)\Minecraft\Install\libraries\net\minecraftforge\forge\1.16.1-32.0.108\forge-1.16.1-32.0.108-client.jar