scripting:reference:debugging
Differences
This shows you the differences between two versions of the page.
Both sides previous revisionPrevious revisionNext revision | Previous revision | ||
scripting:reference:debugging [2023/04/24 03:46] – mit | scripting:reference:debugging [2023/04/24 04:06] (current) – mit | ||
---|---|---|---|
Line 5: | Line 5: | ||
==== Script Trace ==== | ==== Script Trace ==== | ||
- | Use the command '' | + | Use the command '' |
The mode for script-trace determines where the trace output is sent\\ | 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. | 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' | + | To view the output on the client' |
=== Script Trace Example === | === Script Trace Example === | ||
Line 54: | Line 54: | ||
==== Ask around ==== | ==== Ask around ==== | ||
- | There are lots of quirks and limitations of the game's custom scripting language, some of which are obscure and largely indefensible :]. Sometimes you'll have to resort | + | There are lots of quirks and limitations of the game's custom scripting language, some of which are obscure and largely indefensible :]. Sometimes you'll have to fall back to the last resort and ask someone to help. If you're signed up for the game's patreon you'll have channels there with other folk who might be able to help. Otherwise try posting about your issue on the game's discussion channels on steam. |
scripting/reference/debugging.1682325979.txt.gz · Last modified: 2023/04/24 03:46 by mit