#71158: "Make new options more backwards-compatible (regarding default values for new games)"
Co se stalo? Prosím vyberte níže
Co se stalo? Prosím vyberte níže
Prosím zkontroluj, zda již neexistuje hlášení pro stejnou věc
Pokud ano, HLASUJ pro toto hlášení. Hlášení s nejvyšším počtem hlasů budou řešena PŘEDNOSTNĚ!
# | Status | Votes | Game | Type | Title | Last update |
---|
Detailní popis
• Prosím, zkopíruj a vlož hlášení o chybě, které vidíš na monitoru, pokud to lze.
Time and time again we see forum reports about new game options that have wrong values in Arena or tournament games. For example, a new expansion is added to the game in the middle of a season, and suddenly all new Arena games start with the expansion enabled, when previous games in the same season did not have the expansion. Apparently, this is because the Arena season did not have a value stored for the new option (because it didn't exist when the season started) and then it picks up whatever default is set for new games. Solving this seems to require some manual admin intervention.
I know nothing about the BGA development framework, but it seems to me this could be addressed if for every new option added to a game the developer provided two associated values:
1. Default value for the option (enabled/disabled, number of cards, whatever the option is). This would be used for new games started from the lobby, unless the user actively changes the settings.
2. Value when missing, or value that corresponds to the old behaviour (before the option existed). This could be enabled or disabled, depending on what the option is, or something else. Tournament and Arena games should use this value if they were set up before the option was implemented.• Prosím popiš, co jsi měl v úmyslu udělat, co jsi udělal a co se nakonec stalo
• Jaký prohlížeč používáte?
Mozilla v5
• Prosíme, zkopíruj/vlož text zobrazený v angličtině namísto tvého jazyka. 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.
Time and time again we see forum reports about new game options that have wrong values in Arena or tournament games. For example, a new expansion is added to the game in the middle of a season, and suddenly all new Arena games start with the expansion enabled, when previous games in the same season did not have the expansion. Apparently, this is because the Arena season did not have a value stored for the new option (because it didn't exist when the season started) and then it picks up whatever default is set for new games. Solving this seems to require some manual admin intervention.
I know nothing about the BGA development framework, but it seems to me this could be addressed if for every new option added to a game the developer provided two associated values:
1. Default value for the option (enabled/disabled, number of cards, whatever the option is). This would be used for new games started from the lobby, unless the user actively changes the settings.
2. Value when missing, or value that corresponds to the old behaviour (before the option existed). This could be enabled or disabled, depending on what the option is, or something else. Tournament and Arena games should use this value if they were set up before the option was implemented.• Je tento text k dispozici v systému pro překládání? Pokud ano, byl přeložen před více než 24 hodinami?
• Jaký prohlížeč používáte?
Mozilla v5
• Prosím popiš svůj návrh přesně a konzistentně, aby bylo snadné pochopit, co máš na mysli.
Time and time again we see forum reports about new game options that have wrong values in Arena or tournament games. For example, a new expansion is added to the game in the middle of a season, and suddenly all new Arena games start with the expansion enabled, when previous games in the same season did not have the expansion. Apparently, this is because the Arena season did not have a value stored for the new option (because it didn't exist when the season started) and then it picks up whatever default is set for new games. Solving this seems to require some manual admin intervention.
I know nothing about the BGA development framework, but it seems to me this could be addressed if for every new option added to a game the developer provided two associated values:
1. Default value for the option (enabled/disabled, number of cards, whatever the option is). This would be used for new games started from the lobby, unless the user actively changes the settings.
2. Value when missing, or value that corresponds to the old behaviour (before the option existed). This could be enabled or disabled, depending on what the option is, or something else. Tournament and Arena games should use this value if they were set up before the option was implemented.• Jaký prohlížeč používáte?
Mozilla v5
• Co bylo zobrazeno na monitoru, když došlo k tvému zablokování? (Černá obrazovka? Část herního prostředí? Hlášení o chybě?)
Time and time again we see forum reports about new game options that have wrong values in Arena or tournament games. For example, a new expansion is added to the game in the middle of a season, and suddenly all new Arena games start with the expansion enabled, when previous games in the same season did not have the expansion. Apparently, this is because the Arena season did not have a value stored for the new option (because it didn't exist when the season started) and then it picks up whatever default is set for new games. Solving this seems to require some manual admin intervention.
I know nothing about the BGA development framework, but it seems to me this could be addressed if for every new option added to a game the developer provided two associated values:
1. Default value for the option (enabled/disabled, number of cards, whatever the option is). This would be used for new games started from the lobby, unless the user actively changes the settings.
2. Value when missing, or value that corresponds to the old behaviour (before the option existed). This could be enabled or disabled, depending on what the option is, or something else. Tournament and Arena games should use this value if they were set up before the option was implemented.• Jaký prohlížeč používáte?
Mozilla v5
• Která část pravidel nebyla dodržena adaptací hry na BGA
Time and time again we see forum reports about new game options that have wrong values in Arena or tournament games. For example, a new expansion is added to the game in the middle of a season, and suddenly all new Arena games start with the expansion enabled, when previous games in the same season did not have the expansion. Apparently, this is because the Arena season did not have a value stored for the new option (because it didn't exist when the season started) and then it picks up whatever default is set for new games. Solving this seems to require some manual admin intervention.
I know nothing about the BGA development framework, but it seems to me this could be addressed if for every new option added to a game the developer provided two associated values:
1. Default value for the option (enabled/disabled, number of cards, whatever the option is). This would be used for new games started from the lobby, unless the user actively changes the settings.
2. Value when missing, or value that corresponds to the old behaviour (before the option existed). This could be enabled or disabled, depending on what the option is, or something else. Tournament and Arena games should use this value if they were set up before the option was implemented.• Je vidět porušení pravidel na záznamu hry? Pokud ano, ve kterém tahu?
• Jaký prohlížeč používáte?
Mozilla v5
• O jakou herní akci ses pokoušel/a?
Time and time again we see forum reports about new game options that have wrong values in Arena or tournament games. For example, a new expansion is added to the game in the middle of a season, and suddenly all new Arena games start with the expansion enabled, when previous games in the same season did not have the expansion. Apparently, this is because the Arena season did not have a value stored for the new option (because it didn't exist when the season started) and then it picks up whatever default is set for new games. Solving this seems to require some manual admin intervention.
I know nothing about the BGA development framework, but it seems to me this could be addressed if for every new option added to a game the developer provided two associated values:
1. Default value for the option (enabled/disabled, number of cards, whatever the option is). This would be used for new games started from the lobby, unless the user actively changes the settings.
2. Value when missing, or value that corresponds to the old behaviour (before the option existed). This could be enabled or disabled, depending on what the option is, or something else. Tournament and Arena games should use this value if they were set up before the option was implemented.• Co ses pokoušel/a udělat, abys spustil/a tuhle herní akci?
• Co se stalo, když ses o tuto akci pokusil/a (vyskočila chybová hláška, lišta ve hře, ...)?
• Jaký prohlížeč používáte?
Mozilla v5
• V jaké fázi hry problém nastal (jaký byl poslední herní pokyn)?
Time and time again we see forum reports about new game options that have wrong values in Arena or tournament games. For example, a new expansion is added to the game in the middle of a season, and suddenly all new Arena games start with the expansion enabled, when previous games in the same season did not have the expansion. Apparently, this is because the Arena season did not have a value stored for the new option (because it didn't exist when the season started) and then it picks up whatever default is set for new games. Solving this seems to require some manual admin intervention.
I know nothing about the BGA development framework, but it seems to me this could be addressed if for every new option added to a game the developer provided two associated values:
1. Default value for the option (enabled/disabled, number of cards, whatever the option is). This would be used for new games started from the lobby, unless the user actively changes the settings.
2. Value when missing, or value that corresponds to the old behaviour (before the option existed). This could be enabled or disabled, depending on what the option is, or something else. Tournament and Arena games should use this value if they were set up before the option was implemented.• Co se stalo, když ses pokusil/a udělat akci (chybová hláška, oznámení stavového řádku hry, ...)?
• Jaký prohlížeč používáte?
Mozilla v5
• Prosím popište vyobrazený problém. 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.
Time and time again we see forum reports about new game options that have wrong values in Arena or tournament games. For example, a new expansion is added to the game in the middle of a season, and suddenly all new Arena games start with the expansion enabled, when previous games in the same season did not have the expansion. Apparently, this is because the Arena season did not have a value stored for the new option (because it didn't exist when the season started) and then it picks up whatever default is set for new games. Solving this seems to require some manual admin intervention.
I know nothing about the BGA development framework, but it seems to me this could be addressed if for every new option added to a game the developer provided two associated values:
1. Default value for the option (enabled/disabled, number of cards, whatever the option is). This would be used for new games started from the lobby, unless the user actively changes the settings.
2. Value when missing, or value that corresponds to the old behaviour (before the option existed). This could be enabled or disabled, depending on what the option is, or something else. Tournament and Arena games should use this value if they were set up before the option was implemented.• Jaký prohlížeč používáte?
Mozilla v5
• Prosíme, zkopíruj/vlož text zobrazený v angličtině namísto tvého jazyka. 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.
Time and time again we see forum reports about new game options that have wrong values in Arena or tournament games. For example, a new expansion is added to the game in the middle of a season, and suddenly all new Arena games start with the expansion enabled, when previous games in the same season did not have the expansion. Apparently, this is because the Arena season did not have a value stored for the new option (because it didn't exist when the season started) and then it picks up whatever default is set for new games. Solving this seems to require some manual admin intervention.
I know nothing about the BGA development framework, but it seems to me this could be addressed if for every new option added to a game the developer provided two associated values:
1. Default value for the option (enabled/disabled, number of cards, whatever the option is). This would be used for new games started from the lobby, unless the user actively changes the settings.
2. Value when missing, or value that corresponds to the old behaviour (before the option existed). This could be enabled or disabled, depending on what the option is, or something else. Tournament and Arena games should use this value if they were set up before the option was implemented.• Je tento text k dispozici v systému pro překládání? Pokud ano, byl přeložen před více než 24 hodinami?
• Jaký prohlížeč používáte?
Mozilla v5
• Prosím popiš svůj návrh přesně a konzistentně, aby bylo snadné pochopit, co máš na mysli.
Time and time again we see forum reports about new game options that have wrong values in Arena or tournament games. For example, a new expansion is added to the game in the middle of a season, and suddenly all new Arena games start with the expansion enabled, when previous games in the same season did not have the expansion. Apparently, this is because the Arena season did not have a value stored for the new option (because it didn't exist when the season started) and then it picks up whatever default is set for new games. Solving this seems to require some manual admin intervention.
I know nothing about the BGA development framework, but it seems to me this could be addressed if for every new option added to a game the developer provided two associated values:
1. Default value for the option (enabled/disabled, number of cards, whatever the option is). This would be used for new games started from the lobby, unless the user actively changes the settings.
2. Value when missing, or value that corresponds to the old behaviour (before the option existed). This could be enabled or disabled, depending on what the option is, or something else. Tournament and Arena games should use this value if they were set up before the option was implemented.• Jaký prohlížeč používáte?
Mozilla v5
Historie hlášení
When an option is fixed for arena before activation, itwould be nice to set this settings to all tournaments created before the activation.
Doplňte tuto zprávu
- 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.