[slashnhax]

Slack
Not too sure what causes this, but when it occurs it spams the terminal, even after stopping the bot.
 
@Arbiter @Cloud
 
I have a sneaking suspicion it has something to do with LoopingThreads.
 

java.lang.UnsupportedOperationException: Calling methods that must query the session for information is no longer allowed within non-
bot threads. 
 at nul.IIiIIIiIIIIi.this(aic:181) 
 at com.runemate.game.api.hybrid.Environment.getScript(xec:266) 
 at com.runemate.game.api.script.framework.core.LoopingThread$ExceptionHandler.uncaughtException(gpb:69) 
 at java.lang.ThreadGroup.uncaughtException(ThreadGroup.java:1057) 
 at java.lang.ThreadGroup.uncaughtException(ThreadGroup.java:1052) 
 at com.sun.glass.ui.Application.reportException(Application.java:453) 
 at com.sun.glass.ui.gtk.GtkApplication._runLoop(Native Method) 
 at com.sun.glass.ui.gtk.GtkApplication.lambda$null$49(GtkApplication.java:139) 
 at java.lang.Thread.run(Thread.java:745)

 

[cloud]

It's caused by a call to Environment.getScript within an UncaughtExceptionHandler. What that means is your looping thread is causing an exception and then the handler is failing and throwing an exception. The UncaughtExceptionHandler will be fixed for V1.0.19, then it'll be your turn to fix your bug .

 

[slashnhax]

It's caused by a call to Environment.getScript within an UncaughtExceptionHandler. What that means is your looping thread is causing an exception and then the handler is failing and throwing an exception. The UncaughtExceptionHandler will be fixed for V1.0.19, then it'll be your turn to fix your bug .

Haha I've already found the bug and fixed it, it was an NPE caused by calling something before I had set what it relies on xD
 
Turns out that it wasn't the bug, or rather, the bug I fixed wasn't the only one xD Keen for v1.0.19 :3