@volkerk: I have only one thing to say: you don't have to be angry, just play with "Slow" or even "No time limit"
Fast turn based and other clock improvements
- sourisdudesert
- Administrateur
- Posts: 4630
- Joined: 23 January 2010, 22:02
- battletoad
- Posts: 3
- Joined: 25 June 2017, 01:35
Re: Fast turn based and other clock improvements
Great thoughtful changes!
Re: Fast turn based and other clock improvements
Very nice changes. Thanks for making BGA better and better!
Re: Fast turn based and other clock improvements
I would like to hear more about this algorithmic time measurement thing. Is this one-and-done type of situation, where times were calculated, adjusted and they will stay as such for some time or is this ongoing/live calculator, which would result in this spyral of less time=shorter average playing times=even less time for every game.
- sourisdudesert
- Administrateur
- Posts: 4630
- Joined: 23 January 2010, 22:02
Re: Fast turn based and other clock improvements
This is a live calculator (daily), but there is no spiral of less time => shorter average playing time => even less time for at least 2 reasons:Respublik wrote:I would like to hear more about this algorithmic time measurement thing.
_ we take into account the average time of ALL players, including those who go over time.
_ we have an important margin compared to the average time (in fact, it is important enough to have the exact opposite dynamic - to increase thinking time - if needed).
I extracted the logs for Carcassonne. As you can see from December 21th to today, the additional time per turn vary from 36 seconds to 38 seconds, so this is quite stable.
22/12 06:31:02 [info] carcassonne: table.player founds: 2712 - - Avg/turn = 17.07s - deviation = 75.57% - Bonus 37s => 37s
23/12 06:31:02 [info] carcassonne: table.player founds: 3419 - - Avg/turn = 17.23s - deviation = 75.21% - Bonus 37s => 38s
24/12 06:31:03 [info] carcassonne: table.player founds: 4263 - - Avg/turn = 17.1s - deviation = 74.81% - Bonus 38s => 37s
25/12 06:31:02 [info] carcassonne: table.player founds: 5005 - - Avg/turn = 17.1s - deviation = 74.72% - Bonus 37s => 37s
26/12 06:31:02 [info] carcassonne: table.player founds: 5003 - - Avg/turn = 17.14s - deviation = 74.53% - Bonus 37s => 37s
27/12 06:31:03 [info] carcassonne: table.player founds: 4981 - - Avg/turn = 17.33s - deviation = 74.16% - Bonus 37s => 38s
28/12 06:31:02 [info] carcassonne: table.player founds: 4984 - - Avg/turn = 17.38s - deviation = 73.77% - Bonus 38s => 37s
29/12 06:31:03 [info] carcassonne: table.player founds: 5061 - - Avg/turn = 17.34s - deviation = 73.42% - Bonus 37s => 37s
30/12 06:31:02 [info] carcassonne: table.player founds: 5205 - - Avg/turn = 17.05s - deviation = 73.36% - Bonus 37s => 37s
31/12 06:31:02 [info] carcassonne: table.player founds: 5078 - - Avg/turn = 17.16s - deviation = 73.09% - Bonus 37s => 37s
01/01 06:31:03 [info] carcassonne: table.player founds: 4968 - - Avg/turn = 17.2s - deviation = 73.03% - Bonus 37s => 37s
02/01 06:31:02 [info] carcassonne: table.player founds: 5038 - - Avg/turn = 17.23s - deviation = 72.76% - Bonus 37s => 37s
03/01 06:31:03 [info] carcassonne: table.player founds: 5166 - - Avg/turn = 17.29s - deviation = 72.94% - Bonus 37s => 37s
04/01 06:31:03 [info] carcassonne: table.player founds: 5329 - - Avg/turn = 17.12s - deviation = 73.39% - Bonus 37s => 37s
05/01 06:31:04 [info] carcassonne: table.player founds: 5311 - - Avg/turn = 17.21s - deviation = 73.87% - Bonus 37s => 37s
06/01 06:31:04 [info] carcassonne: table.player founds: 5293 - - Avg/turn = 17.57s - deviation = 74.25% - Bonus 37s => 38s
07/01 06:31:03 [info] carcassonne: table.player founds: 5345 - - Avg/turn = 17.72s - deviation = 74.15% - Bonus 38s => 38s
08/01 06:31:03 [info] carcassonne: table.player founds: 5490 - - Avg/turn = 17.87s - deviation = 73.66% - Bonus 38s => 38s
09/01 06:31:03 [info] carcassonne: table.player founds: 5520 - - Avg/turn = 17.81s - deviation = 73.78% - Bonus 38s => 38s
10/01 06:31:03 [info] carcassonne: table.player founds: 5408 - - Avg/turn = 17.79s - deviation = 73.14% - Bonus 38s => 38s
11/01 06:31:03 [info] carcassonne: table.player founds: 5304 - - Avg/turn = 18.02s - deviation = 72.53% - Bonus 38s => 38s
12/01 06:31:03 [info] carcassonne: table.player founds: 5394 - - Avg/turn = 18.15s - deviation = 71.76% - Bonus 38s => 38s
13/01 06:31:03 [info] carcassonne: table.player founds: 5284 - - Avg/turn = 18.2s - deviation = 71.31% - Bonus 38s => 38s
14/01 06:31:02 [info] carcassonne: table.player founds: 5161 - - Avg/turn = 18.17s - deviation = 71.18% - Bonus 38s => 38s
15/01 06:31:02 [info] carcassonne: table.player founds: 5127 - - Avg/turn = 18.08s - deviation = 71.89% - Bonus 38s => 38s
16/01 06:31:02 [info] carcassonne: table.player founds: 4971 - - Avg/turn = 18.07s - deviation = 71.91% - Bonus 38s => 38s
17/01 06:31:03 [info] carcassonne: table.player founds: 4952 - - Avg/turn = 17.83s - deviation = 72.23% - Bonus 38s => 38s
18/01 06:31:03 [info] carcassonne: table.player founds: 4918 - - Avg/turn = 17.61s - deviation = 72.81% - Bonus 38s => 38s
19/01 06:31:03 [info] carcassonne: table.player founds: 5016 - - Avg/turn = 17.39s - deviation = 73.69% - Bonus 38s => 37s
20/01 06:31:03 [info] carcassonne: table.player founds: 5060 - - Avg/turn = 17.12s - deviation = 73.91% - Bonus 37s => 37s
21/01 06:31:02 [info] carcassonne: table.player founds: 5189 - - Avg/turn = 17.25s - deviation = 73.56% - Bonus 37s => 37s
22/01 06:31:03 [info] carcassonne: table.player founds: 5190 - - Avg/turn = 17.04s - deviation = 73.16% - Bonus 37s => 37s
23/01 06:31:04 [info] carcassonne: table.player founds: 5384 - - Avg/turn = 16.9s - deviation = 73.25% - Bonus 37s => 36s
24/01 06:31:02 [info] carcassonne: table.player founds: 5410 - - Avg/turn = 16.93s - deviation = 73.72% - Bonus 36s => 36s
25/01 06:31:02 [info] carcassonne: table.player founds: 5426 - - Avg/turn = 16.9s - deviation = 74.49% - Bonus 36s => 37s
26/01 06:31:02 [info] carcassonne: table.player founds: 5340 - - Avg/turn = 16.94s - deviation = 74.11% - Bonus 37s => 37s
Re: Fast turn based and other clock improvements
EVERY time I try to select fast-turn based games, I get an error message that reads "invalid option." Has anyone else had this problem?
I love the idea and am a little frustrated that I can't use this feature.
I love the idea and am a little frustrated that I can't use this feature.
-
- Posts: 3
- Joined: 03 May 2018, 00:15
Re: Fast turn based and other clock improvements
How to change the night time?
It shows 3:00 to 15:00, doesn't match my sleeping time
It shows 3:00 to 15:00, doesn't match my sleeping time
- sourisdudesert
- Administrateur
- Posts: 4630
- Joined: 23 January 2010, 22:02
Re: Fast turn based and other clock improvements
When you create a table, if you select "Fast turn based" as the game speed, there is a new option "Playing hours" where you can define the night time.sosankable wrote:How to change the night time?
If the Playing hours shows 3:00 to 15:00 on an existing table, this is probably because the creator of this table is living in an another part of the world: you shouldn't join this table.
- RicardoRix
- Posts: 2115
- Joined: 29 April 2012, 23:43
Re: Fast turn based and other clock improvements
With the idea of trying to pair players with similar time restraints and playing habits, is it possible to add a statistic to a players profile of say, the average time to make a turn-based move in any given day where they have at least 1 current turn based game, maybe just in the last 30 days to be currently relevant
Or if that is too hard to calculate and perhaps slightly obscure, what about simply just the average moves made per day / #games in rota.
This should give you an in-sight on just how many turns they will be playing. Not everyone sets up their table with strict time limits yet play very quickly anyway.
------------edit---------------
Actually the average number of moves is not very relevant, they might be very fast players but the games might be very slow. So the first average time when it's your turn would be better. This statistic for each game is shown at the end of the game so somehow if you can collate this over all a players turn-based game rota.
Or if that is too hard to calculate and perhaps slightly obscure, what about simply just the average moves made per day / #games in rota.
This should give you an in-sight on just how many turns they will be playing. Not everyone sets up their table with strict time limits yet play very quickly anyway.
------------edit---------------
Actually the average number of moves is not very relevant, they might be very fast players but the games might be very slow. So the first average time when it's your turn would be better. This statistic for each game is shown at the end of the game so somehow if you can collate this over all a players turn-based game rota.
Last edited by RicardoRix on 30 January 2019, 00:34, edited 1 time in total.
Re: Fast turn based and other clock improvements
On a similar note, it would be awesome to be able to limit a game's access based on how "active" a turn-based player is. I can't state how annoying it is to get a very highly rated player into a turn based game and see that they have no other turn based games and then they end up just forgetting this game exists. Even having high karma and ELO says nothing about how active you are on turn based games.RicardoRix wrote:With the idea of trying to pair players with similar time restraints and playing habits, is it possible to add a statistic to a players profile of say, the average time to make a turn-based move in any given day where they have at least 1 current turn based game, maybe just in the last 30 days to be currently relevant
Or if that is too hard to calculate and perhaps slightly obscure, what about simply just the average moves made per day / #games in rota.
This should give you an in-sight on just how many turns they will be playing. Not everyone sets up their table with strict time limits yet play very quickly anyway.