#71158: "Make new options more backwards-compatible (regarding default values for new games)"
Petra a zo c'hoarvezet ? Trugarez evit dibab amañ dindan
Petra a zo c'hoarvezet ? Trugarez evit dibab amañ dindan
Gwiriit mar-plij ma n'eus ket dija un danevell evit an hevelep dodenn
M'oc'h a-du, VOTIT evit an danevell-mañ. An danevelloù gant ar muiañ a vouezhioù a vo studiet DA GENTAÑ !
# | Status | Votes | Game | Type | Title | Last update |
---|
Deskrivadur dre ar munud
• Mar-plij, eilit/pegit ar gemennadenn fazi a zo war ho skramm, ma zo unan.
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.• Displegit deomp, mar-plij, ar pezh ho poa c'hoant d'ober, ar pezh ho peus graet hag ar pezh a zo c'hoarvezet 'benn ar fin
• Peseurt merdeer eo hoc'h hini ?
Mozilla v5
• Mar-plij, eilit/pegit an destenn e Saozneg ha n'eo ket en ho yezh. M'ho peus ul lennad skramm eus ar gudenn (ho pezit soñj d'eus se !), gellout a rit implij Imgur.com evit e bellgargañ hag eilañ/pegañ al liamm amañ.
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.• Ha dibres eo an destenn-mañ er sistem treiñ? Ma ya, daoust ha troet eo bet ouzhpenn 24 eur 'zo ?
• Peseurt merdeer eo hoc'h hini ?
Mozilla v5
• Displegit ho kinnig mar-plij, e berrgomzoù met en un doare resis, evit ma vefe an aesañ posupl kompren mat ar pezh ho peus c'hoant lâret.
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.• Peseurt merdeer eo hoc'h hini ?
Mozilla v5
• What was displayed on the screen when you were blocked (Blank screen? Part of the game interface? Error message?)
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.• Peseurt merdeer eo hoc'h hini ?
Mozilla v5
• Which part of the rules was not respected by the BGA adaptation
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.• Ha posupl eo gwelet torridigezh ar reolenn e replay ar bartienn ? Ma 'z eo ya, da be niverenn taol ?
• Peseurt merdeer eo hoc'h hini ?
Mozilla v5
• Peseurt taol ho peus c'hoant c'hoari ?
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.• Petra emaoc'h o klask ober evit delankañ an ober c'hoari-mañ ?
• What happened when you try to do this (error message, game status bar message, ...)?
• Peseurt merdeer eo hoc'h hini ?
Mozilla v5
• Da be bazenn ar bartienn eo en em gavet ar gudenn (petra oa testenn kemenn ar c'hoari) ?
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.• What happened when you try to do a game action (error message, game status bar message, ...)?
• Peseurt merdeer eo hoc'h hini ?
Mozilla v5
• Mar-plij, diskrivit kudenn an diskwel. M'ho peus ul lennad skramm eus ar gudenn (ho pezit soñj d'eus se !), gellout a rit implij Imgur.com evit e bellgargañ hag eilañ/pegañ al liamm amañ.
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.• Peseurt merdeer eo hoc'h hini ?
Mozilla v5
• Mar-plij, eilit/pegit an destenn e Saozneg ha n'eo ket en ho yezh. M'ho peus ul lennad skramm eus ar gudenn (ho pezit soñj d'eus se !), gellout a rit implij Imgur.com evit e bellgargañ hag eilañ/pegañ al liamm amañ.
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.• Ha dibres eo an destenn-mañ er sistem treiñ? Ma ya, daoust ha troet eo bet ouzhpenn 24 eur 'zo ?
• Peseurt merdeer eo hoc'h hini ?
Mozilla v5
• Displegit ho kinnig mar-plij, e berrgomzoù met en un doare resis, evit ma vefe an aesañ posupl kompren mat ar pezh ho peus c'hoant lâret.
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.• Peseurt merdeer eo hoc'h hini ?
Mozilla v5
Roll-istor an danevelloù bog
When an option is fixed for arena before activation, itwould be nice to set this settings to all tournaments created before the activation.
Ouzhpennañ un dra bennak d'an danevell-mañ
- Niverenn taol all / Niverenn ar fiñv
- Ha renket eo bet ar gudenn gant an douchenn F5 ?
- Ha c'hoarvezet eo ar gudenn meur a wech ? Bewech ? Cheñch-dicheñch ?
- M'ho peus ul lennad skramm eus ar gudenn (ho pezit soñj d'eus se !), gellout a rit implij Imgur.com evit e bellgargañ hag eilañ/pegañ al liamm amañ.