#71158: "Make new options more backwards-compatible (regarding default values for new games)"
Mitä tapahtui? Valitse alta
Mitä tapahtui? Valitse alta
Ennen ilmoituksen tekoa, tarkista onko sellainen jo olemassa samasta aiheesta
Jos kyllä, ole ystävällinen ja ÄÄNESTÄ tätä raporttia. Eniten ääniä saaneet raportit laitetaan ETUSIJALLE!
# | Status | Votes | Game | Type | Title | Last update |
---|
Tarkka kuvaus
• Kopioi/liitä virheilmoitus näytöltäsi, jos sait sellaisen.
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.• Selitä mitä halusit tehdä, mitä teit ja mitä tapahtui
• Mikä on selaimesi?
Mozilla v5
• Ole hyvä ja kopioi teksti englanniksi oman kielesi sijasta. Jos sinulla on kuvankaappaus tästä bugista, voit käyttää Imgur.com:a sen lähettämiseksi. Kopioi ja liitä linkki tähän.
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.• Onko tämä teksti saatavilla käännösjärjestelmässä? Jos on, onko sen käännöksestä yli 24 tuntia?
• Mikä on selaimesi?
Mozilla v5
• Selitä ehdotuksesti tarkasti ja ytimekkäästi, jotta se on ymmärrettävissä niin helposti kuin mahdollista.
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.• Mikä on selaimesi?
Mozilla v5
• Mitä näytöllä näkyi kun olit estettynä (Tyhjä ruutu? Osa pelin käyttöliittymästä? Virheilmoitus?)
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.• Mikä on selaimesi?
Mozilla v5
• Mitä osaa säännöistä BGA:n sovellus ei noudattanut
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.• Onko sääntörikkomus nähtävillä pelin toistossa? Jos kyllä, mikä on siirron numero?
• Mikä on selaimesi?
Mozilla v5
• Minkä pelin toiminnon halusit suorittaa?
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.• Mitä yritit tehdä tämän pelitoiminnon käynnistymiseksi?
• Mitä tapahtui kun yritit tehdä tämän (virheilmoitus, pelin tilapalkin viesti, ...)?
• Mikä on selaimesi?
Mozilla v5
• Missä vaiheessa peliä ongelma ilmeni (mikä oli silloinen pelin ohje)?
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.• Mitä tapahtui kun yritit tehdä tämän pelin toiminnon (virheilmoitus, pelin tilapalkin viesti, ...)?
• Mikä on selaimesi?
Mozilla v5
• Kuvaile näyttöongelmaa. Jos sinulla on kuvankaappaus tästä bugista, voit käyttää Imgur.com:a sen lähettämiseksi. Kopioi ja liitä linkki tähän.
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.• Mikä on selaimesi?
Mozilla v5
• Ole hyvä ja kopioi teksti englanniksi oman kielesi sijasta. Jos sinulla on kuvankaappaus tästä bugista, voit käyttää Imgur.com:a sen lähettämiseksi. Kopioi ja liitä linkki tähän.
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.• Onko tämä teksti saatavilla käännösjärjestelmässä? Jos on, onko sen käännöksestä yli 24 tuntia?
• Mikä on selaimesi?
Mozilla v5
• Selitä ehdotuksesti tarkasti ja ytimekkäästi, jotta se on ymmärrettävissä niin helposti kuin mahdollista.
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.• Mikä on selaimesi?
Mozilla v5
Raportin historia
When an option is fixed for arena before activation, itwould be nice to set this settings to all tournaments created before the activation.
Lisää jotain tähän raporttiin
- Toinen pöydän tunnus / siirron numero
- Ratkaisiko F5 ongelman?
- Ilmestyykö ongelma useita kertoja? Joka kerta? Satunnaisesti?
- Jos sinulla on kuvankaappaus tästä bugista, voit käyttää Imgur.com:a sen lähettämiseksi. Kopioi ja liitä linkki tähän.