Developers

###How it works To simply put it there are some basics build blocks that every mission have to/should contain for it to work.

1. mission.sqf
   The mission.sqf contains all entities in the actual mission.
2. description.ext
   While the description is holding all the settings, it also the one that initializes the functions.

After that there are more advanced things.
The Core folder says how and when everything is executed, while the module folder contains all features.
You may say that each module is a category of scripts for a focused, organized and easy to configure system.
For full list go to modules folder.
If you are interested in creating your own module go ahead and use the example-module.

###Why macros Because they offer a simple and fast way of developing, with them they give us a great way of debugging and keeping things organized without having to change the entire projects.
Editors that's familiar to Macros from CBA's will find this very easy to use.
For people not familiar with this, will be confused however start looking in the example or other modules and it should soon be understandable.

###Debugging This system is easy to use however can not be de/activated in runtime and requires a restart of the script to work.
Enable one of the following levels by copy(without "") and paste it right above #include "scriptComponent.hpp"

"#define DEBUG_MODE_FULL"
"#define DEBUG_MODE_NORMAL"
"#define DEBUG_MODE_MINIMAL"

After that, look inside the .rpt file to find the messages, if you have the external debugger enabled it will also be displayed there.