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!

[StandAlone] Yet Another Relogger!

Status
Not open for further replies.
katt88 said:
2 questions
1) Can I use this program to set the length of time I wanna bot for and have it close D3 after the time has been reached?

2) I still can't get the program to enter in my username and password when D3 window pops up. I'm trying to use this with Alkaizer Gnome Proof and A1-A3 simple Key farming. I have fresh copies of everything and it's still not working =(.
Click to expand...

1. Yes, there's the scheduler. You can also set max time per profile.

2. First rule of bugs/errors, post logs: http://www.thebuddyforum.com/honorb...-how-attach-your-hb-db-log-file-pictures.html
 
This plug-in is really easy to use!But I am a little worried about whether the backdoor.
 
Sorry for being a bit sluggish last days.. I had some trouble with Datagridviews and databindings :( and I do not have as much free time as I used to have I will do my best to keep developing every minute I can and am allowed to ;)

anyway here is a new update
Version: 0.1.8.5 BETA
  • Added Hotkey bindings
  • Changed Log file extension from .log to .txt to match Demonbuddy logging
  • Improved responsiveness
 
i have an issue, when demonbuddy stopping randomly. "was this requested?" then just character hangs and DB stops. I have 360 sec goldafk enabled, but relogger should kill the processes in this case (db+d3) then restart them? Or do i miss something? Becouse its been 2 hours now, and it doesnt restart them

Amazing job by the way, thank you sir :)
 
[02.12.2012 15:59:40] Relogger Crashed! with message Object reference not set to an instance of an object.
[02.12.2012 15:59:40] at YetAnotherRelogger.Relogger.ReloggerWorker()
[02.12.2012 15:59:40] Waiting 10 seconds and try again!
[02.12.2012 15:59:50] Relogger Crashed! with message Object reference not set to an instance of an object.
[02.12.2012 15:59:50] at YetAnotherRelogger.Relogger.ReloggerWorker()
[02.12.2012 15:59:50] Waiting 10 seconds and try again!

Using exact same settings as before, only the second of two bots give this error, the first one is running. What gives?
 
katt88 said:
2 questions
2) I still can't get the program to enter in my username and password when D3 window pops up. I'm trying to use this with Alkaizer Gnome Proof and A1-A3 simple Key farming. I have fresh copies of everything and it's still not working =(.
Click to expand...
I'm trying to use gnome's alkaizer profile as well and it requires radsatom to be enabled before loading. The relogger loads the profile and then logs in and plugins aren't enabled until logged in to D3. Is there any way to change the order around to make it log into D3 and then start demonbuddy?
View attachment 1808 2012-12-02 12.27.txt
 
The hotkey features works great! Thank you for implementing that in!

Can you add a hotkey feature to FullScreen AND reposition to a second display?

Like all my bots are on Display1, but sometimes I need to fullscreen Bot#1 on Display1, and then fullscreen Bot#2 on Display2. I've been doing that with hotkeynet, but if you can implement that in, I can delete hotkeynet altogether.

Also, I tried to use RepositionAll but it doesn't seem to do anything? I had a couple windows fullscreen and then did RepositionAll but nothing happened.

Edit:

Another request:

Can you implement this feature for Anti-Idle measures. What I been noticing is sometimes the bot will mess up like vendoring and then sitting in town, or sitting by the stash, etc. And how I fix it is I just click "Stop" on the bot and "Start" again. And it fixes the hiccup. Can you make it so that if it detects idle like that for X minutes, then fix it by clicking stop/start? Because YAR's anti idle measures are if it detects idleness, it closes out D3/DB and starts them up again. I think that process can be avoided by first trying the STOP/START method to fix a simple hiccup.
 
Last edited:
Hi
I cant get it to logg in to d3. I dont know what i have missed or do wrong.
And does this work whit [Plugin] AntiIdle ? Or should i go whit Unstucker v2.2.0
Plz help me
 
Last edited:
Donated! Thx for your awesome work, mate.

This is a call to all YAR users. PAY THIS MAN! WE LOVE HIM! WE NEED HIM! ;D
 
Hey sinterlkaas.
First of all I want to say thanks for a wonderful plugin, prevents my bots from crashing during the night, and makes my efforts much smaller. Said short: It's lovely!
I was wondering, when using the break timer, the fields from let's say 10-12 are green and then I have a break at 13. Would my bot then stop from 13-14 and resume the playing? Or how does it work?
 
is there any way to edit the discription of YET ANOTHER RELOGGER, it says it in the proccess discription

let me know. i dont want blizz reading YAR in my proccess good way to get banned
 
Madske said:
Hey sinterlkaas.
First of all I want to say thanks for a wonderful plugin, prevents my bots from crashing during the night, and makes my efforts much smaller. Said short: It's lovely!
I was wondering, when using the break timer, the fields from let's say 10-12 are green and then I have a break at 13. Would my bot then stop from 13-14 and resume the playing? Or how does it work?
Click to expand...

Yes, stops from 13-14 if 13 = grey. Then starts again at 14.
 
Velando said:
Yes, stops from 13-14 if 13 = grey. Then starts again at 14.
Click to expand...

Is there any way we can see improvement on this in a later update? I would like to have my bot say stop/logout at 13 for only like 10-15 min. then start back up instead of having to wait a full hour. This is the only reason I still use db_run.

Or it could be as simple as making the randomization feature always tag on an extra say 30-45 min. in my example to the 13. Which would make it always stop at 13:30 - 13:45 which would result in a 15-30 min. break and starting back up at 14.
 
Last edited:
urn357 said:
Is there any way we can see improvement on this in a later update? I would like to have my bot say stop/logout at 13 for only like 10-15 min. then start back up instead of having to wait a full hour. This is the only reason I still use db_run.

Or it could be as simple as making the randomization feature always tag on an extra say 30-45 min. in my example to the 13. Which would make it always stop at 13:30 - 13:45 which would result in a 15-30 min. break and starting back up at 14.
Click to expand...
You could use Atom for you to take breaks ..
 
Status
Not open for further replies.
Back
Top