Talk:Sacrifice/@comment-7435337-20180407091040

Unfortunate multiplayer oversight or a possible bug: When being revived by your Sentinel, a teammate can join in with the revival process like normal, doing this will cancel your Sentinel's Sacrifice (probably to prevent the Sentinel from wasting its life when you're being revived by a teammate). However, if your teammate is then interrupted or cancels the revive action before reviving you completely your Sentinel might not re-activate Sacrifice, which means you get returned to the bleeding out state with 0 seconds remaining on your clock, killing you instantly and forcing you to manually revive.

I'm not sure if this is a problem with Sacrifice having an internal cooldown, or if my precept order was messed up or something, maybe it's a Sentinel AI issue where there's simply no condition to check if a teammate has cancelled the revive and to re-activate Sacrifice in that case, but yeah, this is annoying when it happens.