"You have caused a matchmaking error"

nemir

For ages, the matchmaking detection vexed me.

Then for quite some time, it seemed not to.

Recently, the nightmare has returned.

I sit in the queue. I get a game. It launches. I see an ICE error letting me know that my opponent has noped out of this game before it even starts.

I wait for some time longer. The message in the client saying "match launching" disappears.

So... I quit the game to rejoin the queue.

And I get the message that I caused the error.

Or worse.... I just wait and wait and wait and then the game times out, and I get another error.

Only this time, I am timed out for ten minutes. Next time, it's 30!!!

I only have one life. I have a lot to do. If the detection was accurate it might be fair, but it's just not.

Can you turn it off until it's more accurate please?

magge

That is understandable very frustrating. We had it disabled some time ago for testing purposes, but that resulted in a significant drop in the match connectivity success rate. If no one receives a penalty anymore, then no one bothers to look into it and just blame everyone else.

If I look at the Grafana dashboard for connectivity quality, it appears that it works for the majority of players.

For which MM queue do you encounter the connecitivy issue?
Is it for a specific player you encounter, or is it "random" ?

nemir

It seems pretty random, maybe about ten percent of the time. It happens on all queues, too.

It's a little more likely to happen in 3v3 or 4v4 queues as there's more chance of a player dropping out or not connecting with the game and the system misattributing that.

And a lot of the time, it doesn't matter much. Because if it only happens once in a session, you just get your warning and carry on. But sometimes, as for me last night, it happens several times. I was in the middle of a ten minute timeout when I posted this. I went back and immediately got timed out for half an hour.

Does grafana show enough detail about who is responsible for matchmaking failures? Or just that there are failures and it points at someone. I am pretty sure that the testing for it is not 100% right, given my experiences.

Especially after watching the ICE reconnection message when someone saw the map and dropped out of the game. I waited another 45 seconds, and only dropped out myself when the launch timer was down to about 15 seconds, so I could get back into the next queue.

I definitely recognise the need for this, just feel that maybe it's not necessarily picking up the right culprit all the time.

magge

Unfortunately, there are no specific statistics that indicate who caused the connectivity error. I wish we would, and perhaps that feature can be tackled in the future somehow. If you can share the logs related to the issue, it may help identify which player was involved.

I know that certain countries have difficulties connecting to us, and the average user usually has no idea how to fix that. They just keep trying until it works, and reach out to the mods/technical support after they got annoyed enough by the penalty system. (Solution for those cases is mostly: use a VPN)

The new ice adapter is WIP and looks promising so far. There is no ETA, but work is ongoing. Hopefully it will tackle those connectivity issues more gracefully. But it will not be a "magic fix" for everything. My understanding of this subject is limited, because the architecture is extremely complicated.

@nemir said in "You have caused a matchmaking error":

maybe about ten percent of the time

You are exactly right with that observation. There is a ~10% connectivity failure rate in the 1on1 queue. Which is relatively low, when 90% of the started games can be played.