So this bug has been around for such a while now, and i felt that i should create a report about this once and for all.
When you're in combat, and your opponent deals you a hit that would be 'fatal' the hit registers 0.5 seconds before your actual death occurs. within that 0.5 seconds, you CAN'T eat. The game has the hit registered before you die, so at that moment, not much can save you (probably only an earlier casted teleport that has the perfect timing).
I've realized this in so many different scenarios, mostly pking for me.
Could this be fixed? because it's really affecting the possible risks you can take in a pvp situation and i've heard from people that it's a nuisance in pvm scenarios.

its called client-side lag.. Or as most of you guys know it, ping. youre already dead for the server it just took a few milisecond to travel to you and give you the news visually

its called client-side lag.. Or as most of you guys know it, ping. youre already dead for the server it just took a few milisecond to travel to you and give you the news visually

Would that be listed as a bug? It needs fixing imo
Also, this does not happen because of bad connection, it can happen always if your eating timing is respective to the killing blow, which causes you to not be able to eat

Quote from: Mary on June 01, 2016, 10:41:53 pm

its called client-side lag.. Or as most of you guys know it, ping. youre already dead for the server it just took a few milisecond to travel to you and give you the news visually

Would that be listed as a bug? It needs fixing imo
Also, this does not happen because of bad connection, it can happen always if your eating timing is respective to the killing blow, which causes you to not be able to eat

ofc that cant be fixed that is lag on your side. Things just need time to travel between the server and back to your computer, it's not instant. I have no idea what you mean with 'respective' in this context, do you mean 'almost at the same time' or something??

Quote from: Attacker35 on June 02, 2016, 07:53:45 am

Quote from: Mary on June 01, 2016, 10:41:53 pm

its called client-side lag.. Or as most of you guys know it, ping. youre already dead for the server it just took a few milisecond to travel to you and give you the news visually

Would that be listed as a bug? It needs fixing imo
Also, this does not happen because of bad connection, it can happen always if your eating timing is respective to the killing blow, which causes you to not be able to eat

ofc that cant be fixed that is lag on your side. Things just need time to travel between the server and back to your computer, it's not instant. I have no idea what you mean with 'respective' in this context, do you mean 'almost at the same time' or something??

Yeah, basically if you try to eat in the 0.5 seconds it goes something like this : you get hit, the animation of your opponent hitting you begins, you can even die mid animation when the animation is long eunogh, claws are a perfect example and after the hit is registered, if the hit is a killing blow the server registers it before you die (visually) and you can't eat in the 0.5 sec interval.
this is by far definetly not a ''lag'' bug and it's something that's a ''feature'' because there is no way for you to eat in that 0.5 seconds

Yeah, basically if you try to eat in the 0.5 seconds it goes something like this : you get hit, the animation of your opponent hitting you begins, you can even die mid animation when the animation is long eunogh, claws are a perfect example and after the hit is registered, if the hit is a killing blow the server registers it before you die (visually) and you can't eat in the 0.5 sec interval.
this is by far definetly not a ''lag'' bug and it's something that's a ''feature'' because there is no way for you to eat in that 0.5 seconds

For the server the animation and the hit is already over: youre already dead. You just dont see it starting earlier because of client sided lag. When someone attacks > attack travels to server over internet > attack travels to you its already like half a second further and for the attacker his attack is already over when your animation for getting attacked is still playing. THAT is client sided lag and you cannot prevent this other than getting minimal ping/minimal lag internet connection. But there will always be atleast 0.02s before information is finished travelling over the internet, so an attack will always be seen by you 0.02s later (or longer if you have bad internet connection). You try to eat but you cannot eat because for the server to accept your food it will first check if you're dead, and if you are (even if you dont see it yet) it will not accept food.

It couldn't be made so you CAN eat in that small period of time?

It couldn't be made so you CAN eat in that small period of time?

No, as it would make you practically immortal until you run out of food.

It couldn't be made so you CAN eat in that small period of time?

No, then you will always be able to eat at 0 hp and heal up to 23 (whatever food ur using). Considering Emps does not do overkill (a hit of 40 on a 10hp target will be a hit of 10), you will only be killed if you're too late clicking food when you die (doesnt happen cuz everyone spams food when they get a high hit)

To display the hit animation correctly, the hit displays 0.5s after the actual hit (after the attack animation started). This will be reverted so there will be no delay to see the hit.
So this change will only be cosmetically, and will no longer give the fake impression to players that they still have time to eat when a deadly hit animation already started.

This will be changed in the next update.