Seems to bootloop when client starts.

[xqozbd]

Bug description

I am experimenting with this mod and I tried joining my local hosted server. It got the mod files and closed the game, I re ran the game and it shows this.

I looked in the logs, nothing. I havent changed any configs at all yet.

I did see the other issue about the mods in allowEditinFiles config section, there was no mods thing in that.

Steps to reproduce

1. Get Server with mods, get client with Automodpack
2. Join server, get updates and close game
3. Start client and it fails

Expected behavior

To load into the game, and allow me to join the server.

Actual behavior

After clicking play, it says Automodpack updated.

Relevant logs

No response

Minecraft & Mod Loader versions

1.20.1 Fabric 0.16.5

Minecraft launcher

Minecraft launcher, and tried the beta curseforge launch.

Operating system

Windows 11

AutoModpack version

automodpack-mc1.20.1-fabric-4.0.0-beta18

Other information

No response

Check list

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

[Skidamek]

Could you please share you client log and automodpack server config?

[xqozbd]

latest.log
Server config from local hosted server:
automodpack-server.json
Server config from the client folder:
automodpack-server.json

[Skidamek]

Are you manually coping over all mods to mods directory every time it shows that popup?

If not then that's strange because what there should happen is that automodpack should remove all duplicated modpack mods from mods directory and relaunch the game with mods from special automodpack mods directory.

Looks like it fails for some strange reason so you should try do it manually just purge your mods folder on client and put there only automodpack. (You can then add additional mods which are not in server modpack no worries)

[xqozbd]

Ill try it, ill let you know how it goes

[xqozbd]

Yea it seemed to work now. Thank you!

[Skidamek]

Great i will leave it open as a solution for someone and also that just should not happen it's a bug

[Xiarno]

Great i will leave it open as a solution for someone and also that just should not happen it's a bug

Yeah I had that happened too on ATM10 and this fixed it. I did have to manually place back all clientside mod tho.

[Skidamek]

It might have been fixed in beta 19, need testing