What's new
  • Visit Rebornbuddy
  • Visit Panda Profiles
  • Visit LLamamMagic
  • Visit Resources
  • Visit Downloads
  • Visit Portal

Arelog never logs me into D3

Cukie

Active Member
Joined
Dec 3, 2011
Messages
1,255
Reaction score
3
As the title says, it never logs me into D3. I have tried everything I can think of. I am going to attach pictures and logs of everything, and maybe someone can help me out with whatever I am doing wrong....I have tried every variation on times possible in the scheduler, from 0-9866 hours, and the same thing for number of runs.
Management.webp task management.webp Manage.webp
 

Attachments

it logs in when you start demonbudd bot, ie click start on demonbuddy window when it opens and it should start loggin you in, or just check the option in Arelog to autostart.
 
It logs into DB, but never goes any further than that, and as you can see from my pictures, Autostart is checked.
 
oh yes sorry didn't pay attention, thats weird because it works fine for me. Do you use any remote control programs?
 
Teamviewer when needed, but not very often.
 
try loading without teamviewer turned on on the PC, i use it too and it used to screw with my arelog.
 
Arelog is not relogging you in once you DC. Pretty sure tony said it was not fixed yet.
 
i have the same issue, also it does not do its job when we get a crash =/
 
I have found my issue I believe. AGB does not seem to play well with Arelog. The AGBLoader.xml file does not load up for some reason....
 
We need a relogger! Please guys! :(((
I have the same problem as Tbboltzz and everyone else...
 
Arelog is the DB relogger

Except it's not working properly!

As i have mentioned in another thread it doesnt work for me either. It starts up D3 and then waits for the d3 process to become idle (thats what it says in the log). This however is either not detected properly or is never the case in the first place (despite d3 window is up and ready in <5 seconds). Thats why the login is not happening for me... same thing if you start db with command line settings (timeout after 20s because d3 window is not idle).
System is Windows 7, compatibility features are beeing used.
 
Arelog is the DB relogger
Did you even bother reading this thread before replying with such a stupid reply? Do you even read these forums? Arelog is SHIT for DB....MANY MANY people have problems with it, it is not just a few.....

Quite honestly, If Arelog logged into D3 FIRST, like it does with WoW, and not trying to log into DB first, all these issues with AGB and Arelog would go away. Why in the hell was it designed to log into DB first? What possible advantage is there by doing this? It only causes problems and is fucking stupid to begin with....
 
Last edited:
Did you even bother reading this thread before replying with such a stupid reply? Do you even read these forums? Arelog is SHIT for DB....MANY MANY people have problems with it, it is not just a few.....

Quite honestly, If Arelog logged into D3 FIRST, like it does with WoW, and not trying to log into DB first, all these issues with AGB and Arelog would go away. Why in the hell was it designed to log into DB first? What possible advantage is there by doing this? It only causes problems and is fucking stupid to begin with....

I totally agree with this. Furthermore this is a really easy fix since they just have to move two functions so it logins first and then starts DB.
 
Did you even bother reading this thread before replying with such a stupid reply? Do you even read these forums? Arelog is SHIT for DB....MANY MANY people have problems with it, it is not just a few.....

Quite honestly, If Arelog logged into D3 FIRST, like it does with WoW, and not trying to log into DB first, all these issues with AGB and Arelog would go away. Why in the hell was it designed to log into DB first? What possible advantage is there by doing this? It only causes problems and is fucking stupid to begin with....

you can make your own relogger if you think that Arelog is shit
or you can make a proper bug report

also if you find my replies stupid dont bother to ask for support again
 
why can't you built-in relogger ( like relog when d3 crashes or dc from server or internet at certain interval of times) in db? it seems not that difficulty at all, right? and the point about making a plugin relogger like Tony, it just may causes bugs later when everytime db update.
 
If they just FIXED Arelog so it DOES NOT log into DB BEFORE logging into the game it would fix a TON of peoples issues that are using Plugin based profiles. Log into D3 THEN log into DB. Not the other way around.....


EDIT:
Also, with it done the correct way, it would also help out the people with slow computers and D3 not loading within 20 seconds, SINCE D3 WOULD ALREADY BE STARTED when trying to launch DB!
 
Back
Top