Difference between revisions of "Script Debugging"

From SphereWiki
Jump to: navigation, search
(Example 1)
(Example 1)
Line 9: Line 9:
 
This is a great example from MalucoBeleza that illustrates the kind concept of logging out your results to the console for further insight into what objects a trigger is referencing  
 
This is a great example from MalucoBeleza that illustrates the kind concept of logging out your results to the console for further insight into what objects a trigger is referencing  
  
The trigger in this example is [@kill]
+
The trigger in this example is [[@Kill]] || Fires when the character kills another character.
  
 
I.SAY My name is <I.NAME>!
 
I.SAY My name is <I.NAME>!

Revision as of 16:09, 18 August 2022

So you've got a problem with a script and you don't know where to turn? Or everyone you've spoken to doesn't have the answers you seek? You're about to start pulling out your hair, you feel alone and lost, and no one can seem to help you. Well you're about to help yourself! Let's talk about debugging your script


Examples

We'll go through some examples here to explain how one could get helpful information that will lead them to their solutions

Example 1

This is a great example from MalucoBeleza that illustrates the kind concept of logging out your results to the console for further insight into what objects a trigger is referencing

The trigger in this example is @Kill || Fires when the character kills another character.

I.SAY My name is <I.NAME>! SRC.SAY My name is <SRC.NAME>! SAY My name is <NAME>!

When dealing with a trigger that is new to you... its essencial to check the wiki and do tests like this:

ON=@Kill

 SERV.LOG NAME: <NAME>
 SERV.LOG I.NAME: <I.NAME>
 SERV.LOG SRC.NAME: <SRC.NAME>
 SERV.LOG ARGO.NAME: <ARGO.NAME>
 SERV.LOG <NAME> (<UID>) HAVE JUST KILLED <ARGO.NAME> (<ARGO>)