Titan issues that need addressing.

[Arixtotle]

And that is where we disagree. In reality neither of us can confirm which is correct, but why do you think the server would send two bits of information (the trigger for the castbar and telegraph) separately to the player's client rather than as one single event? To do otherwise would be just asking for problems.

Because if you think of the connection ad a continuous stream, which it is, then the server should send information the second the code does something. I mean, yes you could code it in for the information to wait until a certain amount is collected but that's asking for trouble honestly since you'd end up with superfluous code and much larger amounts of data hitting our computers at once. The first means more work for the servers and the latter means more work for our computers.

[Gyson]

Because if you think of the connection ad a continuous stream, which it is, then the server should send information the second the code does something. I mean, yes you could code it in for the information to wait until a certain amount is collected but that's asking for trouble honestly since you'd end up with superfluous code and much larger amounts of data hitting our computers at once. The first means more work for the servers and the latter means more work for our computers.

Seems to me the server would just send the telegraphs coordinates and then the client would know to a) start the cast bar display and b) render the telegraph. Pointless to debate, however, as we're not able to examine the code (which means all of us are just speculating).