It is possible that a GM is at fault here, but it is something that we find very difficult to believe. Our team is very tight knit, we all know each other from outside of GLB and have been together since the middle of season one. All our GMs are people who have earned the position through EXTENSIVE effort on the team's behalf; every one of us has put way more time into this internet dot simulation than any sane person probably should, in order to get us to the point of being one of the top teams in Canada Pro (after starting in Canada AA initially). So you'll have to forgive us for being reluctant to point fingers at each other.
I have worked in software QA, and I know exactly how rare truly "inconsistent and unreproducible bugs" are. I also know that it's a major cop-out to fall back on that as an excuse, especially in a situation like this where the QB settings were different than the other positions, which is pretty inexplicable. Nevertheless, it isn't an IMPOSSIBLE explanation, and given the level of team unity we've had since the beginning, I consider the unreproducible bug to be a more likely explanation than intentional sabotage.
The only way I'll believe a GM was responsible is if I see a log of the changes being made.
Edit: I refer to intentional sabotage by a GM. Intentional external sabotage is another story. I do think it's more likely that we were hacked than that a random bug caused it, since it really doesn't make sense as a bug. If this is the case, I would really like to see the log of the changes being made though, and while I don't expect IP info to actually be released, I would want to be told whether the login IP of the person making the changes matched the normal login IP of that account...
Last edited Jul 15, 2008 15:06:36