16 replies to this topic

[OsirisOmega]

Yep, doing the same thing as last week again... Reservation has been cancelled.

[LuxiLux]

anyone GM wanna respond to this?

[asayuu]

Valk server right? There is a huge mob of people in the place... even me dual clienting.

[Jyunosayshi]

Let us in T.T

[Ralis]

I can only assume it's because there are too many people in the instance.

And if that's correct, another reason why the cooldown needs to be extended.

[Dl2agon]

no ralis it even happens when no one is there you can be at hazy at 4am with no one in front and not get in

[Ralis]

Not in my case, I have no problem getting in at night...

[Dl2agon]

well you are a very lucky man last time hazy broke no matter what time it was how many were there you could not get in

[Jyunosayshi]

We waited an hour and couldn't get in. Then a party after us came and got in somehow. Waited another hr. Kept canceling our reservation. Then everyone just gave up >.<

[Ralis]

Yep, I waited 45 minutes to get in this time.

[OsirisOmega]

I think the problem is that the instance creation isn't infinite. I think it caps out for the server after so many are created, and then it fizzles and only spits one out every now and again. It seems to break until the server is rebooted, and I think it only made it this far this week because the memorial dungeon and eden group servers were rebooted wednesday night. It'll probably remain down until the server is restarted again

[asayuu]

So we need to find a way to lower the instance creations... [or increase the amount of zone resets]

1- Restrict it to parties of at least 2 people.
2- Put the spawn of "Dragon" only after islands #57 [therefore, people DOING THE QUEST will need to backtrack to find Loki, and spend more time in the instance]
3- [the easiest IMO] make an automatic/manual GM restart of the MF zone in a fixed time every day or every two days.

Edited by asayuu, 14 January 2012 - 07:06 AM.

[iiNote]

Seriously.. something has to be done about this. I spent an hour and a half waiting on that bridge and it never happened...

[LuxiLux]

So we need to find a way to lower the instance creations... [or increase the amount of zone resets]

1- Restrict it to parties of at least 2 people.
2- Put the spawn of "Dragon" only after islands #57 [therefore, people DOING THE QUEST will need to backtrack to find Loki, and spend more time in the instance]
3- [the easiest IMO] make an automatic/manual GM restart of the MF zone in a fixed time every day or every two days.

1- minimum party requirement will not slow anybody down. You can stick a level 1 novice inside and it will still count. The only thing it will accomplish is forcing farmers to log an extra account.

2- Pointless. It would take less than 1 minute to pop a mysterious seed, and walk back to #56. The amount of people farming the dragon is the majority, while the people doing the quest is the minority. Why should we deter people who've never done the quest, when it's the people farming the dragon creating the absurd amount of instances?

3- no comment

[asayuu]

*yawn*... Well, the 3-hour cooldown must become a real cooldown then... To force farmers to use their alts to kill instead of using a main killer and only use the alts to open the gate. It will not deter people like Cerulean with over 20 150/50 characters, but at least will delay few people.

I'm not sure if lowering OCA drop would reduce or increase the amount of people doing the quest. But removing it at all would make the instance useless... As all the others except ET. [If someone says "SS" I answer with "Cat Ear Beret"]. Remember finishing the instance gives NO REWARDS AT ALL?

By the way... If the person is farming dragons, they don't need to go to Loki.

[LuxiLux]

By the way... If the person is farming dragons, they don't need to go to Loki.

that was a statement on how easy it is to walk through 56 islands, which was a response to #2.

[OsirisOmega]

I think the automatic memorial dungeon close and restart of their servers is probably the best option atm. I wonder if it's possible to set something up like that, though it'd be hard to correlate with people all over the server being in different instances.