Flicking down for counter-thrust and then holding quickly is often registered as letting go of the guard stance instead of executing counter-thrust

携帯端末情報(必須)/Mobile Device Information(Required)*

Samsung S23 Ultra, Android 16, One UI 8.0

アプリのバージョン(必須)/App Version(Required)*

v117.0-260323-1859

問題が発生する頻度/Frequency of the issue occurring

頻繁/Frequent

問題の詳細/Issue Details

  1. Equip any lance with default style
  2. Start a large monster hunt
  3. Hold the screen so that your hunter enters the guard stance
  4. Wait for the monster to attack
  5. Just before the monster hits you, while still holding the guard stance, flick down and then quickly hold the screen again so that you go into the counter-thrust stance and hold it there
  6. Observe that the monster’s attack is not blocked at all and the character suffers damage from the monster’s blockable attack

Please see the video here (turn down your audio device volume before playing the video):

Observe my white touch dot on the top left of my hunter (I slowed down the video to 1/8 of the regular speed). It’s shown that I did let go of the screen to perform a downward flick in order to perform a counter-thrust, and within a split second I touched the screen again in order to hold the counter-thrust stance, in case the monster failed to hit me.

But for unknown reasons, I got hit, as if I let go of my guard stance and did not activate counter-thrust. Once we go into the guard stance on the lance, there’s no reason for us to get hit when we flick left/right for guard dash or flick down for counter-thrust. I certainly didn’t flick up for the dash, and I certainly didn’t let go of my guard stance here. Therefore this hit is unreasonable.

I’ve been hit like this a few times since the introduction of v117. I’ve been doing this regularly while using lance and never had this issue before.

@Stampeder
Thank you for your report regarding counter-thrust.

The information you have provided has been shared with the development team for further investigation. If there is any additional information we can share on this, we’ll do so on this thread.

1 Like