Bug Being overly charged on botting hours

I've been running regal agility since yesterday, not sure if it's been wasting my hours or not since but as far as I know it's been waiting hours today.



I can honestly say I've only botted 2 hours of that today and the rest + whenever it decides to actually end will have been wasted hours. :,(

I've tried restarting runemate client but nothing working atm.

@Party @kazemanie @SlashnHax @Arbiter @EvilCabbage

 

I had just stopped the script bot normally because I had to traverse to different courses.

--- Double Post Merged, May 15, 2017, Original Post Date: May 15, 2017 ---

@Party

Party I'll try to find the log of regal agility literally just draining my bot hours w/o even using it.
This is the last regal log I have;
00:00:00 INFO Logger Initialised - this log file can be found at C:\Users\PeeCee\RuneMate\logs\05-14 02-14-44 - Alpha Agility.txt
00:00:00 INFO Logging level can be adjusted in the Preferences tab.
00:00:00 DEBUG [WebServices] New session created!

java.lang.NullPointerException
at nul.iiIiIiiIiiiII.break(pab:34)
at nul.iiIiIiiIiiiII.<init>(pab:40)
at nul.iiiIiiiIIiiii.<init>(iya:124)
at nul.iIIiiiiIIIIii.<init>(fib:172)
at nul.IIiIiiiIIIiii.break(kxa:20800)
at nul.IiiIIiiIiIiii.super(txa:8526)
at nul.IiiIIiiIiIiii.this(txa:4445)
at nul.IiiIIiiIiIiii.break(txa:99)
at nul.IIIIiiiIIiIii.break(txa:157)
at nul.iIiIIiiIIIIii.break(ce:80)
at nul.IIiiiiiIIiiii.super(lm:11296)
at nul.IIiiiiiIIiiii.break(lm:162)
at nul.iIIiiiiIiIIii.break(lm:22506)
at nul.iIiIIiiIIIIii.break(ce:80)
at nul.IiiIIiiIiIiIi.break(gk:5)
at nul.IIiiiiiIIiiii.super(lm:16098)
at nul.IIiiiiiIIiiii.super(lm:162)
at nul.IiIiIiiIIIIiI.break(lm:16877)
at nul.iIiIIiiIIIIii.break(ce:80)
at nul.iiiIIiiIiiiii.break(txa:18393)
at nul.iiiIIiiIiiiii.break(txa:92)
at nul.IiIiiiiIIIIii.break(txa:16136)
at nul.iIiIIiiIIIIii.break(ce:80)
at nul.IIiIIiiIiiiii.break(jab:14)
at nul.IIiIIiiIiiiii.break(jab:21)
at nul.iIIiiiiIiiIIi.break(pi:90)
at nul.IIIIIiiIiIiii.run(pi:165)
at nul.iIIIIiiIiiiIi.run(kcb:63)
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
at java.lang.Thread.run(Thread.java:745)