What players are reporting
Players in the opening-beta mob-tagging discussion describe crowded starting areas and competition for quest enemies. Some want shared tagging; others argue the initial crowd is not representative of later play. These are player observations and opinions, not Blizzard patch notes.
The useful question for your group is narrower than whether one version of tagging is better: under the current build, which members receive credit for the objective you are doing? Do not treat a crowded launch report as proof of every quest’s rules, a future policy change or the population you will encounter at level 60.
Separate kill credit, quest drops and ordinary loot
A group can finish the same fight and still need to check several outcomes. Record whether each member’s objective counter advanced, whether the required quest item appeared and whether ordinary loot was available. Do not use one of those results as a substitute for all three.
| Question | What to record |
|---|---|
| Did the objective advance? | Counter before and after, for each member. |
| Did the quest item appear? | Who could loot it and who still needs one. |
| Was everyone eligible? | Quest state, party membership and location. |
| Could you repeat the outcome? | Same conditions, next suitable enemy, current build. |
Try one small, controlled group test
Pick one ordinary quest your testers actually share. Agree who starts the fight and which enemy you are observing, then compare the outcome immediately. If it differs between members, record the difference before changing the party or moving elsewhere.
A party test is worth trying; this article does not promise that grouping fixes every credit or loot issue. Where practical, compare it with a solo observation under similar conditions. Avoid changing several variables at once and then attributing the outcome entirely to tagging.
If the area is too crowded to make the test useful, agree a time limit and switch to another suitable objective your group has available. Keep a list of unfinished objectives so one member is not left behind while everyone else assumes the quest is complete.
Make crowded questing part of the session plan
Ask members to arrive with a shared objective and a fallback activity rather than a promise to reach a particular level by an exact time. Nominate someone to check who still needs credit before moving the group. That keeps a short delay from turning into several disconnected solo sessions.
Our week-one testing plan helps keep the session manageable. Record the date and build alongside findings; if Blizzard changes tagging or layering, update the result rather than carrying forward an old beta assumption.