Modpack for Forge 1.20.1 doesn't update correctly

[ChelloVibes]

Operating System

Windows

Version of Prism Launcher

Prism Launcher 8.0

Version of Qt

Qt 6.6.0

Description of bug

I was trying to update a modpack to a newer version but "Update Pack" didn't work, so I had to update from file. I downloaded the .zip from CurseForge manually and tried to update from file which seemed to work just fine, but when I then started the instance, the game opened up for a few seconds and the crashed again with Exit Code 2.

Steps to reproduce

1. Download the .zip file
2. In the launcher update from file
3. Try to run the instance

Suspected cause

I suspect it might be because not all mods that are packaged get downloaded.

This issue is unique

• I have searched the issue tracker and did not find an issue describing my bug.

[Trial97]

What's the name of the pack? From what version did you update? It was for neoforge? Any Minecraft logs to share? Any prism logs regarding the failed update?

[ChelloVibes]

It's the Better MC Modpack for Forge 1.12.1 and I updated from v24 HF from v25.5. Here is the Minecraft log.

I tried to update the pack normally again and this time I wasn't met with an error message, but the game still crashed with the same error nonetheless.

[landaro]

I can confirm that something similar is happening for me as well.

Modpack in Question: ATM 9 from curseforge
OS: Windows
Prims verison: 8.0

Observed behaviour: pack update goes through without apparent error but instance fails to laod properly due to "missing mod dependencies".

I compared the number of mods in the pack for a freshly installed isntance, and the instance after the borked update and the mod counts differ (with the updated one having fewer than there should be).

This happend with differnt update steps of the modpack and started about oen or two weeks ago, as far as I know.

[mixednutts]

I can confirm same behavior with ATM9 update as mentioned above.

Crash log and Prism Launcher log containing update session attached:

crash-2024-02-12_15.08.48-fml.txt

PrismLauncher-0.log

If I was to guess I would say it's something to do with the API call and managing dependent mods

[mixednutts]

Just had the issue occur again with ATM9 updating from version 0.2.45 to 0.2.46

Update in Prism completes without error. Upon starting the instance the following errors are shown:

Prism Log:

PrismLauncher-0.log

ATM9 Instance Log:

Uploading latest.log…

ATM9 Crash Log:

crash-2024-02-13_03.48.23-fml.txt

Current work around is to install a fresh instance and move the save and journey map data over to it or revert to the previous version of ATM9.

The Prism log shows these as the last entries immediately after the update:

20.855 C | "Failed to apply override from C:/Users/mickj/AppData/Roaming/PrismLauncher/instances/.LAUNCHER_TEMP/261a5d82-22a8-4df0-8a9c-9b9edad46515 to C:/Users/mickj/AppData/Roaming/PrismLauncher/instances/All the Mods 9 - ATM9(2)" 20.855 C | Reason: "unknown error" 20.855 W | Failed to override "C:/Users/mickj/AppData/Roaming/PrismLauncher/instances/.LAUNCHER_TEMP/261a5d82-22a8-4df0-8a9c-9b9edad46515" to "C:/Users/mickj/AppData/Roaming/PrismLauncher/instances/All the Mods 9 - ATM9(2)" 20.855 D | Failed to commit instance "All the Mods 9 - ATM9 (3rd)" Initiating backoff: 1

If you manually copy and paste from the .LAUNCHER_TEMP dir to the instance dir the ATM9 instance is able to start

[MattSG]

This also happens for me.

Modpack in Question: ATM 9 from curseforge
OS: Windows 10 22H2
Prism verison: 8.0

Observed behaviour: Update successful but on loading game it either crashes or shows screen with missing dependencies (mods)