[Plugin] Giles Trinity

del

 

Giles, Sir. I don't want to look very abusive but could you point out the part of the code responsible for shamans' priority in Act3 or come up with a quick solution like you did with the treasure goblins' issue. Appreciated much and thank you in advance.

 

For some reason my bots will not kill the crap on the ground in the screenshot below inside the swamp cellar

 

V 1.2 works fine for me (except for some suck avoidance when it comes to moving from molten. it just stands in it)
V 1.3 = Cannot even use it whenever it gets near mobs i get 3 fps and he basicly just stands there until hes beaten to death, Playing Monk btw never had any problems with previous versions of trinity. something must of gone wrong when you updated from 1.2 - 1.3

Maybe its just for monks? im not sure

 

v1.3.1 uploaded:
- Changed settings-saving for AOE-values to use space separation instead of comma-separation, to fix issues for certain countries that use commas for decimal separation.
WARNING: This will reset your AOE settings on first run after update, sorry!
- Added a new "Defaults" button to every single config tab - this will reset the default settings ONLY FOR THAT TAB! (the reset all button is still at the bottom of the config window)
- A new setting added to the main combat options: "Extend trash-kill range after combat" - this feature was already built in and forced on, but you can now disable it.
-- This feature simply extends your kill radius for clearing trash mobs for a very short time after combat, to allow for multiple-kill-exp bonuses. If you simply want to ignore trash mobs as much as possible, then disable this option. Disabling this may also help prevent some stuck-situations where grey mobs are in awkward places.
- Settings now correctly saves/loads the advanced option for logging stuck positions.
- The "Minimum gold pile" value to pickup now allows for a bit of "fuzz" - eg, it can pick up smaller gold piles if they are particularly close, and ignore slightly larger gold piles if they are far away.
- Increased the weight of health globes, and item pickups, during combat.
- Fixed minor bug with the "follower items ignored" stat in item stats file being completely huge and wrong.
- If you have wrath of the berserker on cooldown when you first enter Azmodan's lair, the bot will force you to wait until it is off cooldown before continuing on to fight Azmodan.
- You now use wrath of berserker against boss-targets (eg Azmodan) when the boss is at 60% health, instead of waiting for 50% health, for the "final burn-down".
- If you have wrath of the berserker, earthquake, or call of the ancients ready to cast (and the bot wants to cast them), you will no longer use rend until you have enough fury to cast both.
- Some minor changes to various other skills for all four classes (apologies, I constantly give them minor tweaks based on user feedback, and don't remember to log them all!).
- Further reduced extra weight of very-close-range monsters to help targeting ranged/summoners more easily (note that if your bot gets "body-block-stuck", it will still prioritize very close range mobs first to try and clear a path).
- Increased weight of suicidal-attacking on treasure goblins when treasure goblins are set to priority (again, be aware that being body-blocked while chasing will cause you to prioritize close range mobs).
- Tweaked scoring of stats based on primary attribute levels (anything involving score from primary attributes now needs slightly higher primaries for the same score-bonuses etc.)

I have seen others with the same problem say that a fresh, clean install of a newly downloaded DB into a new, empty folder and then getting latest plugins (generally just mine and Rad's profile manager) fixed this issue. Can you confirm the same? I run with a monk and barbs and have no issues at all. Also try 1.3.1 first (with a fresh clean install). Do you run in a virtual machine? Do you run lots of bots? Have you tried playing with the "TPS" setting in the advanced tab?

 

ty for fast update

 

oh no! you reckon 1.3.1 will fix this with more aggresive looting in combat? or maybe up the loot radius in the profiles?

Total tracking time: 8h 17m 5s
===== Item DROP Statistics =====
- Legendary: 2 [0.24 per hour] {0.09 %}
--- ilvl 60 Legendary: 1 [0.12 per hour] {0.04 %}
--- ilvl 63 Legendary: 1 [0.12 per hour] {0.04 %}
===== Item PICKUP Statistics =====
- Legendary: 1 [0.12 per hour] {0.21 %}
--- ilvl 60 Legendary: 1 [0.12 per hour] {0.21 %}

 

I think upping the loot-radius in profiles anywhere that is particularly low might be a good idea, if they have loot-settings that are very low on certain segments of the map anyway - stuck issues should be heavily reduced from looting items that are not possible to reach within Trinity anyway.

And 1.3.1 will help a bit too - I gave an extra boost to legendary weight too.

And finally - look back a bit and see where I mentioned the item DROP stats can sometimes read an item quality wrongly - and due to stats not "updating" items each loop (since it logs an item when first seen then blacklists it from being added to stats again), stats won't get any updates on the item's "correct" quality count later (whereas actual pickup code will). Have to say though I think this is quite unlikely/rare - but it's certainly a possibility for the drop-stats the way the code works and the way DB reads memory and D3 sometimes has wrong values in memory for one brief "loop".

 

I was thinking of a couple of possible enhancements to prevent this:

1. If a legendary drops, picking it up could be priority #1. No combat unless blocked by monsters of course.

2. Since the bot sees the legend drop, remember where that was and go back and get it. Dont worry about stucks since we all agree legendaries are a special case and worth the stuck risk.

 

thanks for updates once again

 

The 1.3.1 update didn't prompt any "plugin enabled" messages into the db logging window. It also seems to cause DB and Diablo to "stuck-n-go" pretty much non stop when running champion farming profiles.

 

Just updated to 1.3.1 from using your older standalone plugins. Did the old plugins use 10 or 12 TPS? With trinity, the frenzy spam @ 10 TPS seemed inefficient, but its fine at 12 (I'll probably experiment with higher settings later).

Everything else is working great. Thank you for your hard work.

 

Not using spirit walk for movement.. please add this

 

Can i change tps to 50?

Is rend fixed in 1.3.1?

 

Hmm was trying out Azmodan, but it seems like the avoidance doesnt work properly, for me at least. It was just standing in the pools, till i manually moved it far back (like middle of the room) and then it started avoiding them on its own.

We'll looks like it will kill it even in pools, but might still be nice to fix for lesser geared chars :>

 

Barbarians - To Spam Leap - READ THIS

Hey guys - a lot of you have requested that your barbarian spam leap as soon as it comes up (Iron Impact).

Search for this line (just Ctrl + F and type in a bit of this, and you'll find it)

// Less than 75% health *OR* target >= 18 feet away *OR* an elite within 25 feet of us
(playerStatus.dCurrentHealthPct <= 0.75 || fDistanceFromTarget >= 18f || iElitesWithinRange[RANGE_25] > 0)

See that current health <= 0.75? just change 0.75 to 1. Your baba will then spam leap, without the issue of it waiting until he gets to 75% health.

I also noticed the timing for leap is off in the timing dictionary. It set the timer for leap at 9000, when I believe leap has a 10000 cooldown.

Search for this line: {SNOPower.Barbarian_Leap, 9000}, and change the 9000 to 10000.

Hope this helps. Giles, you're unbelievable. We all feel very fortunate that you're lending your astounding genius to this endeavor.

 

Ol chap giles this would bring me back to default since i tweaked CM Wizzie, unless the layout still the same so i can copy paste my config.

PS: iF got my reading right with ur introduction of avoidance sliders.. Would this fckd up my config? Can u clear this out sport?

 

is anyone else having performance issues with this new 1.3.1 update? everything was smooth before the update but after i installed the new one it seems to lag my d3 client very badly and is causing extreme deaths because of it.

 

fresh install

 

yeah, same with me
I just updated and I was wondering what all this lag is. Going back to 1.3 for now