What's new
  • Visit Rebornbuddy
  • Visit Panda Profiles
  • Visit LLamamMagic
  • Visit Resources
  • Visit Downloads
  • Visit Portal

Trinity 1.8.23

Status
Not open for further replies.
ProfileOrderManager.OnGameJoined, Reloading profile.
[Trinity] New Game - resetting everything
Loaded profile Rifter - A Bot for Rifts!

Endless loop in .22,.23,.24
 
How about you tell me why you can't do bounties or rifts? I'm running them fine...

Bot will stay at the cursed Chest till inactivity timer or Teleports to town and Leaves.
Bot blacklists All Pony's and bears that are elite/Champion packs
Bot get stucks at nephelem portal
2014-04-17 22:30:10,963 [Main Bot Thread] INFO Logger (null) - [Trinity] Clicking UI element Conversation Button (928698368)
2014-04-17 22:30:11,048 [Main Bot Thread] INFO Logger (null) - [Trinity] Clicking UI element Conversation Button (928698368)
^ but it does this while standing at the portal

also a lot of back tracking of the same areas 3-5 times even after full explored.

Posting logs
 

Attachments

Last edited:
I believe you are trying to run the new rift profile without replacing trinityexploredungeon.cs that is included in the first post of the profile.. Also if you have ezupdater enabled it will overwrite it and you will bug out again.
 
bot talks again and again with tyreal before he start normal profile like kulle ...

[Trinity] Clicking UI element Conversation Button (799682560)
[Trinity] Clicking UI element Conversation Button (799682560)
[Trinity] Clicking UI element Conversation Button (799682560)

newest DB BETA + Trinity works good

only the conversation thing is shitty^^

maybe send me a message how i can fix that^^
 
Last edited:
The Trinity Combat Settings for Demon Hunter are not working properly. My DH is suiciding into molten, standing on top of arcane and basically going afk on desecrate (not even attacking while it stands on the desecrate).

Arcane: 15-100
Desecrate: 11-100
Molten: 27-100
 
Trinity will now automatically interact with Quest Giver

Please let us disable this. This breaks all kinds of profiles for me, and also closes rifts during town runs even when you're not done clearing them completely. I use blank profiles to play, and this made me close a rift on my party when I was playing with them. Had a hard time explaining that one.
 
This issue has been in the last few releases

WD Issue:
- Not casting Big Bad Voodoo on single Boss's (Testing on Ghom) Seems to work when multiple elites are there (Kulle)

Quoting in case it gets lost

BBV settings in WitchDoctor.cs are identical as in 1.8.19... it worked in that but not the last 2/3 releases

Changing it from 12f > 20f works but it casts it too far away meaning i lose the buff shortly after. I'm not sure what has changed since 1.8.19 but it worked a lot better in that release.
 
Last edited:
I dont know really what this is but when it spams my diablo 3 client freezes for 1-3 seconds its really annoying.

Code:
[Trinity][Performance] Execution of the block RefreshDiaObjectCache.AvoidanceCheck took 1010.88ms.
[Trinity][Performance] Execution of the block RefreshDiaObjectCache took 1016.81ms.
[Trinity][Performance] Execution of the block TargetCheck.RefreshCache took 1017.11ms.
[Trinity][Performance] Execution of the block TargetCheck took 1030.91ms.
[Trinity][Performance] Execution of the block RefreshDiaObjectCache.AvoidanceCheck took 1082.71ms.
[Trinity][Performance] Execution of the block RefreshDiaObjectCache took 1089.46ms.
[Trinity][Performance] Execution of the block HandleTarget.CheckForNewTarget took 1089.73ms.
[Trinity][Performance] Execution of the block HandleTarget took 1366.56ms.
[Trinity][Performance] Execution of the block RefreshDiaObjectCache.AvoidanceCheck took 1093.58ms.
[Trinity][Performance] Execution of the block RefreshDiaObjectCache took 1101.40ms.
[Trinity][Performance] Execution of the block HandleTarget.CheckForNewTarget took 1101.70ms.
[Trinity][Performance] Execution of the block HandleTarget took 1385.65ms.
[Trinity][Performance] Execution of the block RefreshDiaObjectCache.AvoidanceCheck took 1500.98ms.
[Trinity][Performance] Execution of the block RefreshDiaObjectCache took 1518.17ms.
[Trinity][Performance] Execution of the block HandleTarget.CheckForNewTarget took 1518.50ms.
[Trinity][Performance] Execution of the block HandleTarget took 1834.59ms.
[Trinity][Performance] Execution of the block RefreshDiaObjectCache.AvoidanceCheck took 1483.26ms.
[Trinity][Performance] Execution of the block RefreshDiaObjectCache took 1494.59ms.
[Trinity][Performance] Execution of the block HandleTarget.CheckForNewTarget took 1494.89ms.
[Trinity][Performance] Execution of the block HandleTarget took 1817.30ms.
[Trinity][Performance] Execution of the block RefreshDiaObjectCache.AvoidanceCheck took 1891.68ms.
[Trinity][Performance] Execution of the block RefreshDiaObjectCache took 1903.16ms.
[Trinity][Performance] Execution of the block HandleTarget.CheckForNewTarget took 1903.45ms.
[Trinity][Performance] Execution of the block HandleTarget took 2168.24ms.
[Trinity][Performance] Execution of the block RefreshDiaObjectCache.AvoidanceCheck took 1228.17ms.
[Trinity][Performance] Execution of the block RefreshDiaObjectCache took 1248.49ms.
[Trinity][Performance] Execution of the block HandleTarget.CheckForNewTarget took 1249.03ms.
[Trinity][Performance] Execution of the block HandleTarget took 1333.53ms.
[Trinity][Performance] Execution of the block RefreshDiaObjectCache.AvoidanceCheck took 1698.93ms.
[Trinity][Performance] Execution of the block RefreshDiaObjectCache took 1709.58ms.
[Trinity][Performance] Execution of the block HandleTarget.CheckForNewTarget took 1709.87ms.
[Trinity][Performance] Execution of the block HandleTarget took 1951.20ms.
[Trinity][Performance] Execution of the block RefreshDiaObjectCache.AvoidanceCheck took 1040.91ms.
[Trinity][Performance] Execution of the block RefreshDiaObjectCache took 1048.18ms.
[Trinity][Performance] Execution of the block TargetCheck.RefreshCache took 1048.54ms.
[Trinity][Performance] Execution of the block TargetCheck took 1048.78ms.
[Trinity][Performance] Execution of the block RefreshDiaObjectCache.AvoidanceCheck took 1042.51ms.
[Trinity][Performance] Execution of the block RefreshDiaObjectCache took 1053.95ms.
[Trinity][Performance] Execution of the block TargetCheck.RefreshCache took 1054.19ms.
[Trinity][Performance] Execution of the block TargetCheck took 1080.87ms.
[Trinity][Performance] Execution of the block RefreshDiaObjectCache.AvoidanceCheck took 1394.82ms.
[Trinity][Performance] Execution of the block RefreshDiaObjectCache took 1402.62ms.
[Trinity][Performance] Execution of the block HandleTarget.CheckForNewTarget took 1402.93ms.
[Trinity][Performance] Execution of the block HandleTarget took 1920.56ms.
[Trinity][Performance] Execution of the block RefreshDiaObjectCache.AvoidanceCheck took 1360.30ms.
[Trinity][Performance] Execution of the block RefreshDiaObjectCache took 1368.49ms.
[Trinity][Performance] Execution of the block HandleTarget.CheckForNewTarget took 1368.79ms.
[Trinity][Performance] Execution of the block HandleTarget took 1785.00ms.
[Trinity][Performance] Execution of the block RefreshDiaObjectCache.AvoidanceCheck took 1311.83ms.
[Trinity][Performance] Execution of the block RefreshDiaObjectCache took 1319.79ms.
[Trinity][Performance] Execution of the block HandleTarget.CheckForNewTarget took 1320.09ms.
[Trinity][Performance] Execution of the block HandleTarget took 1893.98ms.
[Trinity][Performance] Execution of the block RefreshDiaObjectCache.AvoidanceCheck took 1119.98ms.
[Trinity][Performance] Execution of the block RefreshDiaObjectCache took 1135.36ms.
[Trinity][Performance] Execution of the block HandleTarget.CheckForNewTarget took 1135.65ms.
[Trinity][Performance] Execution of the block HandleTarget took 1467.90ms.
 
I dont know really what this is but when it spams my diablo 3 client freezes for 1-3 seconds its really annoying.

Code:
[Trinity][Performance] Execution of the block RefreshDiaObjectCache.AvoidanceCheck took 1010.88ms.
[Trinity][Performance] Execution of the block RefreshDiaObjectCache took 1016.81ms.
[Trinity][Performance] Execution of the block TargetCheck.RefreshCache took 1017.11ms.
[Trinity][Performance] Execution of the block TargetCheck took 1030.91ms.
[Trinity][Performance] Execution of the block RefreshDiaObjectCache.AvoidanceCheck took 1082.71ms.
[Trinity][Performance] Execution of the block RefreshDiaObjectCache took 1089.46ms.
[Trinity][Performance] Execution of the block HandleTarget.CheckForNewTarget took 1089.73ms.
[Trinity][Performance] Execution of the block HandleTarget took 1366.56ms.
[Trinity][Performance] Execution of the block RefreshDiaObjectCache.AvoidanceCheck took 1093.58ms.
[Trinity][Performance] Execution of the block RefreshDiaObjectCache took 1101.40ms.
[Trinity][Performance] Execution of the block HandleTarget.CheckForNewTarget took 1101.70ms.
[Trinity][Performance] Execution of the block HandleTarget took 1385.65ms.
[Trinity][Performance] Execution of the block RefreshDiaObjectCache.AvoidanceCheck took 1500.98ms.
[Trinity][Performance] Execution of the block RefreshDiaObjectCache took 1518.17ms.
[Trinity][Performance] Execution of the block HandleTarget.CheckForNewTarget took 1518.50ms.
[Trinity][Performance] Execution of the block HandleTarget took 1834.59ms.
[Trinity][Performance] Execution of the block RefreshDiaObjectCache.AvoidanceCheck took 1483.26ms.
[Trinity][Performance] Execution of the block RefreshDiaObjectCache took 1494.59ms.
[Trinity][Performance] Execution of the block HandleTarget.CheckForNewTarget took 1494.89ms.
[Trinity][Performance] Execution of the block HandleTarget took 1817.30ms.
[Trinity][Performance] Execution of the block RefreshDiaObjectCache.AvoidanceCheck took 1891.68ms.
[Trinity][Performance] Execution of the block RefreshDiaObjectCache took 1903.16ms.
[Trinity][Performance] Execution of the block HandleTarget.CheckForNewTarget took 1903.45ms.
[Trinity][Performance] Execution of the block HandleTarget took 2168.24ms.
[Trinity][Performance] Execution of the block RefreshDiaObjectCache.AvoidanceCheck took 1228.17ms.
[Trinity][Performance] Execution of the block RefreshDiaObjectCache took 1248.49ms.
[Trinity][Performance] Execution of the block HandleTarget.CheckForNewTarget took 1249.03ms.
[Trinity][Performance] Execution of the block HandleTarget took 1333.53ms.
[Trinity][Performance] Execution of the block RefreshDiaObjectCache.AvoidanceCheck took 1698.93ms.
[Trinity][Performance] Execution of the block RefreshDiaObjectCache took 1709.58ms.
[Trinity][Performance] Execution of the block HandleTarget.CheckForNewTarget took 1709.87ms.
[Trinity][Performance] Execution of the block HandleTarget took 1951.20ms.
[Trinity][Performance] Execution of the block RefreshDiaObjectCache.AvoidanceCheck took 1040.91ms.
[Trinity][Performance] Execution of the block RefreshDiaObjectCache took 1048.18ms.
[Trinity][Performance] Execution of the block TargetCheck.RefreshCache took 1048.54ms.
[Trinity][Performance] Execution of the block TargetCheck took 1048.78ms.
[Trinity][Performance] Execution of the block RefreshDiaObjectCache.AvoidanceCheck took 1042.51ms.
[Trinity][Performance] Execution of the block RefreshDiaObjectCache took 1053.95ms.
[Trinity][Performance] Execution of the block TargetCheck.RefreshCache took 1054.19ms.
[Trinity][Performance] Execution of the block TargetCheck took 1080.87ms.
[Trinity][Performance] Execution of the block RefreshDiaObjectCache.AvoidanceCheck took 1394.82ms.
[Trinity][Performance] Execution of the block RefreshDiaObjectCache took 1402.62ms.
[Trinity][Performance] Execution of the block HandleTarget.CheckForNewTarget took 1402.93ms.
[Trinity][Performance] Execution of the block HandleTarget took 1920.56ms.
[Trinity][Performance] Execution of the block RefreshDiaObjectCache.AvoidanceCheck took 1360.30ms.
[Trinity][Performance] Execution of the block RefreshDiaObjectCache took 1368.49ms.
[Trinity][Performance] Execution of the block HandleTarget.CheckForNewTarget took 1368.79ms.
[Trinity][Performance] Execution of the block HandleTarget took 1785.00ms.
[Trinity][Performance] Execution of the block RefreshDiaObjectCache.AvoidanceCheck took 1311.83ms.
[Trinity][Performance] Execution of the block RefreshDiaObjectCache took 1319.79ms.
[Trinity][Performance] Execution of the block HandleTarget.CheckForNewTarget took 1320.09ms.
[Trinity][Performance] Execution of the block HandleTarget took 1893.98ms.
[Trinity][Performance] Execution of the block RefreshDiaObjectCache.AvoidanceCheck took 1119.98ms.
[Trinity][Performance] Execution of the block RefreshDiaObjectCache took 1135.36ms.
[Trinity][Performance] Execution of the block HandleTarget.CheckForNewTarget took 1135.65ms.
[Trinity][Performance] Execution of the block HandleTarget took 1467.90ms.

Restart Diablo 3 and Demonbuddy and see if that helps.
 
'''What steps will reproduce the problem?'''
Avoiding monster's with min distance till kite (wizard)

'''What is the expected result?'''
Bot should run from monsters to specific range then continue to nuke (using disintegrate with temporal flux passive 80% slow 2s)

'''What happens instead?'''
Toon runs from them then almost immediately runs right back to the monster's sorta like it hits the distance it's meant to keep then something overrides it so it runs back in real close, Particularly annoying on giant hammer mobs but also it get's stuck in kite/dont kite loop for a bit so doesn't do damage more pronounced if it has just run into a pack and is surrounded.

'''Please provide any additional information below.'''

This is with newest DB beta and .24 Trinity using Nowaylol's hellrift exp/gold profile

Edit seems intermittent not sure if it's freaking out due to the warping guys but just watched it do a run where it kited pretty flawlessly i'll delete my logs and see if i can catch it in the act so u can see if something it interfearing
 
Last edited:
Suggestion: For Arcane Orb - Arcane Orbit, could you shorten the range to melee range? For melee wizards :)
Not a big deal though, not sure if anyone is doing that.
 
Last edited:
Where is the auto turn in quest code. .24 runs great, but I really need to disable that and I don't want to rollback to .22
 
Hmm.. my bots just sitting here attempting to cast town portal; the portal is bugged though until I manually move the character a step. Then it works. Not sure what's causing it, but it seems Trinitys auto-unstuck feature isn't working as intended.
 
Status
Not open for further replies.
Back
Top