I think in order to be safe to bot....

[thegosu]

We need a profile randomizer.

Something that allows DB to rotate between sarkoth/core and another type of gold farming profile RANDOMLY.

So that it's completely random and you're not running one thing over and over. DB is undetectable... otherwise if it was there'd be alot more than 7 pages worth of ban reports...

There needs to be some kind of profile randomizer so that you can do sarkoth runs... then randomly quest switch to something else and continue botting.

Everything has to be random.

That's just my input at least.

 

[Sko]

They are already working on implementing this.

 

[MuffStuffer]

I am starting to wonder if some of you guys are blind. Look around and you will see many plugins for this. Here is one for example

http://www.thebuddyforum.com/demonb...ol-antiidle-profile-scheduler-capability.html

 

[thegosu]

I am starting to wonder if some of you guys are blind. Look around and you will see many plugins for this. Here is one for example

http://www.thebuddyforum.com/demonb...ol-antiidle-profile-scheduler-capability.html

I have this never tried it to a full potential though, with full randomizing aspects.

 

[stevelulwow]

Sark for any amount of time right now wouldn't be very smart, profile switching or not... There are few that are still running 24/7 or as they say... Hard to believe right now.

 

[momo1029]

yea, profile restarter does the trick
randomize profile

 

[RouXXX]

I am starting to wonder if some of you guys are blind. Look around and you will see many plugins for this. Here is one for example

http://www.thebuddyforum.com/demonb...ol-antiidle-profile-scheduler-capability.html

IMHO, the mass public shouldn't have to depend on the nice, *giving* few in the community that decide to share their 'fixes'; nor should we have to spend hours researching whats crap/legit.
I believe that this, along with a large amount of selectable profiles should be somewhat supported by DB by itself.

Right now, the community is responsible for a large void (imho) in this bot program - considering the circumstances.
The problem with this, is that a large section (to make the bot work as intended) is unregulated, unmonitored, and unsupported.

Hell - there are a FEW GOOD plugin/profile creators that do/has done a helluva lot for DB. If it wasn't for them, we would still be running into walls in Core, making 300GPH MAX. <-put them to work, DB.