Input issues are still relevant.

iStaplesiStaples Member Posts: 46 ★
in Bugs and Known Issues
I wanted to share with the community and Kabam proof that the input issues indeed were not fixed that they said they were. In the video you can see I parried Xbones a few times, you clearly see parry on the side and the stun didn't even trigger. You can see later that I was able to stun Xbones (which he then shrugged off). This was recorded in the EQ 3.2 path A, there are no nodes preventing parry from triggering. Kabam this needs to be addressed.

Comments

  • CoatHang3rCoatHang3r Member Posts: 4,965 ★★★★★
    Crossbones reduces your ability to stun him via parries with his furies. Only thing you’ve proved is players are attributing normal champion interactions to input issues.
  • CoppinCoppin Member Posts: 2,601 ★★★★★
    U got wrecked...
    The parry issue was parry not being timed or detected...
    I can see the word parry on screen at least 5 times... So it was "working"
  • iStaplesiStaples Member Posts: 46 ★
    Well I am glad to have learned something new then. But we could all agree that parry and dex are not functioning 100% like they used to.
  • CoppinCoppin Member Posts: 2,601 ★★★★★
    iStaples said:

    Well I am glad to have learned something new then. But we could all agree that parry and dex are not functioning 100% like they used to.

    Specially against Crossbone
  • Camby01Camby01 Member Posts: 572 ★★
    There are plenty of relevant fights that you could use to support your argument. Using a xb example only gives folks a chance to chirp that you didn't read the node, don't understand his ability, etc.
Sign In or Register to comment.