Skript

Skript for Zed

Write Minecraft server scripts in Zed, with the tooling Skript has never had.

Full language support for Skript — the scripting language Minecraft server owners use to write plugins without writing Java.

Writing Skript has always meant writing it blind. No editor knew the language, so you found your mistakes by uploading the file, watching the console, and doing it again. This extension moves that loop into your editor.

• Stop guessing at syntax. Hover any line for its documentation, pulled from Skript's own database — every effect, condition and expression, with examples and the version it was added in.
• Catch the mistakes before the upload. Indentation Skript would reject, unclosed ### blocks, duplicate declarations, calls to functions that do not exist, deprecated syntax.
• Navigate a real project. Go to definition, find every reference, and rename across every file — including the ones you have not opened.
• Completion that understands context. Only events after on , only conditions inside if , only expressions inside %…%. Patterns insert with a tab stop per slot.
• Your addons, not just core Skript. It reads your server's plugins/ folder and loads syntax for SkBee, skript-reflect, SkQuery and 160+ others — so your addon syntax gets the same hover and completion as everything else.
• Looks right in your theme. No colour is defined anywhere in this extension. It uses the capture names your theme already styles.

Free, MIT licensed, and held to SkriptLang's own repository: ~540 real scripts must parse with zero errors on every change.

Install

1. Install the extension. In Zed, open the command palette (Cmd/Ctrl+Shift+P), run zed: extensions, search for Skript, and click Install. Open any .sk file — that is it. The language server downloads itself the first time you open a Skript file; there is nothing to install by hand.

2. Turn on semantic tokens. You want this. Zed ships with semantic_tokens set to "off", and semantic tokens are what colour Skript's effects, conditions and expressions — which is most of what you actually write. Without this setting the extension works, but a lot of your file stays grey.

Run zed: open settings and add:

{
  "languages": {
    "Skript": { "semantic_tokens": "combined" }
  }
}

On the bundled showcase file the grammar alone colours 90% of visible characters; with semantic tokens it is 97%. Prefer "combined" over "full" — "full" discards what the grammar already knows about strings and variables.

{
  "languages": {
    "Skript": {
      "semantic_tokens": "combined",
      "tab_size": 4,
      "hard_tabs": true,
      "formatter": "language_server",
      "format_on_save": "on"
    }
  }
}

Not published to the registry yet? See installing from source.

What you get

Addons

Most Skript projects run addons, so the server detects them: it finds your plugins/ directory, reads each JAR's manifest, and loads syntax for what is actually installed. SkBee ships only a paper-plugin.yml, which is why the manifest is read rather than the filename.

Nothing to configure if your scripts live under plugins/Skript/scripts/. Otherwise point at the server:

{
  "lsp": {
    "skript-lsp": {
      "initialization_options": {
        "serverPath": "/srv/minecraft/my-server"
      }
    }
  }
}

See docs/addons.md — including what is not supported, and why unknown syntax is never treated as an error.

Settings

All optional, under lsp.skript-lsp.initialization_options:

To use a language server you built or installed yourself:

{ "lsp": { "skript-lsp": { "binary": { "path": "/path/to/skript-lsp" } } } }

{
  "lsp": {
    "discord_presence": {
      "initialization_options": {
        "languages": {
          "skript": {
            "large_image": "{base_icons_url}/zed.png",
            "large_text": "Skript"
          }
        }
      }
    }
  }
}

Themes

No colour is named anywhere in this extension. Highlighting uses capture names your theme already defines, and refinements fall back along their dot-prefixes, so a minimal theme still gets sensible colours rather than none.

Tested against Catppuccin (Mocha and Latte), One Dark, Material Theme Darker and the OLED themes. If something looks wrong in your theme, that is a bug worth reporting. See docs/theming.md to override individual captures.

Three things that are not what you expect

Ordinary statement prose is not coloured by the grammar. Skript has no fixed vocabulary — every effect, condition and expression is a pattern registered at runtime by Skript or an addon, and nothing lexical distinguishes set {_x} to 5 from player is op. The grammar therefore colours only what is structurally certain, and the language server classifies the rest via semantic tokens. This is why step 2 of the install matters so much.

"Unknown syntax" diagnostics are off by default, and should usually stay off. Any addon can register syntax this extension has never heard of, so reporting every unmatched line would light up most scripts on a real server.

Setting docsPath does not make it safe, and an earlier version of this README wrongly said it did. /sk gen-docs produces one docs.json per addon, and the one Skript writes describes Skript only — no SkBee syntax, no skript-reflect syntax, nothing from any addon you have installed. Every addon line in your project would still be flagged. Turn it on only if your scripts use core Skript and no addons, or if you have supplied every addon's syntax yourself through customSyntaxPaths.

docsPath is still worth setting, for a different reason: it pins the catalog to the exact Skript build your server runs, forks and nightlies included.

{
  "lsp": {
    "skript-lsp": {
      "initialization_options": {
        "docsPath": "/path/to/plugins/Skript/docs/docs.json"
      }
    }
  }
}

The syntax database is downloaded, never bundled. Hover and completion are driven by Skript's own generated database plus SkriptHub's addon catalog. Both are fetched at runtime and cached. That is partly licensing — they are GPL-3.0 and no-licence respectively, and this project is MIT — and partly that it keeps documentation matched to the Skript version you actually target.

Without the language server

Everything structural keeps working, because it comes from the grammar rather than the server:

On a first run with no network, a small built-in catalog takes over and the server tells you so.

Troubleshooting

Everything is grey / only strings are coloured. semantic_tokens is still "off". See step 2 of the install.

No hover or completion. The syntax database has not loaded. Check dev: open language server logs — the server logs what it loaded, what it detected, and what it fell back to.

Nothing is highlighted at all. The grammar failed to build. Zed's log (zed: open log) will say why; a missing wasi-sdk or an unreachable grammar revision are the usual causes.

Which version am I actually running? Two separate things, so check both:

• The extension — its version is in the Extensions panel.
• The language server — Zed's log (zed: open log) records the binary it started, and the folder name is the release tag: …/extensions/work/skript/skript-lsp-v0.2.0/skript-lsp. You can also run that binary with --version.

The server's update check is cached for a day, so a release published in the last 24 hours may not have been picked up yet. Quit Zed, delete the extensions/work/skript folder, and reopen to force a fresh download.

My addon's syntax is not recognised. Check the log for what was detected. If your addon is not on SkriptHub, point customSyntaxPaths at its syntax file. Open an issue with the addon name and version.

How it works

Skript cannot be described by a context-free grammar, so this is deliberately two layers. The tree-sitter grammar owns structure — lines, indentation, sections, strings, variables — and never tries to guess what a statement means. The language server owns meaning, matching each line against 2,660 published Skript patterns plus 12,877 addon patterns, and returning the answer as LSP semantic tokens.

The grammar is held to SkriptLang's own repository: roughly 540 real .sk files must parse with zero errors on every change.

More in docs/architecture.md, docs/grammar.md and docs/language-server.md.

Contributing

Bug reports, grammar fixes and addon syntax are all welcome — see CONTRIBUTING.md.

The most useful bug report is a .sk snippet that Skript accepts and this grammar does not.

Licence

MIT — see LICENSE. Third-party dependency notices are in THIRD-PARTY-NOTICES.md.

Skript itself is GPL-3.0 and is not included here; its syntax database is downloaded at runtime rather than redistributed.