How to install Skript on a Minecraft server

An eight-step walkthrough for self-hosted and panel-hosted Paper servers, ending with a working test command.

Before you begin

You need access to the server files (local folder, SFTP or a hosting panel), permission to stop and start the server, and about ten minutes. Skript 2.16.2 runs on Paper 1.21.4 to 26.2.

Spigot servers

Current Skript releases do not run on Spigot or CraftBukkit. Switch to Paper first; it loads most Spigot plugins and existing worlds.

Step 1: Check server software and Java

Type version in the console. The output names the server software and Minecraft version. Then confirm the Java version the server starts with:

Terminal
$ java -version

Paper 1.21.x needs Java 21. Paper 26.x needs Java 25. Hosting panels usually expose this as a "Java version" or "Docker image" setting.

Step 2: Download Skript

Open the official releases, check the "Supports" line, and download the .jar from Assets. The download page explains how to tell the official file apart from re-uploads.

Step 3: Stop the server

Run stop in the console or use the panel's stop button. Adding plugins to a running server, or using /reload, can leave plugins half-loaded.

Step 4: Upload the jar

Self-hosted servers

Copy the jar into the plugins folder beside your Paper jar.

Hosting panels and SFTP

Use the panel file manager or an SFTP client to upload into /plugins. Do not unzip the jar, and do not put it in a subfolder.

Remove any older Skript jar so only one remains.

Step 5: Start the server

On first start Skript creates its folder:

plugins/Skript/
plugins/Skript/
  config.sk        # main settings, including variable storage
  lang/            # language files
  scripts/         # your .sk files go here
  variables.csv    # appears once variables are saved

Step 6: Verify the plugin

Run /sk info in game or sk info in the console. It shows the Skript version and documentation links. /plugins should list Skript in green. If not, read the startup log and see troubleshooting.

Step 7: Create a test script

plugins/Skript/scripts/hello.sk
command /hello:
    permission: demo.hello
    trigger:
        send "&aSkript is working, %player%!" to player

Use four spaces for each indentation level. Any plain-text editor works; code editors that show whitespace make indentation easier.

Step 8: Reload and test

Console
> sk reload hello
[Skript] Reloading hello.sk...
[Skript] Successfully reloaded hello.sk.

Type /hello in game. If it replies, the installation is complete.

Useful Skript commands

/sk reload <script> reloads one file, /sk reload scripts reloads all scripts, /sk enable and /sk disable toggle a script, and /sk help lists the rest.

Updating and removing Skript

To update, back up plugins/Skript/, read the release notes and your addons' supported versions, stop the server, replace the jar and start again. Fix any parse errors the console reports. To remove Skript, stop the server and delete the jar; delete plugins/Skript/ too if you no longer need your scripts and saved variables.