[StandAlone] Yet Another Relogger!

Do you use CPU priority option?

 

What would be the position (X and Y I guess) required to put the windows up in the top right corner of the screen instead of the default ones?

 

usin 0.0.0.5 could u add that ur relogger sets cpu priority on d3 startup to high not when its already have been loaded

 

is there any release date for next generation beta with gold-timer?

 

Hey, was just wondering something.
When I have set everything up (using 2 accounts atm) and run them, they seem to load perfectly fine, start the game, loads the profile (big red act3), goes to first waypoint, works fine for 30 seconds, then it suddenly just TPs to town, resets grid and goes to the next one instead of finishing the level completely.

Starting d3 then DB on 2 different accounts work fine, so its not some setup with DB, but I cant for the life of me figure out what the problem might be.
I am choosing to load the "START_HERE" profile btw (in YAR).

Any help would be deeply appreciated!

Best regards
Fukinkou

 

Hey sinterlkaas,
I wanted to write you a pm, but your inbox is full ;D. So I do it public
_____________________________________________
Hey mate,

thank you so much for this f*cking awesome relogger. It makes so much, so much easier. In my opinion it's the best developement since trinity. I'll donate these days to support your work.

But I've a question. The profile scheduler isn't working for me. It just picks the first profile in the scheduler and just loop it. How do I set it up correctly? Can you give me a detailed explanation plz?

Thx in advance!
_____________________________________________

 

Just add command line options to auto start all bots and this will be perfect

 

I just can't seem to find a way of making it restart the bot after 90 minutes of running.. the randomizer on the schedule part doesn't seem to work?

 

Thanks for your public "PM"
The profile schedule indeed seems to be broken somehow it does count down and it does send the new profile to DB but somehow DB is choking in this process I am aware of this and will be fixed very soon

The profile schedule indeed seems to be broken somehow it does count down and it does send the new profile to DB but somehow DB is choking in this process I am aware of this and will be fixed very soon

Already added this and you can find it on github or be patience for next update very soon

 

I don't even need it to restart profiles, I just need it to restart diablo + db.. Is that broken too?

 

I tried to manually close the DB, alas, but logging in D3 is still not happening

 

In your log I find the following..

For some reason the bnetpassword is send twice to demonbuddy dont ask me why but this does not seem to be a issue from the relogger are you linking this file ? or is there a other way you can think of why it could receive a the bnetpassword twice ?
this is passed to demonbuddy by a commandline argument for example:

C:\Demonbuddy.exe -bnetpassword="password" -bnetusername="username"

EDIT:
Does your password contain any spaces ?

+ try to load demonbuddy without the relogger but use it to log into D3 example:
append the -autostart to let it start from initial launch like it should be done when launching it from commandline

C:\Demonbuddy.exe -bnetpassword="password" -bnetusername="username" -autostart

 

Can't wait for next version :0

 

Update Version: 0.1.7.7

Version: 0.1.7.7 BETA

• Added Support for Atom 2.0.15 "Take a break"
• Added Option to start with windows
• Added Option to minimize on start
• Added Buddy Auth Session killer
• Added option to remove window frame on diablo
• Added Coinage check (2 minutes w/o gold change => reset) (*tomasd)
• Added Crash detection for demonbuddy
• Added Demonbuddy initialize time limit
• Added CPU Affinity support (*tomasd)
• Changed Version numbereing to v 0.1.inc_new_features.inc_new_test_release
• Foreground check improved the way demonbuddy is set to front
• Fixed some issues with the profile schedule
• Fixed Connection check IP range was not implemented (somehow forgot this sorry...)
• Fixed Layout problems with schedule and settings on some systems
• Improved AntiIdle system
  • Limited to 3 fixing attempts in 5 mins
  • Added a new way to fix no pulse
    • First check if plugin is enabled
• Fixed Language support for Traditional Chinese

 

Sink, first off thanks for the update! looking good!

just something I saw in the last beta from the github yesterday
If I took a 90 sec break between games + time till it starts and all, it triggered the 120sec timer and so closing DB and d3
Is that fixed here?

also for the Ping check, is there a way maybe to check if the bnet server is up? so if they initiate maintaince we won't get 200 login attemps.

 

How can I make it restart diablo 3 + demonbuddy every 90 minutes? What option should I use?
Thanks

 

Just to say ... I love you!
Will test it NOW!

 

This relogger is GREAT! I got a question and an idea.

QUESTION: If I makes my 4 bots window smaller, with Position W: 320 H: 200 will diablo 3 use less CPU and RAM?

IDEA: Maybe you should encrypt Bots.XML where it stores the login/pass.

 

Thanks to you, I found what was the problem
Of characters in the password has a comma ","
Probably have to add this information to guide, because this problem has many
* Thank you once more the

 

And now the bad news.
Why is that the bot does not want to fight - he is on the route, but does not fight. All plug-ins to work actively.
If or just press Stop - Start or DB restart, starts to fight.
This started happening today, and for 284 and 285 DB with YAR 0.0.0.5, 0.0.0.6 and 0.1.7.7.

The log is attached.