Setting for variables (per-variable) to set them to be "modpack-update-save" (store them outside the Minecraft instance)

[caela-uk]

Describe my idea? Oh, it would be a pleasure 🫡

A way for variables to carry between instances and modpack updates would be so handy, I'm currently trying to do this with random .txt files in the .minecraft folder and it's not fun 😭

I currently have an "onboarding" system and accent colour selection that gets reset for the user after every update since the variables file is included in my exports, not including the normal user_variables.db in my exports is simply not an option for me either since that would remove default values that should be shipped but no need to fear because I propose a solution:

A toggle for existing variables to have them become "local" and referenced using another .db file located somewhere in .minecraft/ (please allow a custom path like my planned .minecraft/BUTR/, using normal config folders there may also be issues with the official Minecraft launcher's instances being .minecraft too).

Having a new type of value or variable from scratch that is referenced with a different placeholder would complicate existing action scripts and variable stuff for me and probably other users, preventing a switch over. It would be easier for this variable to use the existing placeholders and have anything to do with the "local" part be exclusively in the main user_variables.db file and variables screen (e.g. instructions on how to find its value, its custom path for its .db files containing its value).

I can't think straight today lmfao so I am aware this feature request is kind of vague and messy. Even if this feature doesn't end up exactly how I imagined it, I would still be happy 🤣

[Keksuccino]

Wouldn't it be enough if I would allow for setting a custom save path for the variables file?

//Edit: Nvm, wouldn't be enough.

[Keksuccino]

But you wouldn't be able to ship presets/defaults for variables that are set to this special save location, because you can't include it in a modpack. These variables would need to be initialized in a different way on first modpack launch or whatever.

//Edit: Actually, wait. You could ship defaults. You simply set them as the normal variable default, but other than normal variables, these variables stay at default value in the normal variable file and the edited/updated value gets saved elsewhere. That way you can initialize it and then it does not get overridden anymore.

[caela-uk]

But you wouldn't be able to ship presets/defaults for variables that are set to this special save location, because you can't include it in a modpack. These variables would need to be initialized in a different way on first modpack launch or whatever.

//Edit: Actually, wait. You could ship defaults. You simply set them as the normal variable default, but other than normal variables, these variables stay at default value in the normal variable file and the edited/updated value gets saved elsewhere. That way you can initialize it and then it does not get overridden anymore.

Was just thinking, for some launchers or OS's they might not be able to do .minecraft and users probably won't want their settings reset every launch so having an in-instance fallback would be useful