# "Hot" trait on a weapon fires before gems are matched

**URL:** <https://community.gemsofwar.com/t/hot-trait-on-a-weapon-fires-before-gems-are-matched/45843>\
**Category:** Bug Reports\
**Created:** [September 13, 2018, 11:36am UTC](https://community.gemsofwar.com/t/hot-trait-on-a-weapon-fires-before-gems-are-matched/45843 "2018-09-13T11:36:04Z")\
**Posts on this page:** 6\
**Page:** 1

<div class="post-metadata">

**Author:** ![r3drick](https://avatars.discourse-cdn.com/v4/letter/r/a698b9/32.png) [@r3drick](https://community.gemsofwar.com/u/r3drick)\
**Post date:** [September 13, 2018, 11:36am UTC](https://community.gemsofwar.com/t/hot-trait-on-a-weapon-fires-before-gems-are-matched/45843/1 "2018-09-13T11:36:04Z")

</div>

**Platform, device version and operating system**  
PC, Windows 10

**What you were expecting to happen, and what actually happened**  
Weapon - “Summer’s Fury +9”  
On weapon skill use it spawns 6 red gems, then destroys one (due to trait “Hot”) and only then matches gems on the board. This way quite often one destroyed gem removes a possible combination of 3 or more red gems.  
A more logical event flow would be - spawn gems, match gems on board, and only then destroy one gem.

If it “works as designed”, then I would like to know is there a way to downgrade my weapon to turn this trait off?

---

<div class="post-metadata">

**Author:** ![Slypenslyde](https://sea1.discourse-cdn.com/flex019/user_avatar/community.gemsofwar.com/slypenslyde/32/30373_2.png) [@Slypenslyde](https://community.gemsofwar.com/u/Slypenslyde)\
**Post date:** [September 13, 2018, 12:56pm UTC](https://community.gemsofwar.com/t/hot-trait-on-a-weapon-fires-before-gems-are-matched/45843/2 "2018-09-13T12:56:44Z")

</div>

Sadly this is as designed. All abilities trigger before gems are matched. So for weapons that generate gems, an affix that destroys gems can disrupt 4-matches.

There’s not a way to go back. This has been a complaint since the first weapon with the affix was upgraded. The devs have never indicated interest in this.

But now you have joined the forums! Next time the devs add some feature that gets worse the more you use it, you’ll find out before you fall prey! Seriously. Never, EVER spend resources on anything in this game without waiting for someone else to be the guinea pig.

---

<div class="post-metadata">

**Author:** ![Kafka](https://sea1.discourse-cdn.com/flex019/user_avatar/community.gemsofwar.com/kafka/32/33529_2.png) [@Kafka](https://community.gemsofwar.com/u/Kafka)\
**Post date:** [September 14, 2018, 6:25am UTC](https://community.gemsofwar.com/t/hot-trait-on-a-weapon-fires-before-gems-are-matched/45843/3 "2018-09-14T06:25:15Z")

</div>

Just confirming that this is working as intended.

I’ll be making a Help Centre article with this information but essentially the order of execution is:

Spell → Affixes → Check for dead → Resolve board (ie. check for matches) → Cascades → Resolve board  
With Traits executing anywhere in that order in accordance with when the Trait description says it will trigger.

---

<div class="post-metadata">

**Author:** ![TheIdleOne](https://avatars.discourse-cdn.com/v4/letter/t/c68b51/32.png) [@TheIdleOne](https://community.gemsofwar.com/u/TheIdleOne)\
**Post date:** [September 14, 2018, 6:29am UTC](https://community.gemsofwar.com/t/hot-trait-on-a-weapon-fires-before-gems-are-matched/45843/4 "2018-09-14T06:29:31Z")

</div>

> [@Kafka](#):
>
> Spell -\> Affixes -\> Check for dead -\> Resolve board (ie. check for matches) -\> Cascades -\> Resolve board  
> With Traits executing anywhere in that order in accordance with when the Trait description says it will trigger.

Would you consider changing the priority order so that affixes is checked after the Resolve board (ie. check for matches) phase so that a good majority of the weapon upgrades don’t feel like a dramatic waste of time or a weapon downgrade?

---

<div class="post-metadata">

**Author:** ![Kafka](https://sea1.discourse-cdn.com/flex019/user_avatar/community.gemsofwar.com/kafka/32/33529_2.png) [@Kafka](https://community.gemsofwar.com/u/Kafka)\
**Post date:** [September 14, 2018, 6:52am UTC](https://community.gemsofwar.com/t/hot-trait-on-a-weapon-fires-before-gems-are-matched/45843/5 "2018-09-14T06:52:30Z")

</div>

I’ve passed that feedback onto the team for consideration 🙂

---

<div class="post-metadata">

**Author:** ![actreal](https://sea1.discourse-cdn.com/flex019/user_avatar/community.gemsofwar.com/actreal/32/1945_2.png) [@actreal](https://community.gemsofwar.com/u/actreal)\
**Post date:** [September 14, 2018, 7:40am UTC](https://community.gemsofwar.com/t/hot-trait-on-a-weapon-fires-before-gems-are-matched/45843/6 "2018-09-14T07:40:41Z")

</div>

> [@TheIdleOne](#):
>
> Would you consider changing the priority order so that affixes is checked after the Resolve board (ie. check for matches) phase so that a good majority of the weapon upgrades don’t feel like a dramatic waste of time or a weapon downgrade?

Assuming the coding won’t break elsewhere, this would be an elegant solution to the weapon ~~up~~ downgrade problem. A suggestion I would like more than once, for sure.
