Finally see what’s inside your Skript variables.
Run /skv editor and your whole variable tree opens in the browser. Fix a location, correct a balance, delete a namespace, then write it all back with one command. No more hand editing variables.csv.
One command out, one command back.
Drop the jar in your plugins/ folder and you are done setting up. There is no account to create, no database to run, and no config to fill in. Variables still held in memory are included automatically, so you never have to flush them first.
$cp skript-variables-1.0-beta.jar plugins/>/sk reload→✓ skript-variables 1.0-beta enabled
>/skv editor→uploading 9,978 variables→✓ [Open Editor ↗] click to edit in your browser
>/skv apply a7f3c9d2 4821→2 modified, 1 deleted→✓ changes written to Skript storage
Everything you wished Skript had,
behind one clean panel.
Your namespaces, as folders.
A variable like {playerdata::uuid::kills} shows up as a collapsible tree instead of one flat line in a CSV. Per namespace stats tell you what is actually taking up space.
Find the variable, not the haystack.
Search by name, switch on regex, or filter by type and by pending change. Type a username and it resolves to the UUID your script stored.
Real editors for awkward types.
Locations get world, X, Y, Z, yaw and pitch fields. Vectors show live magnitude and a normalize button. Items, block data, dates, timespans and NBT each get their own modal.
Fix a hundred variables at once.
Select many variables and set them to the same value in one action, rename or copy a variable to a new name, or delete an entire namespace with one click.
oopsk structs, field by field.
If you run oopsk, structs are not opaque blobs. Open one and edit its individual fields directly. Entirely optional, the addon works fine without it.
Nothing changes until you say so.
Edits are queued in the browser and only written when you run apply with a one time code. VariablesApplyEvent fires first, so your own scripts can inspect or cancel the write.
Editing live data should feel safe.
This addon writes directly to Skript variable storage, so it is built to be deliberate about it. Here is exactly what it needs and exactly what it will not do behind your back.
- Server
- Paper 1.21.4 or newer
- Skript
- 2.14.x to 2.15.x
- Java
- 21 or newer
- oopsk
- Optional, adds struct editing
Your edits stay queued.
Everything you change in the browser is held there. The server is untouched until you run the apply command in game.
Apply codes are single use.
Each session produces one code that expires the moment it is used, unless you deliberately pass --force to keep it alive.
Op only by default.
Both skriptvariables.use and skriptvariables.editor default to op, so nobody opens an editor session without permission.
Your scripts get the last word.
VariablesApplyEvent fires before anything is written and can be cancelled from Skript or another plugin.
skript-variables is free and open source under the GPLv3. Drop the jar in, run one command, and see the whole tree. Questions, bugs and feature ideas are all welcome in the Discord.