User Tools

Site Tools


scripting:reference:debugging

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revisionPrevious revision
Next revision
Previous revision
scripting:reference:debugging [2023/04/24 08:50] mitscripting:reference:debugging [2025/05/28 18:58] (current) – external edit 127.0.0.1
Line 5: Line 5:
 ==== Script Trace ==== ==== Script Trace ====
  
-Use the command ''*scripttrace [mode]'' to activate the script trace functionality. When this is on, as the server runs through each line of script code it will print out what its doing. Sometimes this is useful just to confirm which lines of script are running (e.g. to confirm that you are actually triggering the event you thought you were triggering). Sometimes the script trace will also show when a line fails to execute because its not formatted correctly (or etc).+Use the command ''*scripttrace [mode]'' to activate the script trace functionality. When this is on, as the server runs through each line of script code it will print out what its doing. Sometimes this is useful just to confirm which lines of script are running (e.g. to confirm that you are actually triggering the event you thought you were triggering). Sometimes the script trace will also show when a line fails to execute because its not formatted correctly (or etc). Note that the script trace is automatically turned off when you leave the world.
  
 The mode for script-trace determines where the trace output is sent\\ The mode for script-trace determines where the trace output is sent\\
scripting/reference/debugging.1682326236.txt.gz · Last modified: (external edit)