Guild Wars 2

Is this working as intended to still be punished even though you’ve reconnected and continue playing? I was punished regardless even though I had got back in.

This is after a computer crash, and logging back in into the match.

Yup its for real. Personally I think you rejoin and complete match there should be no penalty. Meanwhile someone sits afk entire match and gets off scot-free smh

If you’re gone for more than 2 minutes, you get dishonour. I think it’s working as intended and it’s fair.

It sucks for you, but it also sucks for your team if you do disconnect. 2 minutes is a long time and can easily be the difference in a match. It may or may not be your fault that you DC, but it’s definitely not your team’s fault. I don’t think they should be punished for it. (Edit: and of course somebody does need to be punished, or else people would leave matches to save pips with no consequence)

As for AFKs… Yeah, that part is broken. The report system needs to be able to deal with that more appropriately (but somehow still prevent abuse).

If you are gone for more than 2 mins you should get dishonor. That is a total of 360 points for 3 nodes, plus deaths, plus any map mechanics that were on the line. The other team could easily put the match out of reach in that time. If they can’t put it away, do you really think you should get points for being carried to a win?

Faux Play.6104:

do you really think you should get points for being carried to a win?

This isn’t about receiving points but receiving dishonor.

Jessie.5379:

Faux Play.6104:

do you really think you should get points for being carried to a win?

This isn’t about receiving points but receiving dishonor.

You possibly ruined a match. You deserved the dishonor. Even smaller times than 2min can ruin matches already, so 2min is a very generous time already.
And the dishonor is only like 20min unless it happens all the time to you, then it grows exponentially.

Malediktus.3740:

Jessie.5379:

Faux Play.6104:

do you really think you should get points for being carried to a win?

This isn’t about receiving points but receiving dishonor.

You possibly ruined a match. You deserved the dishonor. Even smaller times than 2min can ruin matches already, so 2min is a very generous time already.
And the dishonor is only like 20min unless it happens all the time to you, then it grows exponentially.

Analogy: Heard the difference between car collisions and car accidents? A collision doesn’t denote guilt yet while an accident denotes there is no guilt.

It’s completely reasonable to not receive pips or even lose a pip for being gone. But receiving dishonor on an first offense it’s just salt on the wound when there was no menacing intention. It’s especially crude when you’re in a party, and now the party gets punished for an accident along with you.

Here’s the thing, ANET doesn’t know why you disconnected. The point of dishonor is that disconnecting is a very bad thing for your team, and since some players are either oblivious to this fact or simply don’t care, ANET needs to signal that it’s a bad thing to those players, too.

That’s why Dishonor exists. To signal that disconnecting is a very bad thing. And honestly, they’re probably WAY too generous with their 2 minute time limit.

Zui.9245:

Here’s the thing, ANET doesn’t know why you disconnected.

This is specifically why guilt should not be assumed.

Based on reconnection, this becomes an indication that a player might’ve lost connection without ill intention. You still lose a pip or gain no pip. But get no dishonor.

This isn’t perfect so there should be a step system where after several offenses, dishonor will kick in. This will affect abuse of disconnection to avoid dishonor. Regardless, you still lose a pip or gain no pip (if your team wins); or if you want it more punishing, 100% loss of pips on all scenarios except for reconnecting before a specific time.

No. Guilt is not assumed. Nothing about guilt even matters here. It’s about incentives and disincentives.

Disconnecting, for any reason, is a “kitteny” thing for the other team and especially for your team. If you just lost a pip for disconnecting, that would not be enough disincentive for disconnecting. Hence, dishonor.

If you disconnect with extreme rarity, it’s not a big deal. The fact you’re making such a big deal out of it makes it seem like you disconnect and are gone for more than 2 minutes often.

Zui.9245:

No. Guilt is not assumed. Nothing about guilt even matters here. It’s about incentives and disincentives.

Disconnecting, for any reason, is a “kitteny” thing for the other team and especially for your team. If you just lost a pip for disconnecting, that would not be enough disincentive for disconnecting. Hence, dishonor.

If you disconnect with extreme rarity, it’s not a big deal. The fact you’re making such a big deal out of it makes it seem like you disconnect and are gone for more than 2 minutes often.

Just because I don’t disconnect often doesn’t void a system fault. If I had to pick between losing a pip or extra wait time, I’d take the extra wait time. Losing a pip is far more punishing than dishonor. You break a winstreak, and lose a pip that takes about 9 minutes or so to gain.

And this is me saying that losing a pip is completely reasonable. Dishonor is the fault.

This has nothing to do with guilt and there is absolutely no fault in the system. It’s very plain and simple: If you screw your team by disconnecting for 2 minutes or more, the system rightfully screws you back.

Velimere.7685:

It’s very plain and simple: If you screw your team by disconnecting for 2 minutes or more, the system rightfully screws you back.

The very argument for why it’s a fault. The system does not consider one importantn scenario: an accident. The very foundation of dishonor, in its name, is to punish the offensive: the guilty – the disgraceful. There is no disgrace in accidents.

Again, as said above messages: since the system cannot know everything, there are protocols that can made, to the best of its ability, to determine dishonor. A tier system of offense: after several instances of disconnection and reconnection (the specific factor: reconnecting), it will then apply dishonor.

Jessie.5379:

The very argument for why it’s a fault. The system does not consider one importantn scenario: an accident.

Bottom line: Accidents still have consequences.

Of course. Which is why I stated in my previous comments that pip loss is completely reasonable. This still doesn’t detract the arguments against dishonor.

Jessie.5379:

Of course. Which is why I stated in my previous comments that pip loss is completely reasonable. This still doesn’t detract the arguments against dishonor.

Pips are only for ranked season and have nothing to do with off-season or unranked.

I don’t even know why I’m bothering to reply. Your biased arguments will fall on deaf ears and will thankfully have literally zero influence on this beautiful system. Cheers, friend!

The dishonor system should hold some integrity and discretion in how it’s implemented. As in: if you do something intentionally dishonorable then yes you should receive dishonor. If you disconnected by the fault of your ISP or firewall and still wish to continue the fight and are able to get back into the fight and help your team, that is definitely honorable. Dishonor as a punishment as it is now offers little reparation to the victims of the offending player anyway. So what if they can’t queue again for 15 minutes? The chances (in primetime) of you getting them as a teammate again are extremely low and even then, you’d still have the option of dealing with them 15 minutes later, which is just the length of a single match. Either way, why should you care if the person who intentionally left the game and didn’t play, doesn’t get to play? That’s like punishing a kid by telling them to go to their room full of toys and video games.

szshou.2193:

Dishonor as a punishment as it is now offers little reparation to the victims of the offending player anyway.

I suppose it’s at least something to punish bad players, the dishonor system. I agree that there are other instances where the system just fails, and seen its abuse. We need better report functions; like reporting for feeding, intentional AFKing, etc. And, I suppose one reparation in this instance of a player disconnecting is that if the team that has the disconnected player loses, they will not receive a loss. Which brings me to another issue that’s majorly broken:

If you’re losing, you could pay off a teammate to disconnect so everyone on the team, except that disconnected player, will not lose the match.

Jessie.5379:

Malediktus.3740:

Jessie.5379:

Faux Play.6104:

do you really think you should get points for being carried to a win?

This isn’t about receiving points but receiving dishonor.

You possibly ruined a match. You deserved the dishonor. Even smaller times than 2min can ruin matches already, so 2min is a very generous time already.
And the dishonor is only like 20min unless it happens all the time to you, then it grows exponentially.

Analogy: Heard the difference between car collisions and car accidents? A collision doesn’t denote guilt yet while an accident denotes there is no guilt.

It’s completely reasonable to not receive pips or even lose a pip for being gone. But receiving dishonor on an first offense it’s just salt on the wound when there was no menacing intention. It’s especially crude when you’re in a party, and now the party gets punished for an accident along with you.

First offense is 2 minutes.

Get a drink, take a leak, check the TP. You took 2(+) minutes of 5 other players’ time, I think it’s only fair that the game takes 2 minutes from you.

Personally I don’t think it scales fast enough. I think it should go 2-10-30-120-12h-72h. This will keep other people from being punished for being grouped with someone with a highly unstable internet connection, and actually punish ragequitters. Someone with a fully functional computer and stable internet should not have 5+ crashes in 12 hours.

Jessie.5379:

Velimere.7685:

It’s very plain and simple: If you screw your team by disconnecting for 2 minutes or more, the system rightfully screws you back.

The very argument for why it’s a fault. The system does not consider one importantn scenario: an accident. The very foundation of dishonor, in its name, is to punish the offensive: the guilty – the disgraceful. There is no disgrace in accidents.

Again, as said above messages: since the system cannot know everything, there are protocols that can made, to the best of its ability, to determine dishonor. A tier system of offense: after several instances of disconnection and reconnection (the specific factor: reconnecting), it will then apply dishonor.

Wrong the point of Dishonor is to stop players from leaving matches in which they are put on that have no chance in winning just to be farm animals for some premades giggles and enjoyment.

Can you imagine if the 2 or more solo qeuuers that has been farmed by that premade for the past 5 games see them for the 6rh game and just say, screw that kite we are just going to leave and start another game. That premade will start to have less and less solo queuers to farm then they start to quit the game. ANet places premade team’s entertainment above everyone else even though we all may have spent as much or more money supporting ANet. Just for ANet to say solo queuer don’t matter, get a premade or get farmed.

The fact that this problem is exclusive to GW2 for the past few months and not in the other mainstream sPvP games I’ve played over the past 4 months or so, tells me ANet does this intentionally to FORCE solo queuers to form premades. The only problem is when you have strong willed solo queuers that refuse to play the how ANet wants them to play and instead play their way till they get completely fed up and simply leave. Again which allows amber qualitiy players to reach legendary division.

#SoloQueuersLiveMatter!
#BringBackSoloPlayersRankedQueues!