Alright so what is Skript? Skript allows you to create custom commands and many more things, it offers many things to make and it will severely improve your server.

Okay so how do we add script files? Firstly you need the Skript plugin, once you got that, head to https://playerservers.com/dashboard/filemanager then click on the "plugins" folders and then click on "Skript" folder, once your there, head to "scripts" folder and then you will find a bunch of .sk files. You can check them out if you'd like! Once you made a skript as shown in Basic Events or Registering Commands, type /sk reload (skript file name) to reload the skript file! You can play around with many things to learn more about skript. It will also send warnings and errors about your skript if you have done anything wrong. It is really handy when it comes to making some hard skripts or some big skripts.

Alright so we learned how to register script files, now lets move to events. Firstly, what are events? Events is when something happens in game like if a player's hunger changes or if a mob spawns, I will be showing you some events that can become useful.

I will be showing you the "On Break" event and the "On Place" event, it's pretty self explanatory, it just means when you break a block or place a block. Here is how the code looks like:

on break: # Registers the on break event, Also the hashtag means comments in skript and will be ignored.
    cancel event # Cancels the event which means it will stop the player from breaking any type of blocks which is really cool.

Before we get any further, lets talk about indenting, indenting pretty much means spacing things out. You mostly want to indent when there is a semi colon, so like you can see the on break event, it has a semi colon and you indent after that, I mostly indent with 1 tab which is 4 spaces. (Tabs don't work in cubedcraft editor, you can use some kind of editor like parser.skunity.com it shows you any errors although it does sometimes break).

Now lets talk about the on place event.

on place: # Registers the on place event.
    if event-block is dirt: # It checks if the block is dirt, event-block basically means the placed block. The code basically means "if the placed block is dirt, then do this".
        send "You placed dirt!" to player # This will send "You placed dirt!" to the player, so in chat it will say "You placed dirt!"

You can find MANY more events in https://skripthub.net/docs once you get there, click on the "events" and click on "Skript" in the left side.

Now that we have talked about events, let's learn how we can register some custom commands, let's start off with sending a "Hello" text, here is how you register commands:

command /test: # The command name, you can specify it whatever you would like.
    aliases: /test2 # Here you can define aliases which basically means you can execute this command with /test2 and /test, very handy and this is optional.
    permission: test.usage # You can specify whatever permission you would like in here, so if the player has permission "test.usage" they can execute this command. This is optional
    permission message: No Perms! # Right here this will send "No Perms!" in chat only for the player if they don't have the "test.usage" permission. This is also optional.
    trigger: # You must add a trigger which basically means the code will trigger after this line.
        send "Hello" to player # This is the line after trigger, it sends a "Hello" message only to the player in chat once they execute /test or /test2, you can do /test2 because we defined it.

Lets try a more useful command, like /broadcast which will send a message to everyone in the server.

command /broadcast [<text>]: # This is the command. [<text>] means an argument which you can do like: "/broadcast Hello!" instead of just /broadcast. We'll talk more about them later.
    aliases: /bc # This is the aliases, so you can execute this command with /bc and /broadcast. (Warning: Essentials will override /bc if you have it installed).
    permission: cmd.broadcast # This will register the permission to where only the player with the permission "cmd.broadcast" can use this command.
    permission message: Sorry! But you don't have permission. # This will send the message in chat if they do not have the permission "cmd.broadcast".
    trigger: # If your registering command it must have a trigger which will trigger the code after this line.
        send "Broadcast: %arg-1%" to all players # Now this is where arguments come into place. This will send "Broadcast: (specified argument)" to everyone in the server.

You can use arguments in skript for many different things, like you see above, %arg-1% just means the first specified argument, you can specify more arguments like:
command /argument [<text>] [<number>]: # First Argument: [<text>], Second Argument [<number>] etc etc.
This will specify a text and a number argument which means you can specify a number in the second argument, so if you want to broadcast the second argument (the [<number>]) it will be %arg-2% which is the second argument as you can see. Don't get confused when you see them, you can specify arguments whatever you like. For example:
command /argument2 [<number>] [<string>]: # This will specify the [<number>] argument which is %arg-1% and the second argument is [<string>]. A string is just basically some text that you have written.

Back to our broadcast command:

command /broadcast [<text>]:
    aliases: /bc
    permission: cmd.broadcast
    permission message: Sorry! but you don't have permission.
    trigger:
        send "Broadcast: %arg-1%" to all players

Once you write /broadcast Hello! it will send "Broadcast: Hello!" in chat. If we do not have the [<text>] we cannot do /broadcast Hello and will send an error that %arg-1% does not exist once you reload the skript.</text></text></string></number></string></number></number></number></text></number></text></text></text>