12 replies to this topic

[Lmxar]

MWO does a lot of things right. I only have a few gripes with the game: ECM, no knockdowns for lights, lag shield, and...

people disconnecting at the start of a game.

The last one really ****** me off. It also seems like such an easy fix. People manipulating the system in this way really hurts gameplay. And it seems to happen in half of the games I play (I only play in PUGs unfortunately). There is even an easy way to fix this:

If a player disconnects for any reason before they die in a match, they get banned from joining new games for X minutes and don't get cbills for the match.

I would suggest 10 minutes.

If that is too hard, just make it a 10 minute ban for people that quit in the first 300 seconds of a match (unless the game ends). This discourages suicidal charges by individuals and prevents people immediately disconnecting before the match even starts.

I know that the game is still in development, and there are many different bugs that a player can experience at the start of a match, but in my experience I can play upwards of 20 games before I get a single bugged match. PG is doing a good job of addressing things that need to be fixed, and with a few more patches the number of crashes and bugs will likely be much smaller than they are now.

Personally, I would much rather be banned from joining a game for 10 minutes every 20th game or so than deal with constant mismatched fights.

[Thundersquall]

League of Legends has a similar system. The only catch is there needs to be a "Reconnect" button if you do get disconnected. You know, for those of us who really might have encountered lag/latency failure. They shouldn't be banned if the disconnect was unintentional.

[xRatas]

Lmxar, on 22 January 2013 - 08:43 PM, said:

MWO does a lot of things right. I only have a few gripes with the game: ECM, no knockdowns for lights, lag shield, and...

people disconnecting at the start of a game.

You might have 20+ games without fail, many of us can not. Even though I generally sit in my mech with 4fps, black screen and turn bugs until game ends, it would be even worse insult to injury, if your bugged game would also end up in 10 minute ban, if you don't want to sit and listen the sounds. On top of that, I do get random disconnects quite often. Nothing to do with MWO though, but half century old phone lines.

Also, if they would follow your suggestion, those disconnects would most likely end up heat suicide->disconnects. So only ones that would suffer, are the ones that have real problems. Ofcourse, it could be severely punished if you kill yourself, but again, lot of new people would get even more harsh start.

So no, I do not think this is good solution, I'd rather see something more useful. Maybe that you could only reconnect on your current game, if your mech is still alive. Alone, this does not do much with heat suicide disco ofcourse.

Edited by xRatas, 23 January 2013 - 12:56 AM.

[p4r4g0n]

Been suggested, has never even been considered afaik since there is no way to differentiate between deliberate disconnect and client fault.

[Mike Townsend]

It's the serial disconnect folks that bug me. There's generally one per match, and it really hamstrings whichever team gets the person. I have had a number of crippling bugs, sure. It happens. People crash. I would not be in favor of a flat ten minutes, but for people who disco or are inactive for a whole match I think that a combination of needing the answer a challenge to prove you aren't running a macro plus an increasing penalty is appropriate. If you disco before you are killed, your mech is in match til the match is over. If you disco before you are killed or are idle, no problem. If it happens again without play, add two minutes. Again without play, four to the next. Then eight. Then sixteen. Increase the penalty as long as they have any one mech within penalty time and apply each additional penalty to any mech with penalty time pending. People with legitimate issues would never see a penalty or maybe a two minute penalty on one mech once in a while at worst. Serial disconnecters would, by the time they disco their fourth mech, have them all down for the next eight to twelve minutes, and if they did it again every mech would end up down for sixteen to twenty minutes. They would still be able to screw up six games an hour, but it would significantly reduce their ability to do so.

[Rushin Roulette]

Most of you dont seem to realize, that most disconnects at the start of the match are completely unintentional.

There are several known issues causing players to loose connection due to problems with the game itself or incompatibilities with certain standard setting / hardware combinations. PGI have stated that they are in the process of optimizing the game engine.

Disconnected players do not receive any Cbills and im not sure if they recevie any XP (but this is useless anyways once teh Mechs have been maxed anyways). The Mechs they connected with are locked in battle until the fight is completely over.

[Gunblaze81]

I do fine most of the time, but like tonight I get disconnected constanitly. My internet is working fine so it's not a problem with my connection, which is plenty fast enough to run this game (20mbps). So I disagree with any banning or negative punishment for those of us who are not at fault. Would be nice to have it where you can load into the match if you log in within a short time after being disconnected.

[Xandralkus]

I intentionally disconnect on River City Night. I don't like the map and have no intention on playing it.

...Although my game periodically crashes at random on other maps.

[pjnt]

After the last patch I DC about 50% of the time. You want to ban me for 10 minutes and take my CBills because PGI use their player base as a testing ground?

There won't be anyone left playing for you to watch disconnecting. I've already installed MW4 again since the game is too unstable for me to even play.

If you can not determine why someone leaves, you can not enforce any rule.

The problem lies with PGI, not the players. Please focus your energies to those that so deservedly earned them.

After the last patch I DC about 50% of the time. You want to ban me for 10 minutes and take my CBills because PGI use their player base as a testing ground?

There won't be anyone left playing for you to watch disconnecting. I've already installed MW4 again since the game is too unstable for me to even play.

If you can not determine why someone leaves, you can not enforce any rule.

The problem lies with PGI, not the players. Please focus your energies to those that so deservedly earned them.



lol, even the forum is broken

[Xandralkus]

Agreed, forum is broken. I tried to edit a post and the forum ate the majority of my text.

[Elder Thorn]

as long as there is no reconnect option, there should not be punishments like that. As soon as we got a reconnect option, you should be forced to reconnect once you start the client.

and about forum being broken and that stuff:

Quote

We are currently investigating a server issue; there may be degraded experience while we resolve the situation. Thank you for your patience.

http://www.facebook....chWarriorOnline

[Woska]

Too many variables. And it is impossible to differentiate between a legitimate disconnect and a deliberate one. Also, if the player suffers from one of the really debilitating bugs in a match, he's got little choice but to disconnect and try again.

So if you had a system that wouldn't let you play for ten minutes after a game crash, it would just upset more people than it would help. Also, you already don't get any c-bills or XP if you disconnect while alive, except what you've actually earned through combat.

[Stringburka]

When there is still heavy issues with lag and server connection errors, and since 9th february loads of people experience frequent in-game crashes (i've had 2 today, out of maybe 10 played matches), no, this won't work.