Errors and source lines
Read compiler, policy and runtime failures.
Error locations
Example:
my_script.sk:47 (Java line 3): cannot find symbol
47 is the original script line; Java line 3 is a line within the expanded block. The addon translates internal wrapper line numbers.
Included files
A failure inside a nested .jv file reports that file’s own path and line. Mapping survives includes and reuse of the same cached class from different scripts.
Failure types
| Error | What to inspect |
|---|---|
cannot find symbol |
Variable spelling, fully qualified types, available methods |
Forbidden class / Forbidden System member |
Restrictions and the selected API |
Class is outside the allowed API |
Allowed packages, dependencies and I/O policy |
| Runtime exception | Event values, types, null, indices and stack trace |
The full stack trace remains available. Wrapper failures or exceptions without a matching source frame may fall back to the section line.
Where messages appear
Include preparation can reject a script while parsing. Background compilation and bytecode-policy errors appear in the console after submission. A successful /sk reload alone does not confirm Java readiness.