Monday, March 31, 2008

Magisters Terrace - the good and the bugged

I don't know about you but I am soooo happy to have a new 5 man to run. Especially when there's the chance to pick up a nifty mount or a vanity pet. Although I have to say I find the raucous screech of the hawkstrider most annoying hehe. Sweet lewts aside I also think MrT is a triumph of in game artwork. It's such a lovely beautifully detailed instance. It's also always a pleasure to run an instance with some greenery as opposed to the dreary 'dungeon/cave' appearance of so many of them.

Friday night a group of us got together to give MrT a drubbing. Our group was composed of a Warrior tank, Demo lock, holy priest, fire mage and yours truly. We did the normal version first to get Emelin and myself keyed and then hit it up in heroic mode. We actually did better in heroic mode - probably because after one run through Emelin and I now knew what to expect. The instance definitely benefits from a group make up possessing multiple CC ability which is what we had with sheep, banish, seduce, fear and my traps. The most exciting moment - the phoenix pet dropped! Woooo! The lucky recipient was Tiffi our mage.

The next day we were all set to run the instance on heroic again for a chance at phat loot and for myself increased rep. I've haven't spent much time looking at the loot from MrT but I'm yet to see a drop that would be a clear upgrade for me. There is a nice chestpiece but since I've just got my hands on the Ranger Generals Chestguard, apparently considered one of the best it's no upgrade. No it's the rep I want as there are several nifty Jewelcrafting designs to pick up.

So a group forms. Three party members had run the instance that morning before the reset. So we head in and clear the trash up to the first boss. Wait... where is the first boss. He was totally AWOL! But the door that opens to the next section once you down him was still shut. Hmmm. Very strange.

We head back outside and I made the stupid mistake of asking in General whether anyone had had any issues with the instance. Yup definite mistake since the responses were all about how I needed to L2P and stop QQing just because you find it too difficult. Ugh. I further explained what had happened and then had people telling me to check my raid ID. That if we dropped group and reformed under a new leader all would be fine and so on. Just to prove ourselves right we did just that. Yep as expected, the boss was still missing although the trash respawned (in this group we had a handy rogue who was able to sneakily investigate). As with any heroic we had all been saved to the instance on the same raid id without needing to kill a boss first. Reforming under a new leader and re-entering did nada. I took great satisfaction in announcing that in General although typically no-one actually listened. Great, we were saved to a borked ID and the instance wouldn't reset until the next day. I'd opened a ticket but with little hope of any quick response we decided to pick up the heroic daily and headed over to lay waste to Steamvaults.

A pleasant suprise was that a Blizz CM contacted me just as were entering StV. It seems this is a known issue and Blizz are working hard at solving it. However there was nothing they could do for us and were sorry for our inconvenience. They did tell me that the issue occured when members of the party left the instance for longer than 30-45 minutes and if this was avoided then there would be no problems. I then pointed out that none of us had left the instance and that there were 3 people who had run the instance before it reset. Therefore what I was in effect being told was the instance had not actually reset. The CM said they would add this additional info to the database.

I had read on the interwebs that raid reset information was displaying incorrectly but I hadn't thought that this applied to heroics and admittedly hadn't read the detail. Considering that heroics have a raid ID I guess I should have realised they came under the same 'jurisdiction'.

Here's hoping Blizz fix the issue soon.

No comments: