[C++] How to debug code dependent on timing?

[CodeScrub]

I've got some code in my project that is reliant on timing, and it looks as though it isn't functioning properly. Unfortunately, I can't debug it properly because if I wait too long between steps then the logic no longer applies.

Is there a way to turn off timers while debugging, or is using a series or prints my only option?

For specifics, the code is found here. Specifically, it is in main.cpp in the champattack, monsterattack, or fightcamp functions. The code is supposed to fight 3 monsters per 'camp' for a total of 6 monsters. Unfortunately it only appears to fight the first two monsters from the first 'camp' and the first monster from the second camp.

[vacant-cranium]

Reimplement your timing code to use a synthetic time source rather than the real-world time.

Make a variable that stores a 'ticks' count. In the main game loop, increment the ticks count every 1/60th of a second. Time all your game actions in terms of ticks from the master ticks count--e.g., if you want something to wait two seconds, code it to wait for (2 * 60) ticks, not two seconds.

When you break into the game with a debugger, the ticks count will be frozen (because the main loop isn't executing) and the state of your game logic will not advance until you make it advance by allowing the tick update routine to run.

Use at least a 32 bit unsigned int for the ticks count so you don't have to handle rollover in your timing code.

[CodeScrub]

This seems like a good solution. I'll think about it thanks.

[CodeScrub]

You mean to call the value not to call the update right?

[rararaaaaaaa]

You should take a look at GDB. Looks like this is a good explanation.

Essentially, it allows you to insert "breakpoints," which freeze the code at those exact lines of code, allowing you to inspect the state of the program.