I will update in a bit. Going for late breakfast. Anyway, I found something else with UnitHasIncomingRes, but haven't determined where the source issue lies. I did further testing with a friend, and found if you resurrected someone, but they did not accept (one minute timer running), and you cast again, you could indeed cast again instead of exiting out with a "PENDING" message. We made sure it was during the time stretch where the casualty did not suffer from res delay.
As I said, I haven't determined if the unintended behaviour is coming from LRI or SR2, but thought to give you a head's up.
Edit: wouldn't #6 above cause breaking code, forcing LRI-2.0?
Last edited by myrroddin : 12-20-13 at 11:26 PM.
Reason: Answering questions above.
|