

Shutdown And Disconnecting Mechs Need To Be Dealt With
#21
Posted 10 July 2015 - 06:30 AM
#22
Posted 10 July 2015 - 06:32 AM
Chuck YeaGurr, on 10 July 2015 - 06:19 AM, said:
This is a total straw man.
People actively playing the game (even if they're doing poorly) are not getting their locs reported that I've seen with anything near regularity. No one is even reporting lights that just run around the map for the last 4-5 minutes of the game without even looking in the direction of an enemy.
#23
Posted 10 July 2015 - 06:34 AM
FitzSimmons, on 10 July 2015 - 06:32 AM, said:
This is a total straw man.
People actively playing the game (even if they're doing poorly) are not getting their locs reported that I've seen with anything near regularity. No one is even reporting lights that just run around the map for the last 4-5 minutes of the game without even looking in the direction of an enemy.
FitzSimmons, on 10 July 2015 - 06:32 AM, said:
This is a total straw man.
People actively playing the game (even if they're doing poorly) are not getting their locs reported that I've seen with anything near regularity. No one is even reporting lights that just run around the map for the last 4-5 minutes of the game without even looking in the direction of an enemy.
satire dude satire
#24
Posted 10 July 2015 - 06:49 AM
#26
Posted 10 July 2015 - 07:04 AM
stjobe, on 10 July 2015 - 05:38 AM, said:
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.
I just went through a two week nightmare of repeated disconnects due to some bad RAM. CTD's at loading screen, 10 seconds in, 5 minutes in...I wonder how many times I was reported during my little personal hell.
#27
Posted 10 July 2015 - 07:17 AM
Rhazien, on 10 July 2015 - 06:08 AM, said:
If people don't report it, nothing happens.
I used to Crash to desktop 4 or 5 times a night and it didn't get fixed until the 64 bit client came out....
This results in a DISCONNECT on the game end...I'm no longer in the game servers. (DUH) But if after a week of this issue (which was PGI's and not mine) i got kicked for DISCONNECTING TOO MUCH or some s%$t they wouldn't have a very happy customer....those are the times when i'm glad my brother is a lawyer.
Bilbo, on 10 July 2015 - 07:04 AM, said:
Had same issue...i also wonder. Changed RAM a while back because of this....but also 32 bit client killed me often.
Edited by DarthRevis, 10 July 2015 - 07:18 AM.
#28
Posted 10 July 2015 - 07:50 AM
Sjorpha, on 10 July 2015 - 06:13 AM, said:
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.
Yep. this is where repair and re arm, dropship fees, jumpship fees, comes in(guilds can buy dropships and jumpships to minimize these fees). Also if they added mechbay repair time for mechs in some way and an npc repair crew(astechs?) to level up to shorten repair times and allow for modifications to mechs etc, then all the better.

Edited by Johnny Z, 10 July 2015 - 08:01 AM.
#29
Posted 10 July 2015 - 08:02 AM
TWIAFU, on 10 July 2015 - 05:42 AM, said:
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.
I don't think anyone was seriously saying that, at least not on the "I have engaged in battle" side. In fact, the only ones I remember saying that are those who have been using it as a red herring on the opposite side.
In any case, there will still be those forcing the issue until PGI gives out clearer rules.

#30
Posted 10 July 2015 - 08:03 AM
DarthRevis, on 10 July 2015 - 07:17 AM, said:
I used to Crash to desktop 4 or 5 times a night and it didn't get fixed until the 64 bit client came out....
This results in a DISCONNECT on the game end...I'm no longer in the game servers. (DUH) But if after a week of this issue (which was PGI's and not mine) i got kicked for DISCONNECTING TOO MUCH or some s%$t they wouldn't have a very happy customer....those are the times when i'm glad my brother is a lawyer.
Had same issue...i also wonder. Changed RAM a while back because of this....but also 32 bit client killed me often.
I ran the built-in memory diagnostic tool in Windows 8.1 after finally getting a bsod outside of the MWO client. Then I confirmed it with memtest86. Took about half an hour to run the windows tool. Memtest86 took...considerably longer, but I wanted to make sure as RAM has gotten ridiculously expensive these days. In hindsight I should have done that first. I could have saved myself a lot of time and trouble.
#31
Posted 10 July 2015 - 08:04 AM
FitzSimmons, on 10 July 2015 - 05:41 AM, said:
It does not matter. Giving out positions is clearly against the rules. So your only valid option is to report them and let PGI make the determination.
And instead of twiddling their thumbs, the dead should just move on, period.
#32
Posted 10 July 2015 - 08:27 AM
Make sure they get found out fast before they waste 23 guys time.
#33
Posted 10 July 2015 - 08:42 AM
There's a difference between reporting the location of a mech with completely fresh armor in the spawn area who is the last mech and 10 minutes in the match gone - and reporting the location of someone who's running around with no weapons/armor trying to survive. Also, CTDs happen to everyone. They also don't take 5-10 minutes to rejoin. Even on my old slow laptop it only took 2 min max.
So yes, the above is "against the rules" but so is taking a pen home from the office. While I'm sure the Miltons of the world would immediately report this heinous activity to corporate headquarters, the sane folks don't lose sleep.
#34
Posted 10 July 2015 - 09:19 AM
This problem exists because a mechanic that has a valid purpose becomes a crutch that is an excuse for bad game play. It is also compounded by the lack of players and the mechanics of MM mixing a wide range of skills that really should not be in the same match. It is easier for PGI to make a "rule" than to balance mechanics and expenses to hardwire in a fix. SO if you do get reported remember it is costing PGI money so you may want to consider it taking one for the team to move this issue forward. Honestly I can not support or promote any action that is against the CoC because it may be considered a breach of the ToS etc etc etc wink wink nudge nudge.
1 user(s) are reading this topic
0 members, 1 guests, 0 anonymous users