 |
nostra
Wanderer
Joined: 23 May 2001
Posts: 68
Location: Sweden
|
 Posted: Wed May 14, 2003 12:59 am
What is going on behind the scene...
|
As I started to build more triggers I realized that I somehow lost control on what is going on where.
Indeed, right now one of my triggers is producing a very odd result and I can't find all the sources of this chain reaction.
Is it possible to see what commands (from triggers and variables) that passes along behind the "scene"? :> |
|
|
|
|
MattLofton
GURU
Joined: 23 Dec 2000
Posts: 4834
Location: USA
|
Posted: Wed May 14, 2003 1:01 am
|
quote:
As I started to build more triggers I realized that I somehow lost control on what is going on where.
Indeed, right now one of my triggers is producing a very odd result and I can't find the source from where it comes.
Is it possible to see what commands (from triggers and variables) that passes along behind the "scene"? :>
You can try the debugger, but I find it more comfortable to do it manually (since I debug along the way, there's almost never any large series of code producing hard-to-trace bugs).
li'l shmoe of Dragon's Gate MUD |
|
|
|
|
nostra
Wanderer
Joined: 23 May 2001
Posts: 68
Location: Sweden
|
Posted: Wed May 14, 2003 1:18 am
|
I take your word for it, but this little bug is evading me :>
So, is it possible to see ALL the commands that are triggered through my scripts? I looked at the debug but it didn't roll up the commands as I expected... am I doing something wrong? |
|
|
|
|
Lain
Novice
Joined: 26 Oct 2001
Posts: 38
|
Posted: Wed May 14, 2003 1:47 am
|
In the script parser options in the preferences you can choose to show triggers when they are activated, maybe that would help to finding the problem?
|
|
|
|
|
|
|
|
