Foxlider
commented
8 months ago This is impossible with FASTER and really, not really supposed to work that way for Arma
The SAVE button is used to compile all the settings from each UI tab into their respective file However, mod choice (server side or clientside) is used at launch : When you press the launch button, it gets the list of selected mods from the UI and generates the launch command that is sent to the system to effectively launch arma with the proper settings
Is your feature request related to a problem? Please describe.
Our unit was using TADST for years and there is one neat feature that made one process extremely easy. In Faster, you have Server Profiles and you can customize them and all that. Then you save it and you can use it, launch and so on. But here is the catch with the saving. Every change in mods(Selecting which mods you have enabled) you do is automatically saved and you don’t have to press the save button. This brings an issue to our workflow that we have a profile with core modpack and sometimes we conduct test missions where we want to enable 1 or more mods for that one mission. In TADST we were used to a simple workflow of enabling the mod(s), launching the server but not saving the changes. We had the mission and then we just switched profile back and forth and no changes were saved which was desired. We didn’t have to search again for which addons were temporarily enabled. In FASTER because it autosaves, this complicates things.
Describe the solution you'd like
I would expect it to be saved only when you press the save button.
Describe alternatives you've considered
having the auto save as a toggle in options. Or perhaps having default settings for each profile