azerothcore / azerothcore/mod-aoe-loot
Bug: Single player loot
- Dominant language
- C++
- Stars
- 76
- Forks
- 64
- PR merge metrics
- No merged PRs in 30d
Description
### Current Behaviour
When skinning, I found then when looting multiple creatures AND you click on the creature that you want to skin first to loot all creatures, the creature becomes un-skinable. Looks like the loot table has changed on the creature you loot from when looting multiple creatures.
I also found that if you loot multiple creatures, if you don't take all the loot and close the box, it disappears (when in group).
### Expected Behaviour
Regardless of who you attack first, kill or loot from, everything that should be skinable should stay skinable after loot.
If you close the loot window with items in it, it should still stay with the creatures until fully looted.
### Steps to reproduce the problem
1. Kill more than two creatures in an area at once, one skinable
2. Loot from the creature you want to skin
3. Unable to skin that creature that should be skinable.
### Extra Notes
_No response_
### AC rev. hash/commit
AzerothCore rev. 82d400fd52e2 2026-06-04 22:37:06 +0700 (npcbots_3.3.5 branch) (Unix, RelWithDebInfo, Static) (authserver)
### Operating system
Ubuntu 24.04 lts
### Custom changes or Modules
"azerothcore/mod-rdf-expansion"
"azerothcore/mod-transmog"
"azerothcore/mod-random-enchants"
"azerothcore/mod-custom-login"
"azerothcore/mod-dynamic-xp"
"azerothcore/mod-gain-honor-guard"
"azerothcore/mod-learn-spells"
"azerothcore/mod-aoe-loot"
"Conan1996-2/mod-hard-modes"
Contributor guide
No contributing guide indexed for this repository
Research direction
No source files or tests are named. First reproduce the multi-creature skinning failure and the group-loot window behavior in the reported setup, then trace the module's loot handling; done means skinable creatures remain skinable and unclaimed loot remains available after closing the window.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- cpp
- Domain
- game-dev
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Active
- Clarity
- Mostly clear
- Newbie friendliness
- 48/100