[Plugin] Giles Trinity

Giles, just noticed the bot missing some loot right after a fight. He just ran away, and did not have the time "to process" the drops. Moved him back to the are where he killed the mob and he started picking things up.
Can you please implement something like 1 second timer, so that the bot stays at the killing place of an elite? This way he should get the proper time to check for loot.

 

v1.4 uploaded:
- Huge re-working of retrieving object (target) data from DemonBuddy/Diablo 3 each tick and processing/weighting it to improve performance.
-- You should notice some lower CPU usage in general, smoother/faster repeat-attacks with fast attack abilities, and smoother target selections.
-- Performance will increase over time due to new caching systems.
- The "status bar" of DB is no longer updated with what the bot is currently doing by default - this can be re-enabled in the Advanced tab for debugging purposes (enabling has a slight performance hit). Keep disabled unless you are having problems and need to track down the issue to report to me.
- Fixed some issues with priorities/weights for monsters, particularly at close-range.
- Health globes now have a slightly higher priority than before.
- Unstucker now a little more resilient in certain situations, to help evade specific stuck situations (you're still advised to use a dedicated unstucker on top, and/or set DB Inactivity Timer to a low value such as 2).
- "ItemStats" files are now just named "Stats" files ("<bot name> - Stats - <class type>.log"), and at the top now contain actual total death count and deaths-per-hour. Random other misc stats MAY be added later!
- Fixed many skills interpreting monster positions/range incorrectly, particularly abilities such as ancient spear, acid cloud, leap etc.
- Barbarians no longer wait for wrath of berserker to come off cooldown again AFTER killing Azmodan.
- As with most updates, further fixes/tweaks/minor alterations to a variety of class skills/spell uses.

Updating Plugin Versions:
To minimize problems (random slowdowns, oddities with avoidance settings ignoring certain avoidance types), you should always do the following things every time there is a major (eg 1.3 to 1.4) update to Giles Trinity;
1: Make sure DemonBuddy is closed
2: Go into the DemonBuddy folder, and DELETE the entire "CompiledAssemblies" folder from within the DB folder (this is completely fine and safe to do - DemonBuddy will rebuild this folder!).
3: Go into the /settings/ folder within DemonBuddy - in this folder, delete "GilesTrinity.cfg".
4: Load DB and configure the plugin again
Following these quick, simple instructions will fix a lot of random issues that can crop up between upgrades. The reason for these requirements is largely down to the size and complexity of Giles Trinity.

 

Well this is probably what was I asking for in the first place. I do have inactivity timer set on "2", but in current form the unstucker of your plugin wouldn't even let DB think that it is "inactive", that's the part I actually wanted to report really =)

 

Hey Giles, great work as always!

I think I may have figured out a solution to the rend problem (at least one problem). I think when the avoidance is activated, rend doesn't fire, and this is absolutely critical in some builds. To enable rend to spam so you can heal even when there are arcane orbs, etc around, is it just as simple as removing !bAvoidanceEmergency from the rend conditions?

Thanks

 

Am i the only one with problems with town-run? It loads off into the chest before going for the merchant as expected, but when its trying to talk to the merchant the bot misses him and go back and forth into a loop. So it wont sell and repair unless i stop the bot and do it manually. This started in the last version for me, and also in this one (v 1.4).

Other than that its a great plugin!

 

thanks, looking forward to DH support

 

Selling is working fine for me. Thanks for disabling teleport in town Giles

Still having a little avoidance issues especially with the act 1 tree poison cloud spore things.

Other than that everything is perfect. This new version is insanely fast!

Note to other CM/SC wizards who are using teleport with the "Allow of-out-combat movement powers" option checked, you can make your character teleport faster by changing this line:

{SNOPower.Wizard_Teleport, 16000}

to

{SNOPower.Wizard_Teleport, 1000}

 

what about DHs?

 

It would appear in 1.4 sweeping winds for monks is not being triggered, including large aoe scenarios where blind has just been used.

EDIT: I take that back, restarted DB and everything's working flawlessly. Good work Giles!!

 

Thanks Giles! 1.4 fixes pretty much all the few remaining issues I had.

 

Holy ****

my WW barb is now like god - he moves like a real player!
the update is what i waited for!

but one thing: sometimes he runs away from champs/elites. he fights like 1 minute and then he ignores them.. i changed the range f?r non elite, but didnt change anything.

great work man, in the next days, i will donate to you, keep up the good work *happy*

 

I moved from act 1 to 2 with this update. Farming act 2 like a boss now

 

some still (known) issues:

1) goblin chasing; the bot will stop chasing the goblin as soon as there is a trash mob (no need to be body blocked), probably has to do with elite/trash priorization because of issue 2) (?)

2) elite is not prioritized in combat, noticable e.g. when there are some ranged elite the bot will first attack the near trash. That becomes a problem when the wotb is used and the ranged elite tries to flee. The bot will then attack the closest trash, runnning out of wotb and then chase the elites. Imo there should be some option to burst down the elite in any case disregarding any trash. That would also probably solve the problem with the goblin as he is regarded as elite in D3

3) probably related to 2) is the fact that the bot often lose the ranged elites, especially the ones that try to run in different directions (okkulists, sukkubus etc). After killing one the bot just "forgets" to kill the rest


edit: i am using non-elite-combat radius set to 4, so basically the bot should more or less ignore the trash

edit2: there is some serious flaw in elite priority, as now i also see that the bot suddenly stops to attack melee elite and just runs on ....

 

How come when my wizard go into archon it doesn't hold down right click to keep attacking?

 

1.4 Something is seriously wrong with elite priority because he's leaving out lots of them. What I mean with that in some cases he's just walking right past them in other cases he kills 1 to 3 elites of a pack but leaves out the final 1 or 2..

Other then that 1.4 is a major improvement for Critical Mass / Frost Nova / Explosive Blast / Energy Twister (Storm Chaser) Wizards.

 

Explosive Blast range is set to 12f

 

Notice this as well...big problem master giles. Elites getting skipped..mostly its just the ranged ones. And also its mostly the yellow pack not the blue packs.

 

Blue Range packs get skipped as well (the mage type ones in tower of cursed..)

I changed the priority value for elites seems to be working again.

look for this and make sure to change it above 1000 I changed it to 1500 seems to be okay.

Code:

                                    // Give more weight to elites
                                    if (thisgilesobject.bThisEliteRareUnique || thisgilesobject.bThisBoss)
                                        thisgilesobject.dThisWeight += 850;

edit

okay that doesnt seem to totaly fix it he is still leaving out elites not as many as before but still a range on here and there.

 

Man it still doesn't use rend!

In an elite fight, the bot uses rend ONCE at the start and then spams the main fury generator skill until they die..range is still off

 

Giles, great work as always. I noticed on my monk the combat is smoother and faster. The avoidance is faster too. The only thing I would like to see improved on is how often it spams Mantra. Right now it seems that it doesn't spam it enough.
I did notice one bug over all. If you interrupt the bot during a town run it stops all together. Other then that it seemed to run very well. Thanks again for all you hard work. It is much appreciated.