# \[Reported\] Burning gem causes targeting softlock

**URL:** <https://community.gemsofwar.com/t/reported-burning-gem-causes-targeting-softlock/76479>\
**Category:** Bug Reports\
**Created:** [August 8, 2022, 3:49pm UTC](https://community.gemsofwar.com/t/reported-burning-gem-causes-targeting-softlock/76479 "2022-08-08T15:49:18Z")\
**Posts on this page:** 1\
**Showing post:** 10

<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:** [August 11, 2022, 3:28am UTC](https://community.gemsofwar.com/t/reported-burning-gem-causes-targeting-softlock/76479/10 "2022-08-11T03:28:40Z")

</div>

Also my own report (with video and screenshots) - [[Reported] Lycanthropy Gem caused softlock when spellcasting vs. single opponent](https://community.gemsofwar.com/t/lycanthropy-gem-caused-softlock-when-spellcasting-vs-single-opponent/74955)

> [@CaptainAwesome](#):
>
> In all videos it’s clearly visible that every player tried to cast the spell **BEFORE** the last instance off an status effect gem flying over the board has reached it’s destination.

> [@OminousGMan](#):
>
> I’ve tried to reproduce this issue on our side and I haven’t been able to trigger this soft locking issue that you’re reporting.

Some complications:  
1 - You should match the special gem in a way that grants an Extra Turn so that you can spellcast while it is still homing.  
2 - Special gems seem to home in on their target at randomized speeds, so the time window for the above (i.e. ability to reproduce) is unpredictable.

Per my hypothesis above, it seems like when you cast a manual-target spell, _anything_ that triggers an update to a target’s status (like Ironhawk’s third trait vs. a Submerged target) somehow removes them from the internal list of eligible targets for that spell, which is a BIG problem when it happens (even when it does not happen often). In all these videos (but particularly the last one) you can clearly see that the affected troop is highlighted as a target UNTIL the special gem actually hits them.

Naturally, this problem did not occur until the implementation of special gems and Ironhawk’s release. And it wouldn’t be an issue at all if we could just cancel out of a spellcast in the first place.

---

_[View the full topic](https://community.gemsofwar.com/t/reported-burning-gem-causes-targeting-softlock/76479)._
