New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Skript Parse Error #661
Comments
One of the variables might be null (
But shouldn't it just do nothing instead of throw a NullPointer @bensku? |
This may also be due to the fix for using |
Oops, clicked wrong button on mobile. Anyway, it is quite likely that I somehow caused this by fixing variable comparisions. Probably easy to fix. |
Hi everybody! I think I get pretty much the same error on the dev32b, but I suspect a problem with Skellett? My errors (only two) are concerning mysql result (but the other results in my code work well... O_o)
Good luck! |
Those errors aren't related to the ones presented in the original post, those are from SkQuery. Use latest SkQuery and Skellett to fix. Before posting errors on this issue tracker, you should have ran it without addons. |
Rather a workaround I guess, but what do you think Index: src/main/java/ch/njol/skript/lang/SkriptParser.java
===================================================================
--- src/main/java/ch/njol/skript/lang/SkriptParser.java (revision b10cbd6b250483af1636d211df1b386a7f407509)
+++ src/main/java/ch/njol/skript/lang/SkriptParser.java (date 1531312012001)
@@ -494,7 +494,9 @@
}
if (e != null) { // Expression/VariableString parsing success
Class<?> returnType = e.getReturnType(); // Sometimes getReturnType does non-trivial costly operations
- assert returnType != null;
+ if (returnType == null) {
+ return null;
+ }
for (int i = 0; i < types.length; i++) {
final Class<?> t = types[i];
if (t == null) // Ignore invalid (null) types I'm referring to the original issue The question is, what could this change break? |
Parser has a ton of workarounds already. Please don't add more unless this issue is critical; we should try to locate source of the issue instead. |
I found the source of this issue: ExprDifference line 104. The check is there, to see if I presume Is there any other reason to compare the supertype with EDIT: |
I don't know how to read the error, but it saying Parse.
The text was updated successfully, but these errors were encountered: