8 replies to this topic

[martian]

During the last few days I have experienced some group disconnects. Those groups have never reconnected.

I can tell you that it is not a good feeling, knowing that you are starting the game and it is 0:4 or 0:3 right from the beginning.

It is even worse when that group fields heavy or Assault 'Mechs.

Do you have a similar experience? (especially from the last few days?)


In the yesterday's game we quickly agreed on a defensive strategy and to our surprise, we actually won that improvised defensive engagement. If we consider that our team was missing Mad Cat Mk. II, Daishi and Rifleman IIC, all those active players deserve commendation.



The today's game with the another 4-man group disconnect and the resulting loss of one third of the team strength right from the start. The result is not unexpected ...

[Willard Phule]

I kept getting dumped as a solo, so I've got to assume that whatever was doing it to me was doing it to a premade group. They're tied together before dropping into the MM.

I also had issues where the mechlab would only recognize that I own the mech I was using until I logged out and logged back in.

I'm also gonna guess that regular maintenance is what prevents all the above from happening.

[Bistrorider]

Never seen whole group accidental dc's at once. Wonder what people from that groups have to say?

[Monkey Lover]

Seen this happen before a few times and has been posted on here before. What happens is the group somehow ends up in two matches. They don't even know they didn't show up to the other. Maybe something to do with canceling at a bad time, who knows.

Old bug they have never fixed.

Edited by Monkey Lover, 09 November 2020 - 03:33 AM.

[Bistrorider]

Yeah, maybe some kind of bug, but painful.

[MechWarrior414712]

It's a "known" bug which happens because the group is dropped in to two different matches at the same time somehow

[selfish shellfish]

Yes, this is an interesting issue if it is true. I remember reading about it some time ago and (I think) it was mentioned that it could happen even to solo players. Basically a player enters a match normally and has no idea that a "copy" was in another match disconnected. That would explain some of the players who remain disconnected for the entire duration of a long match.

Edited by selfish shellfish, 09 November 2020 - 04:42 AM.

[Willard Phule]

Also, remember, any "bug" that is known but not addressed is called a "feature." This isn't a bug, it's a feature.

[VonBruinwald]

selfish shellfish, on 09 November 2020 - 04:41 AM, said:

Yes, this is an interesting issue if it is true. I remember reading about it some time ago and (I think) it was mentioned that it could happen even to solo players. Basically a player enters a match normally and has no idea that a "copy" was in another match disconnected. That would explain some of the players who remain disconnected for the entire duration of a long match.

It's happens when you stop searching for matches. When you click stop it takes a split second for the sever to get the message. If the server finds a match before it's received the stop command it drops you in the match but you won't be connected. The higher your lag, the bigger the window of opportunity.

If you refresh the lobby before the phantom match ends it will be displayed as "in progress" and you can join it. But most people won't even notice.


You can sometimes trigger this by start/stop searching repeatedly, when you get in a match exit asap if you get the option to re-join 2 matches it worked. The keen eyed will also notice it's the same mech in both matches, which tells us it's the client that stops you re-dropping in a mech before the match ends, not the server.

Edited by VonBruinwald, 09 November 2020 - 06:40 AM.