Do you think I could just leave this part blank and it'd be okay? We're just going to replace the whole thing with a header image anyway, right?
You are not logged in.
Because you get one die after killing is ended
so far how i know how death works is this: touch spike>death animation comes>death packet get ssend to sever saying you got killed>sever gives packet back to client>client adds a death and respawns you
in the time while the death animation still works you can get in god and you wont be killed it sbecause the packet is delaye duntil the animation is basically over so I think that if yo ureset in that period and the sever gets both pakcte safter each other (in same tick or a tick after) and the reset one is ealier it will detec your reset and before client rechives tghe reset pcket back sever also sends death one while youre being reset the client deetcs the spawn as your 'checkpoint' and gives oyu a death
ok lukem fix me if im worng
thanks hg for making this much better and ty for my avatar aswell
Offline
so far how i know how death works is this: touch spike>death animation comes>death packet get ssend to sever saying you got killed>sever gives packet back to client>client adds a death and respawns you
in the time while the death animation still works you can get in god and you wont be killed it sbecause the packet is delaye duntil the animation is basically over so I think that if yo ureset in that period and the sever gets both pakcte safter each other (in same tick or a tick after) and the reset one is ealier it will detec your reset and before client rechives tghe reset pcket back sever also sends death one while youre being reset the client deetcs the spawn as your 'checkpoint' and gives oyu a death
ok lukem fix me if im worng
You have a developer logic! What about starting coding bots?
[ Started around 1732525333.4325 - Generated in 0.040 seconds, 12 queries executed - Memory usage: 1.38 MiB (Peak: 1.47 MiB) ]