[Plugin] Giles Trinity

[MonsterMMORPG]

elite become far away while fighting and it left attacking elite

was almost killing me

 

[ieee]

Love the going after shaman feature but bot seems to be overly fixated on killing them. To the point where it will die trying to navigate to the shaman through a sea of mobs or if it's blocked. (Yes, I don't have the best of equipment) Maybe you can do a "if life < 50%, kill everything around you first" feature.

Also, monk with fists of thunder does not seem to do avoidance very well. It is always trying to hop around and sneak in a punch at a mob inside an AOE. Inevitably dying to a exploding molten core in the process because fist of thunder teleports you to the mob. I am guessing it's because it uses the standard ranged code which assumes ranged attacks are allowable even for objects in AOE.

Other than that, fantastic job!

 

[sTARk27]

LOL 1.4.7 "The Barrel Breaker". Runs straight parts mobs to break barrels. Weird...

Edit: Ok reducing Destructible range helps but it also seem to run into the middle of mobs, stand there for a second, than attack. Something weird going on....

 

[Arm]

Why bot sometimes just stops and DB tells me this: [12:39:33.619 N] ========== Grid segmentation resetting!!! ============ then after some time he leaves the game.

 

[dlr5668]

<3 new kamikadze option, work very well.
[09:03:19.366 N] Creating new game, Params: <Act:A3 Difficulty:Inferno Quest:101758 QuestStep:1 ResumeFromSave:False IsPrivate:True>
[09:49:34.361 N] Creating new game, Params: <Act:A3 Difficulty:Inferno Quest:101758 QuestStep:1 ResumeFromSave:False IsPrivate:True>
[10:36:40.275 N] Creating new game, Params: <Act:A3 Difficulty:Inferno Quest:101758 QuestStep:1 ResumeFromSave:False IsPrivate:True>
~46 min/ full act3 champ + azmodan run with 2 deaths, bot is so fast now!

 

[b5x1]

awesome job with the gobbers giles! they will gimme they shinies now! (;

 

[GilesSmith]

taker21:

Same issue standing in front of the barricade, Trinity Debug Line says:"Destroy ..., Moving into range, even not attacking near enemys, just standing there.

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!

righttang:

Hey giles,
It looks like I have a rare situation that there is a Legendary Item missed pickup by the Bot. My loot settings are all default without any customization.
I have attached the status log file from here. As you can see, there are one lv 61 legendary item dropped and 2 lv 63 item dropped.

Item stats aren't always accurate - it's generally more likely that the item-stats are slightly off by 1 or 2! Even with that being the likely case, items can still be missed through very bad luck depending on exactly where your bot was when it dropped - eg a grey on the edge of the screen while your bot is fighting other things, in an area where the routine/profile has the loot-radius very low to avoid stucks - but as I say, item-stat can mis-count things anyway!

Bomtox:

Offhand - Quiver 'Target Defiance'. Score = 6980
Dexterity=116. Life Regen=116. Crit Chance %=8. Attack Speed %=15
Isnt the scoring a bit too low for quivers?

As someone else rightly says - depends if you want to be selling 20k quivers all day I certainly don't. But you can reduce required-scores if you want your stash filled quicker and have a lot of patience listing everything - that's what the sliders are for in the town-run tab

Arm:

Why bot sometimes just stops and DB tells me this: [12:39:33.619 N] ========== Grid segmentation resetting!!! ============ then after some time he leaves the game.

The joys of the DemonBuddy nav-system - nothing to do with me or Trinity I'm afraid. We all get that grid segmentation message, is something to do with DB's dungeon navigation code (even if you aren't in a dungeon).

 

[Symbiotic]

I have a feature request!

Separate Furious Charge and Leap option for out of combat movement. Furious Charge needs to be used only in combat, while Leap doesn't matter as much and can be used in and out of combat (helps for getting unstuck at times).

Thanks!

p.s. There shouldn't be a health threshold for Leap either. You don't wait til you're taking damage, you should Leap on cooldown, especially when killing packs, because it's a safe assumption you will be taking some damage while in melee range.
(playerStatus.dCurrentHealthPct <= 0.9 || targetCurrent.fCentreDistance >= 18f || iElitesWithinRange[RANGE_30] > 0) &&

->

(targetCurrent.fCentreDistance >= 18f || iElitesWithinRange[RANGE_30] > 0) &&

 

[gotteshand]

Hello giles,

Found a problem with Azmodan and any other Unique boss monster with a huge body. Right now the trigger range for explosive blast and frost nova is 12 which is perfect expect for boss's like Azmodan due to his huge body he will still get hit by explosive blast and frost nova even while the bot (debug bar) is showing him to be 24 yards away. Some sort of extra check for that would be really great as it would speed up the killing of said boss's for critical mass wizard builds because right now Explosive Blast is not triggered at all in these boss fights.

Also latest version 1.4.7 seems to have problems with destructibles (Barricades and stuff like that) not all of them sometimes it takes the bot 10-15 seconds to destroy them and move on.

 

[Brandew]

I have version 1.4.7 and I did a fresh install. I have been using rend with my bot. For some reason the bot doesn't keep rend on elites. It takes a long time or doesnt rend at all while fighting elites.

 

[mromcy]

This plugin keeps getting better and better. Awesome job.

Any ETA for when DHs will be able to use this?

 

[sTARk27]

Dying much more with 1.4.7. Normally I'm at 0.6 dph in Act 3

Total tracking time: 1h 53m 1s
Total deaths: 4 [2.12 per hour]

 

[kobru]

can you add an option to avoid weapon and armor racks?

 

[lobin]

This plugin keeps getting better and better. Awesome job.

Any ETA for when DHs will be able to use this?

Yeah DH support would be nice. I cannot imagine DB without Trinity. Giles you are AWESOME! Donating now.

 

[lobin]

€5 donated Not much but payday is tomorrow so more will come)

 

[GilesSmith]

Symbiotic:

p.s. There shouldn't be a health threshold for Leap either. You don't wait til you're taking damage, you should Leap on cooldown, especially when killing packs, because it's a safe assumption you will be taking some damage while in melee range.
(playerStatus.dCurrentHealthPct <= 0.9 || targetCurrent.fCentreDistance >= 18f || iElitesWithinRange[RANGE_30] > 0) &&
->
(targetCurrent.fCentreDistance >= 18f || iElitesWithinRange[RANGE_30] > 0) &&

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".

gotteshand:

Hello giles,
Found a problem with Azmodan and any other Unique boss monster with a huge body. Right now the trigger range for explosive blast and frost nova is 12 which is perfect expect for boss's like Azmodan due to his huge body he will still get hit by explosive blast and frost nova even while the bot (debug bar) is showing him to be 24 yards away. Some sort of extra check for that would be really great as it would speed up the killing of said boss's for critical mass wizard builds because right now Explosive Blast is not triggered at all in these boss fights.

I have a fix ready for next release for "large object" monsters, and am working on barricade stuff still (current release is a little experimental for barricades! ).

mromcy:

This plugin keeps getting better and better. Awesome job.
Any ETA for when DHs will be able to use this?

Not yet, but I haven't forgotten about DH's - but as you can see from the changelog, other things have been taking my time!

kobru:

can you add an option to avoid weapon and armor racks?

Can you give me their SNO codes?

lobin:

?5 donated Not much but payday is tomorrow so more will come)

Thank you! I much appreciate the donations from people - they certainly help keep me in supply of coffee and noodles! (and every donator can pride themselves on being in a special approximately 1% of the total plugin users! ).

 

[GilesSmith]

Dying much more with 1.4.7. Normally I'm at 0.6 dph in Act 3
Total tracking time: 1h 53m 1s
Total deaths: 4 [2.12 per hour]

Have you got more specific feedback than that? What class is this with? Have you watched the bot? Are you able to ascertain what is causing more deaths? Are you using the new "Kamikaze" goblin option (which really is kamikaze, but users requested it)? is it an issue with the new target-weighting, perhaps because I "fixed" priority code, it suddenly made the huge priority weight shamans had be too high (and that value should perhaps now be reduced, now that weights are better)? Are you getting body-blocked but not priotizing close-targets when blocked? Some info is good. More info is great. No info makes me a sad panda

 

[jimmiesrustler]

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've gotten stuck on regular barricades, and the barricade lookalike(looks like a parked van) in the fields that is always next to the a weapon rack.
class: wizard
act 3 in skycrown, stonefort, fields of slaughter, and battlefields

 

[Taldoras]

Have you got more specific feedback than that? What class is this with? Have you watched the bot? Are you able to ascertain what is causing more deaths? Are you using the new "Kamikaze" goblin option (which really is kamikaze, but users requested it)? is it an issue with the new target-weighting, perhaps because I "fixed" priority code, it suddenly made the huge priority weight shamans had be too high (and that value should perhaps now be reduced, now that weights are better)? Are you getting body-blocked but not priotizing close-targets when blocked? Some info is good. More info is great. No info makes me a sad panda

Im guessing (since i have the same problem) that it has something to do with rend currently being underused. It barely casts it twice in an elite fight
(im almost constantly full of rage, still no casting )

It would be really cool if you'd look into that.
Thanks for a great plugin and keep up the good work

 

[bombastic]

Giles, can I suggest a major change on how Hammer of Ancients is being used?

					if (!bBuffsOnly && !bWaitingForSpecial && !bAvoidanceEmergency && hashPowerHotbarAbilities.Contains(SNOPower.Barbarian_HammerOfTheAncients) && !playerStatus.bIsIncapacitated && 
                       (playerStatus.dCurrentEnergy >= 85 || (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.50))) &&
					   GilesUseTimer(SNOPower.Barbarian_HammerOfTheAncients))
                    {

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