After completing Michael Berlyn's Suspended, a player is given a special command that allows configuration of the main game- moving robots here and there, changing the timer, etc. I heard about this feature many years before I actually beat Suspended. At the time, it sounded like overkill for a game that I had bashed my head against (although in hindsight, it's really not the Herculean effort I thought it was).
I have to admit that, having beaten the game and finally being familiar with how things fit together, the extra challenge mode seemed like a cool idea. Wow, a player could really make this game as hard or easy as they want to; I could see a fun optimization puzzle emerging. I have to admit that I never actually played much with this extra mode, but it was cool to see and finally understand.
I've pondered nice ways to provide a similar experience for players, and the easiest answer I came up with was to give the player a magic word when the game is completed that turns on debugging mode. They'd be able to look at the object tree, move objects or the player around, or even control how daemons run. I thought this would be a fun way to share the innards of the game with the player; for some reason, having game source available doesn't provide the same thrill unless it's, say, in Hugo and I'm applying new Roodylib functionality to it or something for my own curiosity.
Today's code sample supplies this magic word debugging system.
Now I just need to write a game that players would want to dig into!