I don't know if anyone else has noticed, but you can use the trigger debugger on other's maps over Bnet. I can see what you people are naming your triggers :P No idea if it's intentional or not. Be warned, it seems to significantly increase lag. How to:
1. Test a map via the editor. Make sure windowed mode and trigger debugger are enabled
2. Quit the map, and login to BNet without closing the sc2 window. the trigger debugger should disappear
3. Create/Join a random game. Wait for it to launch.
Pretty sure I made a post about this like 3 months ago....
The debugger shows everything that it normally shows when testing your own map. Its basically listens to the SC2 script engine. So as long as its running it will always provides the same type of information, regardless of whether your playing somebody else's map over bnet or testing your own map locally.
Dunno about it showing variables.... in the variable tab... I generally only use it when Im trying to see how much activity my triggers are actually generating
Rollback Post to RevisionRollBack
Skype
KageNinpo = SN
My Libraries
DialogLeaderboard & TeamSort
My Projects
SPACEWAR Tribute
Infinite TD
Pretty sure you can see the custom functions as well , The game intreprets everything as script. The GUI triggers if youve ever had an error will pop up the script equivlent of your GUI triggers.
To the game everything is script. SO it will show your custom script functions... The debugger doesnt really show you the code inside of the custom triggers though..... It would be nice if the debugger could show you the code its running line by line though.
edit : found out how, and yeah as above said it LAGS THE SH1T out of EVERYTHING
If you turn off the trigger viewer (so you just have variables) the lag disappears.
(Though this isn't really viable unless you're playing phantom mode or something).
there's a setting to turn off the the trigger viewer? Or do you mean just going to the variables tab. Since doing that doesn't absolve the lag (nor does closing the window)
EDIT figured it out. Call me what you want, but cheating at phantom is fun.
Also, I believe there is an alternate way to use the trigger debugger.
On your shortcut of starcraft 2, right click - properties - at the end of the 'target' field, throw this in.
"-trigdebug" without quotes.
Haven't tried this myself, but I don't see why it wouldn't work.
Edit: Think you need windowed mode (non-fullscreen) too - so add "-displaymode 0" on the end.
there's a setting to turn off the the trigger viewer? Or do you mean just going to the variables tab. Since doing that doesn't absolve the lag (nor does closing the window)
EDIT figured it out. Call me what you want, but cheating at phantom is fun.
I figured it out. Right click the bottom part of the debugger (where the timestamped trigger output goes) and you can de-select a lot of lag inducing elements.
-
View User Profile
-
View Posts
-
Send Message
Curse PremiumI don't know if anyone else has noticed, but you can use the trigger debugger on other's maps over Bnet. I can see what you people are naming your triggers :P No idea if it's intentional or not. Be warned, it seems to significantly increase lag. How to:
1. Test a map via the editor. Make sure windowed mode and trigger debugger are enabled
2. Quit the map, and login to BNet without closing the sc2 window. the trigger debugger should disappear
3. Create/Join a random game. Wait for it to launch.
4. ???
5. Spy on the variables/threads/ect of others
6. Profit
@PirateArcade | I make games | Ask me things on Discord
Yep, used it a few times for fun.
Shame you can't see the content of arrays and structs :P
@WhiskeeGX: Go
Blasphemy, those maps are locked, you are not supposed to see those trigger !!!
Wait a minute ....
You don't, you just see their name :D
Also, people don't understand the difference between Run Trigger and simple action/function calls....
Does it show something in the Variables tab?
Pretty sure I made a post about this like 3 months ago....
The debugger shows everything that it normally shows when testing your own map. Its basically listens to the SC2 script engine. So as long as its running it will always provides the same type of information, regardless of whether your playing somebody else's map over bnet or testing your own map locally.
@SouLCarveRR: Go
Well.. uhmm.. does it show variable values when it's locally used?
I hardly ever use it. I debug my script the old way.
But I think I remember that it didn't show me anything in the variables-tab when I used it once.
Dunno about it showing variables.... in the variable tab... I generally only use it when Im trying to see how much activity my triggers are actually generating
-
View User Profile
-
View Posts
-
Send Message
Curse Premium@s3rius: Go
Yup, you can see variable values. And you can therefore use it see who's phantom/paladin in Phantom mode. 0wned.
However, doing this results in enough lag to make everyone else ragequit, so it's kinda moot. I hate sharing cable internet with my roommates...
@PirateArcade | I make games | Ask me things on Discord
stupid question, how do i get the debugger?
edit : found out how, and yeah as above said it LAGS THE SH1T out of EVERYTHING
My first thought as well :-D
Can you see custom scripted triggers? no?
Pretty sure you can see the custom functions as well , The game intreprets everything as script. The GUI triggers if youve ever had an error will pop up the script equivlent of your GUI triggers.
To the game everything is script. SO it will show your custom script functions... The debugger doesnt really show you the code inside of the custom triggers though..... It would be nice if the debugger could show you the code its running line by line though.
@illidans911: Go
If you turn off the trigger viewer (so you just have variables) the lag disappears.
(Though this isn't really viable unless you're playing phantom mode or something).
-
View User Profile
-
View Posts
-
Send Message
Curse Premium@ihatethisregistration: Go
there's a setting to turn off the the trigger viewer? Or do you mean just going to the variables tab. Since doing that doesn't absolve the lag (nor does closing the window)
EDIT figured it out. Call me what you want, but cheating at phantom is fun.
@PirateArcade | I make games | Ask me things on Discord
Also, I believe there is an alternate way to use the trigger debugger.
On your shortcut of starcraft 2, right click - properties - at the end of the 'target' field, throw this in.
"-trigdebug" without quotes.
Haven't tried this myself, but I don't see why it wouldn't work.
Edit: Think you need windowed mode (non-fullscreen) too - so add "-displaymode 0" on the end.
edit : how? :O
-
View User Profile
-
View Posts
-
Send Message
Curse Premium@illidans911: Go
I figured it out. Right click the bottom part of the debugger (where the timestamped trigger output goes) and you can de-select a lot of lag inducing elements.
People think I am a *god* at phantom
:P
@PirateArcade | I make games | Ask me things on Discord