Damn lol, that video

This post was edited by Garnier on Aug 2 2016 06:34am

Last I checked the UA members that discovered switching gear PM'd Paul and this was deemed as acceptable (or at the least was not changed). This was LONG before today and numerous MM have been completed so far. In all reality though, if they used the same gear we did, NOONE would ever have a chance to successfully complete MM because the group would be wiped in the first 5-10 seconds with no chance of recovery (not even with comfreys). The mobs have MORE hps than we can achieve, some still have the monster abilities (such as the stun) which means that they have the advantage at all times and would not be achievable. Sometimes you have to outsmart your opponents to succeed.

wow! that is nuts, thats like rapid fire

I still would have beat it.



For real that sucks, looks like it should get checked out, for fun you guys should try it again without alchy, see if you can recreate the bug or confirm it to that.

Yeah, but it's hard to find ppl now after showing this lol, having 5 feeders doing this would take 2 years to get there lol

First of all, I want to apologize for the problems this bug caused with your attempt at Mirror Maze.

After much searching I did find the issue, which is similar to what someone here said I think, relating to the no weapon on alchemists. Long story short, the mobs were spawned in that same state, which can't happen for a mob under other conditions, which then broke the next attack speed check effectively giving the mob a near 0 base attack speed. This resulted in the "rapid fire" attack that you saw. Since Mirror Maze is the only condition a monster can be generated in this fashion, this bug has no other ways to occur other than Mirror Maze. The issue should now be fixed.

I will be crediting a random guild point reward to all those involved in this climb to compensate for a failed attempt that otherwise by everything I can see would have succeeded. [edit]: Guild Points credited.

Thanks for your patience regarding this issue, and for all the details you provided to help me track it down.