Všechna hlášení
Hlášení The Gnomes of Zavandor
#77727: "Some statistics would be great to improve the own strategy"
implemented: Tento návrh byl implementován
2
Čeho se toto hlášení týká?
Co se stalo? Prosím vyberte níže
Podnět: podle mého názoru by následující významně vylepšilo hru
Detailní popis
• Prosím popiš svůj návrh přesně a konzistentně, aby bylo snadné pochopit, co máš na mysli.
After playing TGOZ several times here on BGA we found out that it would be great to know some statistics to improve the own strategy.
The following statistics would be great to have:
- total number of moves per player (it is a big difference if you buy a Gnomunculus at beginning or at the end of the game...)
- how often did the player "take 4 gold" (per player)
- time divided by total number of moves (per player) (if you have a Gnomunculus you have more time!)
- max. spreading between actual costs for gem type x and gem type y (spreading = difference between actual cost of type x and type y --> max. spreading is max. difference which ever happened in the game)
and which were the type x and type y (e.g. max. spreading between emerald and diamond = 12). Note: It is NOT required to know the spreading between all types of gems, but just the maximum!
- average of max. spreading: spreading must be calculated once every round, i.e. after the mining phase. These values have to be added every round. At the end the average can be calculated by division: total sum/no. of mining phases
• Jaký prohlížeč používáte?
Mozilla 16.0.1
Historie hlášení
17. pro 2022 18:48 •
stefano • Tento návrh byl implementován:
20. pro 2022 9:53 • - total number of moves per player --> Added
- how often did the player "take 4 gold" (per player) --> Added
- time divided by total number of moves (per player) --> Not possible, I cannot make statistics on the time. BGA does some default ones, but I can't
- max. spreading between actual costs for gem type x and gem type y --> Not possible. Stats can be only integer or float values, not string. So I cannot show the gem type min and max
- average of max. spreading: spreading must be calculated once every round, i.e. after the mining phase. --> Not possible. Stats can be only integer or float values, not string. So I cannot show the gem type min and max
- how often did the player "take 4 gold" (per player) --> Added
- time divided by total number of moves (per player) --> Not possible, I cannot make statistics on the time. BGA does some default ones, but I can't
- max. spreading between actual costs for gem type x and gem type y --> Not possible. Stats can be only integer or float values, not string. So I cannot show the gem type min and max
- average of max. spreading: spreading must be calculated once every round, i.e. after the mining phase. --> Not possible. Stats can be only integer or float values, not string. So I cannot show the gem type min and max
PickAPig • Tento návrh byl implementován:
20. pro 2022 21:48 • Thanks for implementation!
Regarding the spreading: I think it is a misunderstanding because of my bad description...
The needed value is only an integer value :-)
It is not required to know what type of gem it was. x and y are just variables for the 4 gem types. It should be something like this:
for (x=0; x<4; x++)
{
for (y=0; y<4; y++)
{
diff = actual_costs[x] - actual_costs[y];
if (diff < 0 )
diff = - diff;
if ( diff > max_spreading )
max_spreading = diff;
}
}
Is this a better description?
Regarding the spreading: I think it is a misunderstanding because of my bad description...
The needed value is only an integer value :-)
It is not required to know what type of gem it was. x and y are just variables for the 4 gem types. It should be something like this:
for (x=0; x<4; x++)
{
for (y=0; y<4; y++)
{
diff = actual_costs[x] - actual_costs[y];
if (diff < 0 )
diff = - diff;
if ( diff > max_spreading )
max_spreading = diff;
}
}
Is this a better description?
PickAPig • Tento návrh byl implementován:
20. pro 2022 22:23 •
1. úno 2023 4:43 • So from my point of view max. spreading (integer) and average of max. spreading (float) should be possible
Doplňte tuto zprávu
Prosím přidej sem cokoli, co by mohlo být relevantní pro reprodukci této chyby nebo pochopení tvého návrhu:
- ID dalšího stolu / ID tahu
- Byla chyba odstraněna stisknutím F5?
- Objevila se tato chyba častěji? Pokaždé? Náhodně?
- Pokud máš snímek obrazvky zobrazující tuto chybu (doporučujeme!), můžeš použít Imgur.com pro nahrání obrázku a pak odkaz na tento obrázek na Imguru zkopírovat a vložit sem.