#71158: "Make new options more backwards-compatible (regarding default values for new games)"
Que s'est-il passé ? Merci de choisir ci-dessous
Que s'est-il passé ? Merci de choisir ci-dessous
Veuillez vérifier s'il existe déjà un rapport sur le même sujet
Si oui, veuillez VOTER pour ce rapport. Les rapports ayant le plus de votes auront la PRIORITÉ !
# | Status | Votes | Game | Type | Title | Last update |
---|
Description détaillée
• Merci de copier-coller le message d'erreur qui s'affiche à l'écran, s'il y a lieu.
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.• Veuillez expliquer ce que vous vouliez faire, ce que vous avez fait et ce qu'il s'est passé
• Quel est votre navigateur ?
Mozilla v5
• SVP copiez / collez ici le texte affiché en anglais au lieu de votre langue. Si vous avez une capture d'écran de ce bug (pensez-y !), vous pouvez utiliser Imgur.com pour la télécharger et copier-coller le lien ici.
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.• Ce texte est-il disponible dans le système de traduction ? Si oui, a-t-il été traduit depuis plus de 24 heures ?
• Quel est votre navigateur ?
Mozilla v5
• Merci d'expliquer votre suggestion de manière précise et concise, de façon à ce qu'il soit aussi simple que possible de comprendre ce que vous voulez dire.
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.• Quel est votre navigateur ?
Mozilla v5
• Qu'était-il affiché à l'écran lorsque vous avez été bloqué·e (Écran vierge ? Une partie de l'interface de jeu ? Un message d'erreur ?)
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.• Quel est votre navigateur ?
Mozilla v5
• Quelle partie des règles n'a pas été respectée par l'adaptation 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.• La violation de règle est-elle visible dans le replay de la partie ? Si oui, à quel numéro de coup ?
• Quel est votre navigateur ?
Mozilla v5
• Quelle action de jeu vouliez-vous faire ?
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.• Qu'essayez-vous de faire pour déclencher cette action de jeu ?
• Que se passe-t-il lorsque vous essayez de faire cela (message d'erreur, message de la barre d'état du jeu, ...) ?
• Quel est votre navigateur ?
Mozilla v5
• À quelle étape de la partie le problème est-il apparu (quel était le texte d'instruction du jeu) ?
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.• Que se passe-t-il lorsque vous essayez de faire une action de jeu (message d'erreur, message de la barre d'état du jeu, ...) ?
• Quel est votre navigateur ?
Mozilla v5
• Veuillez décrire le problème d'affichage. Si vous avez une capture d'écran de ce bug (pensez-y !), vous pouvez utiliser Imgur.com pour la télécharger et copier-coller le lien ici.
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.• Quel est votre navigateur ?
Mozilla v5
• SVP copiez / collez ici le texte affiché en anglais au lieu de votre langue. Si vous avez une capture d'écran de ce bug (pensez-y !), vous pouvez utiliser Imgur.com pour la télécharger et copier-coller le lien ici.
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.• Ce texte est-il disponible dans le système de traduction ? Si oui, a-t-il été traduit depuis plus de 24 heures ?
• Quel est votre navigateur ?
Mozilla v5
• Merci d'expliquer votre suggestion de manière précise et concise, de façon à ce qu'il soit aussi simple que possible de comprendre ce que vous voulez dire.
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.• Quel est votre navigateur ?
Mozilla v5
Historique des rapports de bug
When an option is fixed for arena before activation, itwould be nice to set this settings to all tournaments created before the activation.
Ajouter à ce rapport
- Un autre n° de table / n° de coup
- La touche F5 a-t-elle résolu le problème ?
- Le problème est-il apparu plusieurs fois ? À chaque fois ? Aléatoirement ?
- Si vous avez une capture d'écran de ce bug (pensez-y !), vous pouvez utiliser Imgur.com pour la télécharger et copier-coller le lien ici.