Elandal
New Member
- Joined
- Aug 6, 2014
- Messages
- 338
- Reaction score
- 1
What profile(s) do you use with this?
This is the profile. It's built-in.
What profile(s) do you use with this?
This is the profile. It's built-in.
timeoutType="Timer" timeoutValue="240"
you can find this and increase timeoutValue
I have a feeling a lot of people will notice the issues you mentioned if they watch it for longer than 5 minutes. It's a nice plugin and profile but it is still very buggy.Currently using trinity 2.5.2 / questtools 3.4.4 / and tweaked with the fix by dbmaz on page 3,
running with DH rain/strafe build, on T6 with all kill mode, it's working fine for me.
The only problem I seem to have is sometimes after a warden kill, it fails to recognize it and still keeps on exploring the map for a while before loading the next act's profiles. A little decrease in proficiency but does no harm overall.
Thanks dbmaz for the fix!
EDIT: after supervising for a while, I also noticed sometime the bot will not loot A2 warden's key. I do not have a log but I think it's conflicting with the wait timer on TP. I will try to increase wait time after drop and see if it'll fix this.
EDIT2: Also noticed that after the bot killed A3 warden and successfully looted the key, it treated the run as using A4 profile, and then did a rerun of A3 but skipped A4 (which hasn't been ran yet). However the key drop credit goes to A3 in the plugin interface all right.
Currently using trinity 2.5.2 / questtools 3.4.4 / and tweaked with the fix by dbmaz on page 3,
running with DH rain/strafe build, on T6 with all kill mode, it's working fine for me.
The only problem I seem to have is sometimes after a warden kill, it fails to recognize it and still keeps on exploring the map for a while before loading the next act's profiles. A little decrease in proficiency but does no harm overall.
Thanks dbmaz for the fix!
EDIT: after supervising for a while, I also noticed sometime the bot will not loot A2 warden's key. I do not have a log but I think it's conflicting with the wait timer on TP. I will try to increase wait time after drop and see if it'll fix this.
EDIT2: Also noticed that after the bot killed A3 warden and successfully looted the key, it treated the run as using A4 profile, and then did a rerun of A3 but skipped A4 (which hasn't been ran yet). However the key drop credit goes to A3 in the plugin interface all right.
Damn I will have to watch it for a while then, but what is the ideal amount of keys you should have because this morning after waking up (about 8 hours) I had 20 of each key so that's 5 runs. Is that good? Or you think it's still skipping keys?
That sounds great in my book considering they don't always drop a key.
I have gotten 100+ of each MACHINE from this plugin/profile... that's 400+ of each key... I am not sitting here saying that it sucks at all. All I am saying is if you watch it, despite all the keys it does get you, it does some weird buggy shit no matter what db version or setting you use. I have spent 10+ hours configuring and tweaking to optimize this plugin. I have just accepted that it will be 10-20% less efficient than it could be if it never bugged out.yeah im up to 32 of each now and that's only because I took a break earlier so I really don't see how people are having problems I will attach my files.
1) I use trinity 2.8
2) Demonbuddy version standard version 1.1.2273 build 404
yeah im up to 32 of each now and that's only because I took a break earlier so I really don't see how people are having problems I will attach my files.
1) I use trinity 2.8
2) Demonbuddy version standard version 1.1.2273 build 404