I think I have mentioned this before, but is more apparent now. When selecting the option for Free square is selected to ‘Add Free Square’ Then the most squares selected will max at 24 as in the image below and they players will never reach 25, so the game never automatically ends. When there is no free square then the players can reach 25 out of 25 and the game ends. Wouldn’t it be better to have an extra 1 to the squares marked or reduce the total to for example 24 out of 24 squares marked.
I usually end the game when it reaches 24 manually, but when I have not added the free square in the excitement of the game I have forgotten there is no free square and ended the game at 24 causing a bit of upset with the players.
2 Likes
Ah, good catch. We’ll get that corrected.
2 Likes
We have released an update in our latest version that addresses this issue.
Now, when enabling Add Free Square, the total amount of bingo squares is reduced to 24 instead of saying 25. This is updated on the Experience Dashboard → Rankings tab, the Presentation View’s rankings leaderboard, and on the Rankings CSV export.
The rankings will now display “Marked 24 out of 24” if you’re using, for example, the Full Card bingo pattern.
I wanted to mention though that a bingo game doesn’t automatically end after a certain number of squares are marked. There is a setting called Auto-Finish Bingo Game that will finish after a certain number of bingos are earned.
So prior to this update, a player could still complete a Full Card bingo pattern and the bingo game would automatically end if After 1 Bingo(s) Earned was set for Auto-Finish Bingo Game. There was no issue with this functionality.
The problem was that the rankings would incorrectly display “Marked 24 out of 25 squares.” But it never affected the functionality of the game or automatically ending the game. I just wanted to clarify this. The game automatically ends after earned bingos, not a total amount of squares. And the Full Card bingo could still be earned even though the leaderboard’s display was incorrect.
Thanks for your feedback and reporting this!
1 Like
Thanks for this Ross, much appreciated.