#22186: "Tie Breaker is unsatisfying resolution to a long game"

All reports

potionexplosion_displayed reports

awaiting: This suggestion has not been analyzed by delopers yet

Vote for this report

What is this report about?

potionexplosion #105037657

What happened ? Please select from below

Suggestion: in my opinion, the following would greatly improve the game implementation

What happened ? Please select from below

Suggestion: in my opinion, the following would greatly improve the game implementation

Please check if there is already a report on the same subject

If yes, please VOTE for this report. Reports with the most votes are taken care of in PRIORITY!

#	Status	Votes	Game	Type	Title	Last update

Detailed description

• Please explain your suggestion precisely and concisely so that it's as easy as possible to understand what you mean.
Let games end in a tie, or at least make it fair. One pull is ridiculous.
• What is your browser?
Google Chrome v84

Report history

5. Aug 2020 20:47 • Marklbetya • This suggestion has not been analyzed by delopers yet:

The tie-breaker is incredibly stupid. Let the game end in a tie if that is the alternative. One pull to see who gets more marbles? You play that long for that?! There is nothing wrong with a tie if there is no skillful way to determine a winner. This is like a coin toss.

7. Aug 2020 11:24 • januszk0 • This suggestion has not been analyzed by delopers yet:

But it is in the manual.

7. May 2021 17:29 • betchi • This suggestion has not been analyzed by delopers yet:

Let players have option to use their remaining potions on tie breaker, instead of selecting only one marble.

7. May 2021 18:41 • diamant • This suggestion has not been analyzed by delopers yet:

There was a discussion about the tie break rule here:
boardgamearena.com/forum/viewtopic.php?f=248&t=16259

I expressed my wish that it be allowed to use the remaining potions at the time of a player’s tie-break.

See also bug reports #19006 and #19060.

Add something to this report

Please add here anything that seems relevant to reproduce this bug or understand your suggestion:

Another table ID / move ID
Did F5 solve the problem?
Did the problem appears several time? Everytime? Randomly?
If you have a screenshot of this bug (good practice), you can use Imgur.com to upload it and copy/paste the link here.

LB_CANCEL Update report