loot from identically named mobs is often ignored

Bug #666935 reported by speedwaystar
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
MobInfo2
Status tracked in 4.0
4.0
Fix Committed
Low
speedwaystar

Bug Description

Looting two mobs with the same name and level which drop the exact same loot causes loot from the second (and any subsequent identical mob) to be ignored

Tags: loot

Related branches

Changed in mobinfo2:
assignee: nobody → speedwaystar (speedwaystar)
assignee: speedwaystar (speedwaystar) → nobody
importance: Undecided → Low
milestone: none → 4.0b2
status: New → Confirmed
summary: - Looting two mobs with the same name and level in succession causes loot
- from the second to be ignored
+ Looting two mobs with the same name and level which drop the exact same
+ loot causes loot from the second to be ignored
summary: Looting two mobs with the same name and level which drop the exact same
- loot causes loot from the second to be ignored
+ loot causes loot from the second (and subsequent identical mob) to be
+ ignored
description: updated
description: updated
description: updated
description: updated
summary: Looting two mobs with the same name and level which drop the exact same
- loot causes loot from the second (and subsequent identical mob) to be
- ignored
+ loot causes loot from the second (and any subsequent identical mob) to
+ be ignored
Revision history for this message
speedwaystar (speedwaystar) wrote : Re: Looting two mobs with the same name and level which drop the exact same loot causes loot from the second (and any subsequent identical mob) to be ignored

Example: Kill three level 42 giant spiders. All drop shadow silk. The addon only records the loot which drops from the first spider.

Why: Opening the same unlooted body twice would record the loot on that body twice, poisoning the database. To avoid this, MobInfo2 assigns each new corpse a so-called "Unique ID" in the format "name:levelloot".

Faced with our example from above, the addon ends up assigning the same id, "giant spider:42shadow silk", to each mob. It cannot therefore distinguish between opening each mob in turn from opening the same one three times, and thus only records the loot from the first-opened mob, treating the other two as "reopens".

TODO: we need to improve the "unique ID" format assigned to each new mob so it's a bit more robust.

description: updated
summary: - Looting two mobs with the same name and level which drop the exact same
- loot causes loot from the second (and any subsequent identical mob) to
- be ignored
+ Loot from identically named mobs is sometimes ignored
summary: - Loot from identically named mobs is sometimes ignored
+ loot from identically named mobs is sometimes ignored
Revision history for this message
speedwaystar (speedwaystar) wrote : Re: loot from identically named mobs is sometimes ignored

TODO: does the WoW API return x,y,z coords of the corpse?

summary: - loot from identically named mobs is sometimes ignored
+ loot from identically named mobs is often ignored
Revision history for this message
speedwaystar (speedwaystar) wrote :

Riamus said
Fri Feb 18 2011 06:56:52 GMT+0800 (W. Australia Standard Time) (12 hours ago)

Also, regarding your triaged item on those links (multiple loots of the same items), if you can get an x,y,z location on the corpse, that would also solve all problems when you reopen a partially looted corpse and get duplicates. If it's not possible, then using the player x,y,z coordinates can at least help. Basically, if you loot a corpse with the same loot, but are farther than X away from your original location, it will count because it has to be a different corpse. (X being however far you need to be to not be able to reach the corpse anymore if the original location was on the exact opposite side of the corpse at the farthest distance possible to loot it). In addition to that, you might also consider looking at corpse de-spawn timers and if it's been longer than that, count it as new... that would require knowing if you're in an instance where they last longer or not. Neither option completely solves this problem unlike the x,y,z corpse option, but if that option isn't available, these at least improve things.

Revision history for this message
speedwaystar (speedwaystar) wrote :

now that i actually bother to look, >_> i find that http://www.wowpedia.org/API_UnitGUID returns a unique (for the current realm) 16-digit hex string for each mob. too easy.

tags: removed: events
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.