# Assassinate trait vs entangled **URL:** \ **Category:** Support\ **Created:** [February 28, 2017, 10:09pm UTC](https://community.gemsofwar.com/t/assassinate-trait-vs-entangled/20659 "2017-02-28T22:09:09Z")\ **Posts on this page:** 12\ **Page:** 1
**Author:** ![Zelarith](https://sea1.discourse-cdn.com/flex019/user_avatar/community.gemsofwar.com/zelarith/32/1642_2.png) [@Zelarith](https://community.gemsofwar.com/u/Zelarith)\ **Post date:** [February 28, 2017, 10:09pm UTC](https://community.gemsofwar.com/t/assassinate-trait-vs-entangled/20659/1 "2017-02-28T22:09:09Z")
**What you were expecting to happen, and what actually happened?** The “Assassinate” trait reads “10% chance to kill the last ennemy when I deal skull damage”. An entangled troop doesn’t deal damage unless it lines up more than 3 skulls. Just like any “on hit” trait, I thought this trait would not apply if the hero was entangled, especially since this is kinda hinted in the description… But it did. **What are the steps to make it happen again?** Fight or use a hero with the Assassin class, fully traited. Entangle him and feed him skulls (no 4+ matches though, only 3 matches) **Do you have any screenshots or video you want to share with us so we can see the problem? Attach them to your post!** Nop, I didn’t expect it to happen and it’s kinda hard to reproduce, especially since I didn’t trait my assassin ! I had a lucky opponent trigger this with his first hit while entangled by Sylvanimora 😒 Still won the fight though 😏 ---
**Author:** ![kynetarse](https://sea1.discourse-cdn.com/flex019/user_avatar/community.gemsofwar.com/kynetarse/32/24815_2.png) [@kynetarse](https://community.gemsofwar.com/u/kynetarse)\ **Post date:** [February 28, 2017, 10:20pm UTC](https://community.gemsofwar.com/t/assassinate-trait-vs-entangled/20659/2 "2017-02-28T22:20:48Z")
Archer’s Bullseye trait does the same thing. And there’s all kinds of other wonkiness with entangled. I started another thread a while ago ---
**Author:** ![efh313](https://sea1.discourse-cdn.com/flex019/user_avatar/community.gemsofwar.com/efh313/32/34349_2.png) [@efh313](https://community.gemsofwar.com/u/efh313)\ **Post date:** [March 1, 2017, 12:15am UTC](https://community.gemsofwar.com/t/assassinate-trait-vs-entangled/20659/3 "2017-03-01T00:15:18Z")
This is a known and common “bug”. Some traits fire registering that skulls were matched regardless of the attack stat while others do seem to require actual Dmg dealt. I believe it is on the dev’s radar but I might be wrong about that. Just know: It’s not just you! 😉 ---
**Author:** ![Zelarith](https://sea1.discourse-cdn.com/flex019/user_avatar/community.gemsofwar.com/zelarith/32/1642_2.png) [@Zelarith](https://community.gemsofwar.com/u/Zelarith)\ **Post date:** [March 1, 2017, 9:00am UTC](https://community.gemsofwar.com/t/assassinate-trait-vs-entangled/20659/4 "2017-03-01T09:00:00Z")
Sorry, I didn’t find it when doing a search using the keyword “assassinate” so I figured this one might have gone under the radar 😛 ---
**Author:** ![esslee](https://sea1.discourse-cdn.com/flex019/user_avatar/community.gemsofwar.com/esslee/32/103072_2.png) [@esslee](https://community.gemsofwar.com/u/esslee)\ **Post date:** [March 1, 2017, 9:17am UTC](https://community.gemsofwar.com/t/assassinate-trait-vs-entangled/20659/5 "2017-03-01T09:17:58Z")
🙂 > [@Assasin Trait - Text is wrong or trait is not working correctly](http://community.gemsofwar.com/t/assasin-trait-text-is-wrong-or-trait-is-not-working-correctly/20494): > > I read the text of the enemy troop very carefully before selecting an entangle troop to combat Assasin’s third trait. It says ‘when I DEAL skull damage.’ BUT The first entangled match 3 skulls assasinated my 4th troop even though it did NO damage. The second entangled match 3 skulls (its very next move) assassinated my 3rd troop even tho it did no damage (so much for 10% chance!) I feel the text really should be changed to ‘…when I match skulls’ - unless of course this trait is n… ---
**Author:** ![Kurokazna](https://sea1.discourse-cdn.com/flex019/user_avatar/community.gemsofwar.com/kurokazna/32/11246_2.png) [@Kurokazna](https://community.gemsofwar.com/u/Kurokazna)\ **Post date:** [March 1, 2017, 9:32am UTC](https://community.gemsofwar.com/t/assassinate-trait-vs-entangled/20659/6 "2017-03-01T09:32:29Z")
Zero is a number, and therefore read as damage dealt. This little quirk in the system is part of why you want Archer or Assassin at the head of a skull spam invasion team. I’d love to see it fixed, but it might be a while ---
**Author:** ![Annaerith](https://sea1.discourse-cdn.com/flex019/user_avatar/community.gemsofwar.com/annaerith/32/13840_2.png) [@Annaerith](https://community.gemsofwar.com/u/Annaerith)\ **Post date:** [March 1, 2017, 10:31am UTC](https://community.gemsofwar.com/t/assassinate-trait-vs-entangled/20659/7 "2017-03-01T10:31:40Z")
like this wraith death mark should be also inflicted when doing skull damage (0) but it is not the inconsistency is sure there, not just a “quirk” ---
**Author:** ![Zelarith](https://sea1.discourse-cdn.com/flex019/user_avatar/community.gemsofwar.com/zelarith/32/1642_2.png) [@Zelarith](https://community.gemsofwar.com/u/Zelarith)\ **Post date:** [March 1, 2017, 9:34pm UTC](https://community.gemsofwar.com/t/assassinate-trait-vs-entangled/20659/8 "2017-03-01T21:34:14Z")
I guess I’ve been a bit lazy with my search, kept it to “assassinate”, I was on my portable and I was in an area with bad coverage 😓 ---
**Author:** ![Grundulum](https://avatars.discourse-cdn.com/v4/letter/g/82dd89/32.png) [@Grundulum](https://community.gemsofwar.com/u/Grundulum)\ **Post date:** [March 2, 2017, 12:57am UTC](https://community.gemsofwar.com/t/assassinate-trait-vs-entangled/20659/9 "2017-03-02T00:57:40Z")
I personally wouldn’t have thought to search for “assasin” (sic), so I think you did your due diligence. ---
**Author:** ![kynetarse](https://sea1.discourse-cdn.com/flex019/user_avatar/community.gemsofwar.com/kynetarse/32/24815_2.png) [@kynetarse](https://community.gemsofwar.com/u/kynetarse)\ **Post date:** [March 2, 2017, 3:56pm UTC](https://community.gemsofwar.com/t/assassinate-trait-vs-entangled/20659/10 "2017-03-02T15:56:27Z")
No worries, I wasn’t intending to give you a hard time about it. I think there’s some general inconsistency in match vs damage. Draakulis’s third trait is another example of this happening - the trait reads ‘on damage’ but it triggers on match when entangled. ---
**Author:** ![kynetarse](https://sea1.discourse-cdn.com/flex019/user_avatar/community.gemsofwar.com/kynetarse/32/24815_2.png) [@kynetarse](https://community.gemsofwar.com/u/kynetarse)\ **Post date:** [May 5, 2017, 1:51pm UTC](https://community.gemsofwar.com/t/assassinate-trait-vs-entangled/20659/11 "2017-05-05T13:51:21Z")
@Saltypatra This bug really needs to be fixed in light of Guild Wars. Guilds are exploiting Archer/Assassin bug on defense on brown days, where Sylvanimora’s entangle trait is a popular counter to skull damage. Edited for dumbness. ---
**Author:** ![Whiskeyjack](https://sea1.discourse-cdn.com/flex019/user_avatar/community.gemsofwar.com/whiskeyjack/32/65850_2.png) [@Whiskeyjack](https://community.gemsofwar.com/u/Whiskeyjack)\ **Post date:** [May 5, 2017, 4:02pm UTC](https://community.gemsofwar.com/t/assassinate-trait-vs-entangled/20659/12 "2017-05-05T16:02:54Z")
Hmm not my finest lyrics 🤔 but I wrote a protest song: What do we want? Sensible and varied counters to work against griefing instadeath mechanics being exploited in defence teams When do we want it? As soon as is practicable, please.