A5 - Siege Camp Chest Runner V2.0 w/ Chest Sensing & Movement Management

First of all...i wanna say thx for this profile!!Rly nice....i have 2 questions
1)Any chance to disable Timer for creating new game? It will increase gph ~7-10 to my 55
2)Any reason why my Wiz wont use Blink?
-------------
Have latest Db,Trinity,QuestTools,ChestRUn 2.0A (with OCC 2.0A)

 

You can disable the timer in the Settings> Bot menu on the front of DemonBuddy, change Game Wait time.

 

Big thanks sir!

 

What version of DB/Trinity are you using? If you use EZUpdate did you copy in a fresh version of TrinityOOCToggle.cs after it did it's business?


There were NO changes to the profile in 2.0A and the changes in Toggle were conditional on two character classes Wizard and WD.

 

If you see an error on the game screen that says something along the lines error creating game code something. Means you don't have the required quest that that profile is running off of. Would explain why some toons work and others don't. My profile requires you have the kill Maltheal quest. Anyone that has killed him will have it.

Unless you are referring to a Crusader, there is an issue in their Trinity settings at the moment. Try my combat profile for them.

 

Any reason why my Wiz wont use Blink?

 

Except for the 2nd chest where my character sometimes gets stucked, this profile is great.

Hex don't seem to cast so I've placed tags strategically in the profile to force it to cast. Maybe helpful to some
<UsePower questId="1" powerId="30631" />

Also, if you have the Warzechian armguard (bracers that increases movement speed after breaking stuff), you can use Spirit Barrage- Manitou for breakables. Again, UsePower
<UsePower questId="1" powerId="108506" />

Lastly for Wizards,if sleek skin is not casting properly, again as a workaround you can use tags. Putting one after porting in and another after moving to 2nd chest location seems to work ok.
<UsePower questId="1" powerId="75599" />

Thanks Captain for this awesome profile!

 

Short Answer: Trinity

Long Answer: With the recent changes Blizzard made to Teleport, increasing the range, and the way Trinity handles teleporting. My profile toggles OOC movement and just doesn't give Trinity the distance it is looking for when it wants to teleport. If your a bit adventurous you can edit "PlayerMover.cs" in \Demonbuddy\Plugins\Trinity\Movement\. Look for the line "var maxTeleportRange = 75f;" and change it to something lower, would say start at 45 and experiment from there. If you find a number that works well report back to us. I am running my WD at the moment and will eventually get around looking into teleport. If give me a number that works I will post up a modified PlayerMover.cs so others will just have to replace theirs instead of poking around in code.

Code:

                if (CombatBase.CanCast(SNOPower.Wizard_Teleport, CombatBase.CanCastFlags.NoTimer) &&
                    (hasWormHole && WizardTeleportCount < 3 && DateTime.UtcNow.Subtract(CacheData.AbilityLastUsed[SNOPower.Wizard_Teleport]).TotalMilliseconds >= 250) &&
                    DestinationDistance >= 10f && !ShrinesInArea(vMoveToTarget))
                {
                    // Reset teleport count if we've already hit the max
                    if (WizardTeleportCount >= 3)
                        WizardTeleportCount = 0;

                    // increment the teleport count for wormhole rune
                    WizardTeleportCount++;

                    var maxTeleportRange = 75f;

                    Vector3 vThisTarget = vMoveToTarget;
                    if (DestinationDistance > maxTeleportRange)
                        vThisTarget = MathEx.CalculatePointFrom(vMoveToTarget, vMyCurrentPosition, maxTeleportRange);
                    ZetaDia.Me.UsePower(SNOPower.Wizard_Teleport, vThisTarget, Trinity.CurrentWorldDynamicId, -1);
                    CacheData.AbilityLastUsed[SNOPower.Wizard_Teleport] = DateTime.UtcNow;
                    if (Trinity.Settings.Advanced.LogCategories.HasFlag(LogCategory.Movement))
                        Logger.Log(TrinityLogLevel.Debug, LogCategory.Movement, "Using Teleport for OOC movement, distance={0}", DestinationDistance);
                    return;
                }

 

Oops, just noticed that the profile missed opening the last chest. It walked towards it as if to open but didn't and walked away to open the 2nd last chest and then TP out. What could be the issue?

 

Do you know if UsePower checks for the ability prior to casting? Is it from DB, Trinity, or some other plugin?

 

No it does not check for the ability before casting. Should be DB - refer to this guide for the PowerIDs https://docs.google.com/document/d/1E5QSqHlizgNA8zLR5El3UPYM5jmCXjjjQSGUMhKm9G4/edit

 

I have noticed that myself since Trinity 1.8.26. Gonna to try to get away from depending on Trinity to open chests.

"<TrinityInteract questID="1" snoid="289796" />" usually hits chests on the first go like 75% of the time, hits stones 100% of the time. The other 25% of the time I count on Trinity to take over and open the chest because it is in range. Try increasing the chest open range and tell me if that helps. I tried MoveToActor and although it works every time it is horrendously slow.

That 75% rate is also why sometimes opening chests seems like a quick event and other times the bot is intently thinking about it. When everything works the first go its fun to watch. On the 3rd tier it just quickly taps the 2 chests and dances away from the bomb.

 

my crusader decided to bug out

Code:

05:06:27.990 INFO  BnetParty Creating new game. Params: [Act: A5, Difficulty: Torment6, Quest: 273408, QuestStep: 3, ResumeFromSave: False, IsPrivate: True]
05:06:59.529 INFO  BrainBehavior Closing error dialog
05:06:59.629 INFO  BrainBehavior Closing error dialog
05:07:00.847 INFO  BrainBehavior Waiting 2 seconds before next game...
05:07:02.854 ERROR BotMain Exception when terminating bot thread. 
System.Exception: Only part of a ReadProcessMemory or WriteProcessMemory request was completed, at addr: 00000000, Size: 344

so no long log for it. found game disconected and this error don't rly know what happened there.

 

Many thanks. Were where you two days ago.

Guys use his power suggestions carefully. It is very easy to forget to add the spell in or swap toons and forget to update the profile. You don't want to be spamming Blizzard's game with skill requests you don't have. That just screams that you are doing something you shouldn't be.

 

No problems. Now my WD moves so fast I wonder if it will miss a drop because it zips away before the loot shows haha

 

The OOC.cs seems to be clashing with EZUpdater because it will replace the entire Trinity folder when it updates.

 

You shouldn't miss anything. I set the default range to 150, going to increase in the next profile revision. Believe that is slightly off screen.

 

Yes it will but the only way around that would require coding it as a plugin. May happen down the road but right now just disable EZUpdater while the bot is running and if EZUpdater does any updates on load make sure you copy it in again.

 

At the last few chests is the purpose of the WaitTimer after the interact to wait for the loot to drop? Not sure if the bot will register the drop if it already start casting TP because sometimes I notice the TP casting while the chest "opening" animation is still in progress. I tested with gold i.e. set it to pick minimum pile and it actually still ignore the gold and TP back to town. Perhaps I can increase the WaitTimer slightly?

 

Neither do I. If anyone knows DB error codes could you please translate.