Sick of 3v5, 4v5, and other unfair odds

#1 - Feb. 28, 2013, 12:52 p.m.
Blizzard Post

Anet, please add a system to let people fill spots of missing people in tournaments. The way the current system is, it is game breaking for Spvp. Every other match I wind up in a 4v5 or 3v5 matchup.

There is also an interesting bug where it puts an opponent on your roster, but when you enter the matchup they are on the opposite team and you are forced to 4v5.

#6 - Feb. 28, 2013, 4:37 p.m.
Blizzard Post

We think one problem is that people join into a roster, then before the match is ready, quit the game. Disconnecting does not remove you from the roster, so the game starts and finishes like nothing happened. A lot of these 4v5 games could be completely unintentional from the person leaving. Solving this is a technical issue. We could kick you out of the roster if you disconnect, but you should still be able to switch characters before the match starts.

#10 - Feb. 28, 2013, 4:52 p.m.
Blizzard Post

We think one problem is that people join into a roster, then before the match is ready, quit the game. Disconnecting does not remove you from the roster, so the game starts and finishes like nothing happened. A lot of these 4v5 games could be completely unintentional from the person leaving. Solving this is a technical issue. We could kick you out of the roster if you disconnect, but you should still be able to switch characters before the match starts.

Will this be for solo que’s only? What happens if you dc not by choice and try to reconnect to your premade team only to find out they got thrown into a match with some random.

That’s a really good question. Rosters that were submit full could easily not be put into matchmaking. However if a partial roster queued, it would indeed be a problem. Maybe it should work more like Dota2, if the game can’t start with all 10 players, it doesn’t start at all. It could happen once the match countdown is done.

#12 - Feb. 28, 2013, 5:37 p.m.
Blizzard Post

you think? of course that is one of the problems, the other is people joining and seeing they are on a full pug and facing a full premade and quitting, or seeing they are on a 5v4 and quitting, making it 5v3. And since you don’t punish them what do they lose? the invisible rating they don’t care about? They log-off for 10 mins avoid a spawn camp stomping then log back in.

Learn from Rift, if you get DC’d their system gives you short amount of time to re-boot/log back in and puts you in the same warfront you were in. If you don’t log back in quickly it fills the spot with a new player and when that person eventually does log back in they have a 30-min deserter debuff and can’t queue for pvp. I’m guessing just another thing your system isn’t built to do.

If someone is constantly DC’ing due to crappy ISP or quitting without leaving their roster they should be punished and stick to hotjoin rather than making 4 people suffer a curb stomping 5v4 matchup.

The sad thing is this has been an issue basically since release and doesn’t sound like you have any fixes in the works. Like i said in another thread this is something Rift did a hotfix for shortly after release. And I only use Rift as an example because it was one of the more recently released mmos. pretty much every other mmo pvp also has quitter debuffs/penalties.

The two problems deserve different solutions. If a player is in queue for a bit, but needs to log off to do something else, that player shouldn’t be punished because they didn’t leave the roster first. This is a completely fixable problem. Punishing people who knowingly dodge is a much more difficult problem.

#18 - Feb. 28, 2013, 6:33 p.m.
Blizzard Post

you think? of course that is one of the problems, the other is people joining and seeing they are on a full pug and facing a full premade and quitting, or seeing they are on a 5v4 and quitting, making it 5v3. And since you don’t punish them what do they lose? the invisible rating they don’t care about? They log-off for 10 mins avoid a spawn camp stomping then log back in.

Learn from Rift, if you get DC’d their system gives you short amount of time to re-boot/log back in and puts you in the same warfront you were in. If you don’t log back in quickly it fills the spot with a new player and when that person eventually does log back in they have a 30-min deserter debuff and can’t queue for pvp. I’m guessing just another thing your system isn’t built to do.

If someone is constantly DC’ing due to crappy ISP or quitting without leaving their roster they should be punished and stick to hotjoin rather than making 4 people suffer a curb stomping 5v4 matchup.

The sad thing is this has been an issue basically since release and doesn’t sound like you have any fixes in the works. Like i said in another thread this is something Rift did a hotfix for shortly after release. And I only use Rift as an example because it was one of the more recently released mmos. pretty much every other mmo pvp also has quitter debuffs/penalties.

The two problems deserve different solutions. If a player is in queue for a bit, but needs to log off to do something else, that player shouldn’t be punished because they didn’t leave the roster first. This is a completely fixable problem. Punishing people who knowingly dodge is a much more difficult problem.

why is it so difficult yet every other game has a deserter penalty? If you log off once you have been put into a match you have 1-2 min to log back in, if not game fills spot with another solo queuer and the person that didn’t log back in quick enough gets a 30-minute quitter debuff and can’t join any pvp until it’s up. Rift does this, WoW does this, Warhammer did it, etc.

I don’t even bother playing this game anymore because as a solo queuer more of my matches are 5v4 than 5v5.

This is a very real problem, but we can only work on so many things at once. I would still place it at a lower priority than Custom Arenas.

#38 - March 1, 2013, 9:27 a.m.
Blizzard Post

First, we need to solve the problem of people leaving before the game begins, its simply a flaw in our roster design. Then we need to determine a suitable punishment for people who leave during a match, and do not return.

On top of these, it sounds like some people are describing a bug forcing 4v5’s. We do not know what would be causing this or whether it is a new problem or not. It’s hard to tell when there are multiple ways a team could be missing members.

To clarify, bugs take higher priority over features like custom arenas. However a punishment system is a feature that takes considerable more time, and must be weighed against our current features plans. We always have the option to re-prioritize just like we did with matchmaking.

#40 - March 1, 2013, 9:48 a.m.
Blizzard Post

https://forum-en.guildwars2.com/forum/pvp/pvp/Sick-of-3v5-4v5-and-other-unfair-odds/first#post1548675

#46 - March 1, 2013, 1 p.m.
Blizzard Post

reading areanent’s replies here is disheartening.. its like they walk one step foward and two steps backwards

It just makes our next step that much bigger :P. Honestly, its great to really get to the exact root of problems in a constructive way so we don’t implement features that only half solve the issue.