OSBot version number: 2.3.65 and later

Description of the bug/error:

Starting a script that uses hopping works fine the first time. But after stopping the script and starting it again, hopping fails. (Can take a few attempts at stopping/starting to reproduce)

Instructions how to replicate the bug/error:

1. Run a script that hops worlds.
2. Stop the script

3. Run the script again.

(IF APPLICABLE) SSCCE that causes the bug/error:

@ScriptManifest(author = "Author", info = "TestScript", logo = "", name = "Test script", version = 1.0)
public class TestScript extends Script {

	@Override
	public int onLoop() throws InterruptedException {
		log("Hop");
		worlds.hopToP2PWorld();
		return random(200, 300);
	}

}

(IF APPLICABLE) Script name ran causing the bug/error. Optionally include relevant parts of source code:

Frost Impulses

(IF APPLICABLE) Screenshots:

Worldhopper now also hops to pvp worlds using the method hopToP2PWorld().

 

 

Worldhopper now also hops to pvp worlds using the method hopToP2PWorld().

 

Confirmed. Current client is very dangerous to use with anything that involves hopping.

I believe the issue with hopping to F2P and PvP worlds despite filtering is not an issue of picking the world, but rather clicking the correct spot using the new MouseClick/MouseMove algo

Please fix asap, hopping to pvp worlds is not safe.

EDIT: Posted as a seperate bug

Edited May 21, 201510 yr by FrostBug