AutoModpack deletes itself the first time the new modpack launches, but not on subsequent starts. #473
Description
Bug description
To save time, I placed the new mods directly into the modpack folder atautomodpack\modpacks\AutumnTown\mods,then sent the zip archive to the players. I did not launch the game at all, nor did I modify automodpack-content.
This causes players to see a restart popup when they join. After that, they find that AutoModpack itself has been deleted from the mods folder,and even the new mods I added inside automodpack\modpacks\AutumnTown\mods\ were also deleted.
This only happens on the first launch.After manually adding AutoModpack and the new mods back, the game runs normally afterward.
Steps to reproduce
- I added new mods directly into AutoModpack's mod folder and then sent the modpack to players.
- When players launch the game, they find mods are missing and cannot join my server.
- After checking, I found that AutoModpack deleted itself, and also deleted the new mods I had added in
automodpack/mods.
Expected behavior
join server
Actual behavior
AutoModpack deleted itself, and also deleted the new mods I had added in automodpack/mods.
Relevant logs
Logs after mods were deleted:
latest.log: https://mclo.gs/h5hm50y
debug.log: https://mclo.gs/hWqnstC
Minecraft & Mod Loader versions
1.21.1neoforge 1.219
Minecraft launcher
PCL-CE
Operating system
win11
AutoModpack version
4.0.5
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.
- I have provided all the necessary information to reproduce the issue.
- I have verified that the issue does not occur without the AutoModpack - Ignore if you are reporting a mod conflict issue.