Throne of Storms and other instances bug

[Chillor]

<p>These instances have been bugged for 2 weeks now. Last night tried killing Modfrost multiple times and with the same result. Get him to like 30% and it freezes and then its a 24 man disconnect. This is not the only encounter this happens on. Can't believe SOE has not fixed this issue as yet as it hinders Guild's progression!</p>

[Darkelfelin]

<p>/bump</p><p>Could we have a feedback on this issue please?</p><p>We can't play normally in raid due to whole instances crashing just in the middle of fights... And when I say "middle", it happens sometimes when nameds are at 93% HP or 20%...</p><p>Seems clear to us that one or several AEs are making this problem occur. Two encounters (maybe more but how could we know...) are causing that problem : Arch-Magistor Modrfrost in "Throne of Storms : Halls of Legend" and second named in "Temple of Rallos Zek : Foundations of Stone" (Prime-Curator Undr?)<span style="font-size: small;"><span style="font-family: arial,helvetica,sans-serif;">. Would they by coincidence share an AE?</span></span></p><p>This is extremely aggravating. As soon as it happens, there is nothing we can do for as long as <em><span style="text-decoration: underline;"><strong>15</strong></span></em> minutes, right in the middle of guild events that many of us have had to plan days in advance... 24 people stuck, you cant even log another character, nothing. This has become a moment when some of us wonder why they came back to the game, or wonder why they are still playing. So far, I've seen no answer or ETA on the adressing of the issue and we ressent this as a lack of respect. (I admit that I might have skipped an info about this problem but well... I read update notes, MotDs, I came here... saw nothing)</p><p>I would like to ask politely to persons in charge to take extremely strong and fast action to finally correct this. We have been granted 45 days "for free" and in fact we end up losing our evenings in unplayable raid instances for two weeks already <img src="/eq2/images/smilies/499fd50bc713bfcdf2ab5a23c00c2d62.gif" border="0" /></p>

[Kaszan]

<p><cite>Yerazankha@Storms wrote:</cite></p><blockquote><p>Seems clear to us that one or several AEs are making this problem occur. Two encounters (maybe more but how could we know...) are causing that problem : Arch-Magistor Modrfrost in "Throne of Storms : Halls of Legend" and second named in "Temple of Rallos Zek : Foundations of Stone" (Prime-Curator Undr?)<span style="font-size: small;"><span style="font-family: arial,helvetica,sans-serif;">. Would they by coincidence share an AE?</span></span></p></blockquote><p>We are experiencing crashing on these two mobs as well, its very distruptive and causes any chest in the zone not looted to vanish. Did make another thread about this, didn't notice this thread til now :p</p>

[Loranthala]

<p>Fix is on the way, no estimate when, but "soon" so... yeah.</p><p><a href="http://forums.station.sony.com/eq2/posts/list.m?topic_id=501253">http://forums.station.sony.com/eq2/...topic_id=501253</a></p>

[Gnorbert]

<p>I don't think that the bug being discussed in that thread you linked is the one this thread relates to.</p><p>As far as I can see this thread is about the 24man disconnects in x4 raid zones-my guild has experinced it on the 2nd name in Foundations and it's very annoying.</p><p>The thread you linked is about a bug where everyone frezzes up in an apparent lag spike but pets (or sometimes players) continue to auto for crazy dps leading to the boss dying during the "lag spike".</p><p>Obviously both need fixing and I'm mostly replying as a sneaky bump to this thread in the hope of getting a Dev response<img src="/eq2/images/smilies/3b63d1616c5dfcf29f8a7a031aaa7cad.gif" border="0" /></p><p>Edit; On the subject of the 24man disconnect bug-we've had it happen on zone in as well as during the trash clear between the 1st and 2nd names so I'm not sure it's linked to a specific AoE mobs are using.</p>

[Costa]

<p>We had a 12 man disconnect in ToFS last night and is the 1st time we've seen this happen in any raid zone. Annoyingly it happened after we had killed charm named and were getting ready to pull spider. Meant named we had just killed reset so we had to kill charm named again <img src="/eq2/images/smilies/9d71f0541cff0a302a0309c5079e8dee.gif" border="0" /></p>