12-17-2017, 09:40 PM
(This post was last modified: 12-17-2017, 09:41 PM by VinnyVideo.)
A good question. Typically I use Debug Mode to watch a specific variable (whether a global variable or an object's local variable) and see what events cause it to change. For example, suppose I'm making a boss, but the boss can't be defeated for some reason. I might watch the "hp" variable for the boss and see which events cause hp to go down. This helps me narrow down the problem.
Debug Mode also lets you modify variables in game using the Execute Code dialog box. For example, if I'm tinkering with my code in Cheerwine Deluxe 3, I could type "global.debug = 1" into the Execute Code dialog box, and that would enable the game's special debug mode. (global.debug is just a variable I made for testing things in CD3 - it's not something built in to GM.)
Debug Mode also lets you modify variables in game using the Execute Code dialog box. For example, if I'm tinkering with my code in Cheerwine Deluxe 3, I could type "global.debug = 1" into the Execute Code dialog box, and that would enable the game's special debug mode. (global.debug is just a variable I made for testing things in CD3 - it's not something built in to GM.)
Course clear! You got a card.
![[Image: CourseClear.gif]](https://dl.dropbox.com/s/d5mcpm4nmt0gd14/CourseClear.gif)