Multiplayer browsing

Multiplayer browsing is very tedious. Here is a list of problems
-full lobbies are visible
-some lobbies are shown as not near full(2/6) etc, but when trying to join I am told lobby is full or game is started. I refresh and lobby is still shown with 2/6
-after a online match my social status is set to offline.
-when able to join a lobby, it takes an unreasonable long time to join.
-chat in lobby is very very delayed
-taunts do not make sound in lobby, even though they do in game. I have enabled the setting that lets you hear taunts.
-when my status is set to offline I encounter the problem of not being able join lobbies way more frequently and lobbies that I am able join take much longer to join
-in game chat is incredibly slow. Same goes for flares/pings
-when I try to quick search games I sometimes never find any games regardless if I have set it to accept any number of players(3v3, 2v2, 1v1)
-when I have quick searched I have only ever been able to find 1v1s.

4 Likes

So many people complaining about this, and devs are silent. Seriously considering a refund because this is just insane for a 2024 game to have so many issues with multiplayer.

3 Likes

Agreed. This the type of problem meant to be filtered out before the official release. This is why we have betas. I also agree that major types for problems like this deserve immediate recognition and announcements from devs. The public needs to see that the devs are aware and that they are doing what they can.

The issue could be harder to fix than everyone thinks, and just because there are betas doesn’t mean every single bug can be fixed before a planned release date.

but an official announcement about a gamebreaking bug should not be that hard to accomodate?

1 Like

I suppose, but there’s plenty more bugs than just multiplayer at the moment. They could be still compiling a list of everything that’s been found so far.

Im sorry but “harder to fix” should not be my problem. its 2024 and multiplayer is an integral part of this game.

This should have been fixed or tried fixed before launch.

From what it looked like, it was, and this is just a new bug.