# Bulette is broken

**URL:** <https://community.gemsofwar.com/t/bulette-is-broken/34647>\
**Category:** Support\
**Created:** [January 4, 2018, 4:18am UTC](https://community.gemsofwar.com/t/bulette-is-broken/34647 "2018-01-04T04:18:40Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![LummoxJR](https://sea1.discourse-cdn.com/flex019/user_avatar/community.gemsofwar.com/lummoxjr/32/209_2.png) [@LummoxJR](https://community.gemsofwar.com/u/LummoxJR)\
**Post date:** [January 4, 2018, 4:18am UTC](https://community.gemsofwar.com/t/bulette-is-broken/34647/1 "2018-01-04T04:18:40Z")

</div>

So it turns out Bulette is straight-up broken.

**What you were expecting to happen, and what actually happened?**

After Bulette pushes someone to the back, he’s supposed to damage the new first enemy. Problem is, he aims all damage at the slot where the first enemy used to be. So if that slot is now empty, no damage is done at all.

**What are the steps to make it happen again?**

Use Bulette against the first surviving enemy when the spot below them is empty.

PS: Fizzbang is still broken too, albeit on purpose. Make her explode fewer gems and boost less so the stupid either/or can be nixed.

---

<div class="post-metadata">

**Author:** ![Gleeson](https://sea1.discourse-cdn.com/flex019/user_avatar/community.gemsofwar.com/gleeson/32/35410_2.png) [@Gleeson](https://community.gemsofwar.com/u/Gleeson)\
**Post date:** [January 4, 2018, 6:43am UTC](https://community.gemsofwar.com/t/bulette-is-broken/34647/2 "2018-01-04T06:43:17Z")

</div>

This is exactly what I logged in to report: Bulette does the “knocking” part of its spell, but often completely forgets to do the “damage” part.

---

<div class="post-metadata">

**Author:** ![LummoxJR](https://sea1.discourse-cdn.com/flex019/user_avatar/community.gemsofwar.com/lummoxjr/32/209_2.png) [@LummoxJR](https://community.gemsofwar.com/u/LummoxJR)\
**Post date:** [January 4, 2018, 9:24pm UTC](https://community.gemsofwar.com/t/bulette-is-broken/34647/3 "2018-01-04T21:24:20Z")

</div>

I should add this happens on iOS for me, though since the Unity port that probably doesn’t matter so much.

This bug is 100% reliable; the only requirement is that the spot behind the first enemy is vacant. The resulting shuffle from the knockback moves that vacancy to the spot that the spell targets. The correct behavior would be for the spell to recalculate the first enemy position after the knockback takes place, rather than use the old position that has been vacated.