ML 4 part II Wed 21.4 17:30cet stygia

[Farlon]

Plan is to run 4.2, 4,7, 4.8 and 4.10. Need minimum of 7fg or raid will be postponed to later date. Bg loot and lotto will be held after 4.10

pre-reqs 4.1 4.3 4.4 4.5 4.6 4.9 (not having em doesn't prevent you from getting those nasty 4.2 and 4.8 out of the way)

IMPORTANT: If you join the raid just to avoid doing 4.2 later on, don't log right after it. We'll be doing 4.8 right after it which requires drop from 4.2

Spam your alliance/friends and every random people you meet and start it today to ensure we have enough people to get this out of the way .

Raid moved to thursday at same time due dragon raid on wed, could some moderator change the topic to Thu 22.4

 

[Zapsi]

People who work normal hours not welcome :/

 

[Farlon]

Doing 4.2 takes good amount of time. Join late if you must. Just keep in mind that there won't be a raid at all if enough people don't showup on time.

If you can't showup on time study the Stygia/LoA area a bit we are not going to pick you up you have to find your own way to the encounter.

 

[Karmatika]

postponed? its 17.30 cet didnt see any /as spam nor do i see a zerg anywhere in toa :O

 

[Munson]

Raid moved to thursday at same time due dragon raid on wed, could some moderator change the topic to Thu 22.4

Yes.

 

[BigBlackClock]

Bumping because the raid is today Thursday , 17:30 CET .

 

[Farlon]

Goodjob everyone, that's was closest to succeed 4.2 run I have been on so far. Would I have pulled the mob out of fos on first try, insteady of trying to reclaim fort2 after fort2 and fort3 insta popped(and in the progress prolly make fg that wiped in fort3 since fort2 popped bit later lose the encounter), most people would prolly have gotten the encounter.

I suppose there is no point in trying unless we can get 100+ people to do this with pure force of zerg or be fortunate enough to don't have any fort pop on us or some fort to bug like fort2 did at the end(labourers kept popping on fort that was fully on fire even tho main zerg was clearing em out for 20-30minutes).

As for me I will be content to wait for 1.68 patch to fix this this problem before trying to organize another ml4 raid. Thanks for people for staying after failed attempt on 4.2 and completing the rest of the raid for those that already had 4.2 and 4.8 instead of leaving.