Introduction
Configuration files are text files that can be executed using the EXEC command. These files contain a series of console commands that are executed automatically, eliminating the need to enter each command manually. Configuration files are typically stored in the cfg folder. The application recognizes several special configuration files:
- autoexec.cfg
- convars.cfg
- runonce.cfg
Directory Listing:
+ Application Root
+ cfg
- your_config_files.cfg
- MCNLaunchPad.jar
- autoexec.cfg
- convars.cfg
- (runonce.cfg)
The following image shows how to open the application's root folder from within the application:
Alternatively, you can also click on autoexec.cfg; this will open the autoexec-file in your text editor.
File: autoexec.cfg
This special configuration file gets executed every time the system starts. You can run commands in there that need to run on every start-up.
File: convars.cfg
This special configuration file will store non-volatile console variables.
You should not edit this file. This file gets automatically generated every time you exit the application. You can force this during runtime by sending the command DUMPCFG.
File: runonce.cfg
The runonce.cfg file is a special configuration file that is executed only once. If the file exists during application startup, it is executed and then automatically deleted.
This file is commonly used when upgrading or downgrading between application versions, especially when one-time actions must be performed as part of the migration process.
The feature was designed to support post-update tasks that should run only once. Typical use cases include migrating data models to a newer version, updating configuration settings, or performing cleanup operations before the application enters its normal runtime state.