# \[fix incoming\] Buccaneer's Bounty did not update correctly

**URL:** https://community.gemsofwar.com/t/fix-incoming-buccaneers-bounty-did-not-update-correctly/89681
**Category:** Bug Reports
**Created:** [May 20, 2026, 10:24am UTC](https://community.gemsofwar.com/t/fix-incoming-buccaneers-bounty-did-not-update-correctly/89681 "2026-05-20T10:24:10Z")
**Posts on this page:** 2
**Page:** 1

<div class="post-metadata">

### Author: ![Prisane](https://avatars.discourse-cdn.com/v4/letter/p/ebca7d/32.png) [@Prisane](https://community.gemsofwar.com/u/Prisane)
#### Post date: [May 20, 2026, 10:24am UTC](https://community.gemsofwar.com/t/fix-incoming-buccaneers-bounty-did-not-update-correctly/89681/1 "2026-05-20T10:24:11Z")

</div>

**Platform, device version and operating system:PC, Windows 11, game version 9.2**

**Screenshot or image:**

 ![image](https://us1.discourse-cdn.com/flex019/uploads/gemsofwar/original/3X/d/4/d45a585f1c61d4d8f8b16a7000b0e784e314c5a1.jpeg)

**What you were expecting to happen, and what actually happened:**  
_I’ve updated to 9.2 and restarted the game afterwards. Today I’m offered an Imperial deed in Buccaneer’s Bounty._

**How often does this happen? When did it begin happening?**  
_REPLACE THIS TEXT WITH YOUR ISSUE. e.g. Was this a once-off bug or has it been a consistent issue? Does it only happen after doing a particular game mode?_

**Steps to make it happen again**  
_REPLACE THIS TEXT WITH YOUR ISSUE. e.g. Sometimes there are certain steps that can lead to a problem that may not be obvious! Example: I lose once in the Arena, I then exit to the world map, select broken Spire on the Map and enter Arena. broken spire’s quest lost instead._

---

<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 21, 2026, 12:01am UTC](https://community.gemsofwar.com/t/fix-incoming-buccaneers-bounty-did-not-update-correctly/89681/2 "2026-05-21T00:01:25Z")

</div>

fix should go out today sometime
