By appointment only, or by convincing other teams to queue. (which is why this thread exists) It's not a thing to just get in queue and expect it to pop (unless its coincidence that other teams coordinating getting in queue against each other),

GGs to the ~8 teams in queue last night! Fun was had by all - even if it resulted in a losing record

WAI will be attempting to get multiple teams in queue on Thursday 4/16. Start time TBD. Maybe we can hype the server a bit and get many teams in queue so people don't face the same 1-2 teams. Spread the good word.

a) Ravagers 8m SM b) Working as Intended c) Republic d) Jedi Covenant e) 2:34:13AM UTC; Wednesday, March 4th, 2015 f) 3:01:45AM UTC; Wednesday, March 4th, 2015 g) Video: http://www.twitch.tv/plocks/c/6245692 h) Composition: 1 tank, 5 dps, 2 healers (though one of the DPS, periodically switched stance/gear to tanky)

Yeah, if you see a "lock" with an alt code, it isn't me.

Its a bummer no one would even assume that Lock, Lockness, Lockzilla, Lock-jaw, Plocks, Lockbox, Unlock, and Antilock are the same person! /sarcasm

Gametype - Arena Section - HPS Class - Sage Toon name - Lock Record - 3898.4 Rank: #1? Link - http://imgur.com/bDhrPzf

Working as Intended will now join this list - Reactive Warding raid team. Bulo, you a B****! Bulo HM kill at ~11pm EST on 2.17.15. http://imgur.com/ANAlz3e

Interestingly enough, on the videos and screenshots, Oblivion and Xyzan were seeing the cross in the same place (and the same place as Hayward), so the assumption was that Lock's cross (my cross) was wrong, so I started ignoring the visual location of my cross, and just standing on Xyzan and Oblivion, and we were still failing. Overall it seemed to be extra bad this evening. I agree that it is passable (and we did pass it that night - mostly due to a heavy amount of healing), however at a certain point with a significant level of inconstancy, even properly "adjusting" results with a failed cross. The most humorous part to me is that people are assuming that latency is causing the crosses to be perceived in different spots. Our raid group plays on an EST server. People on the east coast (with lower latency) are consistently seeing the cross in the same place as those playing on the west coast (with relatively higher latency), and those with moderate to low latency are seeing the cross in the "wrong spot". So I'm not so sure that the hypothesis of latency is even the root of the issue.

Lurker is getting very frustrating. We have a full list of items we are making sure not to do (or do) to prevent the bugs, but there is no way to prevent these graphical inconsistencies. Look at our two streams: Note the player marked with a star on both streams (me = Lock). Lock's stream: http://www.twitch.tv/plocks/c/5912121 Hayward's stream: http://www.twitch.tv/torparse/c/5912099

/bumping this one - didn't make it to TORCommunity

WZ Damage taken: 2,857,682 Rank: 1 (Sage/sorc) Name: Lock http://imgur.com/N9G3o6G (might be some other records, including Doom's overall healing for sage/sorc) Arena HPS: 3531.93 Rank: 1 (Sage/sorc) Name: Lock http://imgur.com/ahYhihq

I call for a vote of "no confidence".

He's been playing COD. He asked some questions about COD ranked matches in /pubpvp last night.

RIP in peace, Going.