You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Let's say I created a modpack on 1.20.1 with forge and several mods for that version. I then update my minecraft version, forge, and all my mods to 1.21.1. From there, I generate a modpack with the same name for that version. Currently, players with the 1.20.1 version of the modpack will be stuck on that version unless I have them manually update forge and reinstall automodpack.
Description
It would be great if upon launching the game, automodpack checks if the forge version matches the server and updates if the server is running a newer version. It would also be great if the mod loader could be switched out if the client detects the server is running fabric instead of forge and vice versa.
Other information
No response
The text was updated successfully, but these errors were encountered:
Motivation
Let's say I created a modpack on 1.20.1 with forge and several mods for that version. I then update my minecraft version, forge, and all my mods to 1.21.1. From there, I generate a modpack with the same name for that version. Currently, players with the 1.20.1 version of the modpack will be stuck on that version unless I have them manually update forge and reinstall automodpack.
Description
It would be great if upon launching the game, automodpack checks if the forge version matches the server and updates if the server is running a newer version. It would also be great if the mod loader could be switched out if the client detects the server is running fabric instead of forge and vice versa.
Other information
No response
The text was updated successfully, but these errors were encountered: