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

Demonbuddy Auto Disables plugin

A

Anova

New Member
Joined
Jun 25, 2012
Messages
38
Reaction score
0
Hi guys,

I've just come home to see the bot dying and reviving for a full 50 minutes non stop. Turns out that Trinity was unticked. Is there any way to make sure it never disables itself like this?

Thanks
 
Has happened several times to me too.

I brought this up a long time ago in support section. Nothing was done and I believe you actually just made fun of it....

Was why I asked for an option to auto-force all plugins on every launch - to exactly avoid the issue with this patch of no increasing deathtimer => hundreds of deahts in no time.
 
The only way this would happen is if you updated the Bot or Plugins. As tony said, the bot does not control the enabling of plugins directly.
 
The plugins are probably outdated/incompatible after you've updated to the new version of the bot.
 
My DB and Trinity have been running fine for at least 4 days before this happened and I can confirm 100% that I was not in the process of updating anything. DB is even set to run with parameter -noupdate.

iwaru said:
Has happened several times to me too.

I brought this up a long time ago in support section. Nothing was done and I believe you actually just made fun of it....

Was why I asked for an option to auto-force all plugins on every launch - to exactly avoid the issue with this patch of no increasing deathtimer => hundreds of deahts in no time.
Click to expand...

I remember LOOONG time ago people had a trick of making the settings file read only or something, to effectively force all plugins to always run at startup, but I'm not sure if this is good practice.

Tony said:
DB cant disable your plugins
Click to expand...

Do you have any ideas on how to ensure this does not happen again?
 
I usually check if my plugins are checked after a crash of d3/db . Sometimes they are off after a crash.
 
d0rian said:
I usually check if my plugins are checked after a crash of d3/db . Sometimes they are off after a crash.
Click to expand...

This is only possible if you are manually babysitting. If you have a relogger, it will take care of crashes etc, but leave you vulnerable for the "disabled plugins" problem.

Would I be able to see plugins being disabled or enabled in the log files?
 
I am not using any reloggers ...yes. I use crashes as a way to simulate real human behaviour. Supervising in like 4 hours gaps.
 
There is this "force enable all plugins" function in YAR, which helps.
 
My occurrences of this bug do not correlate with updating either DB or Trinity - it simply just happens and it is actually quite disconcerting.
Would STILL love some kind of "force-enable" like YAR directly built into DB - why do you think it was made for YAR in the first place? => There is a demand for it.
 
iwaru said:
Would STILL love some kind of "force-enable" like YAR directly built into DB
Click to expand...

Can we get a comment from the Dev team / moderators regarding this. I see this as a bug and not a feature request.
 
You must log in or register to reply here.
Back
Top