Titan issues that need addressing.

[Gyson]

I think more than a few critics of this thread are missing a point (which I thought I spelled out clearly enough) in the opening post.

First, I find it difficult to believe that most players monitor Titan's cast bar. Heck, going by the number of interrupt opportunities that pass by unchallenged on everything from the average mobs to dungeon bosses, I would argue that most players aren't watching cast bars anywhere. While it's fantastic that the fraction of people on this forum who are participating in this thread (which make up an even tinier fraction of the people playing the game) are apparently all cast-bar watching pros, as someone who is always tanking I feel like I can safely say that most of the time the only one staring at cast bars seems to be me (as I'm rarely able to count on the average player to help interrupt anything).

Second, this thread is not about what people should be doing - remember, "we're apparently all pros here" , so nobody is dropping any insight bombs on anyone else. But for your average player (you know the one, that fellow who has died early *again* on Titan attempt #X) the issue pointed out in the original post is not making anything easier for anyone. It is very difficult to convince your average player that they failed to react in time when every visual indicator on their screen is reinforcing the idea that they *did* react in time. The average player is not going to want to hear a lecture about castbars versus telegraphs, or theories on video/processor lag versus network latency - on their screen they see themselves clearing the AOE-warning makers before it vanishes and/or explodes, and a) it is a lie, and b) it is a lie they're buying into. To argue with them that they were "late" at that point is to basically tell them to stop trusting their own eyes and the information being displayed on their screen. It doesn't work.

I would argue that tightening up the animations (especially for this trial) such that the castbar and animations are more in sync would be infinitely more useful towards helping players improve compared to a futile attempt to educate everyone in the game about the quirks and workarounds for this encounter. Simply put, if Bob sees his character die in an explosion he will make a real effort to move faster/anticipate better in the future. Where as Bob seeing his character die (when standing a safe distance from an explosion) is not likely to put much effort into improving at all, because in his mind the game got it wrong, not him. And when half your Duty Finder PUG is filled with Bob's having this issue, it sucks for everyone wasting their time on that run (regardless of who is doing it right or wrong).

We can argue about whether or not this can be fixed, but nobody should be arguing about whether or not it would be preferable to have things syncing up better (hint: it would be preferable). And yet some of the responses seem to be doing just that, which is more than a little strange.

Side note: for the memorize and move early crowd that is proudly chiming in on this discussion - I would also argue that you are essentially screwing over the rest of the party in an effort to guarantee your personal survival. If everyone is tightly stacked to minimize the amount of traveling distance needed to clear all those "Weight of the Land' telegraphs, you must realize that by breaking formation early (even a half second early) you're causing those telegraphs to spread out more, which in turn is making escape more difficult for the people who are waiting for the telegraph as a visual cue to start moving. Perhaps you don't realize this or you just don't care, but it is what it is.