We specifically tried NSSN and SSSS and all we do is wait for the "final" turn to happen at one spot first. It still can, and do, lock up. Again, there is very possible other factors that cause this to lock up that has nothing to do with the order of things locking up. Clearly just using one person doesn't work (you'll get overrun by acklays before you finish). I'm saying it's trivial to do it by just going as fast as possible and not caring. It's equally easy to have it fail if you do follow this "SSSS" rule. We're capable of not "making one of those mistakes". It's a bug. We don't know the cause. It might be because you run with 2 shadows instead of 1 for all we know (yes that's unlikely, but my point is we have absolutely no way of knowing what's causing this issue). My advice is to just solve them as fast as you can. It'll work eventually.

Yes, it is in fact RNG. 130 data points is not a lot of datapoints. Unlikely, but amongst millions of people it's perfectly reasonable that this has happened to one person. Drop chance of the tokens is completely predictable (25% chance for each token per kill that has them). It's terribly unlikely that this would happen, but it does. Remember, people win the Mega Lotto despite the one in 175,711,536 chance of winning (odds varies but it's somewhere in that area). This guy was just really anti-lucky in winning the no-inq columni drop lottery. There's no true random numbers without an external source (say the movements of the blobs in a lava lamp), but it's sufficiently random to work in a game. I _am_ a programmer and I have seen the effects on randomness in a game first hand. It feels like it's not random when it is, and feels entirely random when it's artificially modified to reduce some of the randomness in favor of variability.

That I believe is another bug. When you get a single turn to solve, it breaks consistently (to be exact, we've never had it work on a single turn - you can click and click and the pattern doesn't change). It doesn't seem (from the patch note) that there's a fix for that issue in 1.1.5.

We have, and use, the app. Stop assuming people are having this issue from randomly clicking in any odd order. We never did that, ever. They key point is that if Bioware says it's a but, it's a bug. If it doesn't happen to you when you do <something magical>, good for you. However considering how many "must do" solutions there are, it's pretty obvious there is no "must do" way except not just randomly clicking. Still the drawback of going a suboptimal route is not a locked up console, but being overwhelmed by mobs with the soft enrage timer.

That is possible too, but most likely it's just failing to understand the concept of random. Heck, having written a Tetris game once, I intentionally made it less random because I didn't like seeing the same piece coming 3+ times in a row. Once time, in band camp - err - I mean Black Temple, I spent 6 months killing Illidan every week to get the trinket to drop. It never did. Random? Yep. Sucks? yeah, very much.

Indeed. The people stating that there's a special way to solve it are the same people that insisted that Onyxia deep breathed more every patch.

It really doesn't. NSSN - tried, doesn't always work SSSS - tried, doesn't always work NSSS - tried, doesn't always work Pressing buttons in no order, solving in no order: worked There's possibly other things that help trigger, or not, the bug (heck even the class is possible - see Deconstructor) but in the end, it is a bug. Stating otherwise after it's been proven by a fix in an upcoming patch is silly. Also you could just be randomly lucky. See http://friedom.com/?p=302

Actually, that's exactly what random number generator is. Take a few minutes and read this to understand what "random" actually means. http://friedom.com/?p=302 One of these sets of numbers are 10 random numbers between 0 and 5. The other one was manually generated. Which one is random? a) 2 4 4 0 1 0 2 0 0 1 b) 1 5 2 0 3 4 0 5 1 4 Most people would say that clearly, (b) is more random but it's not. I manually wrote those numbers down to get as much variation as possible. The first one, with 4 zeros out of 10, is randomly generated. RNG != "always different" RNG != "evenly distributed" This happens in every game that has random loot it seems.

This bug will be fixed in the 1.1.5 patch: Eternity Vault An issue that could cause buttons to stop responding during the Ancient Pylons encounter has been fixed. As for the people with various magical incantations for "solving" the puzzle without triggering this clearly intentional aspect of the encounter - it's called random luck of the draw. The only think we've consistently seen to be true is the "one turn" issue where it stops turning the wheel entirely. After having spent some time trying all "known to work" solutions to this encounter, we changed tactics to just solve each side as quickly as possible without coordinating the sides - this worked a few tries later. In either case, if you missed the message: This is a bug. There is no correct way of solving the puzzle and it's not an intended mechanic.