What's new
  • 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.
Hey, tell me what to do, set up YAR, start a game, but do not enter a name and password, the login screen just hangs, then Db starts and all ...
What to do, why not game logs
 
Remove window frame is cool!! Once selected though, its is impossible to get the window edge back. We do occasionally need the window edges as this was the way to individually bring each d3 back to a normal size to process items, sell on AH etc. The ability to move the window is probably not too essential, but the ability to make one window big again for processing is definitely needed.

Humble request :) in the auto position settings tab there is an option "remove window frame". This works great. Request that when you UNTICK the box and then click "reposition now" that all the windows would have their edges back. This would solve the problems as then it is a togglable option.
 
here log
diablo don`t logging into the game
[23.11.2012 0:04:24] Relogger Thread Starting!
[23.11.2012 0:04:24] Yet Another Relogger Version 0.1.7.7
[23.11.2012 0:06:57] Adding new bot: bab
[23.11.2012 0:09:37] Editing bot: bab
[23.11.2012 0:09:37] <bab> We are scheduled to start
[23.11.2012 0:09:37] <bab> Deleting: C:\ProgramData\Battle.net\Agent\agent.db
[23.11.2012 0:09:37] <bab> Language set: Russian : ruRU
[23.11.2012 0:09:37] <bab> Region set: Europe : eu.actual.battle.net
[23.11.2012 0:09:43] <bab> Diablo:4176: Found D3 Main Window (2230338)
[23.11.2012 0:09:44] <bab> Diablo:4176: Waiting for process to become ready
[23.11.2012 0:09:46] <bab> Diablo:4176: Process is ready
[23.11.2012 0:09:46] <bab> Demonbuddy start delay, waiting 10 seconds
[23.11.2012 0:09:56] <bab> Current profile: "00_Gnome_START_HERE.xml" Runs:0 Time:0 mintues (C:\Demonbuddy\profiles\Alkaizer Pure 2.98d RC\00_Gnome_START_HERE.xml)
[23.11.2012 0:09:56] <bab> Checking plugin: C:\Demonbuddy\Plugins\YAR\Plugin.cs
[23.11.2012 0:09:56] <bab> Plugin does not exist
[23.11.2012 0:09:56] <bab> Installing latest plugin: C:\Demonbuddy\Plugins\YAR\Plugin.cs
[23.11.2012 0:09:56] <bab> Demonbuddy:1076: Waiting for process to become ready
[23.11.2012 0:09:57] <bab> Found Demonbuddy: MainWindow (395756)
[23.11.2012 0:09:57] <bab> Demonbuddy:1076: Process is ready
[23.11.2012 0:10:30] <bab> Diablo:4176: Process is not running
[23.11.2012 0:10:30] <bab> Killing Agent.exe:3708
[23.11.2012 0:10:30] <bab> Language set: Russian : ruRU
[23.11.2012 0:10:30] <bab> Region set: Europe : eu.actual.battle.net
[23.11.2012 0:10:36] <bab> Diablo:1240: Found D3 Main Window (460492)
[23.11.2012 0:10:37] <bab> Diablo:1240: Waiting for process to become ready
[23.11.2012 0:10:39] <bab> Diablo:1240: Process is ready
[23.11.2012 0:10:39] <bab> Demonbuddy start delay, waiting 10 seconds
[23.11.2012 0:10:50] <bab> Diablo:1240: Process is not running
[23.11.2012 0:10:50] <bab> Killing Agent.exe:3468
[23.11.2012 0:10:50] <bab> Language set: Russian : ruRU
[23.11.2012 0:10:50] <bab> Region set: Europe : eu.actual.battle.net
[23.11.2012 0:10:54] <bab> Stopping
 
Yea, still having issues with Diablo not logging into account. Damn, I guess I'm not good enough to use this one.
 
Hey, tell me what to do, set up YAR, start a game, but do not enter a name and password, the login screen just hangs, then Db starts and all ...
What to do, why not game logs
Yea, still having issues with Diablo not logging into account. Damn, I guess I'm not good enough to use this one.
Check your password, there should be only numbers and letters, no symbols
 
Check your password, there should be only numbers and letters, no symbols

Yea, I tried doing that since I saw you post a couple of pages ago. Still a no go. For some reason, in the logs, DB thinks I logged in even though I'm still sitting at the login page. No errors, no cautions.
 
My Diablo takes too long to launch in VM and YAR is killing it and restarting it over and over again. Is there some way to increase the kill timer, or do I have to find another relogger?
 
If multiple clients then 1 or 2 freezes starting DB
если несколько клиентов то 1 или 2 зависает запуск DB
 
My Diablo takes too long to launch in VM and YAR is killing it and restarting it over and over again. Is there some way to increase the kill timer, or do I have to find another relogger?

There's an option where you can delay the start of DB. Go on settings -> generall and give him 30 sec for example.
 
Hi,

If i start DemonBuddy when im still at D3 login screen it does not load any plugins. If i start it at character selection it does load the plugins fine.
And as you know YAR starts DB while at login screen so no plugins load.

Tried with a fresh DB install, but same thing. Tried my old versions of DB that i save (i never remove them if i want to go back) and its the same thing on them now and they were working fine...
 
Hi sinterlkaas, I encounter a *small* problem where YAR would close my D3 after detecting it as inactive for about 30 seconds when I am actually clearing inventory/checking the auction house. Is there a way to lengthen the inactivity counter? Also, is there any ETA for when the battlenet Authenticator function will be added?

This is a really great plugin though, keep it up!

Cheers!
 
There's an option where you can delay the start of DB. Go on settings -> generall and give him 30 sec for example.

This does not help. Regardless of how long I set the DB delay it still continuously kills agent.exe and relaunches Diablo after I have a few clients running.

ie.

Diablo:3092: Starting diablo timed out!
Restarting...
Diablo:3092: Kill process
Diablo:3092 Process is not running
Killing Agent.exe:792

etc...


over and over and over again
 
"Automatically updates Communicator plugin to latest version". Whats this mean?
 
Last edited:
YAR crashes right on the start of the program itself..
basicly u can not run it when you have a bot profile with a pw like that in it.
I tried to use & as a password and yar does not crash here :/ did you edit the password with YAR or did you manually edit the XML file for your bots ?

Get this kind of error on one bot. Any suggestions?
Code:
[22.11.2012 23:45:40] <botname> Demonbuddy:5624: Delayed start failed! (10,0400373 seconds overtime)
[22.11.2012 23:45:42] <botname> Demonbuddy:5624: Delayed start failed! (12,3400405 seconds overtime)
[22.11.2012 23:45:45] <botname> Demonbuddy:5624: Delayed start failed! (14,6600437 seconds overtime)
[22.11.2012 23:45:47] <botname> Demonbuddy:5624: Delayed start failed! (17,0400471 seconds overtime)
[22.11.2012 23:45:49] <botname> Demonbuddy:5624: Delayed start failed! (19,3600503 seconds overtime)
[22.11.2012 23:45:52] <botname> Demonbuddy:5624: Delayed start failed! (21,6500535 seconds overtime)
[22.11.2012 23:46:12] <botname> Demonbuddy:5624: Delayed start failed! (0,770027 seconds overtime)
[22.11.2012 23:46:15] <botname> Demonbuddy:5624: Delayed start failed! (3,0700302 seconds overtime)
Could this be cause of loading time?
Does it break the bot?

Yea, I tried doing that since I saw you post a couple of pages ago. Still a no go. For some reason, in the logs, DB thinks I logged in even though I'm still sitting at the login page. No errors, no cautions.
Did you try to increase DB delayed startup time?


My Diablo takes too long to launch in VM and YAR is killing it and restarting it over and over again. Is there some way to increase the kill timer, or do I have to find another relogger?
I will add a option to increase the timeout value

If multiple clients then 1 or 2 freezes starting DB
если несколько клиентов то 1 или 2 зависает запуск DB
Could you explain what exactly happens ? cause this is very little information?

Hi,
If i start DemonBuddy when im still at D3 login screen it does not load any plugins. If i start it at character selection it does load the plugins fine.
And as you know YAR starts DB while at login screen so no plugins load.
Tried with a fresh DB install, but same thing. Tried my old versions of DB that i save (i never remove them if i want to go back) and its the same thing on them now and they were working fine...
DB indeed will not load any plugins when at character selection screen and YAR does not login for you DB does YAR just sends some commandline arguments to DB that will tell DB to login. After that it will initialize the plugins

Hi sinterlkaas, I encounter a *small* problem where YAR would close my D3 after detecting it as inactive for about 30 seconds when I am actually clearing inventory/checking the auction house. Is there a way to lengthen the inactivity counter? Also, is there any ETA for when the battlenet Authenticator function will be added?
This is a really great plugin though, keep it up!
Cheers!
Are you using any other software like isboxer or something ?
There is no ETA for the authenticator

"Automatically updates Communicator plugin to latest version". Whats this mean?
This means when you update YAR it will copy the new plugin to Demonbuddy and use this to communicate during gameplay
 
reposition now not work well for inner space, perfect for default window game :)
its working the profile schedule if I put more than one profile? and other bug i find its, if you write the Max randomization minutes/runs, it dont save
 
As promised, a donation is on its way cause of the added gold afk thingy. Keep on updating, great work so far!
 
Could this be cause of loading time?
Does it break the bot?


I dont think it's because of loading time, because I am logged in. It stays at the screen, where you can go to the AH and continue your game. It always affects the same bot of my 5 bots. If I restart the relogger, everything goes fine.
When I get this error, the DB is working but nothing happens. Sometimes I can see a popup (for less then a second, so I cant read it) in d3 startscreen, where you can continue your game, but from this point DB is unable to continue botting or log you in game. I'll have a look, if I made a mistake when I was configuring DB and let you know.
 
Status
Not open for further replies.
Back
Top