For some odd reason occasionally whne I use this method, it goes to the widget, hovers the world, and doesnt actually press. This may be because it tried to go to a world I am currently on? Not quite sure but there definetly looks like there could be some extention of verifying that the bot has switched worls within this method.

 

When this bug occurs the bot just stops aparently waiting for itself to switch worlds, which never happens.

Don't know the cause, as have never experienced it. However an easy fix would be

After your call to hopToP2PWorld, Start a conditional sleep for say 10 seconds, then have it call hoptop2pworld again if your still in the same world.

It's not ideal, but it should work.

Edited October 22, 20169 yr by venetox

For some odd reason occasionally whne I use this method, it goes to the widget, hovers the world, and doesnt actually press. This may be because it tried to go to a world I am currently on? Not quite sure but there definetly looks like there could be some extention of verifying that the bot has switched worls within this method.

 

When this bug occurs the bot just stops aparently waiting for itself to switch worlds, which never happens.

  

Don't know the cause, as have never experienced it. However an easy fix would be

After your call to hopToP2PWorld, Start a conditional sleep for say 10 seconds, then have it call hoptop2pworld again if your still in the same world.

It's not ideal, but it should work.

This is what's I usually do and it works for me it's basically what venetox said

int currentWorld = getWorlds().getCurrentWorld();
if(getWorlds().hopToPTPWorkd()) {
Cond sleep and return this --> getWorlds().getCurrentWorld() != currentWorld;
}

Hope this works for you

Haha thanks thats actually exactly what I was using and @Alek said that was shitty AF. Just wanted to post the bug here so that hopefully he can take a quick peek at it. 

Haha thanks thats actually exactly what I was using and @Alek said that was shitty AF. Just wanted to post the bug here so that hopefully he can take a quick peek at it. 

Im not a dev so this won't really mean much to you but

1) Can you replicate this? or is it a one time rare thing

2) Adding on from above ^ has it happened again?

3) If it does happen have you got a gif/screenshot? Or have you already gotten one?

4) Is there a condition to toggle your world hopping?

 

This would help Alek or Zach understand why it happens.

I've had the same issue occur but with worlds.hopToF2PWorld(); 

 

It seems to always get stuck on world 384 and just hover there

All hop methods have been broken for a looong time now, usually ends up hovering the world widget.

Use my snippy  http://osbot.org/forum/topic/103917-hhopper-hop-to-a-specific-world-interrupt-condition/