Troubleshooting

API status — PROPOSED, NOT IMPLEMENTED. SkCine is currently a design specification in this conversation; no built SkCine.jar or syntax registry was supplied. All SkCine-specific examples are intended API contracts, not verified runnable .sk. Do not advertise these as tested until each example passes a real Skript reload and runtime test.

"Can't understand this condition/effect"

Likely causes: SkCine isn't installed or implemented, incompatible Skript, a typo, or a syntax pattern not actually registered. In the current stage, the supplied examples are proposals and will not parse without the completed addon. Verify startup logs and /sk version and prioritize the first parse error.

Cinematic starts but camera does not move

Check camera backend capability, actual spectator/packet camera support, viewer world, keyframe order and valid non-identical camera positions. Client packet sending does not prove the client accepted the camera anchor.

Player stuck in spectator mode

Treat as a high-severity defect. Check cleanup on all terminal paths and on disconnect/reconnect. Restore only SkCine-owned state; review crash journal. Do not deploy packet camera on production until the relevant lifecycle tests pass.

Display snaps or lags

Review display interpolation and teleport duration. Paper Display setTeleportDuration is bounded 0–59; split longer movement into evaluated segments and verify interpolation settings.

Too many particles / server lag

Lower per-viewer particle budgets, use geometry caching, improve distance culling and avoid per-particle Skript loops. Profile callbacks and packets separately.

No dialogue or custom sound

Check configured output mode and custom sound namespace/resource-pack presence. Not every client installs the server pack. Provide a vanilla fallback.

Duplicate scene ID or double reward

Duplicate definitions can occur across scripts/reloads; IDs need source ownership and atomic replacement. Never grant the same reward in both finish and skip callbacks without an idempotency key.

Get actionable diagnostics

Record Paper, JVM, Skript, SkCine, PacketEvents versions; complete first error; file/line; scene ID; whether PacketEvents is installed; what backend was selected. Never expose secrets or client personal information in public logs.