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

Trinity - Barbarian Class

plzstoplooking said:
still dont understand why we need sprint fury dumping. ww + sprint on cd is enough to extend wotb to full.. that option is completely useless.. only thing i see its useful for is.. maybe if u have blade of the warlord and u have trouble surviving and u always have full rage.. then u might need it?? i dont even..

and it bugs the hell out of normal ww'ing situations.. revert ww back to 1.4.6.1 state imo
Click to expand...

Can you elaborate "bugs the hell out of normal ww'ing situations"

Total tracking time: 12h 57m 41s
Total deaths: 10 [0.77 per hour]

I haven't seen any issues of bugging out and I watch my bot for >50% of the time it is running. Roughly half my deaths are to trinity errors or navserve errors, so we could cut that number to .45 dph.

Hidden. said:
Don't misunderstand my issue. Without the sprint spam, my fury is at 100% with 2+ mobs that don't kite around. However, the sprint spam often forces my barb to go bash a target cos it spams it all the way to 0, which allows my tornadoes to drop off, which slows me down and is annoying, so... I downgraded to a version that doesn't spam sprint. 0 deaths
Click to expand...

It isn't coded to sprint spam all the way to 0 fury, or even close to fury... at most it should drop you to 80. Sounds like something else is going on, but I haven't seen it happen so I'm not really sure. Any chance of a fraps?
 
cdmichaelb said:
It isn't coded to sprint spam all the way to 0 fury, or even close to fury... at most it should drop you to 80. Sounds like something else is going on, but I haven't seen it happen so I'm not really sure. Any chance of a fraps?
Click to expand...

It seems to for me, likely linked to my MS, as for the fraps, I'm not gonna bother with that again. Last time I tried, people who had the issue recognized it straight away, and people who didn't just tried to excuse it. I've fixed it by downgrading, I'm all good for now :)
 
compare ww combat of 1.4.6.1 vs the combat of the latest version cdmichaelb

this version wastes way too much fury for no reason. spamming sprint... for what? i see it gets to 99% then sprint like 3-4x in a row when ITS ALREADY UP. why??? it doesnt help at all to increase wotb when its already at full duration from spamming ww and
sprint on cd. i can tell just from watching but.. even my stats, ilvl63/hr is waaaaaaaaaaaayy lower with latest version due to inefficient combat. sure the prioritizing of monsters better in recent version but the ww combat itself is way inferior due to some dmb changes suggested by i dunno who
 
I just upgraded from a suuuuuuuuper old version of Giles combat to the current version for my ww spec and now it is finally useable. Ww mechanic seems a lot "smarter" and efficient and the barb rarely dies anymore. Well done Gilles. Huge thanks
 
plzstoplooking said:
compare ww combat of 1.4.6.1 vs the combat of the latest version cdmichaelb

this version wastes way too much fury for no reason. spamming sprint... for what? i see it gets to 99% then sprint like 3-4x in a row when ITS ALREADY UP. why??? it doesnt help at all to increase wotb when its already at full duration from spamming ww and
sprint on cd. i can tell just from watching but.. even my stats, ilvl63/hr is waaaaaaaaaaaayy lower with latest version due to inefficient combat. sure the prioritizing of monsters better in recent version but the ww combat itself is way inferior due to some dmb changes suggested by i dunno who
Click to expand...

I can vouch for both hidden and Plzstoplooking now, i literally just updated to 1.5.1.2 From 1.5.1 and im noticing the bot spending fury on sprint too many times while its already activated, i see the cooldown clock refresh constantly when im above 50% fury. This inevitably fury starves him after each fight. im reverting back to the previous trin til this is resolved. thanks!
 
Giles added that little sprint spam because he and some others use life on fury spent gear. However, for those of us who don't, it's just an inconvenience. I think he meant to only use it once or twice at 100% however it uses it 3-4 times for me, Fury starving the crap out of my barb.
 
Hidden. said:
Giles added that little sprint spam because he and some others use life on fury spent gear. However, for those of us who don't, it's just an inconvenience. I think he meant to only use it once or twice at 100% however it uses it 3-4 times for me, Fury starving the crap out of my barb.
Click to expand...

It should only recast sprint if A) Sprint duration ends or B) If you hit 100% fury. So there it shouldn't be casting 4 times in a row unless you hit 100% fury, cast sprint, hit 100% fury instantly, it'll hit sprint 200ms later. But if you cast sprint and drop to 80% fury, it should not recast it unless fury's duration is ending. So if it is actually doing it 4x in a row despite not being fury capped... then there is a bug somewhere.

Theoretically if it is working as it should and you are fighting near the end of combat, if you hit 100% fury then a mob dies and there is only one champion left. You would be at ~80% fury and it would not recast sprint for 3 seconds. So for that 3 seconds you should be using the fury for WW or whatever. So the fury isn't really wasted.
 
Last edited:
woutknutsel said:
Don't shoot me if this is not the correct thread for this, but I see that my barb is doing 200GPH during champ farming in act3. Can I assume that at max paragon level (now lvl 33), it will be doing at least 500GPH. If this continues than he will be doing better in a few days than my goldfarming DH in Hell. Any barbs with higher paragon lvls seeing increase in GPH also?
Click to expand...

I'm running 325Kish gold per hour at Paragon level 59 on a WW Barb.
 
woutknutsel said:
Don't shoot me if this is not the correct thread for this, but I see that my barb is doing 200GPH during champ farming in act3. Can I assume that at max paragon level (now lvl 33), it will be doing at least 500GPH. If this continues than he will be doing better in a few days than my goldfarming DH in Hell. Any barbs with higher paragon lvls seeing increase in GPH also?
Click to expand...

Paragon level increases how much gold drops.
 
cdmichaelb said:
It should only recast sprint if A) Sprint duration ends or B) If you hit 100% fury. So there it shouldn't be casting 4 times in a row unless you hit 100% fury, cast sprint, hit 100% fury instantly, it'll hit sprint 200ms later. But if you cast sprint and drop to 80% fury, it should not recast it unless fury's duration is ending. So if it is actually doing it 4x in a row despite not being fury capped... then there is a bug somewhere.

Theoretically if it is working as it should and you are fighting near the end of combat, if you hit 100% fury then a mob dies and there is only one champion left. You would be at ~80% fury and it would not recast sprint for 3 seconds. So for that 3 seconds you should be using the fury for WW or whatever. So the fury isn't really wasted.
Click to expand...

Yeh but that doesn't happen. It hits 100 fury and hits sprint 3-4 times taking my fury to 0 and stopping ww
 
Hidden. said:
Yeh but that doesn't happen. It hits 100 fury and hits sprint 3-4 times taking my fury to 0 and stopping ww
Click to expand...
Definitely a bug, Giles told me there is a 200ms between each sprint which should have been enough to avoid these bugs, I'll try reading the code myself to see if I figure it out... but we'll prolly have to wait for him.

Edit: What is your latency in D3?
 
Last edited:
cdmichaelb said:
Definitely a bug, Giles told me there is a 200ms between each sprint which should have been enough to avoid these bugs, I'll try reading the code myself to see if I figure it out... but we'll prolly have to wait for him.

Edit: What is your latency in D3?
Click to expand...

Must be... As I said, I had the issue with older versions when others didn't. I'm usually on 240-290
 
Hidden. said:
Must be... As I said, I had the issue with older versions when others didn't. I'm usually on 240-290
Click to expand...
I suspect it may be your latency causing the bug. If the recast delay on sprint is 200ms, and you cast it but it doesn't cast stil 240-290ms, then it will cast twice, or more.
 
id does seem to spam sprint usually when it hits 100 % fury, but not as radical as hidden
 
JoeC said:
id does seem to spam sprint usually when it hits 100 % fury, but not as radical as hidden
Click to expand...
If you have <190MS latency, it should work fully as intended (i've tested it for over 20 hours since the change)
 
whether the sprint bugs out or not doesnt even matter, the spamming sprint itself isnt needed is my point anyway. who da hell asked for that?

also, you are basically nerfing urself for casting sprint when its already up.. u actually end up laying down less tornadoes if u do that

anyways.. anybody at paragon level 100 yet? im almost there :p

and for any ww barbs who are having fury issues with latest version..

heres my code edited 1.4.6.1 code that works really wel.. give it a try

// Sprint buff, if same suitable targets as elites, keep maintained for WW users
if (!bBuffsOnly && hashPowerHotbarAbilities.Contains(SNOPower.Barbarian_Sprint) && !playerStatus.bIsIncapacitated &&
(
// Always keep up if we are whirlwinding
hashPowerHotbarAbilities.Contains(SNOPower.Barbarian_Whirlwind) && GilesUseTimer(SNOPower.Barbarian_Sprint)
) &&
// If they have battle-rage, make sure it's up
(!hashPowerHotbarAbilities.Contains(SNOPower.Barbarian_BattleRage) || (hashPowerHotbarAbilities.Contains(SNOPower.Barbarian_BattleRage) && GilesHasBuff(SNOPower.Barbarian_BattleRage))) &&
// Don't already have sprint up
!GilesHasBuff(SNOPower.Barbarian_Sprint) &&
// The timer is out OR ignore the timer if we don't have sprint
(GilesUseTimer(SNOPower.Barbarian_Sprint) || !GilesHasBuff(SNOPower.Barbarian_Sprint)) &&
((playerStatus.dCurrentEnergy >= 40 && !playerStatus.bWaitingForReserveEnergy) || playerStatus.dCurrentEnergy >= iWaitingReservedAmount) && PowerManager.CanCast(SNOPower.Barbarian_Sprint))
{
return new GilesPower(SNOPower.Barbarian_Sprint, 0f, vNullLocation, iCurrentWorldID, -1, USE_COMBAT_ONLY, USE_SLOWLY);
}
 
Last edited:
plzstoplooking said:
<snip>

also, you are basically nerfing urself for casting sprint when its already up.. u actually end up laying down less tornadoes if u do that

<snip>
Click to expand...

That is false, it doesn't work like DOTs in wow if that is what you are thinking.
 
cdmichaelb said:
Definitely a bug, Giles told me there is a 200ms between each sprint which should have been enough to avoid these bugs, I'll try reading the code myself to see if I figure it out... but we'll prolly have to wait for him.

Edit: What is your latency in D3?
Click to expand...

Aussies, folks and other people who need to work in Oceanic region have pings like 250ms to 600ms.
 
You must log in or register to reply here.
Back
Top