Rescue is Griefing

[Packetdancer]

Cause it's badly designed. A two-part ability that would allow the healer to cast a rescue "buff" on someone else and then allow the person it got casted on to "resolve" it when they choose within a short time frame after the healer casted it would be much better for endgame content because the person it got casted on would be able to time their uptime perfectly and would allow people not to suffer bad rescues from DF healers who think they know best.

While I agree in theory, I strongly suspect the apply-a-buff/accept-the-move system would be even jankier than Rescue itself, timing-wise; as it is, when someone applies a buff to the entire party you can watch the buffs sort of spiral outwards -- sometimes a mitigation or heal will only apply to half the party before the damage goes out. Now, granted this is seemingly a side-effect of how AoE buffs get applied; a single-target scenario could at least avoid that, but it demonstrates that this game's netcode ain't super great at response times sometimes.

Relying on the action -> server, buff applied on server -> sent to client (and "accept" action becomes available) -> "accept" action used -> server, and then person moved... that's a lot of potential timing jank.

But, as previously mentioned, I've developed trust issues where this game's netcode is concerned.

(One reason I thought about the Salvation proc-off-of-buff system is that once the buff is applied, the entirety of the rest happens on the server, meaning you can cut the netcode out of the picture after the initial ability that would apply the buff.)

Now, if you allowed it to be applied enough in advance, you could probably ensure there's enough time that the buff is applied and the action available ahead of time, and thus avoid the jank. Or at least, avoid any greater potential jank than, say, Shukuchi or Aetherial Manipulation can suffer from on bad days. Though it would probably still not work super well for the Syrcus Tower situation or the pull-the-stack-marker-back-to-the-group in Dun Scaith, because even if you fired the ability off in time, in both cases the person generally doesn't know they're about to die so probably wouldn't hit the "accept" button and zip over.

The only other issue I see is that you'd almost certainly need to use the rarely-used "Duty Action II" slot for it; you can't use the more common Duty Action I because there are raids (like Deltascape v2.0, with the gravity mechanic) and trials (like the Vril in the Lakshmi trial) that require the duty action. That's not a problem in 98% of content, since Duty Action II is almost never used... but it would be non-viable in exploratory zones—Eureka and Bozja—where both duty actions are actually used. (For Logos Actions in Eureka or Lost Actions in Bozja.)

But that may not be a deal-breaker for some.