Why you are here
Debugging is essentially problem-solving. Every programmer must know how to debug.

In this short tutorial, I'll demonstrate ways of debugging your problems in Skript



Debugging
[[ Introduction ]]
Debugging is essentially checking if everything works correctly
for instance, A -> B -> C... -> Z
and if A doesn't show Z, it means that anything could have gone wrong

This tutorial covers console debugging as well as other good practices

[[ Explicitly showing the problem ]]

A bad code here looks like this - source : skUnity Discord
And the person says that this is not working because of named ""
If someone were to debug this, it would take ages. So? you should explicitly show what is wrong

Then, you can see that it works
So lets test more things

it also works

then you start making it longer and longer until you realize
you forgot to add a comma there


[[ Condition checking / Debug messages]]
Your problems most occur when you least expect it. So it is a good idea to check if everything else is working

NOTE: DO NOT USE MESSAGE/SEND INSTEAD OF BROADCAST
here is why:
A simple example is a person arguing that 'on mine' doesn't work

If we want to be sure that 'on mine' doesn't work, we can add debug messages

when they ran the code, it broadcasted

on mine called
{mine} is <none>

that means, {mine} was not set at the first place


For example, let's look at a bad code posted on the skUnity Discord
As you can see, there can be multiple things going wrong

• is {kit.%loop-player%::dwarf} not set?
• is loop-player is sneaking condition working?
• is adding 1 to {dwarf.timer::%loop-player%} working?
  
• ...

So, here is a code with debug messages
They should use lists; other than that,
when they ran the code, it broadcasted
looping player notch

so that means, {kit.%loop-player%::dwarf} is not set


[[ Step checking ]]
The use of Functions allows us to embed multiple actions into one line. Because of this, they are prone to bugs

For example
There are a number of things that can go wrong here
So, split the thing into multiple parts

Add broadcast as much as you like

[[ Examples ]]
Examples are a good way of debugging things

For example
Let's say you want to use metadata but the code is not working
Start from the examples.

If the example was
Then check if the below works in the first place
And, without a doubt, that code doesn't work.
That means you cant just use 2 values on metadata.
That also means you cant read syntax


Debugging Tools
Debugging is tedious, debugging is hard. And programmers want to automate such stuff

[[ List debugging tool ]]
I created a debugging tool for lists.
It helps you inspect the layers of a list with ease

Requires Skript 2.4+

[[ Create your own debugging tool ]]
Sometimes, you might want to create a debugging tool yourself, here is an example
This is a debugging tool I use when scripting things related to GUI

Tips & Tricks
[[ Skript effects ]]
Did you know that you can run Skript™ can run effects on the fly?

go to
Skript/config.sk
turn on

then, in a Minecraft server where you are op, try typing
!send "hello world"
it will say something like

executing 'send "hello world"'
hello world

this feature allows you to run Functions as well
if you are wondering what {block::1} is, just type
!send "%{block::1}%"
without the hassle of going to scripts and putting a command debug for that

more detail can be found here
https://forums.skunity.com/wiki/run-effect/

[[ Debug option ]]
Tired of deleting broadcast every time you fixed the problem only to type it again?
There is an easy way to toggle broadcast on these
to turn it off,
[[ Debug broadcast works but code doesn't ]]

a code from skUnity Discord
The debug "true" gets sent but the line below doesn't.
The person also tested the code outside the function and said it executed the second line

This means one of 2 things are happening
1. the second line expression bugged out for some reason

• a) this is possible if addon developers didn't fully consider or put exception handling on their code. => Check console
• b) this is possible if the expression doesn't work on Functions. => clearly show the code not working, issue a bug report on their respective repositories.

2. the second line effect broke for some reason

• a) this is possible on some Functions, where addon developers didn't fully consider the use of effects inside Functions. => try changing parameters to a fixed global variable. if that works, submit a bug issue on git.
• b) the effect doesn't work in those particular parameters inside the function => change all parameters into global Variables and then test it inside and outside a function
  - i) if the global variable version doesn't work, it means that the object has a problem referencing/serializing the data. => submit a bug on git
  - ii) if the global variable works, test if the parameter version is the same. for example
  
  Code (Text):

  1. # is the object same
  2. command objtest:
  3.     trigger:
  4.         set {global} to <something>
  5.         if {global} = param({global}):
  6.             send "no problems"
  7.         else:
  8.             send "something went wrong"
  9.  
  10. function param(o: object) :: object:
  11.     return {_o}

[[ Flawless Debug ]]
If you are checking a string, don't broadcast the string only
Bad example
Good example
This is because if {_str} is not set(<none>), Skript will not broadcast at all, which might confuse you a lot.
Generally a good practice to add more info when debugging


[[ Recursive things ]]
Using recursive features? Good! you are an above-average programmer. However, you are also putting yourself at a high risk of constantly crashing your server.
Put delays and emergency stops on those Functions

Bad example
Good example
If you are so confident that it will never break, you can safely remove those delays and stops
However, it is crucial when developing


[[ Types ]]
Skript Variables have types. strings, integers(longs), booleans, etc. But there seems to be virtually no way to test the type of the variable, right?

Rezz created a snippet that allows you to inspect the type of a variable. https://forums.skunity.com/threads/rezzs-snippets-things-you-can-do-in-pure-skript-2-2.2471/ <- original link. All credits to Rezz
typeof(<variable>) returns type
- Returns the variable's type, or 'object' if its type isn't declared.
declareUsableTypes(<addon name>, <list of types>)
- Declare all types listed in their user-input form. This function simply calls declareUsableType() on each list item.

declareUsableType(<addon name>, <type in standard user-input form>)
- Declare a usable type. It's important to declare specific types before general types because declaration order is preserved. i.e. A variable of a specific type, like 'player', can also be considered a more general type as well -- 'offline player' in this example. If 'offline player' is declared before 'player', 'player' type Variables will always be considered 'offline players'.

You can check more details and examples on the link

[[ Console ]]
If your code creates errors on console, believe it or not, it's actually a good sign. You can find the problem of your code by reading the error logs

Here are some common bugs and how to fix them

• NullPointer
  - this usually happens when the variable you put inside the function as an argument is not set. Also, see array out of bounds exception
• OutOfBounds
  - this happens when you put 2 values in 1 argument when you are only allowed to put 1. This is not your fault. Skript tries to create lists whenever they see a comma. To fix this problem, add parentheses. ex) func(1, 2, 3) -> func((1), (2), (3))
• TypeError
  - this happens when you have the incorrect type. Some of them are unintuitive. If you get "expected integer but number", add round({_thevariable}) to it. Some other TypeErrors are hard to fix but if you encounter them, please shorten your code so the error can be explicit
  
• IllegalArgument
  - you entered an argument that is out of the range of that function. For example, you cant set slot 100 of an inventory
• StackOverflow
  this is a rare error. but most fall into 2 categories
  - lack of ram: simply give your server more ram
  - recursive function: there is a recursive function in your code that isn't working properly.

Common mistakes
just some common mistakes from people

[[ Color ]]
- bold, italics don't show -> color codes reset Formatting. if you want do disable it, go to the Skript config
- color does not change to Minecraft color doe -> use colored expression
[[ List ]]
- lists don't work properly -> lists are probably not what you think. read above and get listprint
- list keeps deleting after restart -> are you sure you don't have a "clear {list::*}" somewhere
- list is not ordered -> list's indices are not what you think. read above and get listprint
- adding stuff to lists is slow -> adding is slow. use set and Loops instead
[[ Addons ]]
- using skquery, wild Skript, umbaska, skrayfall -> just no
- using Skript-mirror for simple stuff -> why
idk ill add more if i see more

Addition to things
Something is wrong? Want to contribute to this page? PM me on this account with details, I will update it.



Update log
- 2020/1/23 : Created page
- 2020/2/5 : added [ Debug sends but code doesn't work ]
- 2020/2/25 : edited format so it looks better
- 2020/2/29 : added Skript effects tutorial
- 2020/3/1 : added more information
- 2020/5/30 : added common mistakes section