[Dev1001] Strategy or Exploit

[Dreamer]

Regardless of what the devs think, I personally consider it an exploit and will never stay in a party that insists on doing it. I really wish they would treat them like local leves - you fail the leve, it's removed from your jounal.

[Viridiana]

Regardless of what the devs think, I personally consider it an exploit and will never stay in a party that insists on doing it. I really wish they would treat them like local leves - you fail the leve, it's removed from your jounal.

But that's missing the entire reason they allowed us to retry failed leves. If you disconnect, you fail; and that's BS. Rather than fix the underlying problem, they allowed us to retry failed leves, and we got the system we have now.

Personally, I'm fine with the system the way it is now, minus the whole disconnect = fail part. But, then I only get to play on weekends, so getting a total of four ranks during one weekend is fine by me. . .

[Dreamer]

But that's missing the entire reason they allowed us to retry failed leves. If you disconnect, you fail; and that's BS. Rather than fix the underlying problem, they allowed us to retry failed leves, and we got the system we have now.

Personally, I'm fine with the system the way it is now, minus the whole disconnect = fail part. But, then I only get to play on weekends, so getting a total of four ranks during one weekend is fine by me. . .

Even though I'm going to sound like a cold-hearted b****h here, I'm sorry, but connection problems are your problem, not SE's. If you get DC'd during a leve and you fail it, sure it sucks, but that kind of thing happens.

I've been dc'd during a leve and failed it before. I've been dc'd and died because of it. It sucks. But I don't expect the game to design it's systems around the possibility that it may happen.

[DurtiMonkeyToe]

Even though I'm going to sound like a cold-hearted b****h here, I'm sorry, but connection problems are your problem, not SE's. If you get DC'd during a leve and you fail it, sure it sucks, but that kind of thing happens.

I've been dc'd during a leve and failed it before. I've been dc'd and died because of it. It sucks. But I don't expect the game to design it's systems around the possibility that it may happen.

Then I guess it's my turn to sound like a cold-hearted a$$. It doesn't matter if it is connectivity issues or not, THIS IS NOT AN EXPLOIT. It doesn't matter if it is 'against your personal code of ethics' because the game developer's have stated as clear as day that this is not an exploit. You can consider it however you want, or call it anything you like, but doing so doesn't change the fact that this issue is BY DEFINITION not an exploit.

[Viridiana]

Even though I'm going to sound like a cold-hearted b****h here, I'm sorry, but connection problems are your problem, not SE's. If you get DC'd during a leve and you fail it, sure it sucks, but that kind of thing happens.

I've been dc'd during a leve and failed it before. I've been dc'd and died because of it. It sucks. But I don't expect the game to design it's systems around the possibility that it may happen.

I realize the connection issue is my problem. Note that I'm not complaining about disconnecting. That's on my end, it's my issue to solve, and so forth. What is a problem, that I will complain about, is automatically failing a leve for no reason as soon as I d/c. There's literally no reason for this that I can see. Nor is there a good reason it should take me ten minutes to get back online. Honestly, if disconnecting meant that I just logged right back in and went about my business, I wouldn't even give a **** that I disconnected. Instead, it means I automatically fail a leve and lose SP. Not "Hey, your time ran out while you were d/c'ed." Not, "Hey, that mob killed you while you stood there and auto-attacked." No, just a straight up failure for no **** reason. That's nothing more than crappy decision-making on SE's part. I'm not even gonna call it crappy coding, because I'm certain it's working as intended. The intention behind it is just plain wrong, though.