AOE looting doesn't work as of 7.0.3 #198


  • New
  • Defect
  • Waiting
Closed
  • AllaraStarmist created this issue Jul 25, 2016
    Author

    WoW 7.0 caused AOE looting to stop working. The loot API functions no longer return GUIDs for empty NPCs or for NPCs with only money.

  • AllaraStarmist added the tags New Defect Jul 25, 2016
  • AllaraStarmist posted a comment Jul 25, 2016

    Something appears to have mysteriously broken in both LOOT_OPENED and LOOT_READY in 7.0. AOE looting is not detected by Rarity in either case now. Need deeper investigation to figure out why.

  • AllaraStarmist posted a comment Jul 26, 2016

    I'm at a loss on this one. From what I can tell, it looks like Blizzard re-broke their AOE looting API in 7.0 so that it no longer returns anything for empty corpses. This used to be a problem in 5.0 but they fixed it in 5.3 and it remained fixed until 7.0. From what I can tell, there isn't anything I can do about it.

    Does anyone know something I don't?

  • AllaraStarmist posted a comment Jul 27, 2016

    I may be able to re-create the old behavior by logging NPC deaths by you, your party, your pet, or your raid, as well as the precise zone and coordinate the death occurred. Then when you receive a LOOT_READY event, I can consult that table and determine which of those NPCs are within an X yard radius of your current position. This, paired with the CanLootUnit(unitGUID) function, should allow me to detect which units were not included in GetLootInfo but are, in fact, eligible for loot by you in the vicinity. If this works, the only remaining factor is determining the precise loot radius for AOE looting.

  • AllaraStarmist posted a comment Jul 27, 2016

    For accuracy, I probably also need to log a timestamp and determine an appropriate age to age out the unused items in the table, in case you kill too many units at once and do not loot them all during the first event.

  • Urtgard posted a comment Jul 28, 2016

    That could work. It really sucks that there is such little documentation about the api and changes by Blizzard.

    Maybe this isn't even an indended change. Have you reported this to Blizzard?

  • AllaraStarmist posted a comment Jul 28, 2016

    It's probably not intended. I haven't reported it, is the best way to just make a thread on the official forums?

    As I think about the below, I found a fatal flaw. The game does not allow determining the location of your pet or the mobs you kill. As a ranged player, you can kill mobs up to 35 yards away (or more if you're running away). Also, your pet and/or some kind of Loot-a-Rang device can do the looting, and the game cannot locate them. Therefore, in order to do this myself I'd have to set a VERY large radius on AOE looting, thereby making it very inaccurate.

    So at this point I think it's not possible.

  • Urtgard posted a comment Jul 28, 2016

    I think so. Maybe use the ingame option to report a bug too.

    At least on the forums you got the chance to receive a response by Blizzard.

  • AllaraStarmist posted a comment Jul 28, 2016

    Putting this here for my notes later:

    local hasLoot, canLoot = CanLootUnit(guid)
    

    Edited Jul 28, 2016
  • AllaraStarmist posted a comment Jul 28, 2016
  • AllaraStarmist removed a tag Accepted Jul 29, 2016
  • AllaraStarmist added a tag Waiting Jul 29, 2016
  • AllaraStarmist edited description Jul 30, 2016
  • AllaraStarmist closed issue May 31, 2017
  • AllaraStarmist posted a comment May 31, 2017

    Closing because it looks like Blizzard doesn't intend to address this.


To post a comment, please login or register a new account.