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

[STANDALONE]DBRelogger

adessis said:
Will try a fresh install.
Weird thing is that this one was fresh as well.
Click to expand...
From ur log agb is running demonbuddy tales 15-30 seconds to kick in after the relogin try to start it up wait a minute or two and tell me if it didnt start
 
adessis said:
Nice relogger, actually really like it.

Running V0.02 now, and come across a few bugs. This might be on my end, but i'll post it anyway:
Relogger logs in DB and D3, then waits in character select screen and does not join game. AGB plugin is enabled.
Log:

edit: manually clicking stop on DB and start after that fixes this.
Click to expand...

just add the plugin autoclickok
 
gawdz said:
I will check to see if db takes a pid parameter if it does then its an easy fix if not then it wont be possible for now
Click to expand...
i know it takes windowtitle as an attach parameter, though i have no idea how to change the windowtitle for an application.
 
gawdz said:
From ur log agb is running demonbuddy tales 15-30 seconds to kick in after the relogin try to start it up wait a minute or two and tell me if it didnt start
Click to expand...

Waited for 5 minutes, doesn't start. Funny thing is, with AGB plugin disabled it does actually start the game like its supposed to, but then doesn't move because the plugin is diabled ofc.
EDIT:
tesslerc said:
just add the plugin autoclickok
Click to expand...

Thanks Tesslerc, this works!


Also found another bug regarding region selection:
Select "Force Select Region", click a region and make profile. When you edit this profile and you click "Force Select Region" again, and select the same region as before you get this error:

uDh0S.png


Sometimes the edit profile window duplicates after this and/or the profile gets duplicated.
 
Last edited:
adessis said:
Waited for 5 minutes, doesn't start. Funny thing is, with AGB plugin disabled it does actually start the game like its supposed to, but then doesn't move because the plugin is diabled ofc.
EDIT:


Thanks Tesslerc, this works!


Also found another bug regarding region selection:
Select "Force Select Region", click a region and make profile. When you edit this profile and you click "Force Select Region" again, and select the same region as before you get this error:

uDh0S.png


Sometimes the edit profile window duplicates after this and/or the profile gets duplicated.
Click to expand...
Thanks for the report will fix this later.
 
Just to give you a heads up, last night after d3 crashed, it logged back in just fine, but never resumed game. it sat at that screen all night long. over 11.5 hours, i made 750k gold lol. Just a question, but why does your relogger work the same as Arelog and log into the bot first? There is obviously an issue with DB and plugin based profiles. Why not log completely into D3 before booting up DB? Like HB and WoW work. This would absolutely get rid of this issue
 
Tbboltzz said:
Just to give you a heads up, last night after d3 crashed, it logged back in just fine, but never resumed game. it sat at that screen all night long. over 11.5 hours, i made 750k gold lol. Just a question, but why does your relogger work the same as Arelog and log into the bot first? There is obviously an issue with DB and plugin based profiles. Why not log completely into D3 before booting up DB? Like HB and WoW work. This would absolutely get rid of this issue
Click to expand...

I had a problem like this, installing notificationOKclicker plugin fixes this!
 
adessis said:
I had a problem like this, installing notificationOKclicker plugin fixes this!
Click to expand...
[09:41:46.882 N] [NotificationOKClick Plugin0.9] Warning ! NotificationOKClick thread is not working!!! This is what i get with using notificationokclicker. It has not worked for me in like the last 4-5 DB updates
 
Also something i would like to add regarding performance when windows are tiled:

My processor is an intel i5 2500k, ran it stock for testing. Tested with 4 clients/DB.

Without tiled windows/relogger (Taken from W7 resource manager):
Max frequency processor: Always 100%
Highest processor usage: usual 45%, but with very regular spikes up to 100%.

With tiled windows/relogger (Taken from W7 resource manager):
Max frequency processor: ~55
Highest processor usage: 40%


The setup is exactly the same for everything but the relogger used or not used. Only difference is that when i run the clients without tile they are set to windowed mode, not windowed fullscreen.
Needles to say performance with tiled windows is much better for me.

might even turn out this fixes most of the crashes i was having anyway! :P
 
Last edited:
@OP
1. Can you try to set up with isboxer, you can get trial for free 7 days and test it out and use relogger with it?
2. You may want add autoclick notification for this. (It may be a better choice because it less buggy to use many other plugins together with relogger, don't ya think?
3. What is lowest resolution for this window resize?


P/S: What your LOL IGN yo? hit me up some games xD we can have fun
 
Tbboltzz said:
Just to give you a heads up, last night after d3 crashed, it logged back in just fine, but never resumed game. it sat at that screen all night long. over 11.5 hours, i made 750k gold lol. Just a question, but why does your relogger work the same as Arelog and log into the bot first? There is obviously an issue with DB and plugin based profiles. Why not log completely into D3 before booting up DB? Like HB and WoW work. This would absolutely get rid of this issue
Click to expand...
please download the new version i updated and should of fixed it.
 
Did some testing, if you run multiple region instances it fails.
Let's say I run EU first and then a US account(*), it bots and all is fine, until EU crashes.
It seems like when it tries to log back on, it forgets about region and logs on US, since US was the last(*).
Is this just me?
 
Daydreamer said:
Did some testing, if you run multiple region instances it fails.
Let's say I run EU first and then a US account(*), it bots and all is fine, until EU crashes.
It seems like when it tries to log back on, it forgets about region and logs on US, since US was the last(*).
Is this just me?
Click to expand...

It works for me, i thought it crashed just now and it wouldn't log in again. Then i discovered US was actually down lol.
 
You must log in or register to reply here.
Back
Top