Tutorials:Install Scripts: Difference between revisions
DoctorDalek (talk | contribs) m (DoctorDalek moved page Tutorials/Install Scripts to Tutorials:Install Scripts without leaving a redirect) |
DoctorDalek (talk | contribs) No edit summary |
||
Line 1: | Line 1: | ||
[[Category:Tutorials]] | |||
== Overview == | |||
LANCommander supports the use of install scripts for handling anything after the download and extraction of a game on a client machine. Common uses for install scripts include importing registry keys, updating configs, and templating file structures. Like all client-side scripts with LANCommander, these are essentially PowerShell scripts that are executed post-extraction. | LANCommander supports the use of install scripts for handling anything after the download and extraction of a game on a client machine. Common uses for install scripts include importing registry keys, updating configs, and templating file structures. Like all client-side scripts with LANCommander, these are essentially PowerShell scripts that are executed post-extraction. | ||
Revision as of 05:52, 31 July 2023
Overview
LANCommander supports the use of install scripts for handling anything after the download and extraction of a game on a client machine. Common uses for install scripts include importing registry keys, updating configs, and templating file structures. Like all client-side scripts with LANCommander, these are essentially PowerShell scripts that are executed post-extraction.
Here are some examples of some post-install actions you may want to consider:
- Import/create registry keys necessary for game execution
- Automatic detection and config update to support the resolution of the primary display
- Scaffolding save game file structures in the user's profile directory
- Automatic installation of dependencies such as a redistributable
Note: After the extraction of the game is complete and the install script has been executed, the LANCommander Playnite extension will automatically execute any name change script