GloSC or Standalone

Q: How can I use GloSC and OSOL together?

A: The most robust way is to do something like the following:

• Open the GloSC configurator, click the Create New button.
• Check Launch game, click the ... button next to Path and select the path to the executable of OSOL you wish to use for this shortcut.
• Make sure Close shortcut when launched application closes is checked.
• Name this GloSC shortcut whatever you like, then click Save at the bottom of the Config section for this shortcut.
• Click the Add all to Steam button.
• Next, open the executable of OSOL that you chose earlier.
• Follow the normal instructions for setting up OSOL with your launcher/game.
• Use the non-Steam game shortcut that GloSC added to Steam earlier to launch your game.

---

Q: Can I use OSOL to run pre/post game commands or scripts as a sort-of standalone launcher?

A: Yes, absolutely! OSOL only requires a valid GamePath, the LauncherPath is totally optional. OSOL also has support for running commands (optionally, with elevated privileges via the ElevateExternals .ini variable) before and after a chosen game using the PreLaunchExecPath and PostGameExecPath .ini variables. You can also delay them with PreGameWaitTime and PostGameWaitTime, and forcefully close them when OSOL exits with ForceKillExternals.