If you like Can't Stop, go vote for bugs

[Wicksweff]

Can't Stop has a couple of bad bugs, but they're not going to get attention from developers if you don't go vote for them.

Can't Stop bugs:
https://boardgamearena.com/bugs?game=11

Please upvote this one:
https://boardgamearena.com/bug?id=12394

Wicksweff

[Romain672]

I just checked that bug.
The two shown examples aren't a bug.

You must use exactly two dices to advanced one of the black token.
And you can't play in finished column. That mean if you can only play in a finished column, you loss immediately.

[Wicksweff]

I think you're mistaking my red tokens for the black turn tokens.
I didn't have black turn tokens on any columns yet, and there ar eno claimed columns yet.
https://imgur.com/a/kKOU5SY

[Jest Phulin]

This image appears to be from a development studio game (or some other game adjusting the graphics), not a production game. Hence the "gameStateChange" messages in the log. Additionally, the log clearly shows that Wicksweff has already progressed on 4, 8 (twice), and 6, and therefore has no temporary tokens to progress on 9, 10, 11, or 12 (the choices when rolling 4-5-6-6).

The example linked in the bug has the player rolling 2-2-6-6 when columns 4, 8, and 12 are already claimed.

These are not bugs, these are correct implementations of the rules.

[Wicksweff]

No, that's a production game.
Steps to get the "gameStateChange" messages:

1. open this link
2. Click Replay game
3. Choose Wicksweff
4. Click Advanced replay features at the top
5. Click the Next visible change button in the centre of the replay controls 3 times

[aesche]

No bug anyway, you already placed 3 black tokens...

[RicardoRix]

According to the log, you've already progressed on 4,6 and 8. So the possibilities of 10,11 and 12 means you fall down.

You only get 3 black tokens to progress each turn and you've used them all up.

[Wicksweff]

In Arthur1er's game (51174907) the issue is with the order of the UI element updates.
I replayed it while recording video.

BGA updates the turn number at the top left before it clears the roll.
The 2-2-4-6 is from Bardo Gaan's turn, but then updates the turn to #127, so you can grab a screenshot with mismatched values.
Then the roll updates to Arthur1er's 2-2-6-6 but everything else is unchanged, except a thin white line at the top of the log.
That's how you can get screenshots of Turn 127 with two different rolls.

So the issue is that the order of UI element updates results in simultaneous display of values from different players' turns at the same time, and it's extra confusing in the case where a player hits all clamed columns on their first roll, because there are two of these between turns states back-to-back.

[Jest Phulin]

Please clarify the gameplay bug, then.

The current bug report states that "at move #127, the three dices indicated impossible choice at my first roll." I have replayed played the game from a few turns before 127 to a few turns after. The only time the impossible move was indicated was the 2-2-6-6 when 4, 8, and 12 were already claimed.

So, what's the bug?
What *exactly* was the game state before the bug? (Whose turn was it, what had they rolled, what did they choose to advance on, where are their temporary markers, are any columns claimed?)
At the end of that turn, what was the next die roll -- the one that has the bug?
What did the BGA implementation do that was against the rules?

Right now everyone who has looked at the big picture can't find what you are describing as a bug. We can only find good code.

[euklid314]

I have not looked at the game. But could it be possible that the dice throw gave an instant fall and Wick saw only the next players dice throw and thus wondered why he fell?