Start here
Open the console or run /sk reload on the problem script and read the first error. Skript names the script and the line. Fix that one first; later errors are often caused by it.
Console
> sk reload shop
[Skript] Reloading shop.sk...
Line 5: (shop.sk)
Can't understand this condition/effect: sendd "&cYou have no diamonds."
[Skript] Encountered 1 error while reloading shop.sk!Common problems and fixes
Each entry lists the likely cause, the fix, and how to confirm it worked.
Skript not loading
- Likely cause
- The server is Spigot or CraftBukkit, the Java version is too old, the Minecraft version is outside the release's range, or there are two Skript jars.
- Fix
- Run Paper, use the Java version Paper requires, pick a Skript release that lists your version, and keep a single jar.
- Verify
- /plugins lists Skript in green and /sk info answers.
Script parse errors
- Likely cause
- A line does not match known syntax: a typo, wrong version syntax, or a missing addon.
- Fix
- Open the file at the reported line and compare it with the documentation for your exact Skript version.
- Verify
- /sk reload <script> finishes with no errors.
Invalid syntax copied from a tutorial
- Likely cause
- The tutorial was written for an older Skript release or assumed an addon.
- Fix
- Check the tutorial date and requirements, then look up each failing line in the current docs.
- Verify
- The script reloads cleanly and the feature works in game.
Plugin dependency errors
- Likely cause
- An addon loaded without Skript, or before a plugin it depends on.
- Fix
- Install Skript and required plugins, then the addon. Remove addons you do not use.
- Verify
- No dependency warnings appear in the startup log.
Version incompatibility
- Likely cause
- Skript or an addon was updated ahead of the other, or Paper moved to a version Skript does not list yet.
- Fix
- Roll back to the last working pair, or wait for releases that support your version.
- Verify
- Startup log shows Skript and addons enabling without warnings.
Java compatibility
- Likely cause
- The server starts on an older Java than Paper needs.
- Fix
- Switch to Java 21 for Paper 1.21.x or Java 25 for Paper 26.x in your host or start script.
- Verify
- java -version reports the expected version and the server boots.
Server startup errors mentioning Skript
- Likely cause
- A corrupted jar, a broken config.sk, or a damaged variables file.
- Fix
- Re-download the jar from GitHub. Rename config.sk to let Skript regenerate it. Restore variables.csv from a backup if it is damaged.
- Verify
- Skript enables and reports how many scripts and variables it loaded.
Scripts not triggering
- Likely cause
- The file is disabled with a hyphen, the event name is wrong, or a condition stops the trigger.
- Fix
- Check the file name and location, then add a temporary broadcast line to see how far the trigger runs.
- Verify
- The debug broadcast appears when you perform the action.
Addon conflicts
- Likely cause
- Two addons register similar syntax, or one is incompatible with your Skript version.
- Fix
- Remove the most recently added addon, restart, and test. Re-add addons one at a time.
- Verify
- The conflicting error stops appearing after the change.
Performance problems
- Likely cause
- Work running every tick, on every movement, or loops over huge variable lists.
- Fix
- Profile with spark, move logic to specific events, lengthen timers and bound lists.
- Verify
- MSPT drops and the trigger no longer leads the profile.
A debugging routine that works
- Reproduce the problem on purpose and note exactly what you did.
- Read the console from the first error or warning.
- Change one thing, reload just that script, and test again.
- Add
broadcast "debug: step 1"lines to see which parts of a trigger run. - Remove debug lines once it works, and keep a backup of the working version.
Still stuck?
Compare your setup on a clean test server with only Paper and Skript installed. If valid syntax from the documentation still fails, search the Skript issue tracker and report your Skript, Paper and Java versions with a minimal example. For detailed walkthroughs, read how to fix common Skript errors and optimising performance.