Page 1 of 1

The problem with the "well" mode

Posted: 18 October 2024, 14:54
by LightKnight
There are 5 modes in this game: only Inferno and Triplet are fit for competitive play.
In theory, "well" (the mode where you have to put your card onto the pile, instead of taking from the pile) could be ok, but the problem is that there is about 1 second of lag animation after you click on the correct symbol, before you are allowed to click on the next one:
and during that 1 second of animation, you gradually see your own next card appear from below:
on one hand, it feels somewhat agreeable, in fact, when you're on a streak and you just click on symbols, you start not to seek symbols at some point, they just kind of shine, reveal themselves automatically,
but
but
that is totally unfit for competitive game, and overall for a good game between players of a high enough level.
The problem is this ~one second of animation lag during which you CAN see the cards you have to match, but you CANNOT click on a symbol,
which means that you're waiting for the exact right moment to click, the very instant it becomes possible,
and if you start spamming left clicks, these stupid notifications will pile up atop your screen.
It's stupid, frustrating, and it makes the victory rely way too much on internet connexion and pure reflex.

Would there be a solution for that?
Would it be possible to have a shorter, quasi immediate animation?...

Re: The problem with the "well" mode

Posted: 21 October 2024, 19:59
by Banaan123456
I had that exact problem playing against you today, I got the red warnings on the top in well mode :(

Re: The problem with the "well" mode

Posted: 21 October 2024, 23:37
by aesche
I was longing for another real-time speed game (set) to come to BGA. After seeing Spot It coming, and its performance, especially on mobile, I gave up on it.

BGA is not, and openly does not seek to be, a place where actual competitive play is possible, and that‘s also very true in terms of performance and usability.

You unfortunately only can file a bug report (actually, there already are 2-3 existing ones around this exact problem), see it go unnoticed for years, and move on.