Mabar Event Closing After Oct 31st

[Loromir]

Except there is an exploit.

Dang....I never find out what exploits are until they shut things down. I guess, I'm just naive, I hadn't heard iof this.

[shibe]

Unfortunately, things changed. Sorry! We did want to announce the decision as soon as possible, though, to give people some time to get their signets between now and early Friday.



We'll let you know once we investigate further, but we do not currently expect Mabar to return this year.

I do not understand. Whats the point of closing it? It lags sometimes and it doesn't others. We can still get signets sometimes. I was looking forward to some of the new stuff you guys had for Mabar now I won't have time to get it. Now I have to wait for who knows how long to update all my stuff because I haven't had time this week to play. I planned on playing next week. This is your best festival I think you should reconsider closing it. At least let us know you will open it back up in a few weeks. I don't get it. Paying customers want to know more then the little sound bites we get once in a while.

[Xaenith]

I can't be the only one who finds this terribly amusing, can I?

[Phoenix-daBard]

The loss of slayers for the monster manual is very signifcant and drops mabar down on events for me. CC gives a ton of XP, great gear, and slayers for even more XP.

Sadly Mr Jibbers from the Cove is sadly absent from the MM. Rather annoying considering how many times I took him out.

[sephiroth1084]

Cordovan, someone in another thread suggested that a big part of the lag issue may be tied to instance i2049 (I believe), saying that their interpretation of why that instance has long been known to have a high incidence of lag is that it's the first instance people go into for a lot of things on the server: the Cannith crafting hall, a lot of raids, Mabar, and some other things...so it's getting the brunt of the load until it's full, at which point people get pushed into i2050 (or 1050 or whatever), etc... Since 49 is the one that fills first, and has so many disparate parts of the game all in there, it's most prone to lag during busy hours.

Is there any way to further compartmentalize the instancing across the game to better distribute this load? At the very least, find a way to wall off Mabar from the entire rest of the game, so people who aren't even interested in playing in the graveyard aren't having their game experience ruined as well. It's ridiculous that you (the Devs) are announcing the early closure of Mabar due to the forum outrage at the lag, when this same exact thing has happened every year we've had Mabar...the lag isn't new. It's not undocumented. Yet, we got the same laggy Mabar that we've had every year, without, as far as I can tell, any effort whatsoever to address this recurring problem. It's a rather prominent example of how Turbine has handled many other such things. It's frustrating, infuriating even.

Stop putting out the event if a solution hasn't be reached for the thing! Just stop.

[GeoffWatson]

Disappointing.

I've managed to get some signets and scales on two of my characters, but the other characters have suffered failures due to lag. As the opening times have slowed to approx 4-6 hours it is very unlikely I'll be able to get the tomes, cloaks, and wraps I was planning on getting (was about 2 hours for the first few days).

Geoff.

[EllisDee37]

Might as well just admit it Cordovan. You're closing it because of an exploit.

I'm guessing it's because you don't need to pull the levers (or even have anyone at any levers) to kill the dragon.

[Xaenith]

Cordovan, someone in another thread suggested that a big part of the lag issue may be tied to instance i2049 (I believe), saying that their interpretation of why that instance has long been known to have a high incidence of lag is that it's the first instance people go into for a lot of things on the server: the Cannith crafting hall, a lot of raids, Mabar, and some other things...so it's getting the brunt of the load until it's full, at which point people get pushed into i2050 (or 1050 or whatever), etc... Since 49 is the one that fills first, and has so many disparate parts of the game all in there, it's most prone to lag during busy hours.

Is there any way to further compartmentalize the instancing across the game to better distribute this load? At the very least, find a way to wall off Mabar from the entire rest of the game, so people who aren't even interested in playing in the graveyard aren't having their game experience ruined as well. It's ridiculous that you (the Devs) are announcing the early closure of Mabar due to the forum outrage at the lag, when this same exact thing has happened every year we've had Mabar...the lag isn't new. It's not undocumented. Yet, we got the same laggy Mabar that we've had every year, without, as far as I can tell, any effort whatsoever to address this recurring problem. It's a rather prominent example of how Turbine has handled many other such things. It's frustrating, infuriating even.

Stop putting out the event if a solution hasn't be reached for the thing! Just stop.

I have to agree with the people who suspect it is being closed because of an exploit. Makes no sense to close it just because of lag complaints.

[schelsullivan]

We've been fighting the "lag" bug or what ever every day so far, dedicating all our play time struggling through the problems in hopes of getting the tomes. Now the time invested so far feels like its going down the drain! Each of my toons has at least 1 signet, but you've just dashed my hopes of getting 2 more before its over! Unless theres a make up week coming soon, I'm going to feel really disappointed.

[Ryiah]

I'm guessing it's because you don't need to pull the levers (or even have anyone at any levers) to kill the dragon.

No, this one is more serious and involves obtaining multiple once per character items on the same character.

[FestusHood]

I'm guessing it's because you don't need to pull the levers (or even have anyone at any levers) to kill the dragon.

I think that's always been the case. The light just makes the dragon easier to kill. Not having the light on doesn't make it invulnerable. Sort of like dr. It's better if you can break it, but you don't have to.

[Darkrok]

What about those that haven't had (for whatever reason) a chance to get their signets? 11 days is a lot of time to lose potential signets from...

I'm not privy to Turbine's reasoning. Some people here have suggested that it's an exploit involved...honestly though it could just as easily be the tone on the forums. When you have 9 to 1 people in threads on the forums practically begging Turbine to shut down Mabar what do you think they're going to do? This is one time they can make their customers happy simple by shutting down a feature? That's a no-brainer for them. I think we can chalk this one up in the 'be careful what you wish for' category.

[Avenging_Angel]

This is strange.

Mabar was laggy last year. Mabar has always had performance issues, and yet you decided to push it out anyway. Now you decided to close it in advance to fix it? Why pull back now?

[Xaenith]

No, this one is more serious and involves obtaining multiple once per character items on the same character.

FWIW, I know some people tested and confirmed this bug when Mabar was on Lam.

[Ravand]

This is too bad. On one hand, the lag was fail-terrible on three of my seven runs this weekend, and there needs to be a fix. And by fail-terrible, I mean the toons couldn't even walk/cast/swing, and this was before the dragon appeared, AoEs were cast, or levers were pulled.

On the other hand, pulling the event and then not allowing a make up after the fix is disappointing. I farmed Mabar pretty hard this weekend (for the time I was able to play), but a lot of my guildies were taking advantage of the +25% XP weekend. This leaves those that wanted to participate, based on the published schedule, in the lurch.

[EllisDee37]

I think that's always been the case. The light just makes the dragon easier to kill. Not having the light on doesn't make it invulnerable. Sort of like dr. It's better if you can break it, but you don't have to.

I think you're right.

I suspect it's been this way ever since the "DR pass" (or whatever you want to call it) that I think went live with MotU. Another example is the ghostly skeletons in Delera's. They used to be virtually undamageable if you didn't break good dr; weapon damages always showed as yellow 0s. Now they just have like DR 5/good or something else trivial. Pretty sure this change went into effect with MotU, but not positive.

[Calleia]

if Mabar is not coming back this year and as not everyone got all day to farm (yeah, some people have a so called real-life. not very common but...) maybe you can change the fact of just getting one signet a day?

[portcityguy]

Why kill it Friday morning? It's not like you guys are gonna work on it over the weekend. Why not leave it up through Sunday night, and take it down early Monday morning when you come back to work?

[karl_k0ch]

This is bad news. I feel like I'm betatesting bananas.

Let's hope I'll be able to collect a tome on all toons I planned to do so.

[PNellesen]

Gotta say that, while I understand why it's being closed, and really can't disagree with the decision, I'm really disappointed. I've been trying since Thursday to get successful 26-30 runs in, and have so far only been able to do one (out of maybe 10 or so attempts, all the fails due to lag.) Otoh, my <25 characters have all been able to have successful runs, and 3 of them have tomes already.

I'll go ahead and ask even though we know the answer - how about make the signets or the tomes BtA? I'm confident I can get multiple <20 runs in before the 31st. I'm not at all confident I can get >=20 (and ESPECIALLY >=26) runs in...