azerothcore / azerothcore/mod-aoe-loot

Bug: Group Loot

Open
#63 2 comments 0 reactions 0 assignees View on GitHub
Dominant language
C++
Stars
76
Forks
64
PR merge metrics
No merged PRs in 30d

Description

### Current Behaviour

The issue is with Group Loot, when the green+ items are displayed the "Need/Greed/Pass" options. If you open the loot 2 times before resolving the loot roll, you won't get any items... they will banish. An example are the key gems in LBRS, if the issue happens, you wont get them, and you will be forced to repeat the dungeon to get them.

### Expected Behaviour

The roll items from the earlier groups shouldn't go missing.

### Steps to reproduce the problem

- Join a LFG dungeon, any of them is ok, you can use the random.
- Go to a room were you can kill 2 different groups of mobs, if they are at least 5 in each group better.
- Kill the first group and open the loot. Without selecting the "Need/Greed/Pass" any of the green+ items.
- Kill the second group and open their loot too, with the first group options still open.
- Choose Need or Greed of any item so that you should get them, and see if you really get the items.

### Extra Notes

_No response_

### AC rev. hash/commit

AzerothCore rev. 8f293d00eef4 2026-05-17 08:06:40 -0300 (master branch) (Win64, RelWithDebInfo, Static)

### Operating system

Windows 11

### Custom changes or Modules

List of enabled modules:
|- mod-1v1-arena
|- mod-ah-bot-plus
|- mod-ale
|- mod-aoe-loot
|- mod-assistant
|- mod-autobalance
|- mod-breaking-news-override
|- mod-fly-in-old-world
|- mod-junk-to-gold
|- mod-npc-services
|- mod-profession-experience
|- mod-quick-respawn
|- mod-starter-guild

Contributor guide

No contributing guide indexed for this repository

Research direction

Start by reproducing the two-group loot sequence described in the issue, then inspect the group-loot handling in mod-aoe-loot. Done means resolving an item from the earlier group after opening the later group still awards it instead of making it disappear.

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
Quiet
Clarity
Mostly clear
Newbie friendliness
48/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.