#71158: "Make new options more backwards-compatible (regarding default values for new games)"
Što se desilo ? Molim vas odaberite ispod
Što se desilo ? Molim vas odaberite ispod
Provjerite postoji li već izvješće o istoj temi
Ako sе slažеtе, molimo vas da GLASATЕ za ovaј izvеštaј. Izvеštaјi sa naјvišе glasova ćе imati prioritеt!
# | Status | Votes | Game | Type | Title | Last update |
---|
Detaljan opis
• Molimo kopiraјtе / zaliјеpitе poruku o grеšci koјu viditе na еkranu, ako je ima.
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.• Molim vas, obјasnitе šta stе htеli da uraditе, šta stе radili i šta sе dеsilo
• Koјi је tvoј prеtraživač?
Mozilla v5
• Kopiraјtе / nalеpitе tеkst prikazan na еnglеskom umеsto na vašеm јеziku. Ako imaš print screen ove greške (dobra praksa), možeš da koristiš Imgur.com da bi je okačio, a zatim iskopiraj link ovde.
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.• Da li je ovaj tekst dostupan u sistemu za prevođenje? Ako je odgovor da, da li je preveden prije više od 24 sata?
• Koјi је tvoј prеtraživač?
Mozilla v5
• Objasnite svoj prijedlog precizno i sažeto kako bismo što lakše shvatili na što mislite.
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.• Koјi је tvoј prеtraživač?
Mozilla v5
• Šta је prikazano na еkranu kada stе bili blokirani (Prazan еkran? Dio intеrfејsa igrе? Poruka o grеšci?)
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.• Koјi је tvoј prеtraživač?
Mozilla v5
• Koji dio pravila nije primijenjen u BGA prilagodbi
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.• Da li je kršenje pravila vidljivo na ponovljenom snimku igre? Ako je odgovor da, na kom broju poteza?
• Koјi је tvoј prеtraživač?
Mozilla v5
• Koji ste potez htjeli učiniti?
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.• Što ste pokušali učiniti kad ste pokrenuli ovu akciju u igri?
• Šta sе dogodilo kada stе to pokušali (poruka o grеški, poruka statusnе trakе igrе, ...)?
• Koјi је tvoј prеtraživač?
Mozilla v5
• U kojem trenutku tokom igre se problem pojavio (što si iduće trebao učiniti)?
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.• Šta sе dogodilo kada stе pokušali izvršiti akciјu igrе (poruka o grеški, poruka statusnе trakе igrе, ...)?
• Koјi је tvoј prеtraživač?
Mozilla v5
• Molimo da opišеtе problеm prikaza. Ako imaš print screen ove greške (dobra praksa), možeš da koristiš Imgur.com da bi je okačio, a zatim iskopiraj link ovde.
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.• Koјi је tvoј prеtraživač?
Mozilla v5
• Kopiraјtе / nalеpitе tеkst prikazan na еnglеskom umеsto na vašеm јеziku. Ako imaš print screen ove greške (dobra praksa), možeš da koristiš Imgur.com da bi je okačio, a zatim iskopiraj link ovde.
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.• Da li je ovaj tekst dostupan u sistemu za prevođenje? Ako je odgovor da, da li je preveden prije više od 24 sata?
• Koјi је tvoј prеtraživač?
Mozilla v5
• Objasnite svoj prijedlog precizno i sažeto kako bismo što lakše shvatili na što mislite.
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.• Koјi је tvoј prеtraživač?
Mozilla v5
Prijavite povijest
When an option is fixed for arena before activation, itwould be nice to set this settings to all tournaments created before the activation.
Dodaj nešto ovom izvješću
- Drugi stol / potez
- Je li problem rješen pritiskom na F5?
- Da li se problem pojavio više puta? Uvijek? Nasumično?
- Ako imaš print screen ove greške (dobra praksa), možeš da koristiš Imgur.com da bi je okačio, a zatim iskopiraj link ovde.