Overview
TheFrostyModExecutor class is responsible for applying Frosty mods to game data and launching the game with modifications. It processes mod resources, applies handlers, generates modified game files, and manages the game launch process.
This API is primarily used by the Frosty Mod Manager, but plugins can extend execution functionality through ExecutionAction classes.
ExecutionAction
Plugins can register execution actions to perform custom operations before or after game launch.Base Class
Properties
PreLaunchAction
- ILogger: Logger instance for output
- PluginManagerType: The manager type (ModManager)
- CancellationToken: Token to check for cancellation
PostLaunchAction
- ILogger: Logger instance for output
- PluginManagerType: The manager type (ModManager)
- CancellationToken: Token to check for cancellation
Registration
Register execution actions using theRegisterExecutionAction attribute:
Example: Anti-Cheat Workaround
Example: Custom Launcher Arguments
Example: File Backup
Example: Discord Rich Presence
FrostyModExecutor Properties
Logger
Important Notes
The PreLaunchAction executes after mods are applied but before the game is launched. The PostLaunchAction executes after the game launch command is issued (not after the game closes).
Common Use Cases
Pre-Launch Actions
- Disable anti-cheat systems
- Create file backups
- Validate mod compatibility
- Configure launch arguments
- Initialize external tools
- Check for updates
Post-Launch Actions
- Re-enable anti-cheat
- Clean up temporary files
- Update Discord presence
- Start monitoring tools
- Initialize overlay applications