I did some looking into this while I did my contributions for the defib, and I couldn't find anything fundamentally wrong with the way the revive request was issued.
But, due to how a revive is performed within TTT2, once it finds an adequate revival zone, if someone happens to walk past that zone and obstruct it briefly, it will completely fail and that minion won't be converted. This is a little confusing, because the revive function already works backwards from:
Corpse position
FindSpawns() near reviving player
...
PlayerSpawns
FindSpawns() near PlayerSpawns
IMO when a revive is issued it should continue to retry until it finds a valid position, or at least X number of attempts / time spent attempting.
'Cause unlike with the defib, you can't just keep retrying until it works.
Some maps are just absolutely going to fail the hull test where a corpse lands despite having ample space.
I did some looking into this while I did my contributions for the defib, and I couldn't find anything fundamentally wrong with the way the revive request was issued.
But, due to how a revive is performed within TTT2, once it finds an adequate revival zone, if someone happens to walk past that zone and obstruct it briefly, it will completely fail and that minion won't be converted. This is a little confusing, because the revive function already works backwards from:
IMO when a revive is issued it should continue to retry until it finds a valid position, or at least X number of attempts / time spent attempting. 'Cause unlike with the defib, you can't just keep retrying until it works. Some maps are just absolutely going to fail the hull test where a corpse lands despite having ample space.