Please STOP making changes that directly affect our gameplay to only be discovered AFTER people waste their time. NCSoft has got to be one of the most irresponsible game developers ever.
Just for those who do not know, NCSoft has changed it ONCE AGAIN, without telling anyone, so you CANNOT relog into Frintezza or Valakas lair upon critical error, loss of internet or anything. You are sent back to town. The other bosses were not adjusted. YOU SHOULD ALERT THE PLAYER BASE WHEN YOU MAKE SUCH CHANGES, its not like changing a boss spawn thats been the same for 4 chronicles, its directly impacting gameplay on an already crit prone buggy client.
Ok im not gonna tell you to relax because I understand where your coming from.
I am however gonna comment on the "already crit prone buggy client" part.
I have not had a crit error in at least a year. Even when i changed my computer about 2 months ago I still havent critted yet. I believe you when you say you crit often im not saying your lying im just saying maybe its not NCSofts fault?
Anyways have a donught and get some fresh air, Im sure crit errors wont affect your mood so much after.
According to the updates this was a change made in Chronicle 5. If you weren't teleported back to town previously then this has actually been a bug which they've now fixed.
If a player is disconnected or restarts while in battle with Antharas, Zaken, Baium, Anakim, Lilith, Valakas, or Frintezza their character will be transported to the nearest town. If the player disconnection is caused by a server crash, the player will not be returned to town upon login if they reconnect within 30 minutes.
According to the updates this was a change made in Chronicle 5. If you weren't teleported back to town previously then this has actually been a bug which they've now fixed.
If a player is disconnected or restarts while in battle with Antharas, Zaken, Baium, Anakim, Lilith, Valakas, or Frintezza their character will be transported to the nearest town. If the player disconnection is caused by a server crash, the player will not be returned to town upon login if they reconnect within 30 minutes.
its stupid cause those are mass port ins.
People get mass d/c on port ins, lose half of their raid parties which took a long time to get to the raid spot.
Ncsoft needs to remove it, cause its not fair to the players, who are raiding at the time.
Agreed, but it also prevents people from being able to camp them. If they added this kind of thing to the Ant Queen you'd see a lot more "legitimate" Ant Queen raids. I guess they're only thinking of you!
According to the updates this was a change made in Chronicle 5. If you weren't teleported back to town previously then this has actually been a bug which they've now fixed.
Well, when we did Valakas raid a while ago, I dc'd and logged back in inside. When we did Antharas raid and I dc'd, I reappeared in Giran. So whatever they decided on, it was not 100% consistent.
Anyway, the good old way "log back in within 15 minutes and you reappear in the lair, after that you reappear in town" seems best to me. On these huge raids, people WILL dc, it's just the way the game is. And when you lose half the ressers on a Valakas raid, the whole 100+ ppl raid is doomed just because of a stupid brain **** the devs had. It makes people ... angry when the boss is 2/3 down and you realize you will not be able to make it just because too many people dc'd and cannot come back. Especially when people died a lot, and now it was all for nothing.
It is a BUG that you get ported back to town when you DC.. maybe not in the sense of programming bug, but someone's logic and common sense has been fried.. <looks at NC Korea> grrrrrrrrrrrrrrrrrrrrrrr and.... GRRRRRRRRR!!
+1 ******ed
At least they could come with some kind of justification for this ******ed change so we can mock it even more. Thanks for ruining our raids! :)
If only someone would invent a "[censored] Prevention Chip" - DPC - and put it in everyones brain, we could maybe avoid [censored] decisions lol Of course it would have to be linked to my brains logic to decide when the DPC would fire 10 000 volts through your brain :)
Ok im not gonna tell you to relax because I understand where your coming from.
I am however gonna comment on the "already crit prone buggy client" part.
I have not had a crit error in at least a year. Even when i changed my computer about 2 months ago I still havent critted yet. I believe you when you say you crit often im not saying your lying im just saying maybe its not NCSofts fault?
Anyways have a donught and get some fresh air, Im sure crit errors wont affect your mood so much after.
Bye
I bet any money never siege lol
Oh and whoever quoted that change about the DC, they implemented a patch in interlude to make it so u CAN be logged out ofr like 10-15 mins
It was like this at the start of Interlude IIRC. Then they changed it so you could log back into the raid again.. and now it's back to ******ed again.. what's up?!
we really need a response from someone on what kinda logic was put into this. It is very short minded especially considering the limited range of live GM support we receive in game as is. Why would you implement changes, WITHOUT alerting us, that have a major impact on gameplay and planning.
Sigh. I said it back when it was like this before, and I'm saying it again now. STUPIDEST IDEA EVER. EVAH! Thrown back to town after a relog/crit is ******ED.
Yep this is just bad thinking on their part and I honestly don't see what was wrong with the old set up..
"log back in within 15 minutes and you reappear in the lair, after that you reappear in town" is pretty fair imo
btw some minus points for the Dev's who failed to mention this in the maintenance notes when the change was applied as that's just bad form when implementing a change with so much consequences for their player base
The crit error thing is kinda odd. I play with 2 people who do it a lot, like prob'ly once per day (they both run -_- instead of the real client at least some of the time).
It almost never happens to me in lin2, but used to happen about 1 in 6 times when I'd alt-tab in WoW. But I'm not particularly good at computer maintenance or anything, and in the past I quit lin2 cuz I couldn't easily get it to run right.
Other guys I play with don't seem to ever crit error, either. And a lot of times some one will say on vent they're getting bad lag, yet no one else is (or sometimes everyone is).
So on the one hand, if a problem isn't happening to every player, you might say it must be the players' computers' fault. But on the other hand, if you consider the customers' experience, nothing sucks worse than getting crit error or DC when you're wanting to play.
Penalizing a customer for something when they're already ****** is really bad practice. Better to risk people "exploiting" the bosses than to send them back to town.
As a grumpy customer, I've got 3 or 4 other mmogs installed on my computer, just begging to be resubscribed instead of lin2.
I can't find the reference to the patch that re-enabled the log-out-for-15-minutes ability, either. Are you sure this was a patch and simply not an observation, or wishful thinking?
Better to risk people "exploiting" the bosses than to send them back to town.
This combined with bosses all being upgraded in difficulty will already degrade raiding even further.
I understand the bosses were no longer fun to Koreans who kill them with 200 people in less than an hour, or high powered alliances who've done them 300 times.
But this isn't Korea, and we all can't be in the top clan. Bad enough getting people together, fighting off farmers, PvPing other alliances, overcoming the boss. Then have a partyworth DC and have to call it.
Pardon my emo-ness. But its just one more straw thats about to break the back of this game.
Realise, though, that it doesn't matter what we want or how we play. If Korea does something, we receive the same code, just (usually) in English.
If Korea decided that Archers now have to stand still to reload their bows... we'll be standing still to reload our bows.
As said before, though, this *seems* to now be "working as intended", whereas the previous manner, with logging right back into the fight, wasn't. I'm sure, eventually, a red name will comment on it and let us know whether or not it is or isn't for sure.
Though, really, it's fairly par for the course. Have we ever been able to dissuade the Devs from doing something they were planning on doing? Nope... in fact, in that interview posted a few months back, they even said that they had considered getting rid of alliances entirely, but found that the communication channel it provided was simply too useful, but left in all their other relevant changes (increase in clan size, decrease in clan numbers allowed to an alliance, OL buffs to Clan-only, etc etc.)
Had they gone through with it completely, it would be a rather different game.
it would be nice to see an official reply to this issue seeing the huge impact it has on the players that participate on epic raids and the lack of any form of communication is kinda bad
it would be nice to see an official reply to this issue seeing the huge impact it has on the players that participate on epic raids and the lack of any form of communication is kinda bad
heh D/C's and criterrors? o.O i can 2-3box when massporting into raids and sieges and not get a single extra spike of lag apart from what the massive ammount of people do to my comp already as it is, lol. My machine is infact more prone to d/c and criterror when i'm only running a single client during normal everyday gameplay, hahah >.<
The only time i had issues with multiboxing 2 buffers on my butt was the other week.. a freaking bluescreen in xp pro!! >.<
Ferst I even sent a pm to Alyra on this to no avail, it's kinda funny/sad as all sides on our server are severly impacted by this and we all want to see it resolved.