Suggestion

Try adding more runtime warnings or errors to console, currently finding bugs in skripts is difficult. For example a line can look like it’s going to do something but still it wouldn’t in some situations. An example of this could be u trying to kill an entity in an unloaded chunk, sometimes this would work fine but (if the chunk is loaded by a player) but othertimes it just wouldn’t do anything. When it does nothing or catches the exception bukkit throws (if it does) it should log it to the console so we can properly bugfix (for this example adding a load chunk expression)

Why?

This is really usefull for bugtesting, skript bugtesting at runtime can defenitly use some work compared to coding in java or kotlin.

Other

No response

Agreement

• I have read the guidelines above and affirm I am following them with this suggestion.

For the killing an unloaded entity, that’s runtime / undefined behavior where it’s not related to Skript, tho if the method does throws an exception then the current Skript version should be able to catch it.

Actually I'm going to close this issue because it's too broad a scope, there's no feasible pr that can complete this, since we could always add more runtime warnings. Rest assured this is something we plan on doing.