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

[Plugin] Giles Trinity

Status
Not open for further replies.
Hey Gile, i think the deaths have gone up because now when my barb's path gets blocked by creeps he just sits there getting hit until hes dead, my trigger range for non-elite combat is 5, I have used that range in previous versions without a problem. Has something changed and should i try extending it?

Jarrod
 
Symbiotic:

The "||" is an "or" command. All you have done is *remove* one of the possible leap reasons (which is an allowance for taking lots of damage against just greys). So instead of "Low health *OR* distance >= 18 *OR* elites within 30 feet", you're now doing "distance OR elites".
lol Giles :)

I'm a C++ programmer. I know what it means. I'm asking if you can make it default since it's better to Leap even with full health.

But never mind, it's not a big deal. I'll just keep personalizing mine on every release.

p.s. By the way, Fire Shaman, Fire Mage, and Goblin priority is working nigh flawlessly now by the way. Props and thanks.
 
Last edited:
Giles, can I suggest a major change on how Hammer of Ancients is being used?
Hammer of Ancients would be use only:
- If fury is >= 85, use in any case / any mob;
- If fury is >= 55, use only in mobs above 50% hp (important to preserve some fury for wotb; we never get below 35 fury);
- If fury is >= 20, use in all elites, minions, goblins, bosses OR if player is below 50% hp (to help kill fast / life steal builds) OR if WotB is activated (we don't need extra fury atm);
- If berserk is ready to be cast, wait till it's activated -- !bWaitingForSpecial flag (the way it's right now, bot spams hammer and never has fury to activate berserk)
These changes helped me a lot to survive / manage fury :)
Sure, I don't use this myself and don't know many that do, so welcome good feedback like this from people on changes, will try and stick this in for the next update!

Hey Gile, i think the deaths have gone up because now when my barb's path gets blocked by creeps he just sits there getting hit until hes dead, my trigger range for non-elite combat is 5, I have used that range in previous versions without a problem. Has something changed and should i try extending it?
Just hold tight, I'll be checking this out for a 1.4.7.1 out later on today/tonight! :D

lol Giles :)
I'm a C++ programmer. I know what it means. I'm asking if you can make it default since it's better to Leap even with full health.
But never mind, it's not a big deal. I'll just keep personalizing mine on every release.
p.s. By the way, Fire Shaman, Fire Mage, and Goblin priority is working nigh flawlessly now by the way. Props and thanks.
Hmm, maybe I'm missing something!? You said that you wanted it to leap "on-cooldown for elites" - which it already does. You wanted to change this line;
(playerStatus.dCurrentHealthPct <= 0.9 || targetCurrent.fCentreDistance >= 18f || iElitesWithinRange[RANGE_30] > 0) &&
To this line;
(targetCurrent.fCentreDistance >= 18f || iElitesWithinRange[RANGE_30] > 0) &&
But those two lines do exactly the same thing *EXCEPT* your change prevents it using leap on greys when low-on-health. Basically my code does this;
(Player low health || OR || target more than 18 feet || OR || an elite within 30 foot radius of us)
And your suggested change would do this;
(target more than 18 feet || OR || an elite within 30 foot radius of us).
I'm not sure what the advantage of PREVENTING it leaping when low on health would be, surely this is useful for times when you get mobbed by greys at close-range and they start hurting you?
 
taker21:

Could you tell me which Act, what area, and what barricades it's getting stuck on please? I either need to blacklist the barricades (if it shouldn't attack them at all), or tell it to ignore at further range/attack at close range. The debug info will be useful for me too - as the debug line (where it says Destroy...) will tell me the object name, and the SNO (in curly bracers) :) Oh! Also, which class are you/which attack did the debug message say it was trying to use (if any)? That might effect the attack ranges!

I solved the problem by using the hint of an other poster to set "Destructible Attack Range" to 0 but i dont know if its a temporary fix so here are more details for you.

Problem: Char is standing infront of the wagon a waits and few seconds (10 or something), also not attacking creatures he gets hit by.

Class: Barbarian
Act: 3
Place: Right down to the Battlefield the first big wagon.(for example, there are more baricades with the same problem)

Trinity Debug Line:
[GilesTrinity] Destroy Target=A3_Battlefield_Wagon_SupplyCart_A_Breakable-10898{121586}. Distance=9,5. MOVING INTO RANGE

Player Position:
x="4116.47" y="440.6724" z="-1.4454" (new Vector3(4116.47f,440.6724f,-1.4454f))

Screenshot:
stuck.webp

Hope that helps :)
 
Last edited:
Giles a suggestion for future Trinity builds how about instead of just having a debug bar adding a debug log file that would help quite a bit looking for fishy things:)
 
Sure, I don't use this myself and don't know many that do, so welcome good feedback like this from people on changes, will try and stick this in for the next update!

Yay! :cool:

btw I did a fine tunning on my previous code for hammer. Please use this:


Code:
					if (!bBuffsOnly && !bWaitingForSpecial && !bAvoidanceEmergency && hashPowerHotbarAbilities.Contains(SNOPower.Barbarian_HammerOfTheAncients) && !playerStatus.bIsIncapacitated && 
                       (playerStatus.dCurrentEnergy >= 75 || (playerStatus.dCurrentEnergy >= 55 && targetCurrent.iThisHitPoints >= 0.50) || 
					   (playerStatus.dCurrentEnergy >= 20 && (GilesHasBuff(SNOPower.Barbarian_WrathOfTheBerserker) || 
					   targetCurrent.bThisEliteRareUnique || targetCurrent.bThisMinion || targetCurrent.bThisTreasureGoblin || targetCurrent.bThisBoss || playerStatus.dCurrentHealthPct <= 0.38))) &&
					   GilesUseTimer(SNOPower.Barbarian_HammerOfTheAncients))
                    {

And like everyone said, goblins/shamans priorities are perfect now. No need to manually change the code anymore :)
 
Last edited:
Rend stops being casted sometimes, mostly when surrounded by several/multiple mobs.
Could we give rend higher priority when surrounded by 4+ mobs? Getting it cast every 2 seconds in surrounds would save LIVES!
 
Hi Giles,
Just got back from a loooooooong day of work, to check out the news here again.
Read all the pages since yesterday, and here's my 2 cents again ;)

Check your loot-rules, and try change the priority order of things - just realized that one thing Trinity does differently is it visits the vendor to sell things first BEFORE checking the blacksmith for possible salvage stuff. Which means your sell-rules need to exclude salvage stuff really... is that possible, or am I going to have to look into re-ordering things for next release?
I could be possible as a dirty-fix, just to keep things running. Maybe other stuff has a higher priority to take a look into first. Don't know the time it would take to throw this around. :) You make the call mate, I'm already pleased to see, we may have found a small bug ;)

Lol, well, turned out 2 pages later, you've already fixed it in the.... OMG NEW RELEASE! Dude..... you keep amazing me mate.

I'll install the new version right away, and I'll let you know asap.
Thanks again!

EDIT:
Just tested this excellent new feature, and I must be honest, you did even more than I expected :)
He went to my stash first, vendor afterwards, then some salvaging, and just before it used the portal to get back to work, it quickly stashed the mats gained from salvaging.
My compliments mate, you blew me away ;)

As a thank you, you'll receive a donation, just right after I've eaten my diner ;)
Thanks again
 
Last edited:
For some reason when my bot restart (i use the batch file) it doesnt use any plugin. (using only giles trinity and rads) any1 experiencing the same issue?
 
For some reason when my bot restart (i use the batch file) it doesnt use any plugin. (using only giles trinity and rads) any1 experiencing the same issue?

It's a known fault with some reloggers (check post #2 of this thread, I have a section about reloggers there). You'll have to try a different relogger/launcher, or check the relogger/launcher thread for the one you use for possible fixes.
 
goblin kamize look good but the fix someone posted here on 1.4.4 was better :/

still wasting time on gray mob and if the goblin run out of the screen is gone
 
I know it's a bit early but can you let us know whether your plugin is compatible with the new DB version ?
Greetings !
 
Still skiping some loots!
When? Where? What circumstances? What was the bot doing? Where was the item? How far away was the item? What item type and item level? What pickup filter options have you set? Are you using custom pickup rules? Was it during combat or out of combat? Are you using backtracking? Are you using the latest version? Have you gone over common problems part #2? Do you have any other plugins? Details, details, details. Without them, all I can do is smile and nod.

I know it's a bit early but can you let us know whether your plugin is compatible with the new DB version ?
Greetings !

I've never seen a DemonBuddy update that broke any of my plugins yet - but of course, you should always, always be sensible, and BACKUP your old version before TRYING an update - so if the update goes wrong/handles worse, you can revert and wait for another DB update :)
 
The Shaman focus is getting my monk stuck sometimes, Shaman would be behind an indestructible object and I would get surrounded by white mobs, it would keep trying to run after the Shaman and eventually die
 
Giles, it spams Revenge-Provocation more often than it does Rend.
It spams Revenge BEFORE the fighting even occurs I mean. Obviously its going to spam revenge more than rend while IN the fight, because it procs more and does more dmg.
But before the fighting even starts, it sometimes starts with Revenge, instead of Rend.
Maybe I'm crazy... Not that it really matters, my barb dies maybe once per run, but I think maybe i could run a bit faster with more Rend spams is all.
 
I know it's a bit early but can you let us know whether your plugin is compatible with the new DB version ?
Greetings !
Just updated to new DB version (227)
For me, the plugin still works like a charm. Not sure if yours does 2 tho :P
 
The Shaman focus is getting my monk stuck sometimes, Shaman would be behind an indestructible object and I would get surrounded by white mobs, it would keep trying to run after the Shaman and eventually die


Just had this happen to me. Ohter than that, all is working really well, and the priority bit does seem better, just besides that situation/issue
 
Giles, it spams Revenge-Provocation more often than it does Rend.
It spams Revenge BEFORE the fighting even occurs I mean. Obviously its going to spam revenge more than rend while IN the fight, because it procs more and does more dmg.
But before the fighting even starts, it sometimes starts with Revenge, instead of Rend.
Maybe I'm crazy... Not that it really matters, my barb dies maybe once per run, but I think maybe i could run a bit faster with more Rend spams is all.


spamming revenge is very good. it really improves survivability
 
Status
Not open for further replies.
Back
Top