Skript is a free, open-source plugin for Paper servers that turns readable lines such as on join: into working commands, events and game mechanics. This site is an independent guide to getting it safely, installing it, and writing scripts that hold up on a live server.
A scripting language for Minecraft servers that reads close to English. You describe what should happen and when, and Skript turns it into server behaviour.
Start with the beginner guideWriting a Bukkit or Paper plugin normally means learning Java, setting up a build tool, compiling a jar and restarting the server for every change. Skript was started by Njol to remove that barrier, was carried forward by Mirreski, and is now maintained by the SkriptLang team on GitHub. The goal has stayed the same: let server owners add their own features without becoming Java developers first.
You write plain text files ending in .sk and place them in plugins/Skript/scripts/. When the server starts, or when you run /sk reload, Skript parses each file, matches every line against its library of known syntax, and registers the result as event listeners, commands and timed tasks. If a line cannot be understood, Skript tells you the file and line number instead of silently failing.
Server owners who want custom commands, join messages, rewards, small economies or minigame rules; staff who need quick tools; and learners who want a gentle first step into programming logic. It also suits Java developers who want to sketch an idea in minutes before committing to a full plugin.
If you are building a large network feature with heavy per-tick logic, complex data models or strict performance budgets, a compiled Java plugin will usually serve you better. Skript is not a replacement for well-designed plugins that already solve a problem; it is the glue and the custom layer around them.
The same /heal command, written both ways. The Java version is not hard for a developer, but it needs a project, a build and a server restart. The Skript version is edited and reloaded live.
SkriptPlugincommand /heal:
permission: demo.heal
trigger:
heal player
send "&aHealed!"getCommand("heal").setExecutor((s, c, l, a) -> {
if (!(s instanceof Player p)) return false;
if (!p.hasPermission("demo.heal")) return true;
p.setHealth(p.getAttribute(Attribute.MAX_HEALTH).getValue());
p.sendMessage("Healed!");
return true;
}); // plus plugin.yml, a build and a restartTreat Skript as the fastest way to get a server idea into players' hands, then measure. Most community servers never outgrow it for commands, messages and light game rules. When a script starts running on every tick or every movement, that is the signal to optimise it or move that one piece to Java.
Nine capabilities that cover most of what server owners reach for, and the practical benefit of each.
Lines like "give player 1 diamond" do exactly what they say. Indentation groups the steps, so a script reads top to bottom like a checklist.
on first join:
give player 16 bread
give player a stone sword
send "&aThanks for joining, %player%!"
on break of diamond ore:
send "&bLucky find!" to playerStaff can read and adjust scripts without a developer on call.
React to joins, deaths, block breaks, chat, damage, respawns and dozens more events with a single header line.
Server rules happen automatically, every time.
Define commands with arguments, permissions, aliases and cooldowns in the command header.
Replace small single-purpose plugins with a few lines.
Global variables save to disk by default, so balances and stats survive restarts.
Track coins, kills or homes without a database.
if, else if, else, loops and functions cover the logic most server features need.
Build real rules, not just fixed messages.
Run code every few minutes, after a delay, or at a set time with every and wait.
Broadcasts, rewards and resets on a timer.
Addons such as SkBee and skript-gui add syntax for menus, NBT, scoreboards and more.
Grow into advanced features when you need them.
Edit a file, run /sk reload, test in game. No compiler, no restart.
Try an idea with players the same afternoon.
Combine events, items and variables into bounties, kits, parkour checkpoints or arena rules.
Give your server features players cannot find elsewhere.
The path every script takes from your text editor to a player's screen.
Plain text in any editor
In plugins/Skript/scripts
Errors list the line number
A join, a command, a timer
Through the Paper API
Message, item, teleport
Skript itself is light. What matters is the server it runs on. These are practical guidelines for 2.16.2; the release notes are the final word for each version.
| Component | Minimum | Recommended |
|---|---|---|
| Server software | Paper 1.21.4 to 26.2 | Latest stable Paper build for your Minecraft version |
| Java | Java 21 for Paper 1.21.x | Java 25 required by Paper 26.x |
| RAM | Whatever your server already needs Skript adds little on its own | Headroom for variables and addons large variable files load into memory |
| CPU | Any CPU that runs Paper well | Strong single-thread speed most script work runs on the main thread |
| Disk | A few MB for the jar and scripts | Room for variable backups over time |
| Network | None beyond the server itself | Optional: update checks reach GitHub |
Spigot and CraftBukkit are not supported by current Skript releases. If you run Spigot, either switch to Paper or check the release notes for the last version that supported it.
Skript is free. The only place you need is the official SkriptLang releases page on GitHub, where every version is published with its changelog.
We do not host or mirror the jar. Files from re-upload sites can be outdated or modified, so always take Skript from the project itself. More detail on the download page.
The same process works on a home PC, a VPS or a hosting panel. Budget about ten minutes.
Get Skript-2.16.2.jar (or the newest file) from the official releases page.
Shut the server down cleanly with stop so worlds and data save.
It sits next to your Paper jar. On a host panel, use the file manager or SFTP.
Place the Skript jar directly in plugins/, not in a subfolder. Remove any older Skript jar first.
Skript creates plugins/Skript/ with its config, language files and a scripts folder.
Run /sk info or /plugins. Skript should be listed in green.
Make plugins/Skript/scripts/hello.sk with this content:
command /hello:
trigger:
send "&aSkript is working!" to playerRun /sk reload hello, then type /hello in game.
Real snippets at three levels. Copy one into a .sk file, reload, and try it.
on join:
send "&aWelcome, %player%!" to playerA trigger line ends in a colon; everything indented under it runs when the event happens.
command /discord:
trigger:
send "&bJoin us: discord.gg/yourserver"Commands can carry permissions and cooldowns right in the header.
on death of player:
attacker is a player
add 25 to {coins::%attacker's uuid%}
send "&e+25 coins" to attackerGlobal variables in braces persist; the condition stops the rest of the trigger when it fails.
every 10 minutes:
loop all players:
give loop-player 1 breadloop-player refers to the player in the current loop pass.
function reward(p: player, amount: number):
add {_amount} to {coins::%{_p}'s uuid%}
send "&a+%{_amount}% coins" to {_p}Functions keep logic in one place so several scripts can call it.
options:
prefix: &8[&6Shop&8]
command /shop:
trigger:
send "{@prefix} &7Opening soon."Options are replaced at parse time, handy for prefixes and settings.
Skript follows a release model that supports roughly the last 18 months of Minecraft versions. Statuses below describe Skript 2.16.2.
| Platform | Status | Notes |
|---|---|---|
| Paper 1.21.4 to 26.2 | Supported | The platform Skript is built and tested for. |
| Older Paper versions | Check documentation | Use an older Skript release that lists your version in its notes. |
| Paper forks (e.g. Purpur) | Partial | Often work because they keep Paper's API, but are not the tested target. |
| Spigot / CraftBukkit | Not supported | Current releases require Paper. |
| Folia | Check documentation | Folia's threading model differs from Paper; confirm support before relying on it. |
| Java 21 / 25 | Supported | Match the Java version your Paper build needs. |
| Menus, NBT, databases | Requires addon | Covered by addons such as skript-gui, SkBee and skript-db. |
| Velocity / BungeeCord proxy | Not applicable | Install Skript on each backend server, not on the proxy. |
An honest view, so you can decide whether Skript fits your server.
Six common situations where Skript earns its place.
Replace three small plugins with one readable file you control.
Scenario: A survival server adds /spawn, a join kit and a daily reward without new jars.
Prototype a mechanic before writing the Java version.
Scenario: A dev tests a bounty system with players for a week, then ports the parts that need speed.
Learn events, variables, conditions and loops with instant feedback.
Scenario: A student builds a quiz command and sees each change in game seconds later.
Add personal touches to a server for friends.
Scenario: A group adds death counters and a /rules command to their private world.
Build challenge rules for videos and streams.
Scenario: A creator scripts "every 5 minutes, a random item" for a challenge series.
Give staff tools without handing out console access.
Scenario: Moderators get /report and a staff chat, all in one script.
What working with Skript actually looks like, from the file tree to the console.
Each fix follows the same pattern: likely cause, the change to make, and how to confirm it worked.
Skript runs with the same access as any plugin, so a script can do anything a plugin can. That is useful, and it is why sources matter.
Only download Skript from the official GitHub releases. Read every script you install from a forum or Discord before it goes on a live server, looking for commands that op players, run console commands, or send data to outside services. Addons extend what scripts can reach, so install the ones you actually use, from their official pages.
Keep permissions explicit on every command, test changes on a copy of your server, and back up plugins/Skript/ including variables.csv before updates. We cannot vouch for any third-party file, and we never claim a download is malware-free.
permission: lineexecute console command linesOther ways to customise a server, and when each makes more sense.
| Solution | Difficulty | Programming knowledge | Best for |
|---|---|---|---|
| Skript | Low | None to start | Commands, events and light game rules, written fast |
| Java plugin (Paper API) | High | Java, build tools | Large systems and performance-critical features |
| Denizen | Medium | Some scripting | Complex NPC behaviour and scripted interactions |
| Vanilla datapacks | Medium | mcfunction commands | Changes that must work without plugins |
| Kotlin plugin | High | Kotlin, build tools | Developers who prefer Kotlin over Java |
The points that come up again and again when people decide whether to adopt Skript. These are recurring themes, not quoted reviews.
Being able to change a line and reload without restarting is the reason many owners start with Skript and stay.
Non-developers on a team can follow a script and make small changes safely.
Fine for most servers; busy networks report needing care with per-tick logic and huge variable sets.
Quick answers. The full FAQ covers installation, compatibility, security and development.
Yes. Skript is open source under the GPL-3.0 licence and every release is free on the SkriptLang GitHub page. Some addons and paid script packs exist, but Skript itself costs nothing. Be wary of any site asking you to pay for or unlock the core plugin.
No. Skript was created so server owners could add features without Java. You write readable lines in .sk files. Knowing basic logic such as conditions and loops helps, and you pick that up quickly by editing working examples.
Current releases require Paper. Skript 2.16.2 supports Paper 1.21.4 to 26.2. If you run Spigot, the simplest path is switching to Paper, which can usually load your existing worlds and plugins.
Save scripts as .sk files inside plugins/Skript/scripts/. Subfolders are allowed. Files whose names start with a hyphen are ignored, which is a handy way to disable a script without deleting it.
Run /sk reload followed by the script name, for example /sk reload welcome. Use /sk reload scripts to reload every script. Avoid the server-wide /reload command, which can break plugins.
Not by default. Most lag comes from scripts that do heavy work on every tick or every player movement. Event-driven scripts with sensible timers run comfortably on busy servers. Profile first, then optimise the hot spots.
Step-by-step articles for every stage, from first install to performance tuning.
Measure first, then fix the patterns that cause most Skript lag: per-tick loops, busy events and runaway variables.
Ten short, working scripts to copy, reload and change: join kits, timers, announcements, bounties and more.
Read Skript errors properly, then fix the parse, indentation, loading and runtime problems that catch most people.
Workflow, performance, reach and long-term maintenance compared, with the same command written both ways.
Global, local, list and memory-only variables, how they are saved, and how to store player data that survives name changes.
Download Skript from the official source, follow the install guide, and have a working command before your coffee cools.
