Mod Structure
Before using one of the template creation options, it will probably be an equally important part to familiarize yourself with their contents. First of all, a mod is a folder with a configuration file build.config, which describes the entire process of loading, compiling and building your mod. Let's look at the contents of the entire folder, and first analyze other, but no less important aspects.
Mod Lifecycle
Usually begins before launching the game, at this moment the mod announces its existence to the launcher and performs a list of necessary procedures for the user. Now we will look at the complete cycle from this moment to closing the game, what happens in the mod during various events and how it can affect the gameplay.
Building Scripts
Besides the ability to directly set an executable script, there is often a need to divide the source code into files. As soon as the project starts to contain the first classes, utility functions, and other things that should be separated, working in a single file becomes simply impossible. This is where build files and advanced toolchain settings come to our aid.
Evaluate Context
Defines the space in which all your code is located. It stores the values of variables and constants, functions and transformed classes, and also performs future code interactions with the space.
Integrating Libraries
Implemented from any mod script. Libraries expand the capabilities of the game, or simplify the creation of existing ones. In addition, you can even allocate part of your code to use it as a library; these are regular scripts, the context of which will now be considered.