Hello, I noticed some problems with the relogger function, sometimes it gets stuck like on the realm selection screen or the login screen, and you have to click manually connect/select realm and so on.

Mainly the relogger is 90% useful when the server crash (at least for me), so since when happens it requires a bit of time to recover, wouldn't be nice to add a wait timer before trying to relog? Like 5-10 minutes so its sure it doesnt bug/stuck when it relogs.

Thanks for the support =)

Hello, do you get this problem? http://wrobot.eu/bugtracker/335a-bot-unable-to-relog-bug-in-reloger-r337/

Yes, sometimes that, other times maybe its stuck on "connecting" or other things, what i need to do its simply cancel everything and re-do the login from start manually, and it works fine.

 

As already said in that topic, maybe add a check for login stuck, or my idea wait like 5-10minutes (or add a custom timer) before attempting to relog.

:)

Bump. Can we count on the appearance of the timer relogger? I'd love to see it, since it would be much better that the connection did not occur immediately after the disconnection, and after x amount of minutes.

And a very big wish is that when you disconnect not only closed the game window, but the bot, then restart bot after logging character in game world. Is it possible to add such a function? Tried to find it in the bot and relogger, but did not find, found only off the bot with timer, amount of stucks/deaths. The problem is that when the game restarts, the bot continues to follow the route, but doesn't start it from first step, in the case of dungeon character already teleports to the beginning, and it starts to get stuck.

+1 with bronson