[1.20.1 Forge] ATLauncher incompatibility - client auto update relaunch stuck infinitely

[MrKashew]

Bug description

let me know if more log data is necessary

Steps to reproduce

During client auto update phase of launch

Expected behavior

No response

Actual behavior

No response

Relevant logs

No response

Minecraft version & Mod Loader

1.20.1, Forge 47.1.43

Operating system

Windows 10

AutoModpack version

3.4.2

Other information

No response

Check list

• [X] I have verified that the issue persists in the latest version of the mod.
• [X] I have searched the existing issues and confirmed that this is not a duplicate.

[Skidamek]

What does hanging on config means?

[MrKashew]

sorry - meaning it gets stuck on this step infinitely

[MrKashew]

removed player companions and artifacts mods as they are the last 2 to be logged, issue still happening (infinite loading)

[MrKashew]

generated another modpack on my server and it gets stuck here now, not really finding any useful info to log https://gyazo.com/07b0b8668891f777ef821e7243937c5d removing solely automodpack solves the launch getting stuck and configs are generated properly tried to remove configs from sync entirely and blacklist configs folder, issue still persists with automodpack

[MrKashew]

I was able to bypass the launch stuck by deleting contents inside automodpack/modpacks/{{server-ip}} however this triggers an update option upon trying to join the server if click yes + relaunch, then it comes back to the same issue still blocking me from playing the game

[Skidamek]

did you try with newer build i send you already few times?

[MrKashew]

currently using automodpack-mc1.20.1-forge-3.4.3+build.82

[MrKashew]

attached wrong log latest.log here is the log from launch getting stuck

[Skidamek]

Without automodpack it loads?

[MrKashew]

yes, it currently launches if I either delete contents inside automodpack/modpacks/{{server-ip}} (until relaunch) or delete automodpack mod, I'll see if I can get more info it is driving me a bit mad

I'll continue debug after work

[Skidamek]

in few minutes should be build with more loging

[Skidamek]

https://github.com/Skidamek/AutoModpack/suites/14543851898/artifacts/823119410

[MrKashew]

narrowed the bug down It happens when using the Forge mod with ATLauncher, it freezes right before where [modloading-worker-0/INFO] [AutoModpack/]: Modpack is already loaded case would happen on Vanilla Launcher I tried it with Vanilla Minecraft Launcher and it worked successfully (tested successfully several forge version 47.1.3 and above)

A bit unfortunate however as ATLauncher is my favorite launcher it doesn't seem JVM argument related as I kept those same on both launchers

[MrKashew]

I've unblocked by moving to prism launcher - no longer have the issue, seems ATLauncher specific

[Skidamek]

It may fix this https://github.com/Skidamek/AutoModpack/suites/14661468566/artifacts/832045729

[Skidamek]

Should be fixed in 3.4.4 if not just use prism lol