Denizen Script Language Explanations

Language Explanations explain components of Denizen in a more direct and technical way than The Beginner's Guide.

Showing 1 out of 81 language explanations...
Name/denizen debug command
DescriptionUsing the /denizen debug command interfaces with Denizen's debugger to allow control over debug messages.

To enable debugging mode, simply type '/denizen debug'.
While debug is enabled, all debuggable scripts, and any invoked actions, will output information to the console as they are executed.
By default, all scripts are debuggable while the debugger is enabled.
To disable a script specifically from debugging, simply add the 'debug:' node with a value of 'false' to your script container.
This is typically used to silence particularly spammy scripts. Any kind of script container can be silenced using this method.

To stop debugging, simply type the '/denizen debug' command again.
This must be used without any additional options. A message will be sent to show the current status of the debugger.

Note: you should almost NEVER disable debug entirely. Instead, always disable it on a per-script basis.
If debug is globally disabled, that will hide important error messages, not just normal debug output.

There are also several options to further help debugging. To use an option, simply attach them to the /denizen debug command.
One option, or multiple options can be used. For example: /denizen debug -sbi

'-c' enables/disables color. This is sometimes useful when debugging with a non-color console.
'-r' enables recording mode. See also: /denizen submit command
'-s' enables/disables stacktraces generated by Denizen. We might ask you to enable this when problems arise.
'-b' enables/disables the ScriptBuilder debug. When enabled, Denizen will show info on script and argument creation. Warning: Can be spammy.
'-n' enables/disables debug trimming. When enabled, messages longer than 1024 characters will be 'snipped'.
'-i' enables/disables source information. When enabled, debug will show where it came from (when possible).
'-p' enables/disables packet debug logging. When enabled, all packets sent to players (from anywhere) will be logged to console.
or, '--pfilter (filter)' to enable packet debug logging with a string contain filter.
'-f' enables/disables showing of future warnings. When enabled, future warnings (such as upcoming deprecations) will be displayed in console logs.
'-e' enables/disables extra output. This will spam more information about various internal things.
'-v' enables/disables advanced ultra-verbose log output. This will *flood* your console super hard.
'-o' enables/disables 'override' mode. This will display all script debug, even when 'debug: false' is set for scripts.
'-l' enables/disables script loading information. When enabled, '/ex reload' will produce a potentially large amount of debug output.
GroupConsole Commands