What NeoSkript is

NeoSkript runs Skript scripts. It isn’t a fork: it’s a clean-room rewrite that treats Skript’s behaviour as the spec, so the .sk files you have today load and behave the same way. What changes is underneath. Each trigger is compiled to JVM bytecode, so the JIT can optimise across a whole script instead of stepping through syntax one element at a time, and the threading model is built for Folia from the start.

In development

NeoSkript itself isn’t released yet. Development builds are for testing on a server you can afford to break. Its script checker is: check your scripts before you switch. Where each milestone stands is in the progress log.

How we check it’s a drop-in

• Skript’s own test suite. Every test in Skript 2.17’s suite runs on NeoSkript, and all 862 pass.
• Side by side with real Skript. A differential test harness runs the same scripts on a real Skript server and a NeoSkript server and compares what they do, message by message.

What it runs on

Platform	Supported
Server	Paper or Folia
Minecraft	1.21.4 or newer
Java	21 or newer

Skript addons don’t load on NeoSkript yet: an addon compatibility layer is planned after 1.0. Addons written against NeoSkript’s own API work from the start.