Platform, device and operation system
Android 11, Samsung Note 20 Ultra
What were you expecting to happen, and what actually happened
Expected: To play a Co-Op match with more than two players.
Actual: Game glitches out with three players (but recoverable, see below), four players causes a “not-a-CLIFFY” error and the match crashes.
How often does this happen? When did it begin happening?
Always since 0.34 was implemented when three or more players attempt to party for a Co-Op match.
Steps to make it happen again
As pictured with an intended party of 4,
The issue is visible in the party UI in the upper left portion of the screen, where the fourth party member fails to load into the match.
When there is a party of three, the hard crash error message does not generate, but the same error persists and carries through the match.
In these instances, Players 1, 2, and 3 enter the match. The match starts normally. However, for Players 1 and 2, Player 3’s UI does not load in the upper left portion of the screen. As Players 1 and 2 finish their first match in the skirmish, they will freeze up. These players can recover by performing a “double force quit” (force quit, then force quit again on the splash screen where the game locks up again), and recovering into the match on their third reload attempt. When Players 1 and 2 reload into the match, they find that the match has carried on while they have been booted out of the game, as Player 3 has not been impacted by the crashes (and is holding open the match instance). At that point, the match can be completed, as normal.
Interestingly, as long as the party configuration does not change, the issue does NOT occur in future Co-Op runs. However, as soon as the 3rd player changes to a new player, the issue re-manifests itself and resolves in the same way mentioned in the previous paragraph. Parties of 4 always results in a server error.