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

[DEMAND] Initialize plugins before logged in!

And you ASSUME the WORD DEMAND is going to get you anywhere? Try to be decent and open a topic for the Devs. Maybe then you will see a change.
 
+1

This is more of a need to solve authenticator issues. We shouldn't have to disable authenticator just to use DB to relog.
 
d3welty said:
And you ASSUME the WORD DEMAND is going to get you anywhere? Try to be decent and open a topic for the Devs. Maybe then you will see a change.
Click to expand...

This has been requested way too many times and it's sad that it gets no attention for months.
So yes seeing as many basic core functions don't work due to this, I believe I am speaking in the name of all the customers
 
+1 to the request, not the demand.

But seriously, it would solve a lot of problems
 
Pretty sure this has already been answered with a big 'no' from the top over on the dev forum. Think about it, how long would it take for someone to make a plugin that circumvents the DB login phase? Free DB for all :P
 
Rakurai said:
Pretty sure this has already been answered with a big 'no' from the top over on the dev forum. Think about it, how long would it take for someone to make a plugin that circumvents the DB login phase? Free DB for all :P
Click to expand...

how would that happen the key request is the very first thing.
 
Rakurai said:
Pretty sure this has already been answered with a big 'no' from the top over on the dev forum. Think about it, how long would it take for someone to make a plugin that circumvents the DB login phase? Free DB for all :P
Click to expand...

It has already been done numerouse site are posting a *****ed DB.
 
please DB developers, give an answer - thanx!!

tesslerc said:
http://www.thebuddyforum.com/demonb...compile-init-before-db-logged.html#post655954

This is like half a year ago!

PROS if initialized prior to login:

1. Enter authenticator
2. Answer secret question
3. Accept EULA changes and crap like that
4. Don't send trillions of login requests when server down / maintaince / some other error.


This is a must!!!
Click to expand...

+1 to the request.


There seems to be a misunderstanding:
it is not that DB should do anything before DB-key validation.
It is that the plugins should be compiled and run before Diablo-3 login is started.
That is quite a difference.

Please read the link above, from the developer forum (only 2 pages):
It has already been admitted that "This shouldn't have been like this in the first place!".
And it has even been told as fixed some posts below that.

And yes, there is a 'demand', in the sense of "market for sth." ;)
Because many DB users would like to use an authenticator - with good support from DB. :D
And the most work is already done with .e.g. radsatom and winauth;
it is too sad that those plugins won't get executed in time!


BR ?Golem
 
uGolem said:
+1 to the request.


There seems to be a misunderstanding:
it is not that DB should do anything before DB-key validation.
It is that the plugins should be compiled and run before Diablo-3 login is started.
That is quite a difference.

Please read the link above, from the developer forum (only 2 pages):
It has already been admitted that "This shouldn't have been like this in the first place!".
And it has even been told as fixed some posts below that.

And yes, there is a 'demand', in the sense of "market for sth." ;)
Because many DB users would like to use an authenticator - with good support from DB. :D
And the most work is already done with .e.g. radsatom and winauth;
it is too sad that those plugins won't get executed in time!


BR ?Golem
Click to expand...

+ 1
Preach on man.
 
uGolem said:
+1 to the request.


There seems to be a misunderstanding:
it is not that DB should do anything before DB-key validation.
It is that the plugins should be compiled and run before Diablo-3 login is started.
That is quite a difference.

Please read the link above, from the developer forum (only 2 pages):
It has already been admitted that "This shouldn't have been like this in the first place!".
And it has even been told as fixed some posts below that.

And yes, there is a 'demand', in the sense of "market for sth." ;)
Because many DB users would like to use an authenticator - with good support from DB. :D
And the most work is already done with .e.g. radsatom and winauth;
it is too sad that those plugins won't get executed in time!


BR ?Golem
Click to expand...
The request said "plugin compile + init before DB is logged in". I assumed that was what the OP meant.
 
I would like it also. A LOT. Please think about how to do it and do it. It will helps so many problems on both sides :(.
 
Urgent!

Bumping because it needs attention! Just had 1 account locked out from blizzard due to it trying to relog over and over and over. It was asking for the security question/answer and trying to repeat it again.

This this how it currently is, which is broken in my eyes:
1. Authenticate DB
2. Log in Diablo account
3. Check for account/character info and load character settings
4. Initialize all plugins
5. Start bot.

How hard is it to change to:
1. Authenticate DB
2. Initialize all plugins / Or add an option for shortcut commands to initialize selected plugins first only (for example -plugin "relogger" / or -plugin "relogger,securityplugin,authenticatorplugin")
3. If -plugin is used, do not -autostart because the plugin(s) should log in for you, but if -plugin is not used, -autostart and Log in Diablo account like normally
4. Check for account/character info and load character settings
5. Re-Initialize plugins (in-case there are plugins that need the character's info/battletag info for it to work properly, but if -plugin is implemented, this would just initialize the remaining plugins instead of all)
6. Start bot.

At least the second method can prevent what I just experienced and also fix all the relog issues and authenticator problems.

Why is this soooo hard to achieve :mad:

Edit: DB will still be authenticating first for valid keys so there won't be any privacy concerns if that's the problem.
 
Last edited:
You must log in or register to reply here.
Back
Top