# \[Resolved\] New Bounty troop releases wrong Gems
**URL:** https://community.gemsofwar.com/t/resolved-new-bounty-troop-releases-wrong-gems/88406
**Category:** Bug Reports
**Created:** [August 8, 2025, 7:46am UTC](https://community.gemsofwar.com/t/resolved-new-bounty-troop-releases-wrong-gems/88406 "2025-08-08T07:46:56Z")
**Posts on this page:** 18
**Page:** 1
### Author:  [@WhoDat](https://community.gemsofwar.com/u/WhoDat)
#### Post date: [August 8, 2025, 7:46am UTC](https://community.gemsofwar.com/t/resolved-new-bounty-troop-releases-wrong-gems/88406/1 "2025-08-08T07:46:56Z")
It releases Barrier Gems instead of Bomb gems.
---
### Author:  [@Namour](https://community.gemsofwar.com/u/Namour)
#### Post date: [August 8, 2025, 8:13am UTC](https://community.gemsofwar.com/t/resolved-new-bounty-troop-releases-wrong-gems/88406/2 "2025-08-08T08:13:05Z")
Yep. The spell produces Barrier gems, not bomb gems.
Suggest you flag as a ‘Bug’ thread.
---
### Author:  [@WhoDat](https://community.gemsofwar.com/u/WhoDat)
#### Post date: [August 8, 2025, 10:26am UTC](https://community.gemsofwar.com/t/resolved-new-bounty-troop-releases-wrong-gems/88406/3 "2025-08-08T10:26:00Z")
Yes, I already submitted a ticket.
---
### Author:  [@Sheba](https://community.gemsofwar.com/u/Sheba)
#### Post date: [August 8, 2025, 10:34am UTC](https://community.gemsofwar.com/t/resolved-new-bounty-troop-releases-wrong-gems/88406/4 "2025-08-08T10:34:23Z")
Was about to post this. It doesn’t just spawn Barrier gems, though, it also converts some gems to yellow. Here are some images of before and then after casting:
---
### Author:  [@Fourdottwoone](https://community.gemsofwar.com/u/Fourdottwoone)
#### Post date: [August 8, 2025, 12:10pm UTC](https://community.gemsofwar.com/t/resolved-new-bounty-troop-releases-wrong-gems/88406/5 "2025-08-08T12:10:01Z")
> [@Sheba](#):
>
> it also converts some gems to yellow
I don’t see any unaccounted yellow gems between those two screenshots, the board only got rearranged a bit due to the explosion.
---
### Author:  [@GreenRaven](https://community.gemsofwar.com/u/GreenRaven)
#### Post date: [August 9, 2025, 1:33am UTC](https://community.gemsofwar.com/t/resolved-new-bounty-troop-releases-wrong-gems/88406/6 "2025-08-09T01:33:32Z")
**WEEZL-300** ’s description says that it generates Bomb gems. But when it came up as a Summon from a Adana mech team, it generated **Barrier** gems. (Summoned by Runegage.)
I have a screencap, but the post won’t let me embed it.
It’s not a big problem, but I thought you’d like to know it needs tweaking.
---
### Author:  [@Shoombry](https://community.gemsofwar.com/u/Shoombry)
#### Post date: [August 9, 2025, 2:11pm UTC](https://community.gemsofwar.com/t/resolved-new-bounty-troop-releases-wrong-gems/88406/7 "2025-08-09T14:11:41Z")
I’m using Weezl-300. It is also creating barrier gems (used so far against yellow, red, and purple gems). So either the description is wrong or the gem type wrong.
---
### Author:  [@SilentCitizen](https://community.gemsofwar.com/u/SilentCitizen)
#### Post date: [August 10, 2025, 12:04pm UTC](https://community.gemsofwar.com/t/resolved-new-bounty-troop-releases-wrong-gems/88406/8 "2025-08-10T12:04:43Z")
I’m curious how the devs make this blatant of an error, then it obviously goes through NO testing (or it does and nobody GAF) and then they go home for the weekend so that the troop is wrong for the entire Bounty event.
And they want us to spend real money on this??
---
### Author:  [@Theoden](https://community.gemsofwar.com/u/Theoden)
#### Post date: [August 10, 2025, 1:26pm UTC](https://community.gemsofwar.com/t/resolved-new-bounty-troop-releases-wrong-gems/88406/9 "2025-08-10T13:26:52Z")
> [@SilentCitizen](#):
>
> I’m curious how the devs make this blatant of an error
Bomb gems are alphabetically adjacent to Barrier gems. They’ve made this sort of error before. For example, on release the Dragon Tales weapon boosted off Drifting Sands allies instead of Dragon’s Claw allies, alphabetically adjacent kingdoms.
Maybe it’s a mix up between zero-based indices and one-based indices? That’s a common rookie programming mistake, forgetting to start counting at zero instead of one.
How testing doesn’t catch this is anyone’s guess.
---
### Author:  [@canadademon](https://community.gemsofwar.com/u/canadademon)
#### Post date: [August 10, 2025, 1:32pm UTC](https://community.gemsofwar.com/t/resolved-new-bounty-troop-releases-wrong-gems/88406/10 "2025-08-10T13:32:10Z")
> [@Theoden](#):
>
> Maybe it’s a mix up between zero-based indices and one-based indices?
I’m 99% certain that’s _exactly_ what happened.
And they have proved in the past that they don’t play their own game.
---
### Author:  [@redtoadstool](https://community.gemsofwar.com/u/redtoadstool)
#### Post date: [August 10, 2025, 2:48pm UTC](https://community.gemsofwar.com/t/resolved-new-bounty-troop-releases-wrong-gems/88406/11 "2025-08-10T14:48:51Z")
It’s a real shame as it might have been useful with bomb gems
---
### Author:  [@SilentCitizen](https://community.gemsofwar.com/u/SilentCitizen)
#### Post date: [August 10, 2025, 7:40pm UTC](https://community.gemsofwar.com/t/resolved-new-bounty-troop-releases-wrong-gems/88406/12 "2025-08-10T19:40:56Z")
> [@Theoden](#):
>
> How testing doesn’t catch this is anyone’s guess.
Look ma! No testing! 😭
---
### Author:  [@Jeto](https://community.gemsofwar.com/u/Jeto)
#### Post date: [August 11, 2025, 3:09am UTC](https://community.gemsofwar.com/t/resolved-new-bounty-troop-releases-wrong-gems/88406/13 "2025-08-11T03:09:47Z")
Fix should go out tonight at some point. It was already fixed, but was missed getting pushed to live with weekly reset
---
### Author:  [@CLARE](https://community.gemsofwar.com/u/CLARE)
#### Post date: [August 11, 2025, 7:33am UTC](https://community.gemsofwar.com/t/resolved-new-bounty-troop-releases-wrong-gems/88406/14 "2025-08-11T07:33:47Z")
this troop helps the enemy activate the barrier more 😐
---
### Author:  [@Zuul-Emo](https://community.gemsofwar.com/u/Zuul-Emo)
#### Post date: [August 11, 2025, 8:19pm UTC](https://community.gemsofwar.com/t/resolved-new-bounty-troop-releases-wrong-gems/88406/15 "2025-08-11T20:19:22Z")
> [@CLARE](#):
>
> this troop helps the enemy activate the barrier more 😐
Yeah, I used it once and immediately realised how annoying it was giving the enemy barrier. Didn’t touch it after that. Like so many required troops and weapons in events, it’s just a lead weight on the team, slowing us down.
---
### Author:  [@Jeto](https://community.gemsofwar.com/u/Jeto)
#### Post date: [August 11, 2025, 11:02pm UTC](https://community.gemsofwar.com/t/resolved-new-bounty-troop-releases-wrong-gems/88406/16 "2025-08-11T23:02:56Z")
Is anyone still having this issue?
---
### Author:  [@TheIdleOne](https://community.gemsofwar.com/u/TheIdleOne)
#### Post date: [August 11, 2025, 11:29pm UTC](https://community.gemsofwar.com/t/resolved-new-bounty-troop-releases-wrong-gems/88406/17 "2025-08-11T23:29:01Z")
the good? news is that its making bomb gems now. the bad news is that we’ve lost the one opportunity to actually use it properly before it gets cycled out for next bounty’s event troop since this troop isn’t all that great.
as much as people make that 50 gem comp joke, this is probably one of those moments where it seems valid
---
### Author:  [@GreenRaven](https://community.gemsofwar.com/u/GreenRaven)
#### Post date: [August 20, 2025, 7:18am UTC](https://community.gemsofwar.com/t/resolved-new-bounty-troop-releases-wrong-gems/88406/18 "2025-08-20T07:18:44Z")
The error is simple, if each Hero Gem is in its own method\* and they called the wrong one in the main code.
Why the method names are close enough someone could typo that and not catch it I don’t know.
\*A type of coding packet, for those who don’t know coding. Helps avoid having to repeat the same code over and over and over.