The reason I suggested sticky targeting was becaust the tank acquires the next target in advance of the DPS switching.
Please correct me if I'm wrong, but I envisaged the following. Given a 100ms latency, the sequence of events would be:
T0: DPS client is targeting current target. Tank client switches target
T100: DPS client thinks tank still targeting current target. Server sees new tank target.
T200: DPS client also sees that tank is targeting a new target, but continues to DPS old target because it is not dead yet (this is the sticky targeting in effect)
T10000 (say): DPS has killed the target, and now switches to tanks target. The switch is instant, because it has been updated with the tank's target since T200.
Agreed, the tank switching cannot be instantly communicated to the other clients. My suggestion was a work-around; an idea to help cope given this premise. Sorry if its a crap idea![]()
Connect With Us