10 thoughts on “Patch for GU57 Breaks Palace of Roehn Theer

  1. Hmm we didn’t have that problem when we went into Palace or Roehn Theer yesterday to be honest. But it was a persistent instance we entered from sunday evening. That time we didn’t have a problem either.

  2. Basically it’s back to the old days of Cauldron Hollow.

    Have one person zone in to create the instance. Invite 3 other people to a group. Have each of them zone in. Now split up into 4 groups and form a raid. Now all 4 groups are tied to the instance. Now everyone else can zone in.

  3. Had this tonight–each person zoning in got their own instance. Not a useful thing, that.

    Sure which they’d concentrate more on keeping the game running properly instead of focusing on monetizing every blasted pixel of the game…

  4. We were able to enter the Palace we had saved from Saturday night, but our raid leader, two healers and a scout all got their own instances due to being absent over the weekend. When we reset and tried a new instance, of course we all got our own instance.

  5. Just for clarity, This zone never had a raid wide zone in. It’s always been everyone needs to click in individually, and if too many people clicked at once we would get multiple instances. The change was that they removed the disk ride prior to zoning in.

  6. No it didn’t but after the change you get multiple instances even if you click one person at a time. We never had the multi -instance issue with my raid no matter if 1 or 24 people clicked at the same time before the “fix”

  7. ya, it was always a single person zone in, and if too many zoned in at once bugs would occur. Either a few split into their own zone, or you could get a pop up saying “this instance has expired” and boots the raid back out. Now its doing something different all together.

Leave a Reply