Troubleshooting & Compatibility
"Can't understand this condition/structure"
Symptoms: Skript rejects obsidrel has item ... or on obsidrel furniture interact:.
- Confirm Skript 2.17.1 is enabled and Obsidrel-Skript is listed as ENABLED in
/obsidrel addons list. - Look for
[Obsidrel-Skript] Syntax registered using Obsidrel public API level 1.during startup. - Make sure the native addon JAR is inside
plugins/Obsidrel/addons/, not in the rootplugins/folder. - Restart the entire server after installing or replacing the native addon. Syntaxes cannot safely be registered after Skript has finished its initial registration.
- Check the exact syntax in the reference articles. Use
obsidrel has item "id", notobsidrel item "id" exists.
"There's no command sender" in an Obsidrel event
A furniture interaction is an event, not a command. Use an appropriate recipient, for example:
on obsidrel furniture interact:
send "Interacted: %obsidrel event id%" to event-player
For player-optional events, the source/actor/killer may be absent; guard the usage of event-player accordingly.
Unknown or missing IDs
- Check the exact namespace and identifier in the Core definition files.
- Query with the dedicated condition before creating an item or executing an action.
- A missing cooldown ID is not considered
ready. - Unknown custom-item expressions return no ItemStack rather than a fatal Skript exception in the validated version.
/obsidrel reload disables Skript integration
This points to a Core build without reload-retention support or an addon descriptor that does not contain core-reload: retain. Updating to the validated Core build and doing a full restart is required. The standalone command /obsidrel addons reload skript is intentionally blocked; it cannot replace a live Skript classloader safely.
Async effects do not run
Obsidrel effects that mutate Bukkit/Core state must run on the primary server thread. The addon logs a warning and ignores an asynchronous mutation rather than executing it unsafely. Do not wrap these calls inside asynchronous Skript sections.
Cooldown says READY / 0 ms
This is expected if the known cooldown is not active. To check a real countdown, trigger an Obsidrel action or item mechanic that starts the cooldown, then query again. A Player Data timer and an Action cooldown are separate systems.
Paper command-tree ConcurrentModificationException
One ConcurrentModificationException in Paper/Brigadier's asynchronous command-tree builder occurred during script reload testing. It did not recur in later tests and was not definitively attributed or fixed by the Obsidrel addon. If it recurs, isolate script command registration and collect the full Paper/Skript versions and stack trace rather than assuming a Core bug.
Support scope
| Area | State |
|---|---|
| Java 21, Skript 2.17.1, Purpur 1.21.11 | Tested |
| Core 1.0.0 with reload-retention | Tested |
| Item/block/furniture operations and representative events | Tested |
| Player Data persistence, HUD, menus, cooldown and timer | Tested |
| All 23 events individually | Not certified |
| Folia and asynchronous mutations | Not certified |
| Custom entity, cosmetics, sound and loot effects individually | Not certified |
For integration implementation details, see the Obsidrel-Skript repository. The public Docs and Marketplace should link to the latest approved 1.0.0 artifact, not an untested development build.