|
| class | MissionDebugLoadingHelper |
| | Decides which mission ids are debug-only QA content that must never reach a production build, even with Cheats enabled there. An id is treated as debug-only when it contains "test_", "debug_", "_debug" or "_test" - a naming convention rather than an authored flag, so no mission JSON needs to change to opt in or out. More...
|
| |
| class | MissionEvent |
| | A class containing definitions of the built-in mission events. More...
|
| |
| class | MissionScriptApi |
| | This class is available under a global missions_api variable. More...
|
| |
| class | MissionScriptProxy |
| | Owns the mission catalogue (every mission JSON found, plus every lone mission script) and routes mission events to Python. A mission's handlers live in the module named after its id when such a script exists; every other mission — built-in, user-authored or mod-supplied — shares DEFAULT_SCRIPT_MODULE, so a JSON file alone is a complete mission, and a script alone is one whose handlers supply what the JSON otherwise would. More...
|
| |