Debugging: Difference between revisions
(Created page with "There are mechanisms intended to help debug the game. ==Printing to the console== The game has an integrated function which you can use to debug output <syntaxhighlight lang="javascript"> GameConsole.print("String", 1); </syntaxhighlight> Passing the 1 as a parameter, allows you to see the output, when you press F1, while the game is open. ==Setting Debug Log Levels== The Commander_Wars.ini file includes options to output more debug data into the game's console. By...") |
No edit summary |
||
| Line 14: | Line 14: | ||
==Setting Debug Log Levels== | ==Setting Debug Log Levels== | ||
The Commander_Wars.ini file includes options to output more debug data into the game's console. By setting LogActions to true, you can get more detailed information about the running functions in the game. | The Commander_Wars.ini file includes options to output more debug data into the game's console. By setting LogActions to true, you can get more detailed information about the running functions in the game. | ||
[[Category:Modding tutorials]] | |||
Revision as of 03:19, 19 August 2022
There are mechanisms intended to help debug the game.
Printing to the console
The game has an integrated function which you can use to debug output
GameConsole.print("String", 1);
Passing the 1 as a parameter, allows you to see the output, when you press F1, while the game is open.
Setting Debug Log Levels
The Commander_Wars.ini file includes options to output more debug data into the game's console. By setting LogActions to true, you can get more detailed information about the running functions in the game.