Warning for "Grief" Tactics?!

[Denji]

My point still stands. No one should be held hostage in an instance. If they want to stay, they will stay. If they want to leave then they are free to leave. All is as it should be.

And you can and you're not held hostage. You just agree to a 30 minute timeout which, to me, is more than reasonable because if it weren't there people would just ditch any dungeon they don't want to do.

If you don't want to be placed in an instance you don't want to do then don't do roulette. The bonuses they provide are exactly that - a bonus. An incentive to run content you may not ordinarily want to run.

[Vahlnir]

And you can and you're not held hostage. You just agree to a 30 minute timeout which, to me, is more than reasonable because if it weren't there people would just ditch any dungeon they don't want to do.

If you don't want to be placed in an instance you don't want to do then don't do roulette. The bonuses they provide are exactly that - a bonus. An incentive to run content you may not ordinarily want to run.

I agree that people should accept what they are given. I'm a pretty regular roulette user, by the way, who almost never leaves. But I also defend everyone's right to leave if they don't want to be there, even if it's a bit of a jerk move in some cases. There doesn't need to be more restrictions or punishments beyond the 30 minute debuff is all I've been trying to say.

[TaleraRistain]

Did you consider if it was the DC thing, you got a warning because someone thought you did it intentionally, reported you, and SE couldn't prove you didn't? They couldn't prove you did, so they couldn't make it a ban but also couldn't prove you didn't so warned you to be careful in the future.

If it's the healing thing, is your party wiping because you aren't healing or raising people? If so, then you're not doing your job for whatever you think your valid reasons are and you're intentionally preventing the party from progressing by doing so. Though I would think something at that level would get a ban.

Either way, it doesn't seem that you intend to take this as an opportunity to reflect on your actions but instead attack all the phantom "snowflakes" you think are doing you wrong.

It shows a very serious lack of maturity.

[Iscah]

If it's the healing thing, is your party wiping because you aren't healing or raising people? If so, then you're not doing your job for whatever you think your valid reasons are and you're intentionally preventing the party from progressing by doing so.

Even if it isn't causing a wipe, it can be a miserable thing to see that the healer is not under pressure and has decided to attack-attack-attack while leaving you dead on the floor. Obviously there are variables like if the fight is nearly over or people need healing, or if it's getting close to the one-minute Swiftcast recharge timer, but it's still not much fun to be stuck there unable to contribute.

(And am I correct in thinking that in any case, it would tend to overall be a DPS increase if the healer sacrifices three turns now to hardcast Raise, allowing the DPS to be alive and attacking three turns earlier than if they had to wait the whole minute to be revived?)

Personally I'd rather revive them sooner, though for a DPS I'm less likely to put myself at risk to complete a cast. They got the "casting Raise" macro announcement; they know I tried. There's also no harm in raising them at the end of the fight – if they know better, they'll reject it and take themselves back to the start of the dungeon anyway; if they don't, they'll accept it and the weakness will probably have worn off by the time they need to do anything important.

[Driavna]

Did you consider if it was the DC thing, you got a warning because someone thought you did it intentionally, reported you, and SE couldn't prove you didn't? They couldn't prove you did, so they couldn't make it a ban but also couldn't prove you didn't so warned you to be careful in the future.

If it's the healing thing, is your party wiping because you aren't healing or raising people? If so, then you're not doing your job for whatever you think your valid reasons are and you're intentionally preventing the party from progressing by doing so. Though I would think something at that level would get a ban.

Either way, it doesn't seem that you intend to take this as an opportunity to reflect on your actions but instead attack all the phantom "snowflakes" you think are doing you wrong.

It shows a very serious lack of maturity.

First time always is going to be a warning unless it was something awful.

[Vidu]

I agree that people should accept what they are given. I'm a pretty regular roulette user, by the way, who almost never leaves. But I also defend everyone's right to leave if they don't want to be there, even if it's a bit of a jerk move in some cases. There doesn't need to be more restrictions or punishments beyond the 30 minute debuff is all I've been trying to say.

While I agree with this general statement, looking at the timeline of this "case" they didnt just leave the dungeon - and didnt communicate with their party about their internet problems. So for the party it might have looked like they got a dungeon they didnt want to do, so they tried to get themself kicked instead of taking the penalty. When that didnt work, they left. At least that would have been an assumption I could have reached after someone DC'd, then lost their tankstance in mysterious ways and wasnt able to tank (anymore) and ultimately left the dungeon. I wouldnt report anyone over it, but my first guess would be "Ah, someone didnt want to do this and didnt want the penalty, so they tried everything to get kicked" - specially if they didnt comment on having a problem with their internet connection. And ofc, no one needs to disclose things like that (though it doesnt seem like terrible private information...), but everyone needs to be aware that if they dont say anything at all, people will be left to guess and come up with their own explantions.

[Arazehl]

My point still stands. No one should be held hostage in an instance. If they want to stay, they will stay. If they want to leave then they are free to leave. All is as it should be.

I have a better idea. Don't queue up to begin with if you have a chance of not staying or you plan on ditching the instance. Problem solved.

[TaleraRistain]

Even if it isn't causing a wipe, it can be a miserable thing to see that the healer is not under pressure and has decided to attack-attack-attack while leaving you dead on the floor. Obviously there are variables like if the fight is nearly over or people need healing, or if it's getting close to the one-minute Swiftcast recharge timer, but it's still not much fun to be stuck there unable to contribute.

(And am I correct in thinking that in any case, it would tend to overall be a DPS increase if the healer sacrifices three turns now to hardcast Raise, allowing the DPS to be alive and attacking three turns earlier than if they had to wait the whole minute to be revived?)

Personally I'd rather revive them sooner, though for a DPS I'm less likely to put myself at risk to complete a cast. They got the "casting Raise" macro announcement; they know I tried. There's also no harm in raising them at the end of the fight – if they know better, they'll reject it and take themselves back to the start of the dungeon anyway; if they don't, they'll accept it and the weakness will probably have worn off by the time they need to do anything important.

Agreed. I very rarely hard cast. Mechanics often don't allow it. If it's not the end of the fight and SC is down, I try to give a quick "SC down, get you when I can" in chat so they know I'm not just leaving them there for no reason. Or if someone at the end of the fight doesn't revive, I'll tell them to go ahead and revive to avoid the weakness debuff. If they don't want to do that and stay there, I just pop a raise on them and continue on. I think a lot of healers who get touchy about that are letting their ego get in the way. I honestly don't care if someone's taken avoidable damage. Things happen. I just heal them and raise them and dps around those duties. That's why I'm there.

[Denji]

You are under no obligation to explain why you can't swiftcast/raise someone and as someone who has had to have a GM intervene or at the very least review my tickets they seemed to imply that they look at everything from chat to skills used and even things like you and your party's health, buffs and debuffs.

I am firm in my belief that nobody has gotten in trouble for not hard-raising someone and anyone who claims they have is probably lying as a cover for the thing they -had- been given a warning/tempban for.

In addition I suspect the "duty recorder" feature is something that always passively records a player's duty whether they have it set to do so or not and is a tool that has always existed for GMs that was only released to players later on; which also is likely how they are able to investigate so thoroughly. My supposition is that it is quite simple to covert what is recorded into something akin to plain text that simply indicates a player's position and what actions they are currently taking which honestly is trivial to store and compress in comparison to, say, a video.

[Imora]

If you were in the EU you'd be able to get them to tell you what happened using a law that requires them to provide transparency.

Unfortunately, you're on excalibur which tells me you're not.