Possible Fixes

Yes

Modpack Version

4.14

Crash Assistant Message (big green button)

All the Mods 10 - 4.14 crashed. The logs have been uploaded to gnomebot.dev:

latest.log | debug.log head / tail (~44k lines) | crash-2025-10-20_10.47.14-client.txt | KubeJS: client.log / startup.log | crash_assistant_app.log | modlist.txt

Mod list changes beyond the modpack:

�[2;34mMod list wasn't modified.�[0m

What happened?

The integration package crashes after about ten seconds of starting.

Crash Log or Disconnect Log

No response

Latest.Log

No response

I also encountered this problem, and the result given by AI is:
java. lang. CollectalStateException: Mod 'architecture' is not available!

Your configs are corrupted, delete config folder and click to update the pack again (use same version) to refresh config folder

Same issue here, tried deleting the config folder and reinstalling the pack (4.14) but issue still persists

Same issue here, tried deleting the config folder and reinstalling the pack (4.14) but issue still persists

post your crash assistant message

Same issue here, tried deleting the config folder and reinstalling the pack (4.14) but issue still persists

post your crash assistant message

Now fixed by removing the simple loot viewer mod, which I'd added separately.

Same issue here, tried deleting the config folder and reinstalling the pack (4.14) but issue still persists

post your crash assistant message

Now fixed by removing the simple loot viewer mod, which I'd added separately.

I think Advanced Loot Info works with ATM10

I have the same problem.

All the Mods 10 - 4.14 crashed. The logs have been uploaded to gnomebot.dev:

latest.log | debug.log head / tail (~44k lines) | crash-2025-10-21_02.32.04-client.txt | KubeJS: client.log / startup.log | crash_assistant_app.log | modlist.txt

Mod list changes beyond the modpack:

�[2;34mMod list wasn't modified.�[0m

I have the same problem.

All the Mods 10 - 4.14 crashed. The logs have been uploaded to gnomebot.dev:

latest.log | debug.log head / tail (~44k lines) | crash-2025-10-21_02.32.04-client.txt | KubeJS: client.log / startup.log | crash_assistant_app.log | modlist.txt

Mod list changes beyond the modpack:

�[2;34mMod list wasn't modified.�[0m

Your configs are corrupted, delete config folder and click to update the pack again (use same version) to refresh config folder

All the Mods 10 - 4.14 crashed. The logs have been uploaded to gnomebot.dev:

latest.log | debug.log head / tail (~44k lines) | crash-2025-10-22_17.52.39-client.txt | KubeJS: client.log / startup.log | crash_assistant_app.log | modlist.txt

Mod list changes beyond the modpack:

�[2;34mMod list wasn't modified.�[0m

Trying to launch the game using the CurseForge App; other launchers such as HMCL will report errors when starting the game.

All the Mods 10 - 4.14 crashed. The logs have been uploaded to gnomebot.dev:

latest.log | debug.log head / tail (~44k lines) | crash-2025-10-22_17.52.39-client.txt | KubeJS: client.log / startup.log | crash_assistant_app.log | modlist.txt

Mod list changes beyond the modpack:

�[2;34mMod list wasn't modified.�[0m

Configs corrupted too

did you update any mod? if so that might be it

I found that it was a problem with the cristellib-neoforge-1.21.1-3.0.0.jar mod, and it is recommended to update Cristellib to 3.0.2 to solve this problem

I found that it was a problem with the cristellib-neoforge-1.21.1-3.0.0.jar mod, and it is recommended to update Cristellib to 3.0.2 to solve this problem

I followed what you said and found this mod, then updated it, and it indeed loaded successfully. Now I can avoid using CurseForge App.