Fixed: "No bounty found" error when accepting bounties at high level
Some players at higher levels were encountering an issue where the Bounty Board would display a valid bounty, but attempting to accept it would return:
"No bounty found matching..."
If you were high enough level, this could affect nearly every bounty on the board.
What was happening?
The Bounty Board performs an internal consistency check between the moment it displays available bounties and the moment you accept one.
Deep within that validation, two separate pieces of logic disagreed about whether the three permanently gated hard-mode zones should ever appear on the Bounty Board:
Obsidian Sanctum
Eldritch Void Core
Ascended Doom Spire
One system considered them valid bounty candidates, while the other rejected them.
Because of that disagreement, the board believed its available bounty list was out of date and regenerated itself every time it was viewed. Each regeneration created an entirely new set of internal bounty IDs, meaning the bounty you were trying to accept had already been discarded and replaced before your acceptance request was processed.
This issue only appeared at higher levels, once characters had progressed beyond the normal portal pool and those gated endgame zones began entering the candidate list.
The Fix
The three permanently gated hard-mode zones have now been removed from the dynamic bounty pool.
Those areas are intended to be endgame challenges that players choose to undertake directly, not randomized bounty objectives.
With those zones removed from bounty generation:
Both internal validation passes now agree.
Bounty postings remain stable.
Accepting bounties works reliably at every level.
All normal scaling portals—including high-level portals—continue to appear on the Bounty Board exactly as intended and still scale appropriately to your character.
We've also verified Bounty Board generation across the full high-level range to ensure boards remain full, varied, and free of dead entries.
Thank You
A huge thank you to Plain of Marathon and Elanarae for the detailed reports.
Plain of Marathon included the exact error message, while Elanarae added the crucial observation that the issue occurred around level 170, survived game restarts, and disappeared after Prestiging.
Those details transformed the investigation from "something is wrong with the Bounty Board" into a very specific progression-related bug, allowing the root cause to be identified and corrected quickly.
Reports like these genuinely make Portalborn better for everyone.
Thank you both for taking the time to help improve the game.
