It seems I'm no more able to open the debug window while playing my map online with other players.
If I try to open the debug window in single player (even while playing it by bnet arcade) it works...
Anyone knows how to fix this? I'm using a simple trigger like that
Game - Player 1 types a chat message containing ".debug", matching Exactly
Debug - Open the trigger debugging window
I seriously hope they didn't remove this feature. I see no reason for doing that.
Just to check, you're running in windowed mode when you do it, right? The debug window can't be opened when you're in fullscreen(I'm not sure about windowed(fullscreen))
Hmm, with the new improved trigger debug window, I think I can understand why it's disabled in multiplayer. Doesn't it allow you to add breakpoints and such? It feels like it could do a lot of potentially bad things.
Sure, they could just disable those features, but I think they might've been too lazy and just decided to disable it entirely in multiplayer.
I hope this will be fixed, otherwise this would be a huge disappointment.
Its very important to be able to analyze performance in multiplayer, because some triggers might scale very differently from others (for example when using player group loops and doing alot of stuff within them), i addition, the most performance issues just show up in multiplayer and most maps are simply designed for multiplayer, so we need a way to monitor them in a realistic environment.
It seems I'm no more able to open the debug window while playing my map online with other players.
If I try to open the debug window in single player (even while playing it by bnet arcade) it works...
Anyone knows how to fix this? I'm using a simple trigger like that
Game - Player 1 types a chat message containing ".debug", matching Exactly
Debug - Open the trigger debugging window
Didn't they disable the debugger for online games because people cheated by looking at variable values?
There's also a built-in chat command to show the debug window: TrigDebug.
@Tolkfan: Go
I suppose they disabled the command but if I did a trigger to show the window why should blizz disable this feature :|
I seriously hope they didn't remove this feature. I see no reason for doing that.
Just to check, you're running in windowed mode when you do it, right? The debug window can't be opened when you're in fullscreen(I'm not sure about windowed(fullscreen))
@Siretu: Go
Yep, I did it in windowed mode (not fulscreen) and it worked only when I was playing alone.
Can anyone try this on a multiplayer arcade map plz?
Hmm, with the new improved trigger debug window, I think I can understand why it's disabled in multiplayer. Doesn't it allow you to add breakpoints and such? It feels like it could do a lot of potentially bad things.
Sure, they could just disable those features, but I think they might've been too lazy and just decided to disable it entirely in multiplayer.
Try to report it on the official US beta forums.
I hope this will be fixed, otherwise this would be a huge disappointment. Its very important to be able to analyze performance in multiplayer, because some triggers might scale very differently from others (for example when using player group loops and doing alot of stuff within them), i addition, the most performance issues just show up in multiplayer and most maps are simply designed for multiplayer, so we need a way to monitor them in a realistic environment.
I don't know why but today I tried again and it worked even with more players... kinda weird :|
Glad to hear that they didnt remove this feature.
Did you test it again since?