Veeshan's Peak Design Re-tuning Criticism/Suggestions - Page 23

Metran · 02-22-2008, 04:43 PM

Seemed that way when people were complaining that the trash and named had respawned in the WW channels. Although the timers were still showing what they were pre-42, zoning in appeared to change that to a new 9 day instance with everything up.

At least that was the case on a few servers, if not all on the day GU42 went live, don't know if they fixed that in a hotfix afterwards, for those that had yet to zone in.

Sudden · 02-22-2008, 04:45 PM

We were clear through Milyex like I said on the 1st night inside vp like normal. The GU went live the next morning. We spent a few days getting our heroic epics figured out and completed. Then when we walked back into our zone with 4 days remaining on the instance the first mob to greet us was the drakenear the entrance. We spent the next few days figuring out nexona till our instance booted us and we got a new one. Sooo. if there were somehow some servers or guilds that didn't get the mobs reset in thier existing instance they know someone or something shadey was going on.

Choadley · 02-22-2008, 04:54 PM

I had heard resets happened, like Brekon said. Our instance was ended two nights before the LU hit, so we were not affected. Is it possible that if you were cleared in to the second wing already, the door remained open while all mobs were repopped?

Gaige · 02-22-2008, 04:57 PM

The easiest way to confirm is to look at mythical disco dates. If the ones that require Nexona/Druushk were last, then something is screwy. /shrug

TheEasternking · 02-22-2008, 05:05 PM

Quote:

Originally Posted by Deludar

wrong wrong wrong wow thats wrong

This is not wrong at all, ...we had both first and 2nd wing cleared prior to gu42 hitting us on thursday (day after us servers), and upon zone in we got a 9day message and everything in the zone had repopped. yet our timers on the persistant tab stayed the same from when we had actually opened the zone till when we could reset.
Everyone got a re-popped zone, they just didnt change the timers on the tabs.

Sudden · 02-22-2008, 05:07 PM

Quote:

Originally Posted by Choadley

I had heard resets happened, like Brekon said. Our instance was ended two nights before the LU hit, so we were not affected. Is it possible that if you were cleared in to the second wing already, the door remained open while all mobs were repopped?

The doors were definately back up.

TheEasternking · 02-22-2008, 05:09 PM

Quote:

Originally Posted by Gaige

I'm under the impression they feel justified making Nexona and Druusk harder because they both reward epics and they block the rest of the mobs that also drop epics, thus justifying why they were remade to be so hard despite having the same shitty loot and being on the first floor.

However I wholeheartedly agree with you and its just a stupid way to block the majority of raiders from their mythicals.

Aye, I agree changing mobs for updates to mythical weapons is fine, to a point, but id at least expected to have them tested and in place before they added the actual quests, guess soe as usual werent expecting people to be at update steps for the mythical version inside 2-3days of gu going live.

what i dont agree with is simply changing content after its been farmed to death b/cos all of a sudden people are bored. new content pls not old stuff beefed up.

Leorrasanoob · 02-22-2008, 05:15 PM

the first mythical discovered was fury I think which means Druushk was killed before any of the others.

Slippery · 02-22-2008, 05:19 PM

We killed Druushk first to get the Fury Mythical but that really had little to do with anything. Even if we killed Nexona first Fury still would have been the first Mythical as our inquis and necro where stuck on other things.

Edit: You will also find the Disco's in order of the zone getting cleared. For us at least, and we got the first and majority of them. /shrug

Leorrasanoob · 02-22-2008, 05:19 PM

As far as i know everyone had VP reset and the timers were what screwed some folks. A few guilds seemed prepared for this to happen and had there timers ready for this, could just be they assumed everything would be reset with the update.