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

Missing Legendary drops

SilentAvenger

New Member
Joined
Oct 27, 2012
Messages
7
Reaction score
0
Anyone else experiencing this? At first i thought maybe it's just a random thing that might have happened. but it's happening a lot now. Any advice how i can avoid loosing legendary drops? I'm using the latest DB and Trinity community edition. I already set wait for loot drop delay to 1000 in trinity.

I'm running a barb with 190k dps unbuffed at MP5 with WW specs.

===== Misc Statistics =====
Total tracking time: 9h 8m 7s
Total deaths: 4 [0.44 per hour]
Total games (approx): 0 [0 per hour]
(a profile manager/death handler is interfering with join/leave game events, attempting to guess total runs based on profile-loops)
Total full profile cycles: 9 [0.99 per hour]

===== Item DROP Statistics =====
- Legendary: 15 [1.64 per hour] {0.21 %}
--- ilvl 60 Legendary: 2 [0.22 per hour] {0.03 %}
--- ilvl 61 Legendary: 1 [0.11 per hour] {0.01 %}
--- ilvl 62 Legendary: 3 [0.33 per hour] {0.04 %}
--- ilvl 63 Legendary: 9 [0.99 per hour] {0.13 %}

===== Item PICKUP Statistics =====
- Legendary: 11 [1.2 per hour] {2.54 %}
--- ilvl 60 Legendary: 2 [0.22 per hour] {0.46 %}
--- ilvl 61 Legendary: 1 [0.11 per hour] {0.23 %}
--- ilvl 62 Legendary: 3 [0.33 per hour] {0.69 %}
--- ilvl 63 Legendary: 5 [0.55 per hour] {1.15 %}
 
same on Trinity community, dont using it. Now on 0.45.
 
Yeah. i switched back to 0.45 as well. Haven't had a missed legendary from that version. I hope the community edition gets fixed.
 
Is anyone else experiencing this? I'm wondering if it's a fluke, or if there's a bigger problem at hand. I haven't experienced it myself so I'd like more information so I can dig into what could be causing this.
 
Is anyone else experiencing this? I'm wondering if it's a fluke, or if there's a bigger problem at hand. I haven't experienced it myself so I'd like more information so I can dig into what could be causing this.

Rrrix, I also encountered this problem. However, I noticed that the "missing" legendaries always happened to have the same item level as the legendary that I have looted. Hence, it is possible that Ginity double counted the same item.
 
Rrrix, I also encountered this problem. However, I noticed that the "missing" legendaries always happened to have the same item level as the legendary that I have looted. Hence, it is possible that Ginity double counted the same item.

At first i thought it's just doubling the count also but i saw it happen with just 1 ilvl legendary as well. Like in the drop stat it has 1 ilvl 61 and 1 ilvl 63 and i only have the ilvl 61 in my stash there's also no ilvl 63 in my stash log so i don't know.
 
I posted in the community thread about it some time ago... The count after 2 days was -12 ilvl 63 legendaries... I have noticed however that it is ALWAYS, at-least in my case, only showing a discrepancy with ilvl 63 legendaries.... This leads me to believe its a DB glitch...
 
it's not only ilvl 63 legendaries for me. happens for other ilvls as well. this is another item stat(Same bot different day)

===== Item DROP Statistics =====
- Legendary: 6 [1.69 per hour] {0.23 %}
--- ilvl 60 Legendary: 2 [0.56 per hour] {0.08 %}
--- ilvl 61 Legendary: 2 [0.56 per hour] {0.08 %}
--- ilvl 63 Legendary: 2 [0.56 per hour] {0.08 %}

===== Item PICKUP Statistics =====
- Legendary: 5 [1.41 per hour] {3.05 %}
--- ilvl 60 Legendary: 2 [0.56 per hour] {1.22 %}
--- ilvl 61 Legendary: 1 [0.28 per hour] {0.61 %}
--- ilvl 63 Legendary: 2 [0.56 per hour] {1.22 %}
 
just curious and i checked mine :confused:
2 and half hr on 1.7.1.4


Items dropped by quality:
--- ilvl 63 Rare: 52 [24.22 per hour] {2.84 %}

Items picked up by quality:
--- ilvl 63 Rare: 35 [16.3 per hour] {23.81 %}
 
If the 'dropped' statistic is accurate and not double counting, then my bots left 3 level 61 legendaries and 2 level 63's on the ground.
 
Guys, after reading the topic i have checked mine also:

Drop:

- Legendary: 5 [0,71 per hour] {0,2 %}
--- ilvl 61 Legendary: 3 [0,43 per hour] {0,12 %}
--- ilvl 62 Legendary: 1 [0,14 per hour] {0,04 %}
--- ilvl 63 Legendary: 1 [0,14 per hour] {0,04 %}

Pick Up

- Legendary: 4 [0,57 per hour] {1,35 %}
--- ilvl 61 Legendary: 2 [0,28 per hour] {0,68 %}
--- ilvl 62 Legendary: 1 [0,14 per hour] {0,34 %}
--- ilvl 63 Legendary: 1 [0,14 per hour] {0,34 %}


You was writing, that ver. 0.45 is good and working well, can you give some download link?
 
Last edited:
Would say this does warrant looking further into what is going on... But I still do believe it is some sort of DB glitch and has little to do with trinity...

I only say that because when i noticed 12 missing legendaries that I monitored a single bot approx. 90% and did not notice a single legendary missed but still noted a discrepancy in the log of 3 ilvl 63 legendaries..

Than again I imaging most of us are running barbs and I wonder if has anything to do with the tornadoes killing off-screen? Just a thought...
 
I think I found a potential scenario where this could happen:

Between 1.7.0.0 and 1.7.1.3 we had disabled combat looting since it was causing stucks/deaths trying to loot through monsters, since the weighting for items was often greater than of monsters, and the combat looting system didn't acknowledge the presence of those monsters in the path-line between you and the item.
My version pre-1.7.0.0 up to 1.7.1.5 (when I release it) had some logic where if an object was out of line of sight (with the exception of bosses) it was basically ignored from being added to the cache system (and subsequently the pickup list). I've changed it so all items, except gold, will be added to the cache/pickup list.

So, potentially, if you were surrounded by mobs, killed an elite, and ended up chasing another monster off to where the legendary dropped but was no longer in LoS, the bot would effectively ignore that legendary, but still count it under the dropped items list.

Thanks for reporting this, We'll be releasing 1.7.1.5 soon (today/tomorrow) so stay tuned.
 
Back
Top