Differences

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

--- scripting:reference:debugging [2023/04/24 03:50] – [Ask around] mit
+++ scripting:reference:debugging [2023/04/24 04:06] (current) – mit
@@ Line 5: / Line 5: @@
 ==== 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\\
@@ Line 16: / Line 16: @@
 If you don't have access to the server executable (e.g. if it is being hosted for you on another machine), sending the output to the client will allow you to trace the execution remotely.
-To view the output on the client's LogScriptTrace stream you will need to set up a debug config, as documented [[debugging:debugconfig|here]].
+To view the output on the client's LogScriptTrace stream you will need to set up a [[debugging:debugconfig|debug config]].
 === Script Trace Example ===