Upgrading from SkBee++
The rename and behavior changes to review in existing scripts.
SkJvm is the new name of SkBee++. It is independent of ShaneBee’s SkBee plugin.
Files, packages and permissions
Stop the server and back up configuration and scripts. Remove the old JAR and install only SkJvm-2.0.0.jar.
| Change | New value |
|---|---|
| Configuration folder | plugins/SkJvm |
| Java entry point | ru.helounn.skjvm.SkJvm |
| Java package | ru.helounn.skjvm |
| Debug permission | skjvm.debug |
| Command aliases | /jvdebug, /jvdb, /skjvm-debug |
The old configuration directory is not automatically migrated. Copy desired settings manually and update Java integrations.
Variable scopes
Names passed to the raw Skript API have been corrected. score and {score} now mean a global variable. _score and {_score} mean an event-local variable. Review scripts that depended on the former incorrect behavior.
Background compilation
Skript readiness does not imply Java readiness. Wait for Java block ready and inspect errors in the console. Pending Java blocks stop the current trigger invocation, including on load.
Successful cache entries survive /sk reload. Reload the calling script after modifying modules or includes.
Access policy
allow-system-io: false is the default. Older direct-I/O code may be rejected. Maven libraries need explicit approval and SHA-256 pins. Read the security boundary before changing policy.