# \[Reported\] Luther doesn't understand Gargoyle gems

**URL:** <https://community.gemsofwar.com/t/reported-luther-doesnt-understand-gargoyle-gems/79204>\
**Category:** Bug Reports\
**Created:** [March 14, 2023, 3:04am UTC](https://community.gemsofwar.com/t/reported-luther-doesnt-understand-gargoyle-gems/79204 "2023-03-14T03:04:13Z")\
**Posts on this page:** 2\
**Page:** 1

<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:** [March 14, 2023, 3:04am UTC](https://community.gemsofwar.com/t/reported-luther-doesnt-understand-gargoyle-gems/79204/1 "2023-03-14T03:04:13Z")

</div>

Screenshot: _(available, but I have to download it from my Switch first)_

Description:

The first time a Gargoyle Gem appears on the board, Luther pops up to explain them – but gets the description wrong:

> [@Luther's tooltip (emphasis added)](#):
>
> "Good Gargoyle Gems will cause a random Ally to gain a random positive status effect. Bad Gargoyle Gems will inflict a random negative status effect on a random enemy."

Destroying Gargoyle Gems actually affects all targets (allies or enemies), which is the better behavior.

EDIT: Apparently this was also reported when it [originally occurred on PC](https://community.gemsofwar.com/t/reported-gargoyle-gems-not-consistently-named/75730) at that start of this campaign.

> **screenshot**
>
> ![grafik](https://us1.discourse-cdn.com/flex019/uploads/gemsofwar/original/3X/e/3/e3311efb193e2ae095a09a69102aa4257bcc8e63.jpeg)

Otherwise, this cannot be strictly reproduced because these tooltips only appear once.

---

<div class="post-metadata">

**Author:** ![Bramble](https://avatars.discourse-cdn.com/v4/letter/b/dfb087/32.png) [@Bramble](https://community.gemsofwar.com/u/Bramble)\
**Post date:** [March 15, 2023, 12:44am UTC](https://community.gemsofwar.com/t/reported-luther-doesnt-understand-gargoyle-gems/79204/2 "2023-03-15T00:44:24Z")

</div>

Hello 🙂

@Stratelier  
Good job on spotting this error, and thank you for the screencapture.

I’ll pass on the information to the development team!
