チャージアックスの挙動がおかしい / Charge blade issue

@Logits
Thank you for reporting.
Could you share us videoclip for further investigation?

Here is a video I uploaded with the same issue. I demonstrate how it works fine for the first hunt but afterwards the charge blade stops working as it should.

Sword mode doesnt over heat And you cannot load phials onto the shield

Even if the bar says you have phials and try to use them they dont work and you cannot go into red shield

when you morh into axe mode it undoes the morph and it just goes into sword mode

@PhazonWolf
@Logits
We apologize for the inconvenience.
This issue is currently being fixed.
Please check the link below for details.

改善要望は上のプルダウンメニューから改善カテゴリーをお選びください/Please select Improvements Category from the pull down menu above for submitting suggestions

on

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

iPhone 14pro/ iOS 26.3

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

V115.0

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

毎回/Every time

問題の詳細/Issue Details

It happens at the second hunt after restart.

  1. Blade doesn’t charge phials.
  2. Axe cannot blast phials. (Sometimes, phials are already charged at the beginning of the hunt)
  3. Axe goes back to blade by every dodge move.
  4. Map is not updated after hunting. Monster symbols remain in the map even after hunting. Monsters are lying on the ground in the waiting room.
  5. After I killed a monster in the quest, that monster shows up in the map and my character doesn’t move. Of course I cannot hunt that monster (the monster is not responsive to touch.)

その他の情報/Other Information

If I restart, it is fine just for the first hunt.
You guys really f**ked up this time.

画像、動画ファイル添付(最大30MB)/Attach screen shots, video files(Max30MB)





I accidentally turned on VPN, so my network was linked to South Korea ( I am leaving in the US). Under VPN network, charge blade bug didn’t happen. To test if this occurs due to some regional network condition, I turned off VPN and connected to the US network, the problem came back immediately. I guess, this problem is linked to the regional network or regional server.