Mystic Lake 2 Anyone?

[Supernova17]

Looks like the cap has either been raised to 100 to open a new Mystic Lake or ML2 is no more. Fortitude and Chaotic Legion fighting over the Matron plus all the random people in the zone = 68 players in zone. End result of this change: 15 Minute Dinner Break!!! <img src="http://img228.imageshack.us/img228/7473/eq2000467aqd9.jpg"> <img src="http://img228.imageshack.us/img228/3451/eq2000468lf9.jpg"> <div></div>

[Kriddle Kraddle]

<DIV>Yeah GG sony. Three guilds kill the mob twice and then Sony says hey lets fix this so that every guild now has at least 1 or 2 other guilds standing on top of them. This mob takes 20 min per pull as it is and now its taking us 40min to an hour per pull. Thanks Sony for your awesome forsight even though it was pointed out to you in previous posts that this would happen.</DIV>

[Supernova17]

Oh, this crash caused a domino effect across the server too! Lyceum, Deathtoll, CT, RE and some of the KoS overland zones chain crashed for the same duration <span>:smileyvery-happy:</span> <div></div>

[pera]

Was the multiple instances of the zones actualy changed to not allow multiple versions, or is this just a bug?  I didnt notice anything int he patch notes off had about this.<div></div>

[Snarks]

Intentional change, no contested is meant to be killed twiceNot saying I agree with it, but thats the reasonit wasn't in the patch notes<div></div>

[Petgroup]

<div><blockquote><hr>snarkteeth wrote:Intentional change, no contested is meant to be killed twiceNot saying I agree with it, but thats the reasonit wasn't in the patch notes<div></div><hr></blockquote>Yet they will leave Terrortarantula and Sinking Sands 2 untouched as its been since KoS.As silly and pointless as it is, some contested mobs spawn in Thundering Steppes and Nek Forest, both of which have been around since day 1, left untouched.Incoming instance version soon <span>:smileysad:</span></div>

[Schmoogles]

<P>I don't understand why they changed it now, when they clearly knew about this when TFD came out.  Nothing against the guilds who have beaten Matron but why did it take 2 guilds to beat it in both worlds to get it changed? (not sure if the 3rd beat it in ML2 or not) Many posts about people talking about both Mystic Lakes many threads that got locked that referred to Mystic Lake 2.   Why didn't you change the zone then?  Did you really think someone would not kill this mob and you totally forgot about having two Mystic Lakes? You figured hey no one will kill this mob when both zones are up. Once someone kills it everyone will be sick of Mystic Lake and we will hot fix the zone to where it can hold 100 people now, we just solved our problem of major lag in the zone when we first release TFD. </P> <P>Edit: I know the reason they changed I'm just saying why 3 months after it came out?</P><p>Message Edited by Schmoogles on <span class=date_text>09-15-2006</span> <span class=time_text>11:40 PM</span>

[Toxi]

We all know the reason for the change.  It was do to the uproar by a few in the community once it happened two times in a row on such a pinnacle mob.  I doubt they will change the mobs in zones nobody cared about.  The ideal solution would take a bit of programming finesse.  Since its not reasonable to lock guild out of a contested/quested instance I imagine the simplest way would be to break the encounter if the same guild tried to again engage the same epic encounter they just very recently destroyed.. Even then I doubt this may happen soon.  We may all be stuck in very crowded zones sometime in the future.  By the way, grats SD on your worldwide first and second.  Now go beat the nightblood and shut every one up. <span>:smileyvery-happy:Toxu.Najena</span><div></div>

[Killerbee3000]

the funny thing is, that its not the first time that contested's can be up multiple times. terrorantula anyone?i dont really understand why they cant just prevent contested mobs from spawning in the second version of the zones, i.e. just dont let matron spawn in mystic lake 2 or no big fat hairy spider in ss 2 if they dont want anyone to be able to get around respawn timers and kill it twice as often as intended.<div></div>

[vinterskugge]

<DIV>Well you obviously can't have uber contested loot like the necklace from princes or the round shield from Hurri or anything from MO drop too often, they have to prevent it entering the game at such a rate.</DIV> <DIV> </DIV> <DIV>Why does it even matter when they've trivialised fabled so much?  Look at how fast they've let relic enter the world, 2 contesteds instead of one will not unbalance anything.</DIV>

[KazzySoJaz]

<BR> <BLOCKQUOTE> <HR> vinterskugge wrote:<BR> <DIV>Well you obviously can't have uber contested loot like the necklace from princes or the round shield from Hurri or anything from MO drop too often, they have to prevent it entering the game at such a rate.</DIV> <DIV> </DIV> <DIV>Why does it even matter when they've trivialised fabled so much?  Look at how fast they've let relic enter the world, 2 contesteds instead of one will not unbalance anything.</DIV><BR> <HR> </BLOCKQUOTE> <P><BR>Amen to the relic thing, saw 2 leather skullcaps drop back to back recently...</P> <P> </P> <P>As for instancing this encounter, meh, princes is hell too with 3 guilds waiting to kill it.  I say they just fix whatever it is that causes immense lag when 24x3 + people are in a zone...  </P>

[Gertack_v2]

Guess it makes too much sense to just not have the contestable spawn in a 2, 3 instance instead of getting rid of the instance.<div></div>

[Dignast]

<DIV>Mystic Lake isnt a big enough zone to harbor a contested mob without instancing imo.  I feel bad for all the guilds going after this mob that now have to deal with multiple raid forces in zone.</DIV>

[Luca Blight]

<DIV>ya Friday night we had horrible button lag with 2 guilds attempting. It was probably our worse attempts at the encounter in the last few days. Just dont think that zone was meant for over 50 people to be in it exping/questing.</DIV> <DIV> </DIV>

[Dogm]

but as has been said before, a contested mob should not spawn in more then one instance at a time (kinda takes the contested out of it).

[MexStrat]

I agree,  Gratz to the guilds the took advantage of SOEs Lack of concern over this.  And a great big 'Shame on you' to the SOE community leadership that supposedly watch these forums and listen to the player base when they site concerns, for completely ignoring all the posts that pointed out this issues multiple times. Personally, I either way works for me multiple contested or not.  My concern is with the complete lack of consistency,   Some contesteds are able to have multiple instances, some don't.  Some have multiple instances for a week then get changed to a single instance.   Please SOE make up your mind and stick to your decision.  <div></div>

[Balerius]

<P>Seems to me that there is a simple solution.</P> <P>Allow multiple instances of the zone to open like before:  at 60 players.</P> <P>Allow multiple Matrons just like before.</P> <P><STRONG>BUT</STRONG>...When any <EM><U>one</U></EM> Matron is killed (in any Mystic Lakes instance that's open), despawn <EM><U>all</U></EM> Matrons in any other Mystic Lake zone.</P> <P>This would allow multiple guilds to attempt kills of the Matron without the inordinate lag and long wait times but prevent the "farming" in multiple Mystic Lake instances that SoE appears to be concerned with.</P>

[Nib]

<div></div>I don't see the point in removing it, who actually kills Matron for loot? That's what relic pickup raids are for. <div></div><p>Message Edited by wyoung on <span class=date_text>09-17-2006</span> <span class=time_text>10:18 AM</span>

[Rutabegah]

What I don't understand is why you posted that enormous pictures, thus breaking the board with horizontal scrolling.  You could have just easily stated that you got knocked to character select and the zone was unavailable for a long time.