HPL3/SOMA/Getting Started/Test Debug and Continue
< HPL3 | SOMA | Getting Started
Jump to navigation
Jump to search
Your mod, map, and first script now work. This final step establishes a repeatable development loop and points to deeper documentation.
Use the development loop
- Make one small map or script change.
- Save the changed file.
- Return to the running game.
- Press
F5when the map must be restarted. - If the change fails, press
F1and check Show Error List and Show HPL Log before changing anything else.
For faster testing, launch the mod in development mode with the -mod command-line argument:
Soma.exe -mod "C:\full\path\to\SOMA\mods\MyFirstMod\entry.hpc"
The path passed to -mod is the full path to the mod's entry.hpc. See Developer Commands for -map, -mapfolder, -mappos, and other launch options.
When something breaks
Work backward to the last passing checkpoint:
- If the script fails, temporarily remove only your newest script change and read the first relevant error.
- If the map fails, reopen it in the editor and check that its split
.hpm_*files are present. - If the mod fails before loading the map, compare
entry.hpc,resources.cfg, andconfig/main_init.cfgwith the cleanMinimalCustomMapMod. - If the editor cannot find mod content, recheck
WIPMod.cfgand the(Working on mod)indicator.
See Developer Debug Menu for the full set of debug controls.
Where to go next
Choose documentation by task rather than reading the entire wiki in order:
- Build a larger environment: SOMA Level Design
- Learn map scripting: HPL3 Scripting Guide
- Learn programming fundamentals: AngelScript Fundamentals
- Understand mod configuration: SOMA Modding
- Prepare for release: Mod Distribution
Final checkpoint
You have completed Getting Started when you can:
- launch your copied mod;
- edit and save its map;
- edit its map script and see the result;
- reload the map; and
- locate script errors and the HPL log.