Author Topic: 1.0.0.8 Cut throat does not stun or bleed if it hits critically?  (Read 1701 times)

Wing

  • Probably not a Spambot
  • *
  • Posts: 29
  • Karma: +2/-0
    • View Profile
I don't know if this is a bug but I was stealthed when I cut throat on an iron head grenadier. The message window says the Cut Throat critically hits but there is no stun or bleed effect. WTF? Luckily I could finish him off with my other weapon the Claw.

Wing

  • Probably not a Spambot
  • *
  • Posts: 29
  • Karma: +2/-0
    • View Profile
Re: 1.0.0.8 Cut throat does not stun or bleed if it hits critically?
« Reply #1 on: January 18, 2016, 12:11:56 pm »
I thought I was behind him and I was in turn based mode. I'll keep a closer watch next time. Would it be possible to disallow Cut Throat if the conditions were not right, like if a you weren't behind or if the enemy has noticed you? This makes sure you don't waste the AP and a cooldown.

Wing

  • Probably not a Spambot
  • *
  • Posts: 29
  • Karma: +2/-0
    • View Profile
Re: 1.0.0.8 Cut throat does not stun or bleed if it hits critically?
« Reply #2 on: January 23, 2016, 04:24:47 am »
I figured out what happened. I was in TB mode behind the enemy undetected when I started the Cut Throat but as the move takes time, the enemy detected me. So you don't just have to fullfill all the conditions for Cut Throat, you also have to hope that while you're performing it(in turn based mode no less), you don't get detected. Ugh!
« Last Edit: January 23, 2016, 04:39:51 am by Wing »

Styg

  • Administrator
  • Godman
  • *****
  • Posts: 2413
  • Karma: +513/-31
    • View Profile
Re: 1.0.0.8 Cut throat does not stun or bleed if it hits critically?
« Reply #3 on: January 25, 2016, 11:56:09 am »
I figured out what happened. I was in TB mode behind the enemy undetected when I started the Cut Throat but as the move takes time, the enemy detected me. So you don't just have to fullfill all the conditions for Cut Throat, you also have to hope that while you're performing it(in turn based mode no less), you don't get detected. Ugh!

Fixed for the next update.