hpl3:tutorials:mod-creation:setting_up_a_mod_entry
| Both sides previous revision Previous revision Next revision | Previous revision | ||
|
hpl3:tutorials:mod-creation:setting_up_a_mod_entry [2015/12/15 11:58] luis [Common Attributes] |
hpl3:tutorials:mod-creation:setting_up_a_mod_entry [2016/07/06 11:41] thomas [Running a Mod] |
||
|---|---|---|---|
| Line 58: | Line 58: | ||
| /> | /> | ||
| </code> | </code> | ||
| + | |||
| + | ===== Running a Mod ===== | ||
| + | |||
| + | There are two different ways to run a mod: | ||
| + | |||
| + | * Using the Mod Launcher app: there's a special Mod Launcher program that will scan subscribed content in SteamWorkshop (where applies) and the local "redist\mods" directory. To make your mod entry appear in the launcher's list, it must be located in its own directory under the "\mods" directory. For example, a mod for SOMA in a directory called "my_mod" would need to have the path "C:\Program Files (x86)\Steam\steamapps\common\SOMA\mods\my_mod" | ||
| + | |||
| + | {{:hpl3:tutorials:mod-creation:modlauncher.png?nolink&400}} | ||
| + | |||
| + | * Using the command line: to run a mod directly, you only need to run the game executable passing the "-mod" option followed by the full path to the mod's "entry.hpc" file as arguments. Using this method, the mod can be placed anywhere as long as the path to the "entry.hpc" file passed is correct. For the previous example, given the full path for the mod "my_mod" is "C:\my_mod\", the command line for running it should read like this: | ||
| + | |||
| + | <code> | ||
| + | soma.exe -mod C:\my_mod\entry.hpc | ||
| + | </code> | ||
| + | |||
hpl3/tutorials/mod-creation/setting_up_a_mod_entry.txt ยท Last modified: 2016/07/06 11:41 by thomas
