Change Details

I'd like to request a feature to create custom profile namespaces, separate from default one operated by profile namespace commands. Reasoning: Current profile namespace grows quite big after playing a lot of different missions and servers, making `saveProfileNamespace` command freeze the game for a bit, rendering mid-game saving problematic because micro freezes ruin performance and fluidity of the game. This happens because each developer uses it as they see fit, some might save a lot of data into it, which would hinder its usage in other missions. I propose to introduce set of command and functionality to let mission developers use their own named profile namespaces. Commands: `<bool> = loadCustomProfileNamespace <string>` `<bool> = saveCustomProfileNamespace` `<namespace> = customProfileNamespace` **loadCustomProfileNamespace** Unary command that loads custom profile namespace with name supplied as string. Target filename could be something like `<profile>.<string>.vars.Arma3Profile` in the profile directory. Returns load failure or success as boolean, true if name was provided, file exists and valid, false otherwise. **saveCustomProfileNamespace** Saves currently loaded custom profile namespace that was previously loaded with load command. Return true if writing was successful, false otherwise (file is read only, custom profile namespace wasn't loaded, etc.) **customProfileNamespace** Returns currently loaded custom profile namespace variable to use in scripts. Null namespace if it wasn't loaded.

I'd like to request a feature to create custom profile namespaces, separate from default one operated by profile namespace commands. **Reasoning:** Current profile namespace grows quite big after playing a lot of different missions and servers, making `saveProfileNamespace` command freeze the game for a bit, rendering mid-game saving problematic because micro freezes ruin performance and fluidity of the game. This happens because each developer uses it as they see fit, some might save a lot of data into it, which would hinder its usage in other missions. I propose to introduce set of command and functionality to let mission developers use their own named profile namespaces.

I'd like to request a feature to create custom profile namespaces, separate from default one operated by profile namespace commands. **Reasoning:** Current profile namespace grows quite big after playing a lot of different missions and servers, making `saveProfileNamespace` command freeze the game for a bit, rendering mid-game saving problematic because micro freezes ruin performance and fluidity of the game. This happens because each developer uses it as they see fit, some might save a lot of data into it, which would hinder its usage in other missions. I propose to introduce set of command and functionality to let mission developers use their own named profile namespaces. Commands: `<bool> = loadCustomProfileNamespace <string>` `<bool> = saveCustomProfileNamespace` `<namespace> = customProfileNamespace` **loadCustomProfileNamespace** Unary command that loads custom profile namespace with name supplied as string. Target filename could be something like `<profile>.<string>.vars.Arma3Profile` in the profile directory. Returns load failure or success as boolean, true if name was provided, file exists and valid, false otherwise. **saveCustomProfileNamespace** Saves currently loaded custom profile namespace that was previously loaded with load command. Return true if writing was successful, false otherwise (file is read only, custom profile namespace wasn't loaded, etc.) **customProfileNamespace** Returns currently loaded custom profile namespace variable to use in scripts. Null namespace if it wasn't loaded.