1.7.48. It was fine, and already running bots are healthy, but when I start new instances, they log this exception after starting script.

 

[iNFO ][09/24/13 09:30:38 PM]: Started client!
[iNFO ][09/24/13 09:30:47 PM]: Started script : Move and test
[ERROR][09/24/13 09:30:48 PM]: Error on executing random worker!
java.lang.NullPointerException
    at org.osbot.CA.shouldActivate(rg:113)
    at org.osbot.script.rs2.randoms.RandomManager.scan(zo:81)
    at org.osbot.UA.run(zm:18)
    at java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source)
    at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source)
    at java.lang.Thread.run(Unknown Source)
[ERROR][09/24/13 09:30:48 PM]: Error on executing random worker!
java.lang.NullPointerException
    at org.osbot.CA.shouldActivate(rg:113)
    at org.osbot.script.rs2.randoms.RandomManager.scan(zo:81)
    at org.osbot.UA.run(zm:18)
    at java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source)
    at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source)
    at java.lang.Thread.run(Unknown Source)

Edited September 24, 201312 yr by darkxor

Tested, this only throws if I enable breaks in account settings, if disable - bot starts flawless.

 

P.S. If I logon first time manually, then it begins to work normally.

Edited September 24, 201312 yr by darkxor

This has been happening to me also. Since 1.7.39 I believe.

tracing back through CA.class at line 113 is

 

    if ((a.bot.B()) && (!a.myPlayer().isUnderAttack())) 

which would make sense, because myPlayer() is null before logging in.

CA.class is Maxi's break taker.

Edited September 24, 201312 yr by dreamliner