33 replies to this topic

[DragoonBrigade]

Ok, so someone shuts down to stay alive is understandable. But when someone shutsdown and then disconnects is unfair to the rest of the people playing and in my opinion there should be something implemented to counter this. I'm sure a script could be written where that mech either powers up or the game ends. Maybe even implement a timeout for the offending player because it ties up everybody else's mech so in turn they should be tied up for at least 1 match.

Anybody have any other ideas on how to implement this? Fair is fair I say.

[Joseph Mallan]

Well if teh individual in on my team. I wait a minute or so and then give the coordinates from teh DCs cockpit!

[FitzSimmons]

Seems like its dealt with by the players well enough already. Shamed and ratted out for AFKers and those who refuse to engage.

[DragoonBrigade]

Doesn't always work because some people can't find them if they don't know how to read coordinates.

[stjobe]

And in your preferred solution, what about re-connects?

Involuntary disconnects are a thing, you know, and it's virtually impossible to distinguish from voluntary disconnects.

Edit: Also, both non-participation and giving out locations are currently against the Code of Conduct and are both actionable offences. According to support@mwomercs.com, they are currently re-writing the CoC to be clearer about these things.

Edited by stjobe, 10 July 2015 - 05:41 AM.

[DragoonBrigade]

at the end of the match powered down and disconnected you should be able to distinguish that the person is not coming back.

[FitzSimmons]

This isn't a court of law. When a player has been disconnected for 5+ minutes they're not coming back in 99% of situations. Power outages, bad lines, etc are not fun, but I also would not be upset that my team didn't twiddle their thumbs for 5 mins on the outside chance that I can reconnect after a few minutes.

[TWIAFU]

stjobe, on 10 July 2015 - 05:38 AM, said:

And in your preferred solution, what about re-connects?

Involuntary disconnects are a thing, you know, and it's virtually impossible to distinguish from voluntary disconnects.

Edit: Also, both non-participation and giving out locations are currently against the Code of Conduct and are both actionable offences. According to support@mwomercs.com, they are currently re-writing the CoC to be clearer about these things.

Why we report and let PGI figure that out. That is supports job and not ours.

Glad they are being more clear with the CoC on these issues. People can finally stop saying it is OK to fire 1 MG round and hit then go shutdown as acceptable.

[DragoonBrigade]

People are focusing on just 1 word "disconnects" but I'm talking about "POWERING DOWN" and disconnecting. That's another situation.

[Joseph Mallan]

DragoonBrigade, on 10 July 2015 - 05:56 AM, said:

People are focusing on just 1 word "disconnects" but I'm talking about "POWERING DOWN" and disconnecting. That's another situation.

Powering down and DC is just the same as just up and DCing. Elvis has still left the building.


That's not to dated a quip is it?

[GeistHrafn]

DragoonBrigade, on 10 July 2015 - 05:56 AM, said:

People are focusing on just 1 word "disconnects" but I'm talking about "POWERING DOWN" and disconnecting. That's another situation.

Report it to moderation@mwomercs.com.

[DragoonBrigade]

and when you report what will happen? I'm guessing nothing.

[Sjorpha]

Just count disconnected and inactive mechs as dead for the purpose of winning. GIve inactive mechs that aren't disconnected a 1 minute counter to allow shutdown for ambush and the like before ending the match, make and exception for conquest if you have a chance to win on caps.

[GeistHrafn]

DragoonBrigade, on 10 July 2015 - 06:05 AM, said:

and when you report what will happen? I'm guessing nothing.

They are logged, and repeat offenders are dealt with. Obviously it happening one time could be accident, twice a coincidence. But 20 times, not so much.

If people don't report it, nothing happens.

[stjobe]

FitzSimmons, on 10 July 2015 - 05:41 AM, said:

This isn't a court of law. When a player has been disconnected for 5+ minutes they're not coming back in 99% of situations. Power outages, bad lines, etc are not fun, but I also would not be upset that my team didn't twiddle their thumbs for 5 mins on the outside chance that I can reconnect after a few minutes.

It isn't a court of law, but it is a game with rules. One of those rules is that you have to participate. That does not mean "always charge at the enemy, firing as you go" - powering down is okay, if you have previously fought in the match.

Another of those rules is that it is never okay to give out a team-mate's location. Never ever, under no circumstances, no way, no how. It is verboten. End of story. You can say he's AFK, but you cannot say where he is.

[Joseph Mallan]

DragoonBrigade, on 10 July 2015 - 06:05 AM, said:

and when you report what will happen? I'm guessing nothing.

nothing immediately, no.

[Sjorpha]

It's never sustainable to try and enforce rules in a computer game through reporting and written rules.

You have to design the game in such a way that anything that is possible to do (short of hacking/cheating) is legit.

The disco/afk/hiding problem is a design failure issue, not a player issue.

[stjobe]

Sjorpha, on 10 July 2015 - 06:13 AM, said:

It's never sustainable to try and enforce rules in a computer game through reporting and written rules.

You have to design the game in such a way that anything that is possible to do (short of hacking/cheating) is legit.

The disco/afk/hiding problem is a design failure issue, not a player issue.

Disconnects, AFK, and hiding is legit - if the 'mech has participated in the match. Team Treason is never legit.

Quote

Non-Participation Abuse
If a player has joined a match, they must have launched the game with intent to play. Players who are not moving, or are otherwise not participating in the spirit of the game, fall under this category. While we all understand the call of nature: Repeated abuse of this behaviour, similarly to 'Mech Suicide and Team Killing, results in an unfair advantage for the enemy teams, and is thus not considered acceptable use. Please keep in mind that idling on your cap point without armour or moving does not constitute a form of tactical "Base Defense".

Team Treason
Treasonous provision of information to enemy combatants, also known as "bird-doging" is forbidden. This involves a player using the in-game chat to provide the enemy team with the locations of their own team mates. While we appreciate that some players may wish to have a round end early by calling out the location of an AFK team-mate, the risk that this could be used against an active participant of the match to deny them the use of cover and movement makes this a form of a griefing. You may declare a teammate AFK but not their coordinates or position.

- http://mwomercs.com/...ploitsgriefing/

Edited by stjobe, 10 July 2015 - 06:18 AM.

[Chuck Jager]

GIving out somebody's location is against the CoC, just like a speeding ticket. You may get in trouble with a written warning after they receive "multiple" complaints. So if you have never received a warning and you are paired up with some POS coward at 90% health wasting your time and they have spent the whole match at 1000m chain firing lrms and medium lasers please be aware that the individual involved may feel intimidated, bullied and responsible for your teams loss while you are risking a possible warning for a time out. I will not point out the risk versus reward factor involved here because it could be seen as promoting actions that are against the CoC. Speeding is bad.

Edited by Chuck YeaGurr, 10 July 2015 - 06:21 AM.

[FitzSimmons]

Considering how often I see people bird dogging AFKers, there are two possibilities.

1) People aren't reporting this because of common sense or because their indignation is BS.
2) PGI doesn't waste their time with it (rightly).