What's new
By:
  • Visit Rebornbuddy
  • Visit Panda Profiles
  • Visit LLamamMagic
  • Visit Resources
  • Visit Downloads
  • Visit Portal
RebornBuddy Forums

Register a free account today to become a member! Once signed in, you'll be able to participate on this site by adding your own topics and posts, as well as connect with other members through your own private inbox!

Relogger?

ILLu710N said:
How is asking a question considered begging? But thx for the quick reply :)
Click to expand...
DocBrown said:
i personally would beg for a relogger like yar
Click to expand...

It was a warning for the morons that are gonna PM me for infos :) offerring 10$ for a complete software lol, no offense.

There's no public projects of that kind, and I personally don't have the time to get on it.
 
I've you are interested in a relogger to avoid crash. google restartoncrash.
I use this soft on all my bots/games.

for scheduling operation, there are tons of soft available. I personnaly use batch scripts to start/stop my VMs and windows event tool.
 
happyfriet said:
I've never had my Exilebuddy crashing so the relogging works fine.
Click to expand...
I believe EB crash/close only because of network issue so you should be fine if your network is stable.
Poe crash happens only in VM for me but its pretty rare.
 
You guys do know that you only need some software that restarts both clients (poe/EB) if they crash and use the -autostart arg. Just google and you will have thousands of options. Every single other shit that YAR @honorbuddy does is built in already in Exilebuddy.
 
Not really, sometimes bot can just stop without crashing, so you better have some communication between relogger and bot via externalcommunication, there is example plugin for this.
 
Last edited:
If you guys find something API wise that EB is missing that would help making a relogger easier, I'm all ears. :)

I am aware of some auth-related stuff when it comes to max sessions and that not being exposed nicely, but handling auth stuff will take a bit of work because it's not EB specific, so I have to be careful what I expose to make sure no unintended side-effects result.

There's certain limitations to the actual PoE login process, which the API doesn't handle well. I treat errors in the login process in PoE as "if it fails, it's always safer to stop and lose botting time than risk something going terribly wrong." Because of that, if you're looking to handle the PoE side of things better, it's not really possible.
 
sometimes bot stacks on deathscreen (no stop) and when char select screen is not fully loaded (no gui for some wierd reason), this is kind of 2 things that is hard to handle.
 
paind said:
sometimes bot stacks on deathscreen (no stop) and when char select screen is not fully loaded (no gui for some wierd reason), this is kind of 2 things that is hard to handle.
Click to expand...

I noticed that too, when the bot is dead it's not always detected, last lines says only that it's "exploring blabla". StuckDetection is not detecting it because of LokiPoe.Me.IsDead.
The second case is caused by your connection failure. I "solved" it by forking autologin and making it exit the game rather than stop. My relogger handles the situation from this time.

EDIT: I think it may get stucked on death while some await is processing like Coroutines.CreateAndTakePortalToTown(). Need pushedx to clarify.
 
Last edited:
It's the CR awaiting for the action to finish. This happens on lower FPS, since low fps means you have an almost infinite frame time. Full logs will help, otherwise pushedx will be left pondering if one out of the thousands of things could be wrong.

Edit - Coroutines.CreateAndTakePortalToTown() has a timeout, since you see the timer run.
 
There is sadly no log, last time when I catched the bot in such situation it was just "Now exploring" as I said before, nothing about being dead. If I'll catch it again, of course I'll post logs.
 
Tormiasz said:
There is sadly no log, last time when I catched the bot in such situation it was just "Now exploring" as I said before, nothing about being dead. If I'll catch it again, of course I'll post logs.
Click to expand...
Ya, more of them the better to trace the roots.,
 
paind said:
sometimes bot stacks on deathscreen (no stop) and when char select screen is not fully loaded (no gui for some wierd reason), this is kind of 2 things that is hard to handle.
Click to expand...

I added code to detect this not too long ago to ResurrectTask and it should logout for you, is it still happening? If you can get me a log of when it happens, I can see if it's triggering correctly or not.

The character selection loading thing is weird. I've been told of it, but I can't really replicate it. They have some sort of background loading that runs while it's waiting for the data, so I'm afraid the best thing to do is just wait longer before character selection each time and hope to avoid it.
 
You must log in or register to reply here.
Back
Top