New record? 15 vs 10

2 Likes

I’ve had worse, I think it was 22 or 20 vs 9, the 9 was 14 before but a lot of them quit

1 Like


also, this

2 Likes

But in those cases it’s because ppl deserted?
The only way to tell how many players that actually played the whole game is look at the scoreboard.

1 Like

nah, the 9 derived from 14 with 5 confirmed quitters. My team had 22 but 4 of them left making 18. Unsurprisingly, the game was toxic af with too much kill steals and I barely got 2.5k

Quite the sight but nothing close to a record.

This implies that the server can run larger maps and battles with more players

1 Like

I know what has happened, 5 real players eventually joined in after the match started and and 5 bot squads were already in action. You must of been on the attacking team because if you check the 5 “people” at the bottom had 0 deaths meaning you creamed the enemy so quickly the bots never had a chance to die.

Bots that are to be replaced by players only get kicked off the leaderboard when they die. As I said before those bots never died so they weren’t kicked from the battle.

I think you’re right, apart from that we were defending.
Look those bottom five names up, they’re indeed bots.
Clever names for being bots, tho.

LeVizo
AMToM
MisterSkillB

only way to confirm concurrent number of players is to have them frag and die. it is stupid, but game removes bots only when squad dies. and your 5 bottom players have 0 death… i guess people just actively hunted attackers close to gray zone not giving bots a chance to die.

btw i think 13 concurrent players is max with current MM bug.

Not actually. If bot did not died, they wouldnt be removed from match.

Hi
Today in the morning (06.00 UTC) we released a potential fix for that problem.
But right now, 14.00 UTC , we must rollback that fix due to unexpected critical bug (Блокировка отрядов, если выйти из матча и запустить снова)
Can anyone answer, did you see this problem in this time span (from 06.00 UTC to 14.00 UTC) ?
If yes, please, send me replay via PM
If not anyone didnt see that problem in this time span, then probably fix was working and we will rollout after fixing critical bug.

1 Like