[2022] Priority (Of Reps, Dmg, Ewar, Etc... ) Within A Server Tick

As far as I can tell all such effects from modules are being evaluated on whatever happens first (either is first in the reactivation queue, reaches the server first - at least as long as the server is not overloaded like in 10% TiDi, when it becomes a bit non-deterministic) and the ship dies whenever the health reaches 0. If the damage is first, then it dies, if the rep is first. then it lives. This calculation is not based on ticks, but some of the messages are only sent out to the clients together with the next destiny tick.

Correct, as far as I can tell. The server tick does not affect this order. So in minorVulpes' specific case it depends just on the cycle duration - and to a small amount on the network latency to the server, as the module only starts as soon as the server received the command.

If the server is getting really busy then the server might take slightly longer to process the events, but the order should still be mostly intact. In the past (several years ago) the server prioritized under lag accidentally events, which were coming from clients over modules, which were already cycling. This caused FCs to tell fleet members under lag to use single activations of their weapons and avoid cycling - which then caused even more lag. This should no longer be the case now and all module events should be handled the same.