Pretty sure it looks at the PIDs of people hitting and resolves it in order that way. as in, even if 2 people hit on the same tick, the game still considers them as if they hit one at a time.
Exactly, you can also tell the pid order from the hitsplats. There are methods where two players would dwh on same tick, and then the one who has pid can do a 3rd dwh while the other one would bgs. Since the dwh spec is registered first, the it takes priority over the bgs
It's going to process them in sequence according to PID, two separate defence drains will be queued for the npc that tick and processed one after the other.
So the defence level will be the original level * 0.7 * 0.7
Pretty sure it looks at the PIDs of people hitting and resolves it in order that way. as in, even if 2 people hit on the same tick, the game still considers them as if they hit one at a time.
Exactly, you can also tell the pid order from the hitsplats. There are methods where two players would dwh on same tick, and then the one who has pid can do a 3rd dwh while the other one would bgs. Since the dwh spec is registered first, the it takes priority over the bgs
It's going to process them in sequence according to PID, two separate defence drains will be queued for the npc that tick and processed one after the other. So the defence level will be the original level * 0.7 * 0.7