# (Not a bug) Stun Impact occurring on skull match and not damage

**URL:** <https://community.gemsofwar.com/t/not-a-bug-stun-impact-occurring-on-skull-match-and-not-damage/47989>\
**Category:** Bug Reports\
**Created:** [October 28, 2018, 6:21pm UTC](https://community.gemsofwar.com/t/not-a-bug-stun-impact-occurring-on-skull-match-and-not-damage/47989 "2018-10-28T18:21:43Z")\
**Posts on this page:** 17\
**Page:** 1

<div class="post-metadata">

**Author:** ![AlphaNate](https://sea1.discourse-cdn.com/flex019/user_avatar/community.gemsofwar.com/alphanate/32/44933_2.png) [@AlphaNate](https://community.gemsofwar.com/u/AlphaNate)\
**Post date:** [October 28, 2018, 6:21pm UTC](https://community.gemsofwar.com/t/not-a-bug-stun-impact-occurring-on-skull-match-and-not-damage/47989/1 "2018-10-28T18:21:43Z")

</div>

**Platform, device version and operating system:**  
Xbox

**Screenshot or image:**

**What you were expecting to happen, and what actually happened:**  
Based on the 4.1 patch notes, previously, effects that say they should occur on skull damage were actually occurring when skulls were matched, and this was fixed. However, based on the wording of the first trait on Titan (forget which tree), it causes stun when hero takes skull damage. Instead of that happening, the stun happens whether damage occurs or not, even when hero has barrier.

**How often does this happen? When did it begin happening?**  
Every time, any mode.

**Steps to make it happen again**  
Match skulls while hero has that talent selected while hero has barrier. It may work like this against entangle as well, haven’t tried.

---

<div class="post-metadata">

**Author:** ![Cyrup](https://sea1.discourse-cdn.com/flex019/user_avatar/community.gemsofwar.com/cyrup/32/50181_2.png) [@Cyrup](https://community.gemsofwar.com/u/Cyrup)\
**Post date:** [October 31, 2018, 4:15am UTC](https://community.gemsofwar.com/t/not-a-bug-stun-impact-occurring-on-skull-match-and-not-damage/47989/2 "2018-10-31T04:15:42Z")

</div>

How many Skulls are you matching each time?

---

<div class="post-metadata">

**Author:** ![AlphaNate](https://sea1.discourse-cdn.com/flex019/user_avatar/community.gemsofwar.com/alphanate/32/44933_2.png) [@AlphaNate](https://community.gemsofwar.com/u/AlphaNate)\
**Post date:** [October 31, 2018, 2:35pm UTC](https://community.gemsofwar.com/t/not-a-bug-stun-impact-occurring-on-skull-match-and-not-damage/47989/3 "2018-10-31T14:35:18Z")

</div>

It happens every time, it’s not carried over damage from 4x skulls or doomskulls, if that’s what you’re asking.

Edit: I am at work, but I can also try when I get home if needed to see if it also happens with entangle, or if it’s unique to barrier.

---

<div class="post-metadata">

**Author:** ![AlphaNate](https://sea1.discourse-cdn.com/flex019/user_avatar/community.gemsofwar.com/alphanate/32/44933_2.png) [@AlphaNate](https://community.gemsofwar.com/u/AlphaNate)\
**Post date:** [November 1, 2018, 12:32am UTC](https://community.gemsofwar.com/t/not-a-bug-stun-impact-occurring-on-skull-match-and-not-damage/47989/4 "2018-11-01T00:32:52Z")

</div>

@Cyrup here you see it happen against barrier to Gorgotha. Then, it happens to TDS against barrier while entangled.

[![](https://us1.discourse-cdn.com/flex019/uploads/gemsofwar/original/3X/8/8/881aab8823a4d1a898f3d15f6b289d0e4b5cf55e.jpeg "Gems of War Stun Impact bug") ](https://www.youtube.com/watch?v=RN2-7hTXNQQ)

---

<div class="post-metadata">

**Author:** ![Cyrup](https://sea1.discourse-cdn.com/flex019/user_avatar/community.gemsofwar.com/cyrup/32/50181_2.png) [@Cyrup](https://community.gemsofwar.com/u/Cyrup)\
**Post date:** [November 1, 2018, 3:18am UTC](https://community.gemsofwar.com/t/not-a-bug-stun-impact-occurring-on-skull-match-and-not-damage/47989/5 "2018-11-01T03:18:17Z")

</div>

Thanks, I’ve made a bug report for the team to look into

---

<div class="post-metadata">

**Author:** ![Cyrup](https://sea1.discourse-cdn.com/flex019/user_avatar/community.gemsofwar.com/cyrup/32/50181_2.png) [@Cyrup](https://community.gemsofwar.com/u/Cyrup)\
**Post date:** [November 1, 2018, 3:42am UTC](https://community.gemsofwar.com/t/not-a-bug-stun-impact-occurring-on-skull-match-and-not-damage/47989/6 "2018-11-01T03:42:27Z")

</div>

This might actually be intended, just confirming the behaviour with the team…

---

<div class="post-metadata">

**Author:** ![AlphaNate](https://sea1.discourse-cdn.com/flex019/user_avatar/community.gemsofwar.com/alphanate/32/44933_2.png) [@AlphaNate](https://community.gemsofwar.com/u/AlphaNate)\
**Post date:** [November 1, 2018, 12:27pm UTC](https://community.gemsofwar.com/t/not-a-bug-stun-impact-occurring-on-skull-match-and-not-damage/47989/7 "2018-11-01T12:27:35Z")

</div>

If it’s intended, then the trait wording is incorrect.

---

<div class="post-metadata">

**Author:** ![Lissandra](https://sea1.discourse-cdn.com/flex019/user_avatar/community.gemsofwar.com/lissandra/32/42131_2.png) [@Lissandra](https://community.gemsofwar.com/u/Lissandra)\
**Post date:** [November 1, 2018, 1:05pm UTC](https://community.gemsofwar.com/t/not-a-bug-stun-impact-occurring-on-skull-match-and-not-damage/47989/8 "2018-11-01T13:05:49Z")

</div>

Hitting a barrier does no damage and similar with being entangled (Well… doom skulls or 4/5 matches but generally no damage). I’m sure it isn’t meant to trigger the trait though if it hits a barrier.

---

<div class="post-metadata">

**Author:** ![Cyrup](https://sea1.discourse-cdn.com/flex019/user_avatar/community.gemsofwar.com/cyrup/32/50181_2.png) [@Cyrup](https://community.gemsofwar.com/u/Cyrup)\
**Post date:** [November 1, 2018, 10:29pm UTC](https://community.gemsofwar.com/t/not-a-bug-stun-impact-occurring-on-skull-match-and-not-damage/47989/9 "2018-11-01T22:29:11Z")

</div>

Hey guys, looks like this might involve some old code and has a few design complications so it’s going to take longer to look into than expected. 🙂

---

<div class="post-metadata">

**Author:** ![AlphaNate](https://sea1.discourse-cdn.com/flex019/user_avatar/community.gemsofwar.com/alphanate/32/44933_2.png) [@AlphaNate](https://community.gemsofwar.com/u/AlphaNate)\
**Post date:** [November 1, 2018, 10:33pm UTC](https://community.gemsofwar.com/t/not-a-bug-stun-impact-occurring-on-skull-match-and-not-damage/47989/10 "2018-11-01T22:33:42Z")

</div>

Thanks for the update.

---

<div class="post-metadata">

**Author:** ![Grath](https://avatars.discourse-cdn.com/v4/letter/g/67e7ee/32.png) [@Grath](https://community.gemsofwar.com/u/Grath)\
**Post date:** [November 24, 2018, 9:04pm UTC](https://community.gemsofwar.com/t/not-a-bug-stun-impact-occurring-on-skull-match-and-not-damage/47989/11 "2018-11-24T21:04:48Z")

</div>

Popping in to add on to this: I just noticed that Wrath’s trait Cataclysm (Explode 2 random Gems when I deal skull damage) does not trigger when entangled, but Bone Dragon’s trait Frozen Soul (Inflict Frozen when enemies deal Skull damage to me) does trigger when entangled. Specifically, my Wrath ended up frozen when attacking an enemy Bone Dragon but didn’t explode gems. Hopefully there’s enough shared code that the same fix resolves both of these, but I just wanted to add this instance of odd interaction.

---

<div class="post-metadata">

**Author:** ![Cyrup](https://sea1.discourse-cdn.com/flex019/user_avatar/community.gemsofwar.com/cyrup/32/50181_2.png) [@Cyrup](https://community.gemsofwar.com/u/Cyrup)\
**Post date:** [November 28, 2018, 4:37am UTC](https://community.gemsofwar.com/t/not-a-bug-stun-impact-occurring-on-skull-match-and-not-damage/47989/12 "2018-11-28T04:37:31Z")

</div>

I have no new news on this issue at this stage ☹

---

<div class="post-metadata">

**Author:** ![Micio](https://sea1.discourse-cdn.com/flex019/user_avatar/community.gemsofwar.com/micio/32/50997_2.png) [@Micio](https://community.gemsofwar.com/u/Micio)\
**Post date:** [November 28, 2018, 2:10pm UTC](https://community.gemsofwar.com/t/not-a-bug-stun-impact-occurring-on-skull-match-and-not-damage/47989/13 "2018-11-28T14:10:13Z")

</div>

Actually the timing of effects never got fixed, x that we got webspinner with perma x3 skull damage and rock troll that do full skull damage to tanks everytime, there are more but those 2 are the most common to run into.

---

<div class="post-metadata">

**Author:** ![Cyrup](https://sea1.discourse-cdn.com/flex019/user_avatar/community.gemsofwar.com/cyrup/32/50181_2.png) [@Cyrup](https://community.gemsofwar.com/u/Cyrup)\
**Post date:** [December 6, 2018, 2:25am UTC](https://community.gemsofwar.com/t/not-a-bug-stun-impact-occurring-on-skull-match-and-not-damage/47989/14 "2018-12-06T02:25:11Z")

</div>

Hi @AlphaNate I’ve heard back from the team, and this is working as intended. The description for the talent says _when enemies deal Skull damage to me_. It doesn’t say when I take damage. This means breaking barrier will trigger the Talent.

---

<div class="post-metadata">

**Author:** ![AlphaNate](https://sea1.discourse-cdn.com/flex019/user_avatar/community.gemsofwar.com/alphanate/32/44933_2.png) [@AlphaNate](https://community.gemsofwar.com/u/AlphaNate)\
**Post date:** [December 7, 2018, 2:15am UTC](https://community.gemsofwar.com/t/not-a-bug-stun-impact-occurring-on-skull-match-and-not-damage/47989/15 "2018-12-07T02:15:01Z")

</div>

@Cyrup based on that, the stun should not occur if the troop attacking is entangled, correct?

---

<div class="post-metadata">

**Author:** ![Cyrup](https://sea1.discourse-cdn.com/flex019/user_avatar/community.gemsofwar.com/cyrup/32/50181_2.png) [@Cyrup](https://community.gemsofwar.com/u/Cyrup)\
**Post date:** [December 10, 2018, 2:13am UTC](https://community.gemsofwar.com/t/not-a-bug-stun-impact-occurring-on-skull-match-and-not-damage/47989/16 "2018-12-10T02:13:43Z")

</div>

The Impact Talent _should_ trigger if the Troop attacking is entangled

---

<div class="post-metadata">

**Author:** ![AlphaNate](https://sea1.discourse-cdn.com/flex019/user_avatar/community.gemsofwar.com/alphanate/32/44933_2.png) [@AlphaNate](https://community.gemsofwar.com/u/AlphaNate)\
**Post date:** [December 11, 2018, 1:29am UTC](https://community.gemsofwar.com/t/not-a-bug-stun-impact-occurring-on-skull-match-and-not-damage/47989/17 "2018-12-11T01:29:34Z")

</div>

@Cyrup maybe I’m not understanding. Why would it trigger if no skull damage is being dealt? Didn’t you just say the opposite?
