# Infernal King Bug

**URL:** <https://community.gemsofwar.com/t/infernal-king-bug/7797>\
**Category:** Uncategorized\
**Created:** [June 1, 2016, 4:37pm UTC](https://community.gemsofwar.com/t/infernal-king-bug/7797 "2016-06-01T16:37:42Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![Meaux50](https://avatars.discourse-cdn.com/v4/letter/m/b2d939/32.png) [@Meaux50](https://community.gemsofwar.com/u/Meaux50)\
**Post date:** [June 1, 2016, 4:37pm UTC](https://community.gemsofwar.com/t/infernal-king-bug/7797/1 "2016-06-01T16:37:42Z")

</div>

Twice since the update I have fired off the Infernal King and it has reduced the top troops life to zero but it has remained showing. Once all of the remaining are killed the zeroed troop remains. Since life is at zero, further skull and magic damage do not effect it and there is no way to trigger the “win”. However, when it continues to match gems it does regular skull damage, however, it does not gather any more gems and cannot cast spells.

---

<div class="post-metadata">

**Author:** ![Ozball](https://sea1.discourse-cdn.com/flex019/user_avatar/community.gemsofwar.com/ozball/32/36110_2.png) [@Ozball](https://community.gemsofwar.com/u/Ozball)\
**Post date:** [June 1, 2016, 4:43pm UTC](https://community.gemsofwar.com/t/infernal-king-bug/7797/2 "2016-06-01T16:43:31Z")

</div>

This is a known bug commonly known as the “Ghost Troop” bug. The devs are still trying to nail it down.

> [@2.0 Known Issues](https://community.gemsofwar.com/t/2-0-known-issues/7368/1):
>
> Dead Troops not disappearing. Status: We fixed one possible cause and are currently investigating further.

---

<div class="post-metadata">

**Author:** ![Nimhain](https://sea1.discourse-cdn.com/flex019/user_avatar/community.gemsofwar.com/nimhain/32/47049_2.png) [@Nimhain](https://community.gemsofwar.com/u/Nimhain)\
**Post date:** [June 2, 2016, 12:48am UTC](https://community.gemsofwar.com/t/infernal-king-bug/7797/3 "2016-06-02T00:48:24Z")

</div>

We do have a fix out on stream for this I believe. iOS and Android require a client update for the fix to come through.
