Frequently asked questions
Troubleshoot loading, compilation, variables and access policy.
A block did not run after reload
Inspect the console. Compilation is asynchronous: before Java block ready, the current trigger invocation stops. Fix compiler/policy failures and reload the calling script. on load can also run before readiness.
The plugin cannot find a compiler
Use a full JDK 25 with jdk.compiler. Check the Java executable in the server startup script: installing a JDK does not help if the server launches through another or stripped runtime.
event.getDamage is not found
event is declared as a general Bukkit Event. Cast it to org.bukkit.event.entity.EntityDamageEvent, or use context.get("damage") for an applicable event.
A variable disappears between commands
The _ prefix selects event-local scope. Use an unprefixed name for a shared value. See variable scopes. A /jvdebug entry does not prove storage persistence.
A changed module still executes old code
Reload the calling .sk, including when a nested include changed. Execution uses the parse-time source snapshot rather than rereading the file for each event.
A lambda compiles but policy rejects it
The JDK compiler supports the syntax, while bytecode policy separately checks its target. A System::exit reference is rejected, for example. Change the operation rather than trying to bypass the checks.
A Maven library will not load
Check dependencies.enabled, exact coordinates, SHA-256, and package prefixes. Declare transitive JARs separately. Restart after configuration changes; script reload allows a transient download failure to retry.
Can I run hostile third-party code
No. Approved Bukkit APIs and libraries retain server privileges; loops and memory are not isolated. See security.