arma:config_formatting
Differences
This shows you the differences between two versions of the page.
Previous revision | |||
— | arma:config_formatting [2024/08/01 15:51] (current) – links added. snakeman | ||
---|---|---|---|
Line 1: | Line 1: | ||
+ | ====== ArmA 1 Config Formatting ====== | ||
+ | |||
+ | [[https:// | ||
+ | |||
+ | **ArmA 1** aka Armed Assault (ArmA) | ||
+ | |||
+ | **Config Formatting** | ||
+ | |||
+ | Configs can be quite intimidating to newbies and hard to read even for oldschool guys if they are written poorly. There is more addons written with poor format than with good ones, some are so hideous that it makes you just want to cry. | ||
+ | |||
+ | Examples of right and wrong config formatting. | ||
+ | |||
+ | Wrong: | ||
+ | <code cpp> | ||
+ | magazines[] = {" | ||
+ | </ | ||
+ | |||
+ | Right: | ||
+ | <code cpp> | ||
+ | magazines[] = | ||
+ | { | ||
+ | " | ||
+ | " | ||
+ | " | ||
+ | " | ||
+ | }; | ||
+ | </ | ||
+ | |||
+ | As you can see we use TAB intend after each { character and after classes. This makes very easy to read configs. | ||
+ | |||
+ | |||
+ | ====== Notes ====== | ||
+ | |||
+ | For complete newbies; in reality it doesn' | ||
+ | |||
+ | Can you imagine that you actually learn faster to write configs when you write them with proper intend. Weird huh. | ||