#71158: "Make new options more backwards-compatible (regarding default values for new games)"
Apa yang terjadi? Pilih di bawah
Apa yang terjadi? Pilih di bawah
Silakan periksa apakah sudah ada laporan tentang hal yang sama
Jika ya, silakan VOTE untuk laporan ini. Laporan dengan suara terbanyak diberikan PRIORITAS!
# | Status | Votes | Game | Type | Title | Last update |
---|
Detil Deskripsi
• Mohon salin/tempel pesan error yang Anda lihat di layar, jika ada.
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.• Mohon jelaskan apa yang ingin Anda lakukan, apa yang kemudian Anda lakukan, dan apa yang terjadi
• Apa browser yang Anda gunakan?
Mozilla v5
• Harap salin/tempel teks yang ditampilkan dalam bahasa Inggris alih-alih bahasa anda. Jika Anda memiliki screenshot bug ini (disarankan), Anda dapat menggunakan Imgur.com untuk menguploadnya dan memberi tautannya di sini.
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.• apakah teks ini tersedia dalam translation system? jika iya, itu bisa diartikan lebih dari 24 jam
• Apa browser yang Anda gunakan?
Mozilla v5
• Tolong jelaskan saran Anda secara tepat dan ringkas sehingga semudah mungkin untuk memahami apa yang Anda maksud.
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.• Apa browser yang Anda gunakan?
Mozilla v5
• Apa yang tampil di layar ketika Anda tidak dapat berjalan (Layar kosong? Hanya tampil sebagian antar-muka? Pesan error?)
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.• Apa browser yang Anda gunakan?
Mozilla v5
• Bagian mana dari peraturan yang tidak diterapkan dengan tepat oleh 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.• Apakah kesalahan peraturan dapat dilihat dari ulangan permainan? Jika ya, pada langkah ke berapa?
• Apa browser yang Anda gunakan?
Mozilla v5
• Aksi permainan apa yang ingin Anda lakukan?
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.• Apa yang Anda coba lakukan untuk memunculkan aksi permainan ini?
• Apa yang terjadi ketika Anda melakukannya (pesan error, pesan status permainan, ...)?
• Apa browser yang Anda gunakan?
Mozilla v5
• Pada langkah ke berapa masalah tersebut muncul (apa petunjuk permainan saat itu)?
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.• Apa yang terjadi ketika Anda mencoba untuk melakukan aksi permainan (pesan error, pesan status permainan, ...)?
• Apa browser yang Anda gunakan?
Mozilla v5
• Mohon jelaskan masalah tampilannya. Jika Anda memiliki screenshot bug ini (disarankan), Anda dapat menggunakan Imgur.com untuk menguploadnya dan memberi tautannya di sini.
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.• Apa browser yang Anda gunakan?
Mozilla v5
• Harap salin/tempel teks yang ditampilkan dalam bahasa Inggris alih-alih bahasa anda. Jika Anda memiliki screenshot bug ini (disarankan), Anda dapat menggunakan Imgur.com untuk menguploadnya dan memberi tautannya di sini.
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.• apakah teks ini tersedia dalam translation system? jika iya, itu bisa diartikan lebih dari 24 jam
• Apa browser yang Anda gunakan?
Mozilla v5
• Tolong jelaskan saran Anda secara tepat dan ringkas sehingga semudah mungkin untuk memahami apa yang Anda maksud.
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.• Apa browser yang Anda gunakan?
Mozilla v5
Laporkan riwayat
When an option is fixed for arena before activation, itwould be nice to set this settings to all tournaments created before the activation.
Tambahkan hal lain di laporan ini
- ID meja / nomor langkah lainnya
- Apakah F5 menyelesaikan masalah?
- Apakah masalah tersebut telah muncul beberapa kali? Setiap kali? Tidak tentu?
- Jika Anda memiliki screenshot bug ini (disarankan), Anda dapat menggunakan Imgur.com untuk menguploadnya dan memberi tautannya di sini.