Added local and global settings, local settings override global settings if they are set, and the global settings are applied otherwise.
Added several new commands for this new api:
--sc set: and --sc get: have been deprecated, the following are their replacements:
--sc setlocal: name; value | --sc setglobal: name; value
These commands now differentiate between setting a global vs local (place-specific) setting
This will be useful if your, say, module import locations are different in each game
--sc resetlocal:
This command is called with no extra args and simply resets the local settings to match the global one
--sc getlocal: name; value | --sc getglobal: name; value
Same as setting local and global values, but getting
--sc exportsettings: local | global
Exporting settings now makes you choose to export local/global settings as a command
I also added newlines inbetween each āchainā
--sc getsettings: local | global
Same thing as exportsettings, just in plain form instead of an executable command
I should probably update the main post by now
DoNe
there should probably be one for global settings to just reset to the default, it may also clear unused values from updates if you donāt already do that
āsc exportsettings: global will export as setlocal
The plugin is configured through the command line, not the plugin toolbar. Read the main postās ācommandsā sections to get started.
To toggle features (couldnāt find it listed in the main post @athar_adv) use --sc toggle: feature; true/false. This currently works with everything listed here
Hi, this is probably because of the global settings :V , when a local setting is nil, the global setting is used instead. Ill probably change this behaviour bc some settings u do wanna be nil without using the global on