• Visit Rebornbuddy
  • Visit Panda Profiles
  • Visit LLamamMagic
  • [Profiles] Adventure Mode Bounties - Community Edition

    Discussion in 'Archives' started by sychotix, Apr 4, 2014.

    Thread Status:
    Not open for further replies.
    1. teninchtotem

      teninchtotem Member

      Joined:
      Apr 17, 2014
      Messages:
      98
      Likes Received:
      0
      Trophy Points:
      6
      How would someone go about blacklisting the chandeliers and such in the cathedral for the bounties? I have watched the bot sit at one of the interaction points for almost 80 seconds doing nothing and almost triggering the inactivity timer?

      Edit: for the record quest tools .45 Trinity .24
       
    2. newb420

      newb420 New Member

      Joined:
      Oct 30, 2012
      Messages:
      367
      Likes Received:
      0
      Trophy Points:
      0
      you need to download DB beta the new trinity is not working with the non beta DB version
       
    3. S o u L D u s T

      S o u L D u s T New Member

      Joined:
      Dec 8, 2013
      Messages:
      96
      Likes Received:
      0
      Trophy Points:
      0
      where do you guys find trinity .24 ???

      only see .23 on the forums!
       
    4. optico89

      optico89 Member

      Joined:
      Jul 13, 2012
      Messages:
      91
      Likes Received:
      0
      Trophy Points:
      6
      you can get the new .24 trinity via ezupdater plugin.

      as of right now, you dont need the bountyprofile.cs or the zbountyprofile plugin.

      Also, the most current up to date version are as follows, please make sure you're fully updated before posting issues, as many of the issues are resolved once fully updated properly.

      DB-Beta Version .391
      QuestTools version .45
      Trinity Version .24
      EZUpdater version .2.1
      SVN Bounties Revision # 178

      Also, Sychotix mentioned a few pages back that EZUpdater should be able to update EVERYTHING as of now, and you don't need to manually update your profiles via SVN unless you want to.
       
      Last edited: Apr 17, 2014
    5. sychotix

      sychotix New Member

      Joined:
      Dec 13, 2013
      Messages:
      727
      Likes Received:
      5
      Trophy Points:
      0
      I was skimming the past couple of pages that happened when I was gone. I saw mention that people wanted to know where the zbountyprofile.cs was. It is deleted for a reason, as it is included in the newest version of Trinity. As has been stated before, please ensure that you are using DemonBuddy Beta (As linked to in the first post) to make sure you can get this working correctly.
       
    6. mrbigsexy

      mrbigsexy New Member

      Joined:
      Apr 13, 2014
      Messages:
      109
      Likes Received:
      0
      Trophy Points:
      0
    7. sdre

      sdre New Member

      Joined:
      Jun 25, 2012
      Messages:
      14
      Likes Received:
      0
      Trophy Points:
      0
      just wanna say that i updated with ezupdater and its runnig act 1 and 4 right now!

      thanks!
       
    8. tuca

      tuca New Member

      Joined:
      Oct 24, 2012
      Messages:
      21
      Likes Received:
      0
      Trophy Points:
      0
      hey one question i dont know what im doing wrong here if someone can help me plz. My problem is that the bot starts a new game after doing the second bounty on act 4 it keeps giving me this error

      System.Exception: Requested value 'BountyComplete' was not found. - Line: 29
      at ..(PropertyInfo , XAttribute , Object )
      at Zeta.XmlEngine.XmlEngine.Load(Object obj, XElement element)
      at ..(PropertyInfo , XElement , Object )
      at Zeta.XmlEngine.XmlEngine.Load(Object obj, XElement element)
      at ..(XElement , Type )
      at ...(XElement )
      at System.Linq.Enumerable.WhereSelectEnumerableIterator`2.MoveNext()
      at System.Collections.Generic.List`1..ctor(IEnumerable`1 collection)
      at System.Linq.Enumerable.ToList[TSource](IEnumerable`1 source)
      at ..(XElement , PropertyInfo )
      at ..(PropertyInfo , XElement , Object )
      at Zeta.XmlEngine.XmlEngine.Load(Object obj, XElement element)
      at Zeta.Bot.Profile.Profile.Load(XElement element, String path)
      at Zeta.Bot.Profile.Profile.Load(String path)
      at Zeta.Bot.ProfileManager.Load(String profilePath, Boolean rememberPath)

      here is my log too View attachment 64808 2014-04-17 16.35.txt View attachment 19016 2014-04-17 21.24.txt
       
    9. sychotix

      sychotix New Member

      Joined:
      Dec 13, 2013
      Messages:
      727
      Likes Received:
      5
      Trophy Points:
      0
      Your trinity is out of date.
       
    10. tuca

      tuca New Member

      Joined:
      Oct 24, 2012
      Messages:
      21
      Likes Received:
      0
      Trophy Points:
      0
      is that the reason why is only doing 2 bounties? whats the last version of trinity? can someone post the link pls
       
    11. Tumzie

      Tumzie Member

      Joined:
      Feb 16, 2013
      Messages:
      341
      Likes Received:
      3
      Trophy Points:
      18
      Hey guys,

      After my last SVN update these profiles stop right after I start them. Using Trinity .22 and latest DB and QuestTools.
       
    12. sychotix

      sychotix New Member

      Joined:
      Dec 13, 2013
      Messages:
      727
      Likes Received:
      5
      Trophy Points:
      0
      We are on trinity .24 now, so I doubt you are using the latest QuestTools either. Please update.

      @tuca, look at the instructions on the first page.
       
    13. xzjv

      xzjv Community Developer

      Joined:
      Mar 17, 2014
      Messages:
      1,243
      Likes Received:
      46
      Trophy Points:
      48
      http://www.thebuddyforum.com/demonbuddy-forum/plugins/157992-plugin-zbountydumper.html is not needed for running adventure profiles. It is just a quick tool i made that lists all the bounties for an act. it was useful to me because i didn't want to waste time waiting until the end of the act to find out if any of them were unsupported. The bot needs to be stopped for the buttons to work. Its probably not that useful right now. I heard Sychotix say ALT+5 also listed the current bounty but i've yet to have that work for me.
       
    14. zennshinagas

      zennshinagas New Member

      Joined:
      Apr 17, 2014
      Messages:
      3
      Likes Received:
      0
      Trophy Points:
      1
      Nothing was working whatsoever on all the latest versions. Did a completely clean install of DB Beta and manually updated all the plugins.

      Bot has been running A4 flawlessly for 3 hours now on my wizard.
       
    15. optico89

      optico89 Member

      Joined:
      Jul 13, 2012
      Messages:
      91
      Likes Received:
      0
      Trophy Points:
      6
      Act 1 - Kill the Butcher - Bot got seriously stuck, then crashed DB....

      Code:
      Loaded profile Act 1 - Loader
      Act 1 Bounties
      Loaded profile Kill the Butcher (347032)
      [Trinity] TrinityTownPortal started - clearing area, waitTime=2500, startHealth=414196
      [Trinity] Town Portal timer finished
      Using Waypoint. Number:17
      [Trinity][Performance] Execution of the block RefreshDiaObjectCache.Kiting took 2912.65ms.
      [Trinity][Performance] Execution of the block RefreshDiaObjectCache took 2958.61ms.
      [Trinity][Performance] Execution of the block HandleTarget.CheckForNewTarget took 2959.48ms.
      [Trinity][Performance] Execution of the block HandleTarget took 3164.92ms.
      [Trinity][Performance] Execution of the block RefreshDiaObjectCache.AvoidanceCheck took 2989.70ms.
      [Trinity][Performance] Execution of the block RefreshDiaObjectCache took 3012.55ms.
      [Trinity][Performance] Execution of the block HandleTarget.CheckForNewTarget took 3013.29ms.
      [Trinity] Your bot got stuck! Trying to unstuck (attempt #1 of 10 attempts) Act="OpenWorld" questId="312429" stepId="2" worldId="58983"
      [Trinity][Performance] Execution of the block NavigateTo took 1575.50ms.
      [Trinity][Performance] Execution of the block HandleTarget.HandleBasicMovement took 1576.70ms.
      [Trinity][Performance] Execution of the block HandleTarget took 4594.33ms.
      [Trinity][Performance] Execution of the block RefreshDiaObjectCache.AvoidanceCheck took 2313.75ms.
      [Trinity][Performance] Execution of the block RefreshDiaObjectCache took 2355.42ms.
      [Trinity][Performance] Execution of the block HandleTarget.CheckForNewTarget took 2356.21ms.
      [Trinity][Performance] Execution of the block HandleTarget took 2599.90ms.
      [Trinity][Performance] Execution of the block RefreshDiaObjectCache.AvoidanceCheck took 2457.15ms.
      [Trinity][Performance] Execution of the block RefreshDiaObjectCache took 2478.95ms.
      [Trinity][Performance] Execution of the block TargetCheck.RefreshCache took 2479.76ms.
      [Trinity][Performance] Execution of the block TargetCheck took 2480.47ms.
      [Trinity] Found Object 158944!
      [Trinity][Performance] Execution of the block RefreshDiaObjectCache.AvoidanceCheck took 1294.46ms.
      [Trinity][Performance] Execution of the block RefreshDiaObjectCache took 1322.36ms.
      [Trinity][Performance] Execution of the block TargetCheck.RefreshCache took 1323.05ms.
      [Trinity][Performance] Execution of the block TargetCheck took 1329.24ms.
      [Trinity][Performance] Execution of the block RefreshDiaObjectCache.AvoidanceCheck took 1378.95ms.
      [Trinity][Performance] Execution of the block RefreshDiaObjectCache took 1397.40ms.
      [Trinity][Performance] Execution of the block TargetCheck.RefreshCache took 1398.24ms.
      [Trinity][Performance] Execution of the block TargetCheck took 1408.97ms.
      [Trinity][Performance] Execution of the block RefreshDiaObjectCache.AvoidanceCheck took 1066.57ms.
      [Trinity][Performance] Execution of the block RefreshDiaObjectCache took 1084.54ms.
      [Trinity][Performance] Execution of the block TargetCheck.RefreshCache took 1085.41ms.
      [Trinity][Performance] Execution of the block TargetCheck took 1091.69ms.
      [Trinity][Performance] Execution of the block RefreshDiaObjectCache.AvoidanceCheck took 1035.95ms.
      [Trinity][Performance] Execution of the block RefreshDiaObjectCache took 1051.75ms.
      [Trinity][Performance] Execution of the block TargetCheck.RefreshCache took 1052.62ms.
      [Trinity][Performance] Execution of the block TargetCheck took 1060.13ms.
      [Trinity][Performance] Execution of the block RefreshDiaObjectCache.AvoidanceCheck took 1047.53ms.
      [Trinity][Performance] Execution of the block RefreshDiaObjectCache took 1063.77ms.
      [Trinity][Performance] Execution of the block TargetCheck.RefreshCache took 1064.78ms.
      [Trinity][Performance] Execution of the block TargetCheck took 1071.52ms.
      [Trinity][Performance] Execution of the block RefreshDiaObjectCache.AvoidanceCheck took 1039.47ms.
      [Trinity][Performance] Execution of the block RefreshDiaObjectCache took 1054.98ms.
      [Trinity][Performance] Execution of the block TargetCheck.RefreshCache took 1055.84ms.
      [Trinity][Performance] Execution of the block TargetCheck took 1063.13ms.
      [Trinity][Performance] Execution of the block RefreshDiaObjectCache.AvoidanceCheck took 1063.68ms.
      [Trinity][Performance] Execution of the block RefreshDiaObjectCache.Kiting took 1432.56ms.
      [Trinity][Performance] Execution of the block RefreshDiaObjectCache took 2513.88ms.
      [Trinity][Performance] Execution of the block TargetCheck.RefreshCache took 2514.64ms.
      [Trinity][Performance] Execution of the block TargetCheck took 2518.82ms.
      [Trinity][Performance] Execution of the block RefreshDiaObjectCache.AvoidanceCheck took 1075.91ms.
      [Trinity][Performance] Execution of the block RefreshDiaObjectCache.Kiting took 1403.81ms.
      [Trinity][Performance] Execution of the block RefreshDiaObjectCache took 2498.15ms.
      [Trinity][Performance] Execution of the block HandleTarget.CheckForNewTarget took 2498.85ms.
      [Trinity][Performance] Execution of the block HandleTarget took 2513.44ms.
      [Trinity][Performance] Execution of the block RefreshDiaObjectCache.AvoidanceCheck took 1115.09ms.
      [Trinity][Performance] Execution of the block RefreshDiaObjectCache.Kiting took 1420.49ms.
      [Trinity][Performance] Execution of the block RefreshDiaObjectCache took 2555.35ms.
      [Trinity][Performance] Execution of the block HandleTarget.CheckForNewTarget took 2556.15ms.
      [Trinity][Performance] Execution of the block HandleTarget took 2614.56ms.
      [Trinity][Performance] Execution of the block RefreshDiaObjectCache.AvoidanceCheck took 1118.02ms.
      [Trinity][Performance] Execution of the block RefreshDiaObjectCache.Kiting took 1412.53ms.
      [Trinity][Performance] Execution of the block RefreshDiaObjectCache took 2550.98ms.
      [Trinity][Performance] Execution of the block HandleTarget.CheckForNewTarget took 2551.73ms.
      [Trinity][Performance] Execution of the block HandleTarget took 2650.03ms.
      [Trinity][Performance] Execution of the block RefreshDiaObjectCache.AvoidanceCheck took 1127.95ms.
      [Trinity][Performance] Execution of the block RefreshDiaObjectCache.Kiting took 1442.13ms.
      [Trinity][Performance] Execution of the block RefreshDiaObjectCache took 2590.86ms.
      [Trinity][Performance] Execution of the block HandleTarget.CheckForNewTarget took 2591.52ms.
      [Trinity][Performance] Execution of the block HandleTarget took 2651.09ms.
      [Trinity][Performance] Execution of the block RefreshDiaObjectCache.AvoidanceCheck took 1025.82ms.
      [Trinity][Performance] Execution of the block RefreshDiaObjectCache.Kiting took 1435.00ms.
      [Trinity][Performance] Execution of the block RefreshDiaObjectCache took 2479.38ms.
      [Trinity][Performance] Execution of the block HandleTarget.CheckForNewTarget took 2480.20ms.
      [Trinity][Performance] Execution of the block HandleTarget took 2540.95ms.
      [Trinity][Performance] Execution of the block RefreshDiaObjectCache.AvoidanceCheck took 1105.40ms.
      [Trinity][Performance] Execution of the block RefreshDiaObjectCache took 1124.45ms.
      [Trinity][Performance] Execution of the block HandleTarget.CheckForNewTarget took 1125.29ms.
      [Trinity][Performance] Execution of the block HandleTarget took 1146.72ms.
      [Trinity][Performance] Execution of the block RefreshDiaObjectCache.AvoidanceCheck took 1063.62ms.
      [Trinity][Performance] Execution of the block RefreshDiaObjectCache took 1081.43ms.
      [Trinity][Performance] Execution of the block HandleTarget.CheckForNewTarget took 1082.34ms.
      [Trinity][Performance] Execution of the block HandleTarget took 1115.66ms.
      [Trinity][Performance] Execution of the block RefreshDiaObjectCache.AvoidanceCheck took 1098.29ms.
      [Trinity][Performance] Execution of the block RefreshDiaObjectCache took 1117.72ms.
      [Trinity][Performance] Execution of the block HandleTarget.CheckForNewTarget took 1118.86ms.
      [Trinity][Performance] Execution of the block HandleTarget took 1167.06ms.
      [Trinity][Performance] Execution of the block RefreshDiaObjectCache.AvoidanceCheck took 1071.14ms.
      [Trinity][Performance] Execution of the block RefreshDiaObjectCache took 1089.08ms.
      [Trinity][Performance] Execution of the block HandleTarget.CheckForNewTarget took 1090.22ms.
      [Trinity][Performance] Execution of the block HandleTarget took 1175.29ms.
      [Trinity][Performance] Execution of the block RefreshDiaObjectCache.AvoidanceCheck took 1096.62ms.
      [Trinity][Performance] Execution of the block RefreshDiaObjectCache took 1116.23ms.
      [Trinity][Performance] Execution of the block HandleTarget.CheckForNewTarget took 1117.47ms.
      [Trinity][Performance] Execution of the block HandleTarget took 1212.04ms.
      [Trinity][Performance] Execution of the block RefreshDiaObjectCache.AvoidanceCheck took 1065.43ms.
      [Trinity][Performance] Execution of the block RefreshDiaObjectCache took 1083.59ms.
      [Trinity][Performance] Execution of the block HandleTarget.CheckForNewTarget took 1084.50ms.
      [Trinity][Performance] Execution of the block HandleTarget took 1149.18ms.
      [Trinity][Performance] Execution of the block RefreshDiaObjectCache.AvoidanceCheck took 1074.42ms.
      [Trinity][Performance] Execution of the block RefreshDiaObjectCache took 1093.41ms.
      [Trinity][Performance] Execution of the block HandleTarget.CheckForNewTarget took 1094.48ms.
      [Trinity][Performance] Execution of the block HandleTarget took 1182.01ms.
      [Trinity][Performance] Execution of the block RefreshDiaObjectCache.AvoidanceCheck took 1086.20ms.
      [Trinity][Performance] Execution of the block RefreshDiaObjectCache took 1106.20ms.
      [Trinity][Performance] Execution of the block HandleTarget.CheckForNewTarget took 1107.18ms.
      [Trinity][Performance] Execution of the block HandleTarget took 1176.02ms.
      [Trinity][Performance] Execution of the block RefreshDiaObjectCache.AvoidanceCheck took 1061.62ms.
      [Trinity][Performance] Execution of the block RefreshDiaObjectCache took 1079.53ms.
      [Trinity][Performance] Execution of the block HandleTarget.CheckForNewTarget took 1080.45ms.
      [Trinity][Performance] Execution of the block HandleTarget took 1148.50ms.
      [Trinity][Performance] Execution of the block RefreshDiaObjectCache.AvoidanceCheck took 1064.42ms.
      [Trinity][Performance] Execution of the block RefreshDiaObjectCache took 1082.24ms.
      [Trinity][Performance] Execution of the block HandleTarget.CheckForNewTarget took 1084.53ms.
      [Trinity][Performance] Execution of the block HandleTarget took 1145.33ms.
      [Trinity][Performance] Execution of the block RefreshDiaObjectCache.Kiting took 1122.39ms.
      [Trinity][Performance] Execution of the block RefreshDiaObjectCache took 2127.92ms.
      [Trinity][Performance] Execution of the block HandleTarget.CheckForNewTarget took 2128.73ms.
      [Trinity][Performance] Execution of the block HandleTarget took 2222.98ms.
      [Trinity][Performance] Execution of the block RefreshDiaObjectCache.AvoidanceCheck took 1057.39ms.
      [Trinity][Performance] Execution of the block RefreshDiaObjectCache.Kiting took 1444.36ms.
      [Trinity][Performance] Execution of the block RefreshDiaObjectCache took 2523.66ms.
      [Trinity][Performance] Execution of the block HandleTarget.CheckForNewTarget took 2524.61ms.
      [Trinity][Performance] Execution of the block HandleTarget took 2610.91ms.
      [Trinity][Performance] Execution of the block RefreshDiaObjectCache.AvoidanceCheck took 1008.77ms.
      [Trinity][Performance] Execution of the block RefreshDiaObjectCache.Kiting took 1326.97ms.
      [Trinity][Performance] Execution of the block RefreshDiaObjectCache took 2354.87ms.
      [Trinity][Performance] Execution of the block HandleTarget.CheckForNewTarget took 2355.86ms.
      [Trinity][Performance] Execution of the block HandleTarget took 2445.70ms.
      [Trinity][Performance] Execution of the block RefreshDiaObjectCache.AvoidanceCheck took 1022.34ms.
      [Trinity][Performance] Execution of the block RefreshDiaObjectCache.Kiting took 1501.88ms.
      [Trinity][Performance] Execution of the block RefreshDiaObjectCache took 2544.52ms.
      [Trinity][Performance] Execution of the block HandleTarget.CheckForNewTarget took 2545.19ms.
      [Trinity][Performance] Execution of the block HandleTarget took 2644.58ms.
      [Trinity][Performance] Execution of the block RefreshDiaObjectCache.Kiting took 1319.11ms.
      [Trinity][Performance] Execution of the block RefreshDiaObjectCache took 2328.59ms.
      [Trinity][Performance] Execution of the block HandleTarget.CheckForNewTarget took 2329.48ms.
      [Trinity][Performance] Execution of the block HandleTarget took 2410.11ms.
      [Trinity][Performance] Execution of the block RefreshDiaObjectCache.AvoidanceCheck took 1024.01ms.
      [Trinity][Performance] Execution of the block RefreshDiaObjectCache.Kiting took 1312.95ms.
      [Trinity][Performance] Execution of the block RefreshDiaObjectCache took 2360.35ms.
      [Trinity][Performance] Execution of the block HandleTarget.CheckForNewTarget took 2361.06ms.
      [Trinity][Performance] Execution of the block HandleTarget took 2381.07ms.
      [Trinity][Performance] Execution of the block RefreshDiaObjectCache.AvoidanceCheck took 1004.55ms.
      [Trinity][Performance] Execution of the block RefreshDiaObjectCache.Kiting took 1306.84ms.
      [Trinity][Performance] Execution of the block RefreshDiaObjectCache took 2329.84ms.
      [Trinity][Performance] Execution of the block HandleTarget.CheckForNewTarget took 2330.62ms.
      [Trinity][Performance] Execution of the block HandleTarget took 2378.17ms.
      [Trinity][Performance] Execution of the block RefreshDiaObjectCache.AvoidanceCheck took 1073.57ms.
      [Trinity][Performance] Execution of the block RefreshDiaObjectCache.Kiting took 1349.30ms.
      [Trinity][Performance] Execution of the block RefreshDiaObjectCache took 2441.52ms.
      [Trinity][Performance] Execution of the block HandleTarget.CheckForNewTarget took 2442.60ms.
      [Trinity][Performance] Execution of the block HandleTarget took 2546.15ms.
      [Trinity][Performance] Execution of the block RefreshDiaObjectCache.AvoidanceCheck took 1068.01ms.
      [Trinity][Performance] Execution of the block RefreshDiaObjectCache.Kiting took 1354.40ms.
      [Trinity][Performance] Execution of the block RefreshDiaObjectCache took 2441.11ms.
      [Trinity][Performance] Execution of the block HandleTarget.CheckForNewTarget took 2441.81ms.
      [Trinity][Performance] Execution of the block HandleTarget took 2520.85ms.
      [Trinity][Performance] Execution of the block RefreshDiaObjectCache.AvoidanceCheck took 1047.35ms.
      [Trinity][Performance] Execution of the block RefreshDiaObjectCache.Kiting took 1359.70ms.
      [Trinity][Performance] Execution of the block RefreshDiaObjectCache took 2428.13ms.
      [Trinity][Performance] Execution of the block HandleTarget.CheckForNewTarget took 2429.00ms.
      [Trinity][Performance] Execution of the block HandleTarget took 2514.48ms.
      [Trinity][Performance] Execution of the block HandleTarget took 1001.99ms.
      [Trinity][Performance] Execution of the block RefreshDiaObjectCache.AvoidanceCheck took 1001.68ms.
      [Trinity][Performance] Execution of the block RefreshDiaObjectCache took 1020.51ms.
      [Trinity][Performance] Execution of the block HandleTarget.CheckForNewTarget took 1021.51ms.
      [Trinity][Performance] Execution of the block HandleTarget took 1095.29ms.
      [Trinity][Performance] Execution of the block RefreshDiaObjectCache took 1000.45ms.
      [Trinity][Performance] Execution of the block HandleTarget.CheckForNewTarget took 1001.36ms.
      [Trinity][Performance] Execution of the block HandleTarget took 1006.42ms.
      [Trinity][Performance] Execution of the block RefreshDiaObjectCache.AvoidanceCheck took 1161.23ms.
      [Trinity][Performance] Execution of the block RefreshDiaObjectCache took 1181.79ms.
      [Trinity][Performance] Execution of the block HandleTarget.CheckForNewTarget took 1182.87ms.
      [Trinity][Performance] Execution of the block HandleTarget took 1265.95ms.
      [Trinity][Performance] Execution of the block RefreshDiaObjectCache.Kiting took 1321.64ms.
      [Trinity][Performance] Execution of the block RefreshDiaObjectCache took 1345.86ms.
      [Trinity][Performance] Execution of the block HandleTarget.CheckForNewTarget took 1346.63ms.
      [Trinity][Performance] Execution of the block HandleTarget took 1440.91ms.
      [Trinity][Performance] Execution of the block RefreshDiaObjectCache.Kiting took 1245.38ms.
      [Trinity][Performance] Execution of the block RefreshDiaObjectCache took 1267.88ms.
      [Trinity][Performance] Execution of the block HandleTarget.CheckForNewTarget took 1268.60ms.
      [Trinity][Performance] Execution of the block HandleTarget took 1294.86ms.
      [Trinity][Performance] Execution of the block RefreshDiaObjectCache.AvoidanceCheck took 1311.62ms.
      [Trinity][Performance] Execution of the block RefreshDiaObjectCache took 1319.73ms.
      [Trinity][Performance] Execution of the block HandleTarget.CheckForNewTarget took 1320.42ms.
      [Trinity][Performance] Execution of the block HandleTarget took 1354.51ms.
      [Trinity][Performance] Execution of the block RefreshDiaObjectCache.AvoidanceCheck took 1073.86ms.
      [Trinity][Performance] Execution of the block RefreshDiaObjectCache took 1091.66ms.
      [Trinity][Performance] Execution of the block HandleTarget.CheckForNewTarget took 1092.74ms.
      [Trinity][Performance] Execution of the block HandleTarget took 1180.06ms.
      [Trinity][Performance] Execution of the block RefreshDiaObjectCache.AvoidanceCheck took 1103.73ms.
      [Trinity][Performance] Execution of the block RefreshDiaObjectCache took 1120.80ms.
      [Trinity][Performance] Execution of the block HandleTarget.CheckForNewTarget took 1121.82ms.
      [Trinity][Performance] Execution of the block HandleTarget took 1202.39ms.
      [Trinity][Performance] Execution of the block RefreshDiaObjectCache.AvoidanceCheck took 1084.64ms.
      [Trinity][Performance] Execution of the block RefreshDiaObjectCache took 1103.86ms.
      [Trinity][Performance] Execution of the block HandleTarget.CheckForNewTarget took 1105.12ms.
      [Trinity][Performance] Execution of the block HandleTarget took 1178.99ms.
      [Trinity][Performance] Execution of the block RefreshDiaObjectCache.AvoidanceCheck took 1070.89ms.
      [Trinity][Performance] Execution of the block RefreshDiaObjectCache took 1087.64ms.
      [Trinity][Performance] Execution of the block HandleTarget.CheckForNewTarget took 1088.55ms.
      [Trinity][Performance] Execution of the block HandleTarget took 1103.05ms.
      [Trinity][Performance] Execution of the block RefreshDiaObjectCache.AvoidanceCheck took 1130.59ms.
      [Trinity][Performance] Execution of the block RefreshDiaObjectCache took 1147.66ms.
      [Trinity][Performance] Execution of the block HandleTarget.CheckForNewTarget took 1148.49ms.
      [Trinity][Performance] Execution of the block HandleTarget took 1170.66ms.
      [Trinity][Performance] Execution of the block RefreshDiaObjectCache.AvoidanceCheck took 1057.62ms.
      [Trinity][Performance] Execution of the block RefreshDiaObjectCache took 1074.67ms.
      [Trinity][Performance] Execution of the block HandleTarget.CheckForNewTarget took 1075.74ms.
      [Trinity][Performance] Execution of the block HandleTarget took 1122.58ms.
      [Trinity][Performance] Execution of the block RefreshDiaObjectCache.AvoidanceCheck took 1079.20ms.
      [Trinity][Performance] Execution of the block RefreshDiaObjectCache took 1099.44ms.
      [Trinity][Performance] Execution of the block HandleTarget.CheckForNewTarget took 1100.29ms.
      [Trinity][Performance] Execution of the block HandleTarget took 1172.58ms.
      [Trinity][Performance] Execution of the block RefreshDiaObjectCache.AvoidanceCheck took 1104.37ms.
      [Trinity][Performance] Execution of the block RefreshDiaObjectCache took 1122.76ms.
      [Trinity][Performance] Execution of the block HandleTarget.CheckForNewTarget took 1123.58ms.
      [Trinity][Performance] Execution of the block HandleTarget took 1234.55ms.
      [Trinity][Performance] Execution of the block RefreshDiaObjectCache.AvoidanceCheck took 1121.49ms.
      [Trinity][Performance] Execution of the block RefreshDiaObjectCache took 1149.35ms.
      [Trinity][Performance] Execution of the block HandleTarget.CheckForNewTarget took 1150.41ms.
      [Trinity][Performance] Execution of the block HandleTarget took 1273.10ms.
      [Trinity][Performance] Execution of the block RefreshDiaObjectCache.AvoidanceCheck took 1176.45ms.
      [Trinity][Performance] Execution of the block RefreshDiaObjectCache.Kiting took 1538.10ms.
      [Trinity][Performance] Execution of the block RefreshDiaObjectCache took 2738.23ms.
      [Trinity][Performance] Execution of the block HandleTarget.CheckForNewTarget took 2738.95ms.
      [Trinity][Performance] Execution of the block HandleTarget took 2829.05ms.
      [Trinity][Performance] Execution of the block RefreshDiaObjectCache.AvoidanceCheck took 1168.98ms.
      [Trinity][Performance] Execution of the block RefreshDiaObjectCache took 1191.04ms.
      [Trinity][Performance] Execution of the block HandleTarget.CheckForNewTarget took 1192.33ms.
      [Trinity][Performance] Execution of the block HandleTarget took 1249.62ms.
      [Trinity][Performance] Execution of the block RefreshDiaObjectCache.AvoidanceCheck took 1126.43ms.
      [Trinity][Performance] Execution of the block RefreshDiaObjectCache took 1144.81ms.
      [Trinity][Performance] Execution of the block HandleTarget.CheckForNewTarget took 1145.72ms.
      [Trinity][Performance] Execution of the block HandleTarget took 1278.97ms.
      [Trinity][Performance] Execution of the block RefreshDiaObjectCache.AvoidanceCheck took 1161.86ms.
      [Trinity][Performance] Execution of the block RefreshDiaObjectCache took 1180.11ms.
      [Trinity][Performance] Execution of the block HandleTarget.CheckForNewTarget took 1181.01ms.
      [Trinity][Performance] Execution of the block HandleTarget took 1273.28ms.
      [Trinity][Performance] Execution of the block RefreshDiaObjectCache.AvoidanceCheck took 1092.53ms.
      [Trinity][Performance] Execution of the block RefreshDiaObjectCache took 1112.25ms.
      [Trinity][Performance] Execution of the block HandleTarget.CheckForNewTarget took 1113.33ms.
      [Trinity][Performance] Execution of the block HandleTarget took 1233.90ms.
      [Trinity][Performance] Execution of the block RefreshDiaObjectCache.AvoidanceCheck took 1101.00ms.
      [Trinity][Performance] Execution of the block RefreshDiaObjectCache.Kiting took 1381.74ms.
      [Trinity][Performance] Execution of the block RefreshDiaObjectCache took 2502.74ms.
      [Trinity][Performance] Execution of the block HandleTarget.CheckForNewTarget took 2503.41ms.
      [Trinity][Performance] Execution of the block HandleTarget took 2589.32ms.
      [Trinity][Performance] Execution of the block RefreshDiaObjectCache.AvoidanceCheck took 1155.81ms.
      [Trinity][Performance] Execution of the block RefreshDiaObjectCache.Kiting took 1410.43ms.
      [Trinity][Performance] Execution of the block RefreshDiaObjectCache took 2584.93ms.
      [Trinity][Performance] Execution of the block HandleTarget.CheckForNewTarget took 2585.88ms.
      [Trinity][Performance] Execution of the block HandleTarget took 2677.14ms.
      [Trinity][Performance] Execution of the block RefreshDiaObjectCache.AvoidanceCheck took 1217.19ms.
      [Trinity][Performance] Execution of the block RefreshDiaObjectCache.Kiting took 1434.84ms.
      [Trinity][Performance] Execution of the block RefreshDiaObjectCache took 2676.28ms.
      [Trinity][Performance] Execution of the block HandleTarget.CheckForNewTarget took 2677.18ms.
      [Trinity][Performance] Execution of the block HandleTarget took 2703.42ms.
      [Trinity][Performance] Execution of the block RefreshDiaObjectCache.AvoidanceCheck took 1150.30ms.
      [Trinity][Performance] Execution of the block RefreshDiaObjectCache took 1168.65ms.
      [Trinity][Performance] Execution of the block HandleTarget.CheckForNewTarget took 1169.67ms.
      [Trinity][Performance] Execution of the block HandleTarget took 1223.62ms.
      [Trinity][Performance] Execution of the block RefreshDiaObjectCache.AvoidanceCheck took 1141.60ms.
      [Trinity][Performance] Execution of the block RefreshDiaObjectCache took 1161.32ms.
      [Trinity][Performance] Execution of the block HandleTarget.CheckForNewTarget took 1162.52ms.
      [Trinity][Performance] Execution of the block HandleTarget took 1238.77ms.
      [Trinity][Performance] Execution of the block RefreshDiaObjectCache.AvoidanceCheck took 1124.58ms.
      [Trinity][Performance] Execution of the block RefreshDiaObjectCache.Kiting took 1390.85ms.
      [Trinity][Performance] Execution of the block RefreshDiaObjectCache took 2534.70ms.
      [Trinity][Performance] Execution of the block HandleTarget.CheckForNewTarget took 2535.57ms.
      [Trinity][Performance] Execution of the block HandleTarget took 2608.61ms.
      [Trinity][Performance] Execution of the block RefreshDiaObjectCache.AvoidanceCheck took 1059.23ms.
      [Trinity][Performance] Execution of the block RefreshDiaObjectCache.Kiting took 1399.22ms.
      [Trinity][Performance] Execution of the block RefreshDiaObjectCache took 2478.09ms.
      [Trinity][Performance] Execution of the block HandleTarget.CheckForNewTarget took 2478.90ms.
      [Trinity][Performance] Execution of the block HandleTarget took 2564.46ms.
      [Trinity][Performance] Execution of the block RefreshDiaObjectCache.AvoidanceCheck took 1061.50ms.
      [Trinity][Performance] Execution of the block RefreshDiaObjectCache.Kiting took 1411.46ms.
      [Trinity][Performance] Execution of the block RefreshDiaObjectCache took 2493.72ms.
      [Trinity][Performance] Execution of the block HandleTarget.CheckForNewTarget took 2494.78ms.
      [Trinity][Performance] Execution of the block HandleTarget took 2575.45ms.
      [Trinity][Performance] Execution of the block RefreshDiaObjectCache.AvoidanceCheck took 1112.33ms.
      [Trinity][Performance] Execution of the block RefreshDiaObjectCache took 1129.53ms.
      [Trinity][Performance] Execution of the block HandleTarget.CheckForNewTarget took 1130.43ms.
      [Trinity][Performance] Execution of the block HandleTarget took 1163.08ms.
      [Trinity][Performance] Execution of the block RefreshDiaObjectCache.AvoidanceCheck took 1187.56ms.
      [Trinity][Performance] Execution of the block RefreshDiaObjectCache took 1211.22ms.
      [Trinity][Performance] Execution of the block HandleTarget.CheckForNewTarget took 1212.49ms.
      [Trinity][Performance] Execution of the block HandleTarget took 1264.58ms.
      [Trinity][Performance] Execution of the block RefreshDiaObjectCache.AvoidanceCheck took 1185.51ms.
      [Trinity][Performance] Execution of the block RefreshDiaObjectCache took 1205.31ms.
      [Trinity][Performance] Execution of the block HandleTarget.CheckForNewTarget took 1206.53ms.
      [Trinity][Performance] Execution of the block HandleTarget took 1269.19ms.
      [Trinity][Performance] Execution of the block RefreshDiaObjectCache.AvoidanceCheck took 1149.02ms.
      [Trinity][Performance] Execution of the block RefreshDiaObjectCache took 1168.12ms.
      [Trinity][Performance] Execution of the block HandleTarget.CheckForNewTarget took 1169.22ms.
      [Trinity][Performance] Execution of the block HandleTarget took 1245.43ms.
      [Trinity][Performance] Execution of the block RefreshDiaObjectCache.AvoidanceCheck took 1075.74ms.
      [Trinity][Performance] Execution of the block RefreshDiaObjectCache.Kiting took 1385.92ms.
      [Trinity][Performance] Execution of the block RefreshDiaObjectCache took 2482.23ms.
      [Trinity][Performance] Execution of the block HandleTarget.CheckForNewTarget took 2483.25ms.
      [Trinity][Performance] Execution of the block HandleTarget took 2583.37ms.
      [Trinity][Performance] Execution of the block RefreshDiaObjectCache.AvoidanceCheck took 1064.06ms.
      [Trinity][Performance] Execution of the block RefreshDiaObjectCache.Kiting took 1469.64ms.
      [Trinity][Performance] Execution of the block RefreshDiaObjectCache took 2552.71ms.
      [Trinity][Performance] Execution of the block HandleTarget.CheckForNewTarget took 2553.42ms.
      [Trinity][Performance] Execution of the block HandleTarget took 2611.64ms.
      [Trinity][Performance] Execution of the block RefreshDiaObjectCache.AvoidanceCheck took 1054.63ms.
      [Trinity][Performance] Execution of the block RefreshDiaObjectCache.Kiting took 1468.67ms.
      [Trinity][Performance] Execution of the block RefreshDiaObjectCache took 2542.60ms.
      [Trinity][Performance] Execution of the block HandleTarget.CheckForNewTarget took 2543.63ms.
      [Trinity][Performance] Execution of the block HandleTarget took 2610.50ms.
      [Trinity][Performance] Execution of the block RefreshDiaObjectCache.AvoidanceCheck took 1141.75ms.
      [Trinity][Performance] Execution of the block RefreshDiaObjectCache.Kiting took 1500.20ms.
      [Trinity][Performance] Execution of the block RefreshDiaObjectCache took 2661.56ms.
      [Trinity][Performance] Execution of the block HandleTarget.CheckForNewTarget took 2662.38ms.
      [Trinity][Performance] Execution of the block HandleTarget took 2680.87ms.
      [Trinity][Performance] Execution of the block RefreshDiaObjectCache.AvoidanceCheck took 1234.66ms.
      [Trinity][Performance] Execution of the block RefreshDiaObjectCache.Kiting took 1611.97ms.
      [Trinity][Performance] Execution of the block RefreshDiaObjectCache took 2867.85ms.
      [Trinity][Performance] Execution of the block HandleTarget.CheckForNewTarget took 2868.75ms.
      [Trinity][Performance] Execution of the block HandleTarget took 2932.05ms.
      [Trinity][Performance] Execution of the block RefreshDiaObjectCache.AvoidanceCheck took 1212.70ms.
      [Trinity][Performance] Execution of the block RefreshDiaObjectCache took 1232.67ms.
      [Trinity][Performance] Execution of the block HandleTarget.CheckForNewTarget took 1233.52ms.
      [Trinity][Performance] Execution of the block HandleTarget took 1263.14ms.
      [Trinity][Performance] Execution of the block RefreshDiaObjectCache.AvoidanceCheck took 1115.53ms.
      [Trinity][Performance] Execution of the block RefreshDiaObjectCache took 1132.93ms.
      [Trinity][Performance] Execution of the block HandleTarget.CheckForNewTarget took 1134.02ms.
      [Trinity][Performance] Execution of the block HandleTarget took 1208.45ms.
      
       
    16. sychotix

      sychotix New Member

      Joined:
      Dec 13, 2013
      Messages:
      727
      Likes Received:
      5
      Trophy Points:
      0
      Crashed DB? Any idea what might have caused that? Nothing from the profiles should be crashing DB.
       
    17. mrbigsexy

      mrbigsexy New Member

      Joined:
      Apr 13, 2014
      Messages:
      109
      Likes Received:
      0
      Trophy Points:
      0
      LOL. Upgrade to .24 and I get the same issues as I was having last night.
      Loaded profile Act 4 - Loader
      Chose Trinity as your combat routine
      Loaded profile Act 4 - Loader
      Chose Trinity as your combat routine
      [Trinity] Bot Starting
      [Trinity] Note: Maintaining item stats from previous run. To reset stats fully, please restart DB.
      ProfileOrderManager.OnGameJoined, Reloading profile.
      [Trinity] New Game - resetting everything
      Loaded profile Act 4 - Loader
      Game joined, Resetting profile caches.
      ProfileOrderManager.OnGameJoined, Reloading profile.
      [Trinity] New Game - resetting everything
      Loaded profile Act 4 - Loader
      Game joined, Resetting profile caches.
      ProfileOrderManager.OnGameJoined, Reloading profile.
      [Trinity] New Game - resetting everything
      Loaded profile Act 4 - Loader
      Game joined, Resetting profile caches.
      ProfileOrderManager.OnGameJoined, Reloading profile.
      [Trinity] New Game - resetting everything
      Loaded profile Act 4 - Loader
      Game joined, Resetting profile caches.
      ProfileOrderManager.OnGameJoined, Reloading profile.
      [Trinity] New Game - resetting everything
      Loaded profile Act 4 - Loader
      Game joined, Resetting profile caches.
      ProfileOrderManager.OnGameJoined, Reloading profile.
      [Trinity] New Game - resetting everything
      Loaded profile Act 4 - Loader
      Game joined, Resetting profile caches.
      ProfileOrderManager.OnGameJoined, Reloading profile.
      [Trinity] New Game - resetting everything
      Loaded profile Act 4 - Loader
      Game joined, Resetting profile caches.
      Stopping the bot.
      Chose Trinity as your combat routine
      ProfileOrderManager.OnGameJoined, Reloading profile.
      [Trinity] New Game - resetting everything
      Loaded profile Act 4 - Loader
      Game joined, Resetting profile caches.
      Bot Thread Ended. Was this requested?

      Already gave you my log. Going back to .22 again and will never upgrade ever again. Why ruin something that is working fine, right?

      EDIT: .22 is working like a charm. The only thing I changed from what you see above and how it works now is Trinity versions. Nothing else was deleted or installed. The problem solely lies with Trinity or how Trinity communicates with these profiles.
       
      Last edited: Apr 17, 2014
    18. optico89

      optico89 Member

      Joined:
      Jul 13, 2012
      Messages:
      91
      Likes Received:
      0
      Trophy Points:
      6
      I have no idea, all i know is it happened as i was looking at it and i was in aww and question the entire time... lol literally stared at the tv for 5 or so minutes like... seriously.. wtf?


      Basically you can see from the log though that the bot loaded the bounty, kill the butcher, then it got stuck...
      after that, all the latency came in and basically took over the log. I did a character check, and its over 48309 characters of "trinity performance execution" dialog in red font.

      when i started seeing the sheets of red continue down the log window, i noticed that the TPS went from 15, down to .82, and then it crashed.

      I'm thinking its maybe the flames that come up from the floor and the bot didnt know where to go since the entire floor, or at least a good majority of it lit up, and got stuck. although after the flames go down, the bot should have been able to say hey im not stuck any more...

      as far as the crash goes, i cant find any info on why it crashed, nor any errors in the log.

      just a dead, blank crash with no info to go over :/
       
    19. Glancey

      Glancey New Member

      Joined:
      Jul 13, 2012
      Messages:
      313
      Likes Received:
      0
      Trophy Points:
      0
      SimpleFollow & Bounty Profile Fix

      1) Replace Plugins/SimpleFollow/FollowTag.cs with the attached updated version. (If you use multiple DB folders make sure you put it in your followers folder.)
      2) Launch or restart DB and continue as normal.

      rrrix's original teleport to leader function use the in-town banners not the actual teleport to player function you can use in game by right clicking a party members portrait.

      My changes replace some follower behavior to ensure that they teleport back to town when the leader switches zones. This allows them to then banner back to the leaders new location.

      *** This isn't tested on anything other than the bounty profile so I suggest you back up your original FollowTag.cs before overwriting so you can switch between them depending on whether you want to run bounties or another profile. Do not place backups in the SimpleFollow folder; this seems to break the plugin even if renamed. That said, none of the changes should, theoretically, even trigger when running a normal (non-bounty) profile so I'm 90% sure it will work universally.
       

      Attached Files:

    20. sychotix

      sychotix New Member

      Joined:
      Dec 13, 2013
      Messages:
      727
      Likes Received:
      5
      Trophy Points:
      0
      To me, it looks like you aren't using updated profiles. If you are able to downgrade to Trinity .22, with the same profiles you were trying to run on Trinity .24, then you are NOT using the same profiles. One huge change, meaning until="BountyComplete" was made. Please update your profiles.
       
    Thread Status:
    Not open for further replies.

    Share This Page