GilesSmith
New Member
- Joined
- Jun 2, 2012
- Messages
- 1,564
- Reaction score
- 34
Anyone launching DemonBuddy from command-line (eg with shortcuts, .bat files, or certain methods employed by some auto restarters/reloggers), will currently find that if there are a lot of plugins, or plugins that need re-compiling by DB, or plugins that are a bit more complex and take more than a brief millisecond to load... that those plugins will screw up and not be running properly because DB will start to run the routine before all plugins have been loaded. At least this is what I and many users have observed - the technical causes may be different but those are symptoms.
If DB could ensure that a routine is never run (and the "start" button is greyed out to prevent manual-starting early) until ALL plugins have been loaded, this should fix it completely.
If that's not possible, then at the very minimum could a command-line parameter be added to delay DB after launch before it starts any routine, so people can add to their command-lines a forced delay to allow plugins time to load.
Edit: Some people also reported that plugins don't get loaded if you launch DemonBuddy while Diablo 3 is on the login screen. I haven't confirmed this myself.
If DB could ensure that a routine is never run (and the "start" button is greyed out to prevent manual-starting early) until ALL plugins have been loaded, this should fix it completely.
If that's not possible, then at the very minimum could a command-line parameter be added to delay DB after launch before it starts any routine, so people can add to their command-lines a forced delay to allow plugins time to load.
Edit: Some people also reported that plugins don't get loaded if you launch DemonBuddy while Diablo 3 is on the login screen. I haven't confirmed this myself.
Last edited: