[Plugin] Giles Trinity

[Buzzalot]

yay Trinity Class forums are going up.

 

[Hidden.]

After the fixes that Bomb and Poly applied to my version of Trin, I'm at a point where I'm not sure if I should be updating either DB or Trinity...
I'm not getting stuck, no DC's, no crashes, no CPU issues, dying 1-3 times per act 3 run and where the bot used to use up about 70 pots every 3-4 hours, over the past 8 hours it used 18 (it used more but I'm basing the number on the ones it used and picked up).

Is there a reason why I should update once the new Trin comes out?

 

[jinny1]

After the fixes that Bomb and Poly applied to my version of Trin, I'm at a point where I'm not sure if I should be updating either DB or Trinity...
I'm not getting stuck, no DC's, no crashes, no CPU issues, dying 1-3 times per act 3 run and where the bot used to use up about 70 pots every 3-4 hours, over the past 8 hours it used 18 (it used more but I'm basing the number on the ones it used and picked up).

Is there a reason why I should update once the new Trin comes out?

Trinity v1.5 will be released tomorrow, with massive speed/cpu improvements, improved uses of many skills, better attack-speed, better stuck-handling, barricade handling, better body-block handling, better avoidance intelligence and handling, and many other things... INCLUDING DEMON HUNTER SUPPORT!

 

[shuto1]

I can't wait.

 

[Hidden.]

Trinity v1.5 will be released tomorrow, with massive speed/cpu improvements, improved uses of many skills, better attack-speed, better stuck-handling, barricade handling, better body-block handling, better avoidance intelligence and handling, and many other things... INCLUDING DEMON HUNTER SUPPORT!

I read them, I'm just currently not finding any issues with the one I have. I will probably just back my version up and give it a go anyways see if anything changes/improves. If not, I can always just go back to this version I guess

 

[shuto1]

New version up! I donated!

 

[brbbX]

I'm still having the spam sprint issue on 1.5!
Could it have something to do with the fact that I set APS to 15?

 

[GilesSmith]

I'm still having the spam sprint issue on 1.5!
Could it have something to do with the fact that I set APS to 15?

That could definitely cause oddities - it's an advanced feature for good reason! Try disabling it, restarting DB, and trying again! Let me know if you still have issues, but I haven't seen any on any of my barbs, and I run on default TPS only (which should be just fine for 99% of users, especially with the new version that is faster anyway!)

New version up! I donated!

Thank you!

 

[brbbX]

That could definitely cause oddities - it's an advanced feature for good reason! Try disabling it, restarting DB, and trying again! Let me know if you still have issues, but I haven't seen any on any of my barbs, and I run on default TPS only (which should be just fine for 99% of users, especially with the new version that is faster anyway!)



Thank you!

nope, without APS edited it's still spamming sprint sometimes (only during battle, not when moving around)

 

[Hidden.]

nope, without APS edited it's still spamming sprint sometimes (only during battle, not when moving around)

Brbb, open up .cs with Notepad++ and change your sprint code lines to this:

// Sprint buff, if same suitable targets as elites, keep maintained for WW users
if (!bBuffsOnly && hashPowerHotbarAbilities.Contains(SNOPower.Barbarian_Sprint) && !playerStatus.bIsIncapacitated && 
(GilesUseTimer(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);
}

 

[Hidden.]

That could definitely cause oddities - it's an advanced feature for good reason! Try disabling it, restarting DB, and trying again! Let me know if you still have issues, but I haven't seen any on any of my barbs, and I run on default TPS only (which should be just fine for 99% of users, especially with the new version that is faster anyway!)



Thank you!

Invalid Attachment specified. If you followed a valid link, please notify the administrator

Did you take it off?

 

[brbbX]

Brbb, open up .cs with Notepad++ and change your sprint code lines to this:

// Sprint buff, if same suitable targets as elites, keep maintained for WW users
if (!bBuffsOnly && hashPowerHotbarAbilities.Contains(SNOPower.Barbarian_Sprint) && !playerStatus.bIsIncapacitated && 
(GilesUseTimer(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);
}

yes, with that fix it works..
I'm thinking that maybe it's also spamming WW, however? is that possible? sometimes my fury goes from 100 to 0 in a second

 

[Hidden.]

yes, with that fix it works..
I'm thinking that maybe it's also spamming WW, however? is that possible? sometimes my fury goes from 100 to 0 in a second

Ever since I used that code, I've had absolutely no Fury issues. It runs like personal lubricant on a pornstar's body. Smooth, and you know it will end well.

 

[bombastic]

...and Giles did it again

Glad to see some of my changes there...

Good Job as always!

 

[GilesSmith]

yes, with that fix it works..
I'm thinking that maybe it's also spamming WW, however? is that possible? sometimes my fury goes from 100 to 0 in a second

Try re-download, I made a couple of minor changes (I don't make it a habit to upload changes without increasing version number, I'm just completely overwhelmed with work right now, setting up the new sub-forums, and it's 5 AM - this is a rarity, for anyone concerned with not knowing if they have the latest or not. The changes have been minor and focused purely on barbarian leap, and barbarian sprint use).
All I've done is remove the check for the buff not being present, and DB's own power-manager check on the skill use, so it's purely based on using it once every 2.85 seconds or so.

As for energy use - energy use should be reduced - there is no way to hold down an attack button in DemonBuddy. Whirlwind is only possible because of the way I have set it up to be able to spam attacks over and over quickly to look like one chain of WW - this will never be quite as efficient as if we had a way to hold down a button, but it works. In Trinity v1.5, I changed whirlwind specifically to limit it's use to only send a new WW command once every 200 milliseconds - long enough for the last WW to still be going, short enough to keep a "chain" of them going in a line - this reduces fury use a lot. That 200 may be able to go slightly higher, but you have to be careful that lag/sudden CPU spikes don't cause the gap to be so large that the WW line "Breaks" and you stop-start your whirlwinds constantly.

 

[Hidden.]

Try re-download, I made a couple of minor changes (I don't make it a habit to upload changes without increasing version number, I'm just completely overwhelmed with work right now, setting up the new sub-forums, and it's 5 AM - this is a rarity, for anyone concerned with not knowing if they have the latest or not. The changes have been minor and focused purely on barbarian leap, and barbarian sprint use).
All I've done is remove the check for the buff not being present, and DB's own power-manager check on the skill use, so it's purely based on using it once every 2.85 seconds or so.

As for energy use - energy use should be reduced - there is no way to hold down an attack button in DemonBuddy. Whirlwind is only possible because of the way I have set it up to be able to spam attacks over and over quickly to look like one chain of WW - this will never be quite as efficient as if we had a way to hold down a button, but it works. In Trinity v1.5, I changed whirlwind specifically to limit it's use to only send a new WW command once every 200 milliseconds - long enough for the last WW to still be going, short enough to keep a "chain" of them going in a line - this reduces fury use a lot. That 200 may be able to go slightly higher, but you have to be careful that lag/sudden CPU spikes don't cause the gap to be so large that the WW line "Breaks" and you stop-start your whirlwinds constantly.

Confirming that the latest version no longer has the inherent Sprint Spam issues

 

[beardi]

Seems that now the plugin fails until death to realize its not in archon form and can use diamond skin.. deathsx20+ in less minutes lol

 

[Hidden.]

PS.
I'm not sure if it's because I was using an altered version, or if you changed it in this version... but the WW pathing is freaking amazing.
Giles, not to add more to your plate, but for the future... Is there a way to give priority to certain avoidances? For example... Frost to be avoided at all costs?
The reason I say this is because if there are Frost Balls on the ground and it tries to avoid it, but it happens to head in the direction of a Desecration Pool, it will avoid the pool and head into the frost. I'd rather take on Desecration than frost any day.

Edit:
ROFL! I my bot just walked into an area with 3 Yellow elite groups. The Big Golgor guys, a Shaman and Trooper. It beat them to a pulp

 

[funker]

as for me, i think my char started to die more often. especially when elites explode after death, bot trys to evade explode and just stands away from it and waits. During this time other mobs kill my char) maybe i just get some strong elites dunno. playing barb

 

[Gurkis]

I'm having issues with the new bot and plugin, he moves to the first area of ACT III and just kind of stands there, waiting to die :/. He doesn't even try to attack.

EDIT:
nvm, I restarted the bot 5 times and it's working