I mean a friend can join the game without the request.
return new TrinityPower(SNOPower.Witchdoctor_Sacrifice, 5f, vNullLocation, CurrentWorldDynamicId, -1, 1, 2, WAIT_FOR_ANIM);
Rrrix, I would like to make small request.
We already have option to force barb to use WOTB only on hard elites. However if this option is unchecked bot will use WOTB every time it's off cooldown.
Is it possible to add in some not so far future option that will force bot to use this skill only on elites and not on trash mobs?
Something like:
Would be really great to have such feature
- Use WOTB on elites only
- Use WOTB on hard elites only
- Use WOTB when it's off cooldown
![]()
Good to know it depends on amount of mobs. However, at current density of mobs at Weeping Hollow it looked like bot used it every time he couldSounds reasonable. P.S. It's not every time it's off cooldown, it's just when certain trash mob thresholds (e.g. certain # in a given area) are met - so maybe that needs an adjust-ability option as well.
this version of trinity uses threatening shout in fights very very seldom ( although its available the whole time ) before patch, i had version 1.7.2.1 ( this version was perfect in terms of spamming shouts in fights & out of fights ( it didnt have a seperate option for threatening shout, which wasnt necessary anyway))
maybe you can have a look into that, thank you so much for ur great work![]()
Download Trinity 1.7.1.12
Known issues:
Changelog 1.7.2.12:
- DH Sentry Turrent still does not work, appears to be DB bug
- Users still reporting "missing loot" - please enable all trinity advanced logs and attach your log file to the Trinity release thread
- Tuned combat for WD Zero Dogs
- Fixed bot start non-Trinity routine warning
- Fixed LoS exception bug
- Added a few more boss SNO's for questing
- Added a shit ton of safety checks to help prevent crashes
- Hopefully fixed Barbarian Bash (e.g. Non-WW) specific targets
- Added Zero Dogs GUI option/logic for WD
- Small tweaks for Barbarian IsWaitingForSpecial + WW - should fix "Barbarian Bashing Elites" bug
- Fixed error in removing object from generic cache
- Added N00b check for running Trinity with any other non-trinity combat routine
Special note to QuestTools users experiencing crashes - make sure to grab the latest from my A3 profiles thread. It does require the latest Demonbuddy BETA.
Hello Rrrix, i wanna know if missing loot dont occur with you? is not possible that this is just me. I already tried putting the log on the website but will not, is loading forever and not complete.
But I can not believe this does not happen to you rrrix... MISSING LOOT
Hello Rrrix, i wanna know if missing loot dont occur with you? is not possible that this is just me. I already tried putting the log on the website but will not, is loading forever and not complete.
But I can not believe this does not happen to you rrrix... MISSING LOOT
can we do smthing with avoidance against poison flowers A1?
because its sucks
@rrrix I am having a problem with a fresh install. Everytime I try to load the script rules The Bot closes. heres the log and I appreiate any help.
[16:52:24.576 N] DemonbuddyBETA v1.0.1407.207 started
[16:52:26.144 N] Logging in...
[16:52:26.824 N] Attached to Diablo III with pid: 7592
[16:52:26.862 N] Flashing window
[16:52:27.822 D] Executable Path: C:\Users\Dad-1\Desktop\DB-Beta-207\Demonbuddy.exe
[16:52:27.822 D] OS Architecture: AMD64
[16:52:27.824 D] OS: Windows 7 Service Pack 1 64-bit
[16:52:27.824 D] OS Language: English (United States)
[16:52:27.858 D] Reloading AssemblyLoader<Zeta.Common.Plugins.IPlugin> - Initializing plugins
[16:52:30.246 D] There are 1 plugins
[16:52:39.994 V] [Trinity]Using Trinity Unstucker
[16:52:40.020 V] [Trinity]Reset bot TPS to default
[16:52:40.021 N] [Trinity]ENABLED: Trinity v1.7.2.12 now in action!
[16:55:21.358 V] [Trinity]Reset bot TPS to default
[16:55:21.358 V] [Trinity]Using Trinity Unstucker
Yes, it's just you. I haven't seen anyone else except you and quadrotony reporting this over and over.
If it happened to me I would fix it.
Since I can't see your full debug logs, and I can't reproduce it, that means i have absolutely NO idea what is causing *you* to have this problem, and that means I can't fix it.