-
Notifications
You must be signed in to change notification settings - Fork 0
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Add function(s) for getting common game directories #8
Comments
Parameter Sets and Reusable Modifier ParametersAfter a moment of thought, the above is a good candidate for refactoring the just added Parent Location ParametersAdd parameter sets that narrow the context into a major area, specified by a
Child Location ParametersTo support the above (and to avoid 50+ switch parameters), the above are augmented with a common The ExamplesThe "Mods" value for these two commands would be different, as they refer to the mods directory for the User and Steam directories, respectively: Get-ZomboidLocation -Context User -Name Mods
Get-ZomboidLocation -Context Steam -Name Mods Furthermore, discovery is possible so a fledgling modder can easily begin to understand the important locations within the user Zomboid directory (and consistently reference these locations from scripts): Get-ZomboidLocation -Context User -Name Logs, Lua, SandboxPresets This isn't necessary by any means, but anything that removes a barrier to development or troubleshooting is a very good thing. Worst case this is something that would likely be refactored into a private function anyways. Making the function easy to use on the shell as well is just a bonus. |
Oof, it turns out that multiple It may be worth looking into dynamic parameter sets, but the alternative would appear to be a parameter for locations from each context. |
Combining an |
Add another quality of life function to get frequently needed directories for modding:
The text was updated successfully, but these errors were encountered: