Server side hit markers for the cutlass

  • I do understand that in theory, hit markers for the cutlass shouldn't be needed. The enemy is right in front of you and you can see whether it hits or not. In reality though, hit reg is a thing and will always be a thing. This is somewhat countered in projectiles with the option of server side hit markers, so at least you know that hit reg has happened and can react accordingly, and communicate with your team mates etc.. But the sword does not have this feedback.

    To be clear, this is NOT A thread to discuss the intended mechanical advantages/ disadvantages of the sword, and whether it needs to be buffed or nerfed or better balanced with other weapons, or whether stunlock should exist at all etc. etc.. I'm not saying we shouldn't have a conversation about whether the cutlass is good or bad or OP or perfectly balanced or what mechanical changes should be made to it. But there are plenty of threads on that topic already. This thread is specifically about the game not working as intended. Not knowing whether you've hit your enemy because of hit reg issues is obviously not intended to be part of the game.

  • 3
    Posts
    483
    Views
  • @eligibleeel6171 This is actually a really good idea.

    The amount of times I've sworded someone 4+ times expecting them to be dead, but they're not is very common, so I don't know whether to rush them or back off in some cases.

    Though in cases, the hit marker could be annoying as the sword is a very fast weapon.

    But yeah, good idea

  • Same. The other thing that bothers me is when I'm mid sword combo, expecting them to be stunlocked and they just change weapon and I take a full blunderbuss hit at close range. In one fight it happened so consistently that I thought they'd just removed the stunlock from the sword and not told us.

3
Posts
483
Views
1 out of 3