11 thoughts on “Guild Hall Lockout Bug Makes It To Live

  1. “After weeks of testers reporting getting stuck in their Guild Halls…”

    That’s what really ticking me off about this whole thing. Players have volunteered (ie, worked for SOE for free) to help them sort out bugs and whatnot, and still the bugs go live. I’m not a tester nor do I want to be (especially in light of how SOE ignores them), but I am grateful to the players who do test and enjoy it. So it makes me pretty upset that people have volunteered to do this testing for SOE, but it gets ignored, their time and efforts are wasted, and we on the live servers still end up facing the bugs and – in essence – doing the exact same thing Test already did, which is to report the bugs and wait for responses. Why is there this redundancy?

  2. The trouble is they are SOOO short handed they can’t do all reported bugs so they pick and chose. WTF they didn’t pick something as major as this to fix is beyond me. Or maybe they did fix it SOE style, which is to think they fixed it but failed.

  3. They shouldn’t be picking and choosing at all. If it’s a bug it needs to be addressed, then put it off until it is addressed. This is seriously a major mess; this is not the result of picking and choosing, but forcing something they knew plain and simple was not ready to be published. At least they should’ve known it, because for most of everything that is being reported, you can find a Tester saying, “We told you.”

  4. After this update i think its time for a month or 2 off let the bugz work there way out and come back to a game thats not going to drive me crazy with zoning and logging issues

    pps love the gear fix the rest

  5. It’s now almost noon Monday at SOE and not one Red Name comment in any of the multitude of threads about GH lockout. There is evidence many have been locked out most of the weekend. Petitions are apparently backlogged 8 hours or so.

  6. I understand the frustration and apologize that it was missed. We looked into the issue as we received reports from the Test Copy community and believed the problem to be related to the copy scripts. Since we didn’t have a clear repro as to the cause of the problem we moved on to other bugs and tabled that one. We made an incorrect assumption that the problem wouldn’t happen on live servers and that was obviously wrong. We worked on the issue over the weekend, found the problem and got it corrected by this morning’s hotfix.

Leave a Reply