# \[Reported\] Bounty is nothing but Ogres? All time low

**URL:** <https://community.gemsofwar.com/t/reported-bounty-is-nothing-but-ogres-all-time-low/80378>\
**Category:** Bug Reports\
**Created:** [July 7, 2023, 10:24am UTC](https://community.gemsofwar.com/t/reported-bounty-is-nothing-but-ogres-all-time-low/80378 "2023-07-07T10:24:18Z")\
**Posts on this page:** 1\
**Showing post:** 34

<div class="post-metadata">

**Author:** ![Stratelier](https://avatars.discourse-cdn.com/v4/letter/s/977dab/32.png) [@Stratelier](https://community.gemsofwar.com/u/Stratelier)\
**Post date:** [July 10, 2023, 10:07pm UTC](https://community.gemsofwar.com/t/reported-bounty-is-nothing-but-ogres-all-time-low/80378/34 "2023-07-10T22:07:55Z")

</div>

> [@Kelana](#):
>
> But it’s not really fair to assume they did nothing at all just because a mistake was made

True, but it’s the _frequency_ of these mistakes that people get the most frustrated over. For example, a new trait that [does literally nothing](https://community.gemsofwar.com/t/reported-ogre-fury-trait-not-working/77808) or [immediately crashes the game](https://community.gemsofwar.com/t/ns-platform-cannot-log-in/80313), or a new troop that starts [automatically banning everyone](https://community.gemsofwar.com/t/information-about-bans/78325). At least two of these are things that should have been immediately rejected by QA and sent straight back to the coders to fix, yet “somehow” they made it through to end-user release prompting immediate complaints.

_(insert famous adage about prevention vs. cure here)_

---

_[View the full topic](https://community.gemsofwar.com/t/reported-bounty-is-nothing-but-ogres-all-time-low/80378)._