Hey man
Thanks for this debugger. its simple but very useful.
I came across a pretty big bug when I added this to my map.
The debugger itself was working and logged all the events... but it caused all the triggers I added it to become unstable
(they were previously working without any issue)
Whatever triggers i added the action "Tell Dr. Debug" the rest of the trigger seemed to be ignored...
(but it was random... sometimes it would do the rest and sometimes it wouldn't...)
As soon as we disabled Dr.Debugger, everything is working again.
I'm not sure if you know what would cause this.

Vicboy AuthorIntro
My banks weren't working. I've read the triggers a hundred times and still found it logically sound. No errors were popping out so I started to assume Blizzard had glitches within its editor. Boy, was I wrong.
It wasn't easy to detect the source of the bug mainly because it's all in the backstage of the game. It's not a process you see while playing your game. And you don't know what values are being outputted. You don't know if a certain action was run or left out.
From my experience, single player debugging is like cleaning up the map. You find this and that bug, then you simply fix it.
Multiplayer debugging is a whole new thing. You're not just a janitor, you'll also have to be a detective.
Then I thought, if I could see what was happening in the backstage, I'd probably figure out the bug, rather than trying to fix something blindly. (Kind of like banging the TV until it worked rather than opening it up to fix it)
So, I introduce to you, the mapmaker's latest weapon against debugging:
Dr. Debug
It improved my debugging and detecting experience... By a long shot.
My banks for my game is now working 100%, so stats are always saving and saving correctly. I thought my logic in triggering was sound, but Dr. Debug proved me wrong several times.
I think this screenshot of a multiplayer game will say how exactly it works:
You only need to use two actions to utilize Dr. Debug.
Hire Dr. Debug to create all the necessary components of Dr. Debug and Tell Dr. Debug which contains a string input/parameter for you to describe what happened in trigger.
Examples:
It's pretty flexible, in my opinion.
You could also have to describe what is happening and what values are being played around, step by step.
Now aside from its main feature which is to report what is happening, it's also a pretty convenient tool.
IS CAPABLE OF
Logging and reporting at real time.
Opening and hiding at command.
Moving the window around.
Changing size.
Extracting the report.
WORKS BEST ON
Malfunctioning triggers that do not display an error.
Player dependent bugs.
Non-visual triggers.
LEARN THE LIMITATIONS
The tool was initially catered for me only until now. Here is a list of things you must be aware of until later updates address it://<<<139905690398664>>> 1. You can only input 999 string variables until it errors. It is currently NOT recommended for constant usage during public games as it will bug up after it passes the 999th variable.
2. It cannot use Text values, so player names in particular CANNOT be used as well as the other text values.
I assume everyone will have a work around for these?
Download here
Triggers not working properly? Get a check up from Dr. Debug!