Please check if your issue has already been reported first!

When reporting a bug, please follow the template provided, otherwise the report will be declined. The information requested is vital to allow us to correctly reproduce and then fix what you are reporting.
We have temporarily disabled Baermar Uraz's Ugly Sweater Cosmetic (all queues) due to issues affecting gameplay.

Visit the Kill Switch Master List for more information on this and other current known issues: https://forums.bhvr.com/dead-by-daylight/kb/articles/299-kill-switch-master-list
It's stats time! Sign up for our newsletter with your BHVR account by January 13 to receive your personalized 2024 Dead by Daylight stats!

Get all the details on our forums: https://forums.bhvr.com/dead-by-daylight/discussion/436478/sign-up-now-to-receive-a-recap-of-your-2024-dead-by-daylight-stats/p1?new=1

PC/PS - survivors too hard to hit a shred

MoltenLily
MoltenLily Member Posts: 3

As seen, demogorgon's shred does not hit even it seems to be hit.

Its hit box in front and both sides have been shortened.

This used to occur in 5.0 as well, but getting worse in this update.


1
1 votes

Pending · Last Updated

Comments

  • crystalkitti
    crystalkitti Member Posts: 391

    Logically, as in 'I'm looking at this from a visual-based standpoint', that hit.. well, shouldn't have hit. Don't think it's bugged.

    (Then again, there's a toooooooooon of times where things that absolutely shouldn't hit, do.. so.. idk anymore. xD)

  • MoltenLily
    MoltenLily Member Posts: 3
    edited July 2022

    miss

    Post edited by MoltenLily on
  • MoltenLily
    MoltenLily Member Posts: 3
    edited July 2022

    I know there are too many cases about hit box, due to the server lags or something... but in the past there was a similar bug and it was fixed - the hit box of demogorgon's claw has been fixed in patch 4.1.1. The current hit box seems to be the one before 4.1.1, when the last moment of shred did not injure suvivors.

    To describe this as a lag or other reasons rather than a bug, it occurs too many times and before this update it used to be very rare, and therefore i reported as a bug here.