Bullet avoidance/ignoring

Yeah I noticed it before that then I was just reminded while watching it.

That's awesome.

The Server sends a packet to the client "mob ID XX shoot bullet type XX"
The client renders the shooting
When client-sided hit, the client sends a packet to the server "has been hit by bullet xx (maybe even with the amount of damage)

I came to this conclusion because when you experience lag, one monster spamshoots a lot of bullets, and all of them are being shot at the same time.
in other words, when you lag, the bullets won't appear randomly on the map, but rather be spam-shot from the appropriate mob.
You could exploit that
either filtering the "client! shoot" packet, or the "I got hit" packet

The server and other clients check if you get hit too.

I sense a storm coming...

I'm curious if the server will believe me, if every client around me says I did not get hit.

Don't know. You should try it. Open a pirate cave and a bunch of mules. The server might not believe you if only your client says you did not get hit. Maybe a couple of mules saying the same would convince it?

The server doesn't base it decision on what other clients say about you getting hit. What you see on your screen isn't what another player sees on his screen so doing any kind of hit detection based off the two (let alone more) different sets of information would be idiotic and wrong. Another reason it would be wrong is you would be able to kill other players if this was the case. That is reason enough not to do detection that way.

I wonder what is the point of OTHERHIT then :/

Not sure what it is used for now. I think it had relavance in the past when god mode was possible.

So something like the spam filter but in reverse .....you could make a script that blocks the client from sending a packet if it contains a line telling the server how much dmg you took.

I think it works like this when a mob shoots.

Client --> Server ("This is my location, pls load map and mobs around me" packet sent)
Server --> Client ("Mob is in range and shoots at you" packet sent)
Client --> Server ("I've been hit" packet sent)
Server --> Client ("This is your damage taken" packet sent)

Then client registers the damage taken and updates your HP bar and that is why there is always that little bit of lag before the auto nexus actually makes you auto nexus. because it is waiting for the damage packet from the server to be sent but by the time it registers that packet, you could of taken 2 or 3 more hits which sends another 2 or 3 more packets to the server before you get auto nexus and that is why the auto nexus RR script tells the client to stop receiving packets after it receives that 1 packet telling RR that your heal has gone below the % you set, to auto nexus at.

So, in theory, stop the packet from Client --> Server, telling the server that you have actually been hit and it wont send you a packet telling your client to take HP away from you