[Plugin] Giles Trinity

[Bajne]

Hey there

Is it possible to adjust the combat settings so all mobs are killed in the areas set?

 

[xzhenx]

Just need to know which blacklist they want adding to - do you still have the SNO dumps? I want to know if the SNO dump (the dump ractors) listed them as a "Unit" or an "Object" - if a Unit, then they need to go in the attack blacklist. If an object, then they need to go in the world-object blacklist! The bot might be trying to "attack" because it thinks it's a unit, or it might be trying to "attack" because it thinks it's a destructible object. I would SUSPECT the fire-spouts it thinks are units, and the table/chairs are destructibles, but I'll need confirmation/clarification!

[18955AA8] GizmoType: Destructible Name: a3dun_Keep_Chair_A_Breakable-4379 ActorSNO: 54952 Distance: 4.884042 Position: <856.6887, 778.223, 0> Barracade: False

[F0634D8] Type: Unit Name: a3dun_keep_firewall2-2463 ActorSNO: 199998, Distance: 33.87622

Couldn't find the the chair and the other firewall (199997) in a couple of runs, basically the other firewall is the extended version with larger surface area. Those walls should be avoided at all cost btw! They tick harder than the center of arcane beams.

 

[Agro]

A change I have been testing which should improve things, you can test yourself until I release (as I have other things being worked on too). Find this;

            // Force update targets at least once every 8 movement loops
            iLoopsSinceLastTargetUpdate++;
            if (iLoopsSinceLastTargetUpdate > 8)
            {
                return RunStatus.Success;
            }

Try changing that 8, to a 4. You could try lower, but I'd recommend trying 4 for now. This is how often (how many loops) the bot re-checks for objects in it's area (for new targets, items, avoidances) while currently trying to move towards a target or object. It may be that I can actually lower than to a 2 - it was set to 8 before Trinity 1.4 - before all the optimization stuff, as object-checking was the biggest performance hit - but since Trinity 1.4, object checking is now hellishly fast, so it shouldn't have much performance hit at all to lower this, and it will improve bot performance everywhere.

So yeah, changing that to 4/lower, is a bit of a "sneak preview" of a small change that should have a big splash in the next Trinity release - but I'd also appreciate people giving me feedback on the performance/CPU hit by setting that to even lower numbers (I have a very powerful gaming machine, so be good to hear from people with not so uber gaming machines)

I just went ahead and jumped right to 1. I don't see any noticeable performance degradation, I'm playing on an i5-2500k 3.2 overclocked to 4.5.. I normally run at @ 21% cpu load, with 1 copy of the game and 1 copy of the bot running. After the change, it went up to 23%, but that's really negligible imo. After making the change, I can see that ice balls and molten explosions are being avoided much much better, but it still acts as if the arcane sentry doesn't exist. Not sure if it's this change, or the actual update to the plugin itself but I also noticed that rend is being used like a beast now. It still misses some times due to being out of range, but it is used much more frequently now. Thanks for the quick response, hope to hear something soon.

 

[Moley]

I just went ahead and jumped right to 1. I don't see any noticeable performance degradation, I'm playing on an i5-2500k 3.2 overclocked to 4.5.. I normally run at @ 21% cpu load, with 1 copy of the game and 1 copy of the bot running. After the change, it went up to 23%, but that's really negligible imo. After making the change, I can see that ice balls and molten explosions are being avoided much much better, but it still acts as if the arcane sentry doesn't exist. Not sure if it's this change, or the actual update to the plugin itself but I also noticed that rend is being used like a beast now. It still misses some times due to being out of range, but it is used much more frequently now. Thanks for the quick response, hope to hear something soon.

good to know, we'll get this avoidance bug tracked down

 

[Dantronix]

You can't be fucking serious. I'm hoping sarcasm?

Yah dude it does not support demonhunters. Give Giles a break man! He does good workk. Just try a different character. I can help you with the build if you need it!

 

[Agro]

I double checked the ActorSNOs for both of the arcane sentrys. They are right in the code, but I'm wondering if DB is reporting their distance incorrectly? In the log window, DB reported an Arcane Sentry 23 yards away from me, but I was actually standing right next to it. Maybe someone else could check that?

 

[Bertrand]

One more thing, rend is working great when there are small to medium number of units arround my toon. The problem seems to start to appear once my character is surrounded by 6+ horde pack. Then he simply fails to use rend when it is of outmost importance, once the number is down to 3-4 he will start using rend... da fak with that Is there any way to make rend priority n1 once there are x+ units arround my character ?

 

[Elmegaard]

It doesn't priorities goblins even if you turn the feature on. If any mob is closer to you than the goblin it will change target and ignore the goblin.

 

[taquitos]

Played around with the bot a bit last night. Tested a variety of setups after doing a clean install. I figured out how to produce the mobtype skipping error (was able to reproduce skipping moloks and heralds) but I don't know why it's doing this. If you start the bot up in a game that has already begun (stop/start - dumping RActors and other testing; starting in a game after cleaning out bank) it seems the bot will flag one kind of mob as a blacklist. I'm unsure of why this happens but I'll test some more and see if I can figure out what exactly is causing it. I just know that the error is reproducible and is specific to games that already are up.

 

[AngelsHalo]

Regarding avoidance, is there a way to set so you only avoid "arcane core" (the main center ball of the arcane) while ignoring the beams? I can tank the beams just fine but sometimes the bot will run or get knocked back into the core and get creamed by tons of damage every second. If I set to just avoid arcane entirely, he will run away from the beams which often confuses the bot and ultimately drops dps the mobs.

 

[frosty]

to those picking up more than 30 rares per hour:
Can you post your stats?
Rares/hour:
DPS (unbuffed):
Resists:
Armor:
Life:
Deaths/hour:
Strength:
LoH:
LifeLeech:
Crit%:
CritDMG%:
Block%:
Movespeed%:
Build:

 

[Bertrand]

Regarding avoidance, is there a way to set so you only avoid "arcane core" (the main center ball of the arcane) while ignoring the beams? I can tank the beams just fine but sometimes the bot will run or get knocked back into the core and get creamed by tons of damage every second. If I set to just avoid arcane entirely, he will run away from the beams which often confuses the bot and ultimately drops dps the mobs.

Yes you can avoid the core, set radius for arcane dodging to 7 or 9, that should do it. The closer you are to the beam (smaller number value in radius) the longer the sentry will apply dmg on u.

 

[AngelsHalo]

Yes you can avoid the core, set radius for arcane dodging to 7 or 9, that should do it. The closer you are to the beam (smaller number value in radius) the longer the sentry will apply dmg on u.

Thank you, will try this soon!

Also, watching the bot for the past hour, I would like to thank Giles for the very smart item pickup... it seems like if an item is near by but enemies are still there, it will often pick the item up first before going to the next enemy to fight. I think its doing a great job with items so far, and not missing things like in the past (which I think is DB's fault, not Giles).

 

[gotteshand]

A change I have been testing which should improve things, you can test yourself until I release (as I have other things being worked on too). Find this;

            // Force update targets at least once every 8 movement loops
            iLoopsSinceLastTargetUpdate++;
            if (iLoopsSinceLastTargetUpdate > 8)
            {
                return RunStatus.Success;
            }

Try changing that 8, to a 4. You could try lower, but I'd recommend trying 4 for now. This is how often (how many loops) the bot re-checks for objects in it's area (for new targets, items, avoidances) while currently trying to move towards a target or object. It may be that I can actually lower than to a 2 - it was set to 8 before Trinity 1.4 - before all the optimization stuff, as object-checking was the biggest performance hit - but since Trinity 1.4, object checking is now hellishly fast, so it shouldn't have much performance hit at all to lower this, and it will improve bot performance everywhere.

So yeah, changing that to 4/lower, is a bit of a "sneak preview" of a small change that should have a big splash in the next Trinity release - but I'd also appreciate people giving me feedback on the performance/CPU hit by setting that to even lower numbers (I have a very powerful gaming machine, so be good to hear from people with not so uber gaming machines)

Tested this earlier and setting it so anything below 8 is really really bad for Critical Mass builds. Attackrate and reaction times turn to utter crap attackrate is slowed down quit a bit and its taking the bot way longer to react to enemys.

 

[Makaronnik]

I've made a fresh install of the latest version and DB/RadManager and I'm shocked. My barb began to die fantastic often. He dies even on white big groups of mobs. He uses rend often vs one mob or when there are no mobs around, but when fighting vs group of mobs - almost never. 80% of time he runs with 100% fury. Also he doesn't avoid most of arcane sentries, plague, molten cores and trail. 24 deaths/hour now vs 2-3 usual.
Giles please make some urgent fixes.

 

[MrWizard516]

I've made a fresh install of the latest version and DB/RadManager and I'm shocked. My barb began to die fantastic often. He dies even on white big groups of mobs. He uses rend often vs one mob or when there are no mobs around, but when fighting vs group of mobs - almost never. 80% of time he runs with 100% fury. Also he doesn't avoid most of arcane sentries, plague, molten cores and trail. 24 deaths/hour now vs 2-3 usual.
Giles please make some urgent fixes.

@Makaronnik: That sounds like you may have done something wrong. I run a barb myself and have not seen anything like you described. What are your character's stats?

@Giles: When you get a chance please look at the town run routine for Act 3. I noticed that sometimes with no help from me it will just stop right in front of the stash box right after vendoring and do nothing. This only happens if I have my town run set to salvage. If it is set to only sell then it runs fine. I have had this happen several times on me. I noticed that it will also do that if you interrupt it while it is trying to do the town run. I have only seen this happen in Act 3.
Other then that it runs AWESOME! Makes my Monk look like a god.

 

[carguy]

I've made a fresh install of the latest version and DB/RadManager and I'm shocked. My barb began to die fantastic often. He dies even on white big groups of mobs. He uses rend often vs one mob or when there are no mobs around, but when fighting vs group of mobs - almost never. 80% of time he runs with 100% fury. Also he doesn't avoid most of arcane sentries, plague, molten cores and trail. 24 deaths/hour now vs 2-3 usual.
Giles please make some urgent fixes.

Clearly user error here.


Sounds like:

A-You aren't nearly geared well enough
B-Your spec sucks.
C-You are trying to use conflicting plugins?
D-You somehow are using an old version of the plugin still (shit happens)

 

[Makaronnik]

That sounds like you may have done something wrong. I run a barb myself and have not seen anything like you described. What are your character's stats?

I can't imagine what could I do wrong. Reinstalled everything from scratch as usual, default settings. 2 days ago bot worked perfectly.
Stats: 50k dps (buffed), 8k armor, 800 allres, 50k hp, 41% block chance (storm shield). Act 3.

 

[ryan12345]

The only problem I am having is my guy doesnt like to avoid arcane at all

Other than that, thanks giles!

 

[bombastic]

Giles, let me say... 1.4.4 is nearly flawless. Good job. Again

Some suggestions

- Goblins are now being chased almost all the time, but on rare occasions the bot still ignores them (like if a elites shows up -- and this is a regular thing). My suggestion: change the IF statement, responsible for prioritize.

// Force a close range target because we seem to be stuck *OR* if not ranged and currently rooted
                                if (bPrioritizeCloseRange && (!thisgilesobject.bThisTreasureGoblin || (thisgilesobject.bThisTreasureGoblin && settings.iTreasureGoblinPriority != 2)))

That way if Prioritize Goblins is set to max level on GUI, goblins are never going to be missed (or maybe create a new Option on GUI, "Suicidal prioritize" or something for goblins and use the IF above )

- Some SNO's chest from act 3, missing on hashObjectSNOContainerWhitelist: 111870, 111947, 213447, 213446, 51300, 179865 (making all these chest to be actually ignored by giles)

- SNO 132951 (bomb flyer, act 3) must be included in hashActorSNOIgnoreBlacklist, but actually is on hashObjectSNOIgnoreBlacklist

- Can you add a GUI switch to disable your unstuck? It's actually pretty good, but I prefer UnstuckMe, and both running at the same time is notable worst than running UnstuckMe alone

- Is it possible make the bot break everything if on a minimum range? Some good things now and then drops from blood containers and other breakable stuff. I tried to change that code, to make everything inside 12 feet to be breakable, with no luck:

line 2490:

if (thisobj.PhysicsSNO <= 0 && tmp_fCentreDistance > 12f)