# \[reported\] Kingdom task collect weapon

**URL:** <https://community.gemsofwar.com/t/reported-kingdom-task-collect-weapon/89748>\
**Category:** Bug Reports\
**Created:** [May 27, 2026, 1:32am UTC](https://community.gemsofwar.com/t/reported-kingdom-task-collect-weapon/89748 "2026-05-27T01:32:53Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![kf6dbs](https://sea1.discourse-cdn.com/flex019/user_avatar/community.gemsofwar.com/kf6dbs/32/98344_2.png) [@kf6dbs](https://community.gemsofwar.com/u/kf6dbs)\
**Post date:** [May 27, 2026, 1:32am UTC](https://community.gemsofwar.com/t/reported-kingdom-task-collect-weapon/89748/1 "2026-05-27T01:32:53Z")

</div>

1. A new player (not me) had increased their Earth Gem Mastery to 3 and unlocked the Giant’s Mace (Rare weapon from Broken Spire)
2. The Prestige Task “Collect a weapon from Broken Spire” was observed as not complete. This is an error as this task has been satisfied.
3. Upgrading it to +1 does satisfy the prestige task.

This issue is possibly connected to other issues with similar prestige tasks. If it is, add this observation to the existing issue.

Thank you.

---

<div class="post-metadata">

**Author:** ![Jeto](https://sea1.discourse-cdn.com/flex019/user_avatar/community.gemsofwar.com/jeto/32/101682_2.png) [@Jeto](https://community.gemsofwar.com/u/Jeto)\
**Post date:** [May 27, 2026, 1:45am UTC](https://community.gemsofwar.com/t/reported-kingdom-task-collect-weapon/89748/2 "2026-05-27T01:45:53Z")

</div>

There is a similar issue with the shiny troop task that randomly wont recognise existing progress till you next do something to one of those troops or collect a troop

---

<div class="post-metadata">

**Author:** ![Bizkit](https://avatars.discourse-cdn.com/v4/letter/b/839c29/32.png) [@Bizkit](https://community.gemsofwar.com/u/Bizkit)\
**Post date:** [August 24, 2026, 11:08pm UTC](https://community.gemsofwar.com/t/reported-kingdom-task-collect-weapon/89748/3 "2026-08-24T23:08:35Z")

</div>

I just came to the forums to mention this bug. It seems to still be happening.
