What's new
  • Visit Rebornbuddy
  • Visit Panda Profiles
  • Visit LLamamMagic
  • Visit Resources
  • Visit Downloads
  • Visit Portal

Trinity 1.7.3.3

Status
Not open for further replies.

rrrix

New Member
Joined
Jul 11, 2010
Messages
3,449
Reaction score
61
Download Trinity 1.7.3.3

[h=3]Changelog 1.7.3.3[/h]
  • Added SpellTracker class - this can be used to track timed spells (like DoT's) without having to use DOTDPS Actor Attribute. This as added as the WitchDoctor
  • WitchDoctor Haunt is no longer spammed, but used after the duration of the DoT spell has expired
  • Cleaned up ItemRules Identification logging
  • Fixed incorrect reference to Target ACDGuid (Was RActorGUID)
  • Removed Demonbuddy Version check (also fixes crash when starting with renamed .exe)
  • Barbarian will now use HOTA on elites when available
  • PreTownRunPosition now checks to make sure we're not in town
[h=3]Changelog 1.7.3.2[/h]
  • Removed 2f distance check for ignoring trash mobs
  • Fixed WOTB Fury Dump
  • Added Barbarian options for Ignore Avoidance in WOTB, and Ignore Gold stacks in WOTB
[h=3]Changelog 1.7.3.1[/h]
  • Fixed all references to AbilityLastUsedCache (Monk combat works again)
  • Fixed picking up white items
 
From the old thread...

im also having a problem with not picking up legendaries, and not real sure why... but its a fairly big concern.

pretty much all of them lose legendaries and some are upwards of 50% of ilvl63 which is a huge deal. i'm not sure why its happening... ive got some running on base new trinity and some running with fluffy's combat edit and they both do it.

ilvl63's
10 drop / 6 pickup
14 drop / 8 pickup
9 drop / 8 pickup
17 drop 12 pickup
etc

these were short logs and if they run longer it evens out somewhat, but there is still a decently high % of missed legendaries. maybe it has to do with avoidance / kiting.

its not an item rules thing and its not a ilvl 58 legendary thing... it misses 63's and its not due to deaths ALL the time. sometimes it will just finish the pack and just run off and leave it on the ground. I knew it was bad when i noticed it happening 3 times over the course of a few hours but I hadn't checked logs till now.

i dont really care about rares or < ilvl62's but 62+63's must not be missed if at all possible. losing 30-50% of ilvl 63's almost negates the whole purpose of running high end characters =(.

is there something i dont know of? is it a profile problem? (act 2 oasis) or settings i need to change somewhere?


my bots dying to elites cause of trash rules (almost never die other than this), skips legendaries at times, and my barbs still stutter step to dump rage. these are the things im having problems with atm. still puts out better numbers than previous trinity tho =)

Run with the default soft or hard rules and reproduce this, please. I'm guessing it's your item rules.

If not, then can you:

Enable "Log dropped items" (in Trinity Advanced tab)
Tell me which profile, character class, build, and monster power you're using
how many deaths per hour do you have?
 
From the old thread...



Run with the default soft or hard rules and reproduce this, please. I'm guessing it's your item rules.

If not, then can you:

Enable "Log dropped items" (in Trinity Advanced tab)
Tell me which profile, character class, build, and monster power you're using
how many deaths per hour do you have?

The item rules I use only culls lvl 58 legendary. those numbers i posted are strictly ilvl63 (it happens to 62/61 also but didnt post those). Its not a certain item or items, nor is anything to do with level. It doesnt discriminate vs ilvl or slot or set vs legendary. It just simply sometimes ignores legendaries on floor.

act 2 oasis / mp10 / barb / no generator rend, ww build.

all base trinity files, no "fixed" combat etc.

Some of them are deaths, but some of them are not deaths. I've seen them do it multiple times. they just run off and leave the legendary on the ground until i force them to return to it and then they pick it up. if i do not force them to return to the legendary they just continue running and leave it.

does profile legendary loot radius supersede trinity/db loot radius? that was 1 of my ideas.. the bot is focused on creating a safe path to loot legendary but gets to far away due to to many mobs and then is out of range?

I cut off avoidance and it seems to help a fair bit? maybe it has something to do with range or something over riding the legendary loot rules such as not dying.

Is is possible / practical to force the use of ww to pick legendaries as long as fury permits? just an idea I had.
 
Enable the dropped items log - it will tell me what was missed and why :)
 
Hello !
Ok i have a question is there any way to decrease sprint spam speed that would be rly helpfull for me. And i read alot about problem with picking up items when there is last slot in inventory i had the same problem and adding protected bag slots on that last slot fixed that issue.
 
Can anyone tell me, why with DB game loads ~5x slower then usual, if i press "resume game" its 1-2 seconds when in game, if DB resumes game, its like 5-7 seconds.. ?
 
Can anyone tell me, why with DB game loads ~5x slower then usual, if i press "resume game" its 1-2 seconds when in game, if DB resumes game, its like 5-7 seconds.. ?

What does it have to do with Trinity?
 
Rrrix,

I've been monitoring it for an hour and can confidently say that its a beaut! Works like a charm and haven't seen any huge issues. I'm running a hybrid Barb (HOTA/WW/Rend) and it uses each skill perfectly under different conditions.

Kudos!

EDIT: Just some constructive observations regarding the use of HOTA vs. elites:

I find when the Barb faces more than one elite, it will HOTA one target a few times and then WW onto another target - then proceed to HOTA the next target. I find that when targeting elites it would be far more efficient to just spam HOTA until said elite is dead, instead of WWing between the targets and HOTAing. Let me know if this doesn't make sense. I can go into more detail if you're interested. Again, great works and thanks for this.
 
Hello rrrix and other posters. This is my first post and I have a few questions for botting with my witch doctor

Since the last update to trinity, using firebats has become a more plausible option (great work man!). However, when I try to use locust swarm to aggro mobs, she casts it far to often, enough to run me out of mana, or screw up the firebats channelling. I've searched around and tried switching the location of the skill around, but it's still too much. Any advice on what I can do?

1 other thing is spirit walk, is there any way to set it so she uses it when low on mana? I had to turn off the use speed skills tab because she doesn't use it to avoid cc or regen mana as often (cool down off, low mana/big cc incoming, still doesn't use). Can I set it so she uses it at a certain % of mana?

Thanks for all the work you've put into these updates. Me and many others appreciate all you've done. I wouldn't be playing this game if it wasn't for these sweet updates!

Any other tips or settings/builds you can share to maximize my witch doctor would be awesome as well
 
Rrrrix,

I've made a video trying to show what I was talking about:

[video=youtube;_p0Q_LTA6p8]http://www.youtube.com/watch?v=_p0Q_LTA6p8&feature=youtu.be[/video]

I know it may be a bit pedantic but loving the new update regardless!
 
constantly getting this

[00:34:07.353 N] System.OutOfMemoryException: Exception of type 'System.OutOfMemoryException' was thrown.
at System.Collections.Generic.List`1.set_Capacity(Int32 value)
at System.Collections.Generic.List`1.EnsureCapacity(Int32 min)
at System.Collections.Generic.List`1.Add(T item)
at Zeta.Pathfinding.PathFinder.FindPath(Point startPoint, Point endPoint, Boolean includeDiagonals, Int32 maxMilliseconds, Boolean allowPartialPaths)
at Zeta.Navigation.DefaultNavigationProvider.(Vector3 , Boolean , Single )
at Zeta.Navigation.DefaultNavigationProvider.(Vector3 , String , Boolean )
at Zeta.Navigation.DefaultNavigationProvider.MoveTo(Vector3 destination, String destinationName, Boolean useRaycast)
at Zeta.Navigation.Navigator.MoveTo(Vector3 destination, String destinationName, Boolean useRaycast)
at Trinity.DbProvider.PlayerMover.NavigateTo(Vector3 moveTarget, String destinationName)

have a fresh DB and Trinity

and when it errors like that it lags the game and bot and usually i die lol
 
constantly getting this

[00:34:07.353 N] System.OutOfMemoryException: Exception of type 'System.OutOfMemoryException' was thrown.
at System.Collections.Generic.List`1.set_Capacity(Int32 value)
at System.Collections.Generic.List`1.EnsureCapacity(Int32 min)
at System.Collections.Generic.List`1.Add(T item)
at Zeta.Pathfinding.PathFinder.FindPath(Point startPoint, Point endPoint, Boolean includeDiagonals, Int32 maxMilliseconds, Boolean allowPartialPaths)
at Zeta.Navigation.DefaultNavigationProvider.(Vector3 , Boolean , Single )
at Zeta.Navigation.DefaultNavigationProvider.(Vector3 , String , Boolean )
at Zeta.Navigation.DefaultNavigationProvider.MoveTo(Vector3 destination, String destinationName, Boolean useRaycast)
at Zeta.Navigation.Navigator.MoveTo(Vector3 destination, String destinationName, Boolean useRaycast)
at Trinity.DbProvider.PlayerMover.NavigateTo(Vector3 moveTarget, String destinationName)

have a fresh DB and Trinity

and when it errors like that it lags the game and bot and usually i die lol

Restart your D3, it should go away. I see this when I restart the bot often and re-attach to the same game session many times.
 
same problem here using db 315
restart do not help fix the OutOfMemoryException
 
rrrix I fired this up and the problem I had launching via cmdline in .3.2 is gone. Don't know whether you fixed this or if its just a coincidence, but thanks alot! I was worried me and my .bat files would be stuck with .13 forever.
 
I have a problem where the bot isn't picking up demonic essences, its skipping over them? not sure whats going on.
 
Wonderfully done rrrix! Could you please also write working keyrun and uberrun plugins and profiles for this version? :)
 
in this version of the Trinity, my barbarian often began to die because of that that was rarely use with bloody wounds to heal the rune
faced with this? You can fix this somehow?

в этой версии Тринити, мой варвар начал часто умирать из-за того что стал редко пользоваться Кровавыми Ранами с руной на отхил
сталкивались с этим? можно это как-то исправить?
 
Erk242, я тоже это заметил и решил, что это связано с настройками боевой системы. В переменных вот что нашел.

"Barbarian.Rend.MinUseIntervalMillseconds int 1500 Cast rend when this many mobs surrounding are not bleeding 1500 1500 False "

Похоже установлен минимальный кулдаун для каста ренда.
 
Wonderfully done rrrix! Could you please also write working keyrun and uberrun plugins and profiles for this version? :)
Did you test keyrun plugin?
If I recall correctly, with previous version Rrrix posted updated keyrun file and made point that it should work with every future version because of changes he made in code.
But I may be mistaken...
 
Status
Not open for further replies.
Back
Top