Include more parameters into the estimation of a game's time. For example the size of the board in Go.
Posted: 08 January 2017, 03:05
As said in the title, my first idea was to trigger the estimated time for a Go game in relation with the size of the Goban : 9*9,13*13 or 19*19.
I started a Go game and noticed the estimated time was 24 minutes whatever size board I chose. This is not really good as the time will be very different between a 9*9 game or a 19*19 game.
This is a just an example of a particular game's option which really have an impact on the length of a game. Other Examples : in Hearts, the number a points you start with (75 or 100) ; in Belote, the number of points a team has to reach to win ; 6/12 rounds in Koï-Koï ; number of rounds in Hell ! (L'ascenseur) ; the type of map in Quantum ...
As it is now, I believe the only parameter used is the number of players. I think this might be useful to trigger the estimated time of a game using more parameters than just the average span. Especially options that are actually made to have an impact on the game's length.
When developing the game, the developer could indicate which options have a significant impact on a game's time and separate time estimations would be made, 1 for each state of this(those) option(s). For Go, there'd be an estimation for 9*9, one for 13*13, one for 19*19. And for games where the number of players can change too, this would require an estimation for each case. For Quantum : 5 dices map * 2 players, 5 dices map * 3 players, 5 dices map * 4 players, 6 dices map * 2 players etc.
People who already played several times to a particular game on this website know what kind of time they should expect, but when playing to a new game on BGA, this could be useful. This improvment isn't very important, and might be difficult since it could need to develop the way this time is calculated. Please consider it if you can
I started a Go game and noticed the estimated time was 24 minutes whatever size board I chose. This is not really good as the time will be very different between a 9*9 game or a 19*19 game.
This is a just an example of a particular game's option which really have an impact on the length of a game. Other Examples : in Hearts, the number a points you start with (75 or 100) ; in Belote, the number of points a team has to reach to win ; 6/12 rounds in Koï-Koï ; number of rounds in Hell ! (L'ascenseur) ; the type of map in Quantum ...
As it is now, I believe the only parameter used is the number of players. I think this might be useful to trigger the estimated time of a game using more parameters than just the average span. Especially options that are actually made to have an impact on the game's length.
When developing the game, the developer could indicate which options have a significant impact on a game's time and separate time estimations would be made, 1 for each state of this(those) option(s). For Go, there'd be an estimation for 9*9, one for 13*13, one for 19*19. And for games where the number of players can change too, this would require an estimation for each case. For Quantum : 5 dices map * 2 players, 5 dices map * 3 players, 5 dices map * 4 players, 6 dices map * 2 players etc.
People who already played several times to a particular game on this website know what kind of time they should expect, but when playing to a new game on BGA, this could be useful. This improvment isn't very important, and might be difficult since it could need to develop the way this time is calculated. Please consider it if you can