Can having too many errors pop up in the log cause the script to freeze? (still running though)

 

and also this is what keeps popping up while the script is running:

 

[

ERROR][Bot #1][05/11 07:07:39 PM]: Failed to wrap : class client.Kuo
java.lang.RuntimeException: Could not initiate wrapper : RS2Widget
at org.osbot.core.api.Wrapper.wrap(fk:62)
at org.osbot.rs07.api.Widgets.getWidgets(lf:167)
at org.osbot.rs07.api.Widgets.get(lf:245)
at org.osbot.rs07.api.Worlds$2.condition(jf:253)
at org.osbot.rs07.utility.ConditionalSleep.sleep(cd:247)
at org.osbot.rs07.api.Worlds.iIiiIIIIIi(jf:61)
at org.osbot.rs07.api.Worlds.hop(jf:177)
at random.hopWorlds(random.java:113)
at random.onLoop(random.java:38)
at org.osbot.rs07.event.ScriptExecutor$InternalExecutor.run(lk:242)
at java.lang.Thread.run(Thread.java:745)
[ERROR][Bot #1][05/11 07:07:44 PM]: Error in script executor!
java.lang.NullPointerException

I think it's a mirror mode issue?

Edited May 12, 20169 yr by Economics

Can having too many errors pop up in the log cause the script to freeze? (still running though)

 

and also this is what keeps popping up while the script is running:

 

[

ERROR][Bot #1][05/11 07:07:39 PM]: Failed to wrap : class client.Kuo
java.lang.RuntimeException: Could not initiate wrapper : RS2Widget
at org.osbot.core.api.Wrapper.wrap(fk:62)
at org.osbot.rs07.api.Widgets.getWidgets(lf:167)
at org.osbot.rs07.api.Widgets.get(lf:245)
at org.osbot.rs07.api.Worlds$2.condition(jf:253)
at org.osbot.rs07.utility.ConditionalSleep.sleep(cd:247)
at org.osbot.rs07.api.Worlds.iIiiIIIIIi(jf:61)
at org.osbot.rs07.api.Worlds.hop(jf:177)
at random.hopWorlds(random.java:113)
at random.onLoop(random.java:38)
at org.osbot.rs07.event.ScriptExecutor$InternalExecutor.run(lk:242)
at java.lang.Thread.run(Thread.java:745)
[ERROR][Bot #1][05/11 07:07:44 PM]: Error in script executor!
java.lang.NullPointerException

I think it's a mirror mode issue?

 

Yes, things like NullPointerExceptions will cause the script to freeze.

 

Assuming that all your code does is getWorlds().hopToP2PWorld() or some similar method, then it looks like that is an issue with the world hopper, you can post it as a client bug here:

 

http://osbot.org/forum/forum/316-bug-reports/

 

As a temporary fix you could always write your own world hopper, or try and use this one (until it is fixed):

 

http://osbot.org/forum/topic/73332-quick-hopper/?p=811421