devtrackers.gg
u/RoCoJared probably should take a look into that. Hydra Maw meta is one thing, it’s another when a gun that is supposed to do no less than 10(?) damage from the furthest range is doing 4 from a car length or two away.
u/RoCoJared probably should take a look into that. Hydra Maw meta is one thing, it’s another when a gun that is supposed to do no less than 10(?) damage from the furthest range is doing 4 from a car length or two away.
EDIT: Whoops I didn't see the video and thought this was in a different post. Yeah u/OB0E this look slike a bug. You should'nt have done 4 dmg there. Passing along to QA to check out
This is a knight. Not a spitfire. Look at the clip
Yeah sorry, I was reading your comment in my messages and not in this post. Sorry, yeah this is absolutely a bug. You should be doing full damage. He was legit in your face
This is a knight. Not a spitfire. Look at the clip
What is also weird is that your damage numbers didn't pop up as you were eating through his overheal. Makes me think his overheal is affecting this issue?
From experience, you can do damage to overheal but it won't show damage numbers until you damage his actual health. You are doing more than four damage trust me
thats still a bug and I want to fix that
Yeah somethings definitely bugged here.
Yep definitely a bug, either the damage is wrong but I'm also noticing that damage numbers aren't showing against overheal HP. We are investigating
do you actually think they think like this? 😐
Of course not. >:(
From the best of my knowledge, this is because chaac was overhealed so it only shows the damage of his normal health and not the overhealed part. 99% sure this is correct but if Jared or someone else wants to jump in and correct me, feel free to
Yep, we are investigating.
This is a knight. Not a spitfire. Look at the clip
ok yeah so looking closely and as others pointed out, looks like damaging an overhealed chaac doesn't show damage numbers, the 4 is the spillover damage once you hit his normal HP. We'll get this fixed, sounds like this issue has been in for a bit. Sorry about that man :(