myxiplx

One point in Steven's thread that may have been missed - he's stated that this was *not* a patch that should have gone live. It sounds like it's code that was in the early stages of being developed and was in no way ready for release.

Having seen how professionally he's dealt with it since, and the quality of the fixes he's proposing, I think this could actually have been a nice feature had it been released as planned.

Steven's said that this shouldn't have gone live, he's fixing it now, and there will be an internal postmortem to find out what happened.

While we've all seen stuff like this far too often from SoE, at least on this occasion the mistake is being handled professionally.