I am not sure, but I think world 100 is added to the game.

In the figure above the script is trying to log-in to world 86, but instead hovers over 85.

Code and boolean result please, I tested this earlier (posted in 3 other threads) and it keeps working for me.

Just now, Alek said:

Code and boolean result please, I tested this earlier (posted in 3 other threads) and it keeps working for me.

@Alek I'll post my code when I'm home today as well; I use a loop with timeout checking the boolean result, but in rare cases the worldhopper will still get stuck hovering a random world in the hopper.

@Alek - This is what I've been using to hop worlds. On occasion the world hopper will open the quick hop menu, start to move the mouse then get stuck hovering a world that is not our target world. I'll see if I can capture more information next time I see it.

boolean result = false;
long timeout = System.currentTimeMillis() + 60000;
while(!result && System.currentTimeMillis() < timeout)
	result = worlds.hop(WORLD);

 

No issues, all returned true. I tried worlds.hop(86) and worlds.hopToP2PWorld() (10 times consecutively). 

2 hours ago, Alek said:

No issues, all returned true. I tried worlds.hop(86) and worlds.hopToP2PWorld() (10 times consecutively). 

Issue is much less common than this, but obviously me just telling you this literally does not help you at all. I'll do some debugging and gather some more information for you.

On 3/13/2017 at 11:15 AM, Alek said:

Code and boolean result please, I tested this earlier (posted in 3 other threads) and it keeps working for me.

The world hopping is working fine. getWorld() is returning the wrong result. For example, if you login to world 50, and hop to world 70, getWorld will still return 50. Forever.

EDIT: World hopping is broken because for example if you are on world 94 from login, and it registers you on world 94, then you hop worlds to say 35. Now, you want to hop back to world 94. It won't hop, because bot.getWorld says you're already on world 94. There is no workaround atm, other than to never login from any world you want to hop to, or logging out before hopping every single time. 

Edited April 4, 20179 yr by dmmslaver

On 3/14/2017 at 8:52 AM, Night said:

Issue is much less common than this, but obviously me just telling you this literally does not help you at all. I'll do some debugging and gather some more information for you.

It happens literally every single time. 

14 hours ago, dmmslaver said:

The world hopping is working fine. getWorld() is returning the wrong result. For example, if you login to world 50, and hop to world 70, getWorld will still return 50. Forever.

EDIT: World hopping is broken because for example if you are on world 94 from login, and it registers you on world 94, then you hop worlds to say 35. Now, you want to hop back to world 94. It won't hop, because bot.getWorld says you're already on world 94. There is no workaround atm, other than to never login from any world you want to hop to, or logging out before hopping every single time. 

So it's not an issue with world hopping, it's an issue with getCurrentWorld()?

36 minutes ago, Alek said:

So it's not an issue with world hopping, it's an issue with getCurrentWorld()?

I can back this up as well, I have been super confused as to why World Hopping has been screwing up but that makes so much sense. It'd work on once cycle and hop away from a world to a specified one but then can never get back to that specified one. 

1 hour ago, Alek said:

So it's not an issue with world hopping, it's an issue with getCurrentWorld()?

Can confirm this too.