MillScript's configuration is growing increasingly more complicated as time goes by. MillScript now has built-in configuration files, a user (or global) configuration file, a website specific configuration file and an optional package configuration file.
Each of these files can be used to configure a slightly different part of a script. Although it might sound quite daunting, each configuration file can only alter a logical part of the script, as follows:
This file can contain any of the available MillScript configuration directives. It is responsible for configuring the MillScript engine for the duration of a script run.
The AddFunction directive adds a function to the
millscript.main package.
This file can only contain the AddFunction function at
the moment. This may change in the future, but at the moment it
doesn't make sense to add a loader or entity just for one pacakge.