The current filter in the games page that lets you choose 'short', 'medium', or 'long' games works well when playing live, but playing turn-based is very different when it comes to game length. The time a turn-based game takes to play is more about the number of turns than about thinking time, and it would be nice if we could have a filter for that It could be "usual number of turns" instead of speed.
When I'm looking for a new turn-based game, sometimes I'd like to know how many turns it's going to take to decide if it will be days or months of playing. Currently there is no way to even see that stat, much less filter for it.
As an example of the problem: A game like Fairy Trails usually only takes a few minutes when played live because thinking time per move is really low, BUT there are 60 tiles in the stack, and if you play turn based at 1 turn/day, that means a game could potentially take two months. :O
On the other side: a game like Small World could take 30-45min real time, but since a whole game (2-player) is only 20 turns, it could potentially finish a lot faster than a 'short' game of Fairy Trails when played 1 turn/day.
I entered the suggestion in the system here: https://boardgamearena.com/bug?id=202929
When I'm looking for a new turn-based game, sometimes I'd like to know how many turns it's going to take to decide if it will be days or months of playing. Currently there is no way to even see that stat, much less filter for it.
As an example of the problem: A game like Fairy Trails usually only takes a few minutes when played live because thinking time per move is really low, BUT there are 60 tiles in the stack, and if you play turn based at 1 turn/day, that means a game could potentially take two months. :O
On the other side: a game like Small World could take 30-45min real time, but since a whole game (2-player) is only 20 turns, it could potentially finish a lot faster than a 'short' game of Fairy Trails when played 1 turn/day.
I entered the suggestion in the system here: https://boardgamearena.com/bug?id=202929