# Do you ever create a running debug log for your game? **URL:** https://forum.kirupa.com/t/do-you-ever-create-a-running-debug-log-for-your-game/327133 **Category:** flash **Created:** [February 7, 2012, 10:59pm UTC](https://forum.kirupa.com/t/do-you-ever-create-a-running-debug-log-for-your-game/327133 "2012-02-07T22:59:20Z") **Posts on this page:** 1 **Page:** 1
### Author: ![tbo](https://avatars.discourse-cdn.com/v4/letter/t/7feea3/32.png) [@tbo](https://forum.kirupa.com/u/tbo) #### Post date: [February 7, 2012, 10:59pm UTC](https://forum.kirupa.com/t/do-you-ever-create-a-running-debug-log-for-your-game/327133/1 "2012-02-07T22:59:20Z")
I have trace statements all over that I may or may not comment out for debugging purposes, once I am done working on some segment, I kind of forget about it and hope I cleaned up after myself or did a decent job. Does anyone ever write to a log or .txt to trace the entire game game path, with details such as: _-init -game menu entered \*\* …waiting_\* -instructions open 3 buttons created \*_…waiting_ - button #2 selected closing screen remove all children 2 of 3 buttons are nulled, 3rd button save for later use -instructions closed -start play level1, -punch character…whatever\* Is this ever done for a debugging workflow? I feel like its a way I could have written notes to myself instead of re-learning some code that I forgot about any might have hacked together at the time.