Since release 2.4.99 the logger shows the following exceptions a few hundred times whilst loading the game:

[ERROR][Bot #1][11/08 11:13:23 AM]: Error in script executor!
java.lang.NullPointerException
	at org.osbot.rs07.api.Widgets.getWidgets(ci:151)
	at org.osbot.rs07.api.Widgets.isVisible(ci:261)
	at org.osbot.rs07.event.ScriptExecutor$InternalExecutor.run(sg:70)
	at java.lang.Thread.run(Unknown Source)

My startup command:

java -jar osbot.jar -login abuse:abuse-bot bot@[member=test].com:test:0000 -allow norandoms -script myscript:uuid

This does not occur when the following commands are used:

java -jar osbot.jar -login abuse:abuse-bot bot@[member=test].com:test:0000 -allow norandoms

 - or -

java -jar osbot.jar -login abuse:abuse-bot bot@[member=test].com:test:0000 -script myscript:uuid

myscript is an empty script skeleton

@ScriptManifest(name = "myscript", author = "Abuse", version = 4.20, info = "", logo = "") 
public class myscript extends Script {		
	@[member=Override]
	public void onStart(){
		
	}
	@[member=Override]
	public int onLoop() throws InterruptedException {
            return 1000;
        }
}

Somewhere in your script you are calling widgets before you are fully logged in. You must handle logging in yourself with norandoms on.

Somewhere in your script you are calling widgets before you are fully logged in. You must handle logging in yourself with norandoms on.

 

He has an empty script though.

 

Check your /scripts folder maybe you have 2 scripts with the same name under different compiled jars. Delete them and recompile

Edited November 8, 20169 yr by Zappster

Say goodbye to already existing automated bot farms and lets make it so that only a handful of people can run them ;)

Say goodbye to already existing automated bot farms and lets make it so that only a handful of people can run them

 

You were given over a week to update your scripts. This update allows bot farmers to have complete control over their scripts. Also your post has no relevance to this topic, please only post if you have something to contribute to the topic being discussed.

Somewhere in your script you are calling widgets before you are fully logged in. You must handle logging in yourself with norandoms on.

 

That's unfortunately not the case.

The test script is the one that I posted in the bug report, no widgets were used.

 

 

 

- Abuse

Edited November 9, 20169 yr by Abuse

I can reproduce this error with a bare-bones script too. 

 

v .99

 

-allow norandoms

Current ghetto fix 

@[member=Override]
	public void onStart() {
		try {
			sleep(2000);
		} catch (InterruptedException e) {
			e.printStackTrace();
		}
	

Fixed in .100