Debug messages and logging.

[IanWitham]

I think it would be easier to see what's going on behind the scenes with liberally scattered debug statements, as per this blog post.

The messages could be routed to a log file or to the terminal, but I think it would be a nice touch if they were routed to an in game HUD which could be brought up with, for example, the tilde key. What do you think?

[kcunning]

I like this, and I've been thinking seriously about this. I needed to add a messages screen anyway. Here are some other things I wanted to add:

• Coords for each of the blocks in an overlay
• Numbers on each of the monsters, so it's easier to follow them around.
• Specific rolls during combat
• Hit points remaining for a monster

[Technohazard]

I have something similar in a module called 'myDebug' - it's not perfect, but it tracks error messages, and renders to a HUD.

https://github.com/Technohazard/Odd-Engine/blob/master/myDebug.py

I usually add two members to every object, errorQueue and isError. If there are any errors / messages in an object, I call self.errorQueue.append and set self.isError = True. After updating an object, check to see if object.isError == True and copy the list from object.errorQueue to the Debug window.

[kcunning]

I like that! I might have to use that (with credit, of course :) )