Shovel/Axe no damage glitch

I've been playing for quite some time now and I've noticed a really messed up glitch with both the axe and shovel. If someone jumps forward and right clicks they can't be hurt or at least take less then 10% damage.

I've done some testing with friends and it's not lag that causes it (that was one of the first things we tried), it's also not missing we tested over and over again and even with blood spraying everywhere still no damage. This isn't a big deal until your in a Ghost Mode match with like 5+ shovelers/axers. The only time we were able to get around the NO damage thing was with a Spaz shotgun and some extraordinary luck, but even with that my friend only took like 30 damage from a point blank shotty blast to the face.

I know someone is going to mention the whole "shovel lag" thing and yes the shovel does seem to activate the glitch more often then the axe but not that much more. Maybe 25% more often.

has anyone else noticed this or is it just me and a handful of others?

Comments

  • It's the registry of the game. Sometimes a shovel right click can do 20 or 30 damage in mid air. It's gay. But idk, could be a glitch.
  • It's the registry of the game. Sometimes a shovel right click can do 20 or 30 damage in mid air. It's gay. But idk, could be a glitch.
    What he said.
    It's odd though, I've tested this with other clan members in previous GM clans, both on my laptop using a cheap-o wireless connection to get a lot of lag (+200 ms on Delta) which plays the game at roughly 80FPS on any given map or my main PC which plays this game around 150FPS (and around 30 ping on Delta) and during most of the testing of shovel lag I don't get the results until the FPS drops. Lag has just about nothing to do with it from what I've seen. I've played with people who have good FPS and very little lag (all of us being under 50ms ping) and I've still had the shovel lag issue.
    The axe, on the other hand, seems to have some damage issues sometimes but only if you swing from too far away.
    Respectfully,
    PROACEX1