Haze Dagger Still Clips Through Opponents As Of April 2025
- Thread starter SV-X
- Start date
SV-X
New member
I cannot stress just how demoralizing this feels as a player. Playing Haze, especially Spirit is already an uphill battle. I don't mind that and find tons of enjoyment in the challenge, but when one of the few kills I can get and need to thrive are ripped from me, not from a mistake or from being outplayed, but just from being denied for what ever obscure reason, it just feels like absolute dogwater.
SV-X
New member
I updated the posts to include the time stamp for both occurrences.
In the first occurrence, the target was moving towards me and clips into me; the dagger missing could have been explained away by ping + dagger spawn location + hitbox. In the second occurrence, the target is standing completely still and at a small distance, I am unsure what could cause this other than wonky hitboxes.
Another player I showed this to noticed that I tend to correct my aim between the time of initiating the dagger throw and the actual throw. They tried to recreate this bug by throwing the dagger as I do in Sandbox mode. While they could not recreate this consistently, they would occasionally have the dagger pass through the target / fail to register when thrown in this manner.
We don't know if that really has anything to do with the cause of this bug, but it could be key.
In the first occurrence, the target was moving towards me and clips into me; the dagger missing could have been explained away by ping + dagger spawn location + hitbox. In the second occurrence, the target is standing completely still and at a small distance, I am unsure what could cause this other than wonky hitboxes.
Another player I showed this to noticed that I tend to correct my aim between the time of initiating the dagger throw and the actual throw. They tried to recreate this bug by throwing the dagger as I do in Sandbox mode. While they could not recreate this consistently, they would occasionally have the dagger pass through the target / fail to register when thrown in this manner.
We don't know if that really has anything to do with the cause of this bug, but it could be key.
