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

GilesTrinity 1.6.3.2: some fixes/changes

bombastic

New Member
Joined
Jun 18, 2012
Messages
430
Reaction score
3
GilesTrinity 1.6.3.4: some fixes/changes

1.6.3.4 v3 changes:
-- Overpower cast doesn't interrupt whirlwind anymore;
-- More fine tunning for berserk activation;
-- Threating shout used no matter what, if berserk is ready to cast and low fury;
-- Berserk activated if chasing a goblin and there's a elite nearby.

1.6.3.4 v2 changes:

-- Berserk should be correctly activated now; (but if you use berserk with the new cooldown shrine trinity will not detect the new cooldown, and berserk will still be used only after 2 minutes. I'll test something and will report later)
* To Giles: powerPrime.powerThis didn't work. I had to revert bWaitingForSpecial in both ww out-of-combat "IF blocks".
-- Threatening shout used to generate fury if whirlwind detected and low fury;
-- Threatening shout used out-of-combat to help battle rage / sprint usage;
-- Overpower used on goblins if in melee range;
-- Added SNO 4409 to ranged and priorities mobs (annoying fallen shaman from act 2);
-- Added Necromancer (4798) and his skeletons (183892) from act 2 to actor sno blacklist;
-- Uber elites (key wardens) gained a special 150 radius kill;

** This will be probably my last custom version. From now on I'll talk to giles first, if is the case he will implement the changes in normal releases to avoid confusion and stuff **

1.6.3.2 changes/fixes:

-- Whirlwind will always be used if there's enough fury; (no pauses to bash)
* Primary attack will be used when there is only one non-elite mob left on the screen, with less than 30% hp;
* Obviously, primary attack will be used if you don't have enough fury to ww, and in certain mobs if you check Selective Whirlwind;

-- Whirlwind do not wait for Wrath of the Berserk anymore; (more harm than good)

-- Ranged enemies from act 3 got a minimum 50 radius kill, to prevent "trying to tp and being killed" in short radius kill scenarios (I died twice after switching to 18 trash radius);

-- Wrath of the Berserker, Earthquake, Call of the Ancients times changed to 120 seconds (already explained here, giles forgot to change / create a new gui option);

-- Battle Rage used for fury dump only in very high fury generation OR if sprint is not present (battle rage generates "mini stucks" if dumping, sprint is much better);

-- Fixed a bug preventing fury dump with sprint, if player didn't have whirlwind;

Finally I discovered why ww pauses after some seconds to bash/frenzy/whatever. The guilt comes from a sprint check. A single milisecond without sprint makes ww not being activated, doing giles to use primary skill instead.

Try it and feedback it :)
 

Attachments

Last edited:
tried this, seems to work ok.. except it doesnt wait to pop WOTB. fury hovers at 25 or so coz bot starts wwing right away at like 9 fury
 
This is intended. As soon as it gets 50 fury, wotb will be activated.
 
hmm.. sometimes it doesnt get to 50 fury during the whole elite fight.

EDIT: also just saw bot not pop a wotb a whole fight against elites at 100 fury
 
Last edited:
I'm watching my bot... he used wotb in 8 elites.

I already saw wotb not being activated, but is very very rare (at least on my end).
 
This is intended. As soon as it gets 50 fury, wotb will be activated.
to each their own..

to anyone else that doesnt like it. line 6677
Code:
if (!bOOCBuff && !bWaitingForSpecial && !bCurrentlyAvoiding && hashPowerHotbarAbilities.Contains(SNOPower.Barbarian_Whirlwind) && !playerStatus.bIsIncapacitated && !playerStatus.bIsRooted &&
 
The funny thing is, stock giles (1.6.3+) doesn't have bWaitingForSpecial for ww in combat.

I just changed my custom version to fit current trinity behavior :)

btw whirlwind is being used non stop now, right?
 
The funny thing is, stock giles (1.6.3+) doesn't have bWaitingForSpecial for ww in combat.

I just changed my custom version to fit current trinity behavior :)

btw whirlwind is being used non stop now, right?
yeah it is :) theres a few other things i edited but overall seems great
 
like what? :p
all my bots are ww/rend with no fury gen skill so the changes are kinda suited towards myself.

changed rend so its used if 3 or more targets are in range (instead of 5) or if 1 elite is in range (instead of 1+ elite in addition to 3+ targets)
changed rend so its only used with 50 or more fury
changed rend so that it waits for wotb
upped the timers on rend so it isnt used as much (base and when fury dumping)
made rend useable on treasure goblins
 
WHat kill radius do you guys generally run with on your barbs? I have a tendency to remove the increased range post combat, and also decrease the overall range to around 12. Basically increasing the focus on just finding elites.

Trying your modified version this minute :)
 
WHat kill radius do you guys generally run with on your barbs? I have a tendency to remove the increased range post combat, and also decrease the overall range to around 12. Basically increasing the focus on just finding elites.

Trying your modified version this minute :)
whatever the default is
 
hey bombastic, you know you can always send me stuff to change, as Moley does - saves people being on two different versions publicly here, gives you more time to test impact of stuff yourself (if you're anything like Moley, you'll make 10 changes, play with it yourself, then a day later tweak 5 of them back to the way they were or completely different again as you watch it!), and means I can be more re-assured about those changes! (eg I had sprint timer set to 2900... you'd changed that to 3000 which I copied in without thinking about it... and then realized what was happening and moved it back again :P).

You can (often) catch me idling on #ciggarc on arg IRC, Moley usually sends me a file and I just windiff it to see the changes - it also allows me to actually discuss/question some of the changes with him, which prevents any potential mistakes/mix-ups, and I usually send him my latest working versions "pre-release" so he's working on the latest stuff rather than the "Last public version".

Up to you anyway, but it'd certainly be better/easier for me this way, it's a bit frustrating not being able to go through the changes 1 by 1 and discuss them live before I edit things in, I often want to question/double-check things! :D

Anyway, currently going through your changes now to see what wants slipping in, and also adding a GUI option for wrath cooldown of 90 seconds.
 
Been running this version for an hour now and it's better than the 1.6.3.3. No offense to Giles obviously, just to let you know that this version (or some of this modified version) has made improvements.

I'm also very pleased at it picking up a key from act 3 keywarden! ;)
 
Been running this version for an hour now and it's better than the 1.6.3.3. No offense to Giles obviously, just to let you know that this version (or some of this modified version) has made improvements.
I'm also very pleased at it picking up a key from act 3 keywarden! ;)

I take no offence at all! Almost all class-skills are done by "experts" in their field, I freely admit to sucking at playing the game and so not being the best person to do the skill-selection code - I much prefer to handle "everything else" and then let class-pros tweak the code I've given them to get things working that bit better, for me to integrate in for all!
 
bombastic can you post your barb build with this vers of trinity , please?
ty
 
getting some kind of stuttering while whirlwinding in wotb, generally after a 3rd zigzag. im not really sure how to explain it, the barb kinda "dances" on the spot briefly before continuing to whirlwind.
while not in wotb whilrwinding is fluid however :|

ill try a few things and post back if i have any success.


edit: the culprit seems to be fury dumping while in wotb.
 
Last edited:
hey bombastic, you know you can always send me stuff to change, as Moley does - saves people being on two different versions publicly here, gives you more time to test impact of stuff yourself (if you're anything like Moley, you'll make 10 changes, play with it yourself, then a day later tweak 5 of them back to the way they were or completely different again as you watch it!), and means I can be more re-assured about those changes!

Spot on, Shrewsberry
 
Back
Top