Disco And Afk... Do Something!
#1
Posted 14 March 2014 - 12:21 PM
Dozen of people log in with a trial mech or whatever, and they just disconnect or either go afk immediately.
And more and more people is starting to do it.
Reason? It's convenient.
There is no penalty in doing that, only less c-bills on this wannabe chinese-farming method.
Please get back some repair cost in the game, something that will penalize those useless players...
#2
Posted 14 March 2014 - 12:31 PM
As far as repair costs...yup
#3
Posted 14 March 2014 - 12:42 PM
Example?
You self disconnected to farm your c-bills? Nice, now get a 10 minute counter before you can launch a game again.
#4
Posted 14 March 2014 - 12:47 PM
Predyz, on 14 March 2014 - 12:42 PM, said:
Example?
You self disconnected to farm your c-bills? Nice, now get a 10 minute counter before you can launch a game again.
Gonna love that when I CTD once every 15 matches. Memory allocations errors are the MWO plague.
#5
Posted 14 March 2014 - 12:55 PM
#6
Posted 14 March 2014 - 01:01 PM
Anyway i don't see why not penalize a problem that occurs mostly in ALL pug matches, instead of not providing support cause someone is still using a 20 years old computer...
#7
Posted 14 March 2014 - 01:06 PM
Predyz, on 14 March 2014 - 01:01 PM, said:
Anyway i don't see why not penalize a problem that occurs mostly in ALL pug matches, instead of not providing support cause someone is still using a 20 years old computer...
I only see them once every 10 matches. Not that big of an issue, really. Get into a group and try to carry harder.
#8
Posted 14 March 2014 - 01:12 PM
Edited by Predyz, 14 March 2014 - 01:13 PM.
#9
Posted 14 March 2014 - 01:19 PM
Option to get back into a game would be great, like if you CTD and start the client again you get put back in the game you left automatically before you can do anything else.
#10
Posted 14 March 2014 - 01:19 PM
The current method of dealing with it is to email support with their name, the map, the time and the issue. One assumes that if they receive enough emails about the same person, they'll discipline them. I'm pretty sure that if they reply back saying that they constantly freeze up, they'll get away with it...but, whatever.
Look...there are some cold, hard facts you've got to look at here.
MW:O is hemorrhaging players faster than it can bring them in. The developers bend over backwards to market this half-finished lame duck to as many gamers that haven't been discouraged with it as they can.
They develop a Matchmaker system that does it's best to keep everyone at a 1:1 win/loss ratio, the artificially inflate new players' Elo scores to put them in the middle of the pile, they do a "free mech" giveaway.....they nerf any and all weapons that are making the game unplayable for them....and still, they players are leaving faster than they're coming in.
Most of these disconnect farmers are newer players...that's how they farm cbills to get their next mech. The LAST thing PGI is going to do is to discipline those people that they're struggling so hard to get to say. It'd be like cutting their own noses off to spite their face.
#11
Posted 14 March 2014 - 01:22 PM
Sometime the noob in question salutes you with something like "gg all, bye" (i've got to screen that? You will be served as soon as possible).
If this for you it's for ipothetic connection problems, sorry to say that, but you are very naive.
End of the story.
Edited by Predyz, 14 March 2014 - 01:24 PM.
#12
Posted 14 March 2014 - 01:22 PM
Predyz, on 14 March 2014 - 01:01 PM, said:
Anyway i don't see why not penalize a problem that occurs mostly in ALL pug matches, instead of not providing support cause someone is still using a 20 years old computer...
Please do tell how you can distinguish between the following from the PGI servers' POV:
- MWO crashing
- PC crashing
- using ALT-F4 to quit MWO
- killing the MWO process using Task Manager
- turning off the router
- disconnecting power from router
- turning off the cable model
- disconnecting power from cable model
- unplugging network cable from PC to router
- unplugging network cable from router to cable model
- turning off the PC
- pulling the power plug of PC from the socket
- electrical power outage
- power spike rebooting/crashing PC
- ISP outage/hiccup
#13
Posted 14 March 2014 - 01:35 PM
Mystere, on 14 March 2014 - 01:22 PM, said:
Please do tell how you can distinguish between the following from the PGI servers' POV:
- MWO crashing
- PC crashing
- using ALT-F4 to quit MWO
- killing the MWO process using Task Manager
- turning off the router
- disconnecting power from router
- turning off the cable model
- disconnecting power from cable model
- unplugging network cable from PC to router
- unplugging network cable from router to cable model
- turning off the PC
- pulling the power plug of PC from the socket
- electrical power outage
- power spike rebooting/crashing PC
- ISP outage/hiccup
Have you ever seen a game console from the server side? Just to know if you have an idea of what you're talking about...
When you create a connection issue, the client disconnects with a ping timeout. You just need a script not to punish those event.
If you want to get disconnected powering off your router, well you have serious brain damage, and no one can do something about that, but i don't think more of the 10% of disco noobs even know where is their router.
This cuts off most of your examples...
When you terminate an application the client side can send a report of application Killing when it logs back in, then you can inflict a punishment.
If your client crashes, the crash is even logged as it was for a bug report (never saw that, do you?)
But of course don't worry, just keep your disco farmers... maybe i'll join the mechanism and farm some accounts to sell, so i will get my gold clan mech for free...
Have a nice day.
Edited by Predyz, 14 March 2014 - 01:36 PM.
#14
Posted 14 March 2014 - 01:45 PM
And I'll be completely honest...if you're having computer issues and you're working your way through them, you might have a few disconnects to get everything straightened out. It happens.
BUT...there are some really strong indicators as to whether this is the case or you're farming cbills.
If you join a match and someone in a Trial Mech disconnects, just shrug your shoulder and game on. But keep the guy's name in the back of your head somewhere.
If you disconnect after you get killed and immediately drop in a new mech (this is power-grinding, if you didn't know that already) and see the SAME guy in a different Trial Mech....and he disconnects again....Odds are pretty good he's farming.
And, get this...you will see that A LOT nowadays. Seriously.
#15
Posted 14 March 2014 - 01:53 PM
Predyz, on 14 March 2014 - 01:35 PM, said:
When you create a connection issue, the client disconnects with a ping timeout. You just need a script not to punish those event.
If you want to get disconnected powering off your router, well you have serious brain damage, and no one can do something about that, but i don't think more of the 10% of disco noobs even know where is their router.
Do you mean to tell me that many MWO players do not know where the network cable attached to their PC is connected to on the other end? And even then, what's to stop them from just disconnecting the network cable from their PC?
Or if they're using wireless, do you mean to tell me that they do not know how to switch off the connection?
Because if the player base is that clueless, then I think I just discovered the source of so many player-related issues with regards to the game.
#16
Posted 14 March 2014 - 02:25 PM
Mcgral18, on 14 March 2014 - 01:06 PM, said:
I only see them once every 10 matches. Not that big of an issue, really. Get into a group and try to carry harder.
Okay, I don't know what matches you are playing, but I rarely see a match where there aren't at least a couple discos in it. There needs to be a way for those who people who want to get back into the fight to do so and a way to penalize the farmers.
#17
Posted 14 March 2014 - 02:31 PM
Mystere, on 14 March 2014 - 01:53 PM, said:
Do you mean to tell me that many MWO players do not know where the network cable attached to their PC is connected to on the other end? And even then, what's to stop them from just disconnecting the network cable from their PC?
Or if they're using wireless, do you mean to tell me that they do not know how to switch off the connection?
Because if the player base is that clueless, then I think I just discovered the source of so many player-related issues with regards to the game.
Ok, how's this for an example?
Prior to my wife building the bad-ass machine I've got right now (i7-4771 CPU, 16g RAM, GE Force GTX 760)....I was playing on an outdated Alienware with a GE 460 GT.
Until I figured out how to set up a user.cfg to bypass a lot of my problems, I had close to a 33% fail rate. That means that 1/3 of the time, until I managed to figure out the several workarounds necessary, I had to ctrl+alt+delete, bring up the task manager and kill the game because I was in a black screen hard freeze.
It's possible....POSSIBLE...that other people experience this. I'm willing to give them the benefit of the doubt. But, when I see the same Derp doing it over and over and over again in different Trial Mechs....well, I'm not a Developer because I have common sense...I can see what's going on.
#18
Posted 14 March 2014 - 03:41 PM
Willard Phule, on 14 March 2014 - 02:31 PM, said:
Prior to my wife building the bad-ass machine I've got right now (i7-4771 CPU, 16g RAM, GE Force GTX 760)....I was playing on an outdated Alienware with a GE 460 GT.
Until I figured out how to set up a user.cfg to bypass a lot of my problems, I had close to a 33% fail rate. That means that 1/3 of the time, until I managed to figure out the several workarounds necessary, I had to ctrl+alt+delete, bring up the task manager and kill the game because I was in a black screen hard freeze.
I can't figure out if you're agreeing with me or not (i.e. disconnects are game/PC/connection problems and there is no fool-proof way of determining otherwise), except ...
Willard Phule, on 14 March 2014 - 02:31 PM, said:
Don't get me wrong, I do see those people -- once or twice a night at worst. But, a dozen in one match as the OP is claiming? That's what I call an exaggeration.
As such, is it any wonder PGI doesn't listen?
Edited by Mystere, 14 March 2014 - 03:42 PM.
#19
Posted 14 March 2014 - 04:09 PM
Predyz, on 14 March 2014 - 01:35 PM, said:
When you create a connection issue, the client disconnects with a ping timeout. You just need a script not to punish those event.
If you want to get disconnected powering off your router, well you have serious brain damage, and no one can do something about that, but i don't think more of the 10% of disco noobs even know where is their router.
This cuts off most of your examples...
When you terminate an application the client side can send a report of application Killing when it logs back in, then you can inflict a punishment.
If your client crashes, the crash is even logged as it was for a bug report (never saw that, do you?)
But of course don't worry, just keep your disco farmers... maybe i'll join the mechanism and farm some accounts to sell, so i will get my gold clan mech for free...
Have a nice day.
Who is buying accounts for this game?
#20
Posted 14 March 2014 - 04:21 PM
support@mwomercs.com
I keep a list and turn in a report at the end of my gaming session with the names of all discos, etc. Let PGI sort it out as far as I'm concerned. If they're "legit" discos due to tech issues PGI can see that, if it's habitual and shows patterns they'll see that as well. They can't take action against griefers if people don't report it.
An easier and more intuitive reporting option would be very welcome though (but that can be said about a lot of things related to this game, groups, MM, lobbies, voip, etc.)
1 user(s) are reading this topic
0 members, 1 guests, 0 anonymous users