Functions Library – Arma 3 Talk
(Created page with "Looking across the CfgFunctions class, there are also those Attributes: headerType, cheatsEnabled that are not referenced here. -Floriangeyer : Those are...") |
(→Explain how and when functions are compiled: new section) |
||
| Line 1: | Line 1: | ||
Looking across the CfgFunctions class, there are also those Attributes: headerType, cheatsEnabled that are not referenced here. -[[User:Floriangeyer|Floriangeyer]] | Looking across the CfgFunctions class, there are also those Attributes: headerType, cheatsEnabled that are not referenced here. -[[User:Floriangeyer|Floriangeyer]] | ||
: Those are system attributes and are used only in special cases. I didn't consider them significant enough to be descibed publicly. -[[User:Str|Str]] ([[User talk:Str|talk]]) 18:10, 28 March 2014 (CET) | : Those are system attributes and are used only in special cases. I didn't consider them significant enough to be descibed publicly. -[[User:Str|Str]] ([[User talk:Str|talk]]) 18:10, 28 March 2014 (CET) | ||
== Explain how and when functions are compiled == | |||
I've talked with plenty of rookies who didn't understand that functions are compiled BEFORE the mission starts / init fields are called, so they were calling their functions using preInit and just exiting if that was the params. | |||
My suggestion is that someone who knows the exact compile steps for functions add that just above "init order". | |||
From my understanding it's goes something like this; | |||
Mission: | |||
In editor: cfgFunctions from description.ext are compiled when mission loaded/previewed/restarted (since you don't have to add recompile flag and don't have to save like with cfgSounds to be read when changed?) | |||
MP: Functions are compiled when "start" is pressed? | |||
Addon: | |||
Functions are compiled when addon is loaded | |||
Revision as of 23:19, 19 November 2014
Looking across the CfgFunctions class, there are also those Attributes: headerType, cheatsEnabled that are not referenced here. -Floriangeyer
- Those are system attributes and are used only in special cases. I didn't consider them significant enough to be descibed publicly. -Str (talk) 18:10, 28 March 2014 (CET)
Explain how and when functions are compiled
I've talked with plenty of rookies who didn't understand that functions are compiled BEFORE the mission starts / init fields are called, so they were calling their functions using preInit and just exiting if that was the params.
My suggestion is that someone who knows the exact compile steps for functions add that just above "init order".
From my understanding it's goes something like this;
Mission: In editor: cfgFunctions from description.ext are compiled when mission loaded/previewed/restarted (since you don't have to add recompile flag and don't have to save like with cfgSounds to be read when changed?) MP: Functions are compiled when "start" is pressed?
Addon: Functions are compiled when addon is loaded