What config to change
Fabulously Optimized should consider introducing a "content lock" to its included mods prevent accidental deletion or updating of them by the users. This would not prevent users from adding mods, nor manipulating them in the file manager.
The lock should only be present on supported versions of the modpack, meaning as soon as a version gets unsupported, a version update shall be released that unlocks all mods. The lock would not be implemented on included resource packs, as self-updating these would rarely cause issues.
Prerequisites:
- The feature must be present in the 3 main launchers, currently it is in:
- UI must be easy enough to understand and disable by the user, although there will be instructions for that too.
- The feature should not interfere with the modpack creation process.
Why should it be changed
- Users can then use the "update all mods" buttons freely with their extra mods, without worrying about updating FO mods.
- Users will not break their instance by updating to a mod version that is known to be broken/incompatible/untested.
- Users are more inclined to update the modpack properly and get all changes it includes (especially configuration changes)
- Users are more aware which mods are included in the modpack at all
- Most modpack mods' features can already be disabled in-game, so disabling modpack mods is often not necessary
- As outdated versions will stay unlocked, this indicates to the user "now you're on your own"
Why should it not be changed
- Some users may get confused
- Some users may become less inclined to update any mods unless necessary
- Some users may find it limiting
Additional details
This was already tested in 12.0.0-alpha.6 on CurseForge App, but reverted to prevent launcher-specific confusion.
See also: the mod list of #1060
Discord discussion link
No response
Confirm
What config to change
Fabulously Optimized should consider introducing a "content lock" to its included mods prevent accidental deletion or updating of them by the users. This would not prevent users from adding mods, nor manipulating them in the file manager.
The lock should only be present on supported versions of the modpack, meaning as soon as a version gets unsupported, a version update shall be released that unlocks all mods. The lock would not be implemented on included resource packs, as self-updating these would rarely cause issues.
Prerequisites:
#2396#3475#3324#2996#4040)#764#4470)Why should it be changed
Why should it not be changed
Additional details
This was already tested in 12.0.0-alpha.6 on CurseForge App, but reverted to prevent launcher-specific confusion.
See also: the mod list of #1060
Discord discussion link
No response
Confirm