Independent Beta threads report persistent already-used/no-loot errors on quest objects across several zones.Beta Verified
WOW FOREVER · GUIDE
WoW Forever “That Is Being Used” / “There Is No Loot” Quest Bug
Quest chests or ground items will not loot? Compare current Durotar, Westfall, Elwynn and Skyborne reports, mixed attempts and what to include in a bug report.
Quick answer
Independent October 4–5 Beta reports describe quest objects refusing interaction with 'already being used' or 'there is no loot', even with nobody nearby. Benedict's Chest, Threat from Below objects and Westfall pickups are among the reported cases. No confirmed general fix or official root cause was found. Relogging and abandonment have mixed or failed results; preserve quest items before trying anything destructive.
Beta VerifiedView evidence
Try this first
- Record the exact quest, object and error, then check your objective and inventory.
- Test one reversible relog or return later; record whether the same object remains blocked.
- Preserve keys and quest items and report the reproducible failure.
What not to do
- Do not abandon item-started quests or discard unique items as a guaranteed reset.
Durotar: Benedict's Chest and Threat from Below
Players report Benedict's Chest remaining open or claiming it is in use, and Threat from Below pickups returning no loot. Named objects include the Orcish Dagger, Banner Scrap and Broken Bone Trident. Thazzril's Pick also appears in follow-up reports. These are specific player observations, not confirmation that every object in Durotar is broken or that an unrelated Voidwalker quest has the same cause.
Westfall and Elwynn: the same error, different objects
One thread reports Furlbrow's cupboard/pocket watch, a mining node and bags of oats in Westfall; another reply describes farm flowers in Elwynn. Record the actual object and quest name instead of assuming that an uncertain forum description identifies every affected quest. A gathering-node failure and a quest pickup may share an error message without sharing one proven defect.
A Last Request: old successes are not a current fix
September 18 players reported blocked body interactions and some success after turning in other quests and relogging. October 2–5 replies report the problem continuing despite rebooting or abandonment. This related Skyborne case belongs here rather than in a duplicate guide. Halaan's gift dialogue failure is a different progression step; use the Anchors of Zephras guide for that symptom.
Check eligibility before calling it the same bug
Editorial checklist: read your current quest objective, check whether you already hold the item or have completed its step, and note the exact error. If another player is visibly using the object, allow that interaction to finish. If nobody is there and the failure persists, capture the object state and try a separate eligible object to narrow the scope.
What can you safely try?
A player says a long logout helped one object but not another. A short relog or returning later can be a comparison, not a reliable fix. Record your inventory and quest state first. Do not repeatedly abandon item-started quests, discard keys or delete unique items: re-acquisition is not guaranteed, and dropping/re-taking a quest failed in the current reports.
No confirmed fix: separate guesses from evidence
Respawn changes, bots, layering and server state are proposed explanations, not a confirmed root cause. October 1 notes adjusted particular respawns; that does not diagnose all later loot errors. No universal reset, layer change, addon installation or client reinstall is established as a repair in the sources checked here.
Report the object, not just 'quest broken'
Include quest/object names, zone, faction, build, whether it is open or closed, exact error, inventory and nearby-player conditions. List attempts and results. A timestamped short clip or screenshot from your own client can help Blizzard reproduce it. Continue another available quest while preserving the blocked chain, rather than spending all playtime repeating an unproven reset.
Claim evidence
The named Durotar, Westfall and Elwynn objects are individual player reports, not an exhaustive affected list.Community Reported
Logout and quest reset attempts have mixed or failed results, including recent A Last Request reports.Community Reported
A shared root cause and reliable universal repair are not established.Unverified
How evidence labels work
OfficialConfirmed by Blizzard or an official WoW channel.
Beta VerifiedSupported by multiple independent Beta reports.
Community ReportedReported by players, but not confirmed enough.
UnverifiedNot enough reliable evidence yet.
FixedVerified in the currently checked build.
Sources
If this didn’t solve it
Record your current client build, exact symptom, region and the checks already tried. Use the related problem cluster below to separate a matching issue from a different failure; no community workaround guarantees recovery.
Continue from here
Choose the next answer you need.
WoW Forever Beta Known Issues & Workarounds
WoW Forever Beta known issues and workarounds: current quest blockers, FPS and Mac reports, character-list problems, official fixes and what remains unverified.
WoW Forever The Anchors of Zephras: Halaan Dialogue Bug
Halaan's gift dialogue does not advance The Anchors of Zephras? Check the intended objective, both-faction Beta reports and safe next steps without a fake fix.
WoW Forever Leveling from 20 to 30
What opens after the Beta cap rises to 30: quest areas, new dungeon ranges, dungeon quest XP changes and practical leveling checks without invented XP/hour routes.
Related problem cluster: Current WoW Forever issues and detailed troubleshooting
Found something outdated?
Help us keep this guide accurate.