How marcos2221/dcs_tpe works
DCS_TPE is a DCS mission-persistence system for single- and multiplayer missions. A mission designer loads MIST, CTLD, and CSAR in timed mission triggers, then runs the persistence loader; TPE saves mission progress to files and uses those files to restore correctly named groups on later loads. The README also documents a TPE hook, a network-side script, JSON, and a generated configuration file. Source excerpts were unavailable, so the internal call paths and several integrations remain undocumented.
Main entry points: mainPersitentEgineNet.lua Network engine · PersistentMissionFileLoad.lua Mission loader · TPE.lua TPE hook · JSON.lua JSON support
Components 14
Mission runtime
- Timed triggers
- MIST
CTLD_CSAR/mist_4_3_74.lua - CTLD
CTLD_CSAR/CTLD.lua - CSAR
CTLD_CSAR/CSAR.lua - Mission loader
PersistentMissionFileLoad.lua
TPE runtime
- TPE hook
Scripts/Hooks/TPE.lua - Network engine
Scripts/net/TPE/mainPersitentEgineNet.lua - JSON support
JSON.lua - Mission scripting setup
SlmodMissionScripting.lua
Persistence state
- TPE save directory
- Mission state file
- TPE config
Other components
- Mission designer
- DCS runtime
Connections 14
- Mission designer → Timed triggers: configures
README.md - Timed triggers → MIST: loads first
README.md - Timed triggers → CTLD: loads second
README.md - Timed triggers → CSAR: loads third
README.md - Timed triggers → Mission loader: runs afterward
README.md - DCS runtime → TPE hook: hosts
README.md - DCS runtime → Network engine: hosts
README.md - TPE hook → TPE save directory: creates
- Network engine → TPE save directory: uses
- TPE save directory → Mission state file: holds
README.md - TPE save directory → TPE config: holds
README.md - Mission loader → Mission state file: restores from
- JSON support → Network engine: supports
- Mission scripting setup → DCS runtime: configures