所有案件
{THIS_GAME_BUGS}
#71158: "Make new options more backwards-compatible (regarding default values for new games)"
#71158: "Make new options more backwards-compatible (regarding default values for new games)"
發生什麼事? 請從下方選擇
建議:依我所見,下列調整將大幅改善此站
發生什麼事? 請從下方選擇
建議:依我所見,下列調整將大幅改善此站
請檢查是否已有同課題案件
若肯定,請「投票」給這樁案件。最高票的案件將「優先」處理!
# | Status | Votes | Game | Type | Title | Last update |
---|
細節描述
• 如果可以的話,請轉貼螢幕顯示的錯誤訊息。
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.• 請說明你當時想做什麼,你做了什麼,然後發生了什麼事
• 你的瀏覽器是什麼?
Mozilla v5
• 請轉貼未翻譯的英文字句。 建議將此錯誤的螢幕截圖上傳到 Imgur.com 並轉貼連結。
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.• 這些文字存在於 翻譯系統 中嗎?若為真,其是否已被翻譯超過 24 小時?
• 你的瀏覽器是什麼?
Mozilla v5
• 請簡明精確地解釋你的建議,以便讓人一目了然。
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.• 你的瀏覽器是什麼?
Mozilla v5
• 當你不能動作時,螢幕上顯示什麼?(螢幕全黑?部份遊戲介面?錯誤訊息?)
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.• 你的瀏覽器是什麼?
Mozilla v5
• 遊戲規則的哪部分在 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.• 這項違反規則之處可否在遊戲重播中看到?若可以是在哪步?(重播時左上角資訊)
• 你的瀏覽器是什麼?
Mozilla v5
• 你當時想採取哪個遊戲行動?
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.• 你想觸發這個遊戲行動時做了什麼?
• 當你試著這麼做時發生了什麼(錯誤訊息、遊戲狀態條訊息...)?
• 你的瀏覽器是什麼?
Mozilla v5
• 問題發生在遊戲的哪一步?(當前遊戲指示是什麼)
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.• 當你試著進行遊戲動作時發生了什麼(錯誤訊息、遊戲狀態條訊息...)?
• 你的瀏覽器是什麼?
Mozilla v5
• 請描述顯示問題。 建議將此錯誤的螢幕截圖上傳到 Imgur.com 並轉貼連結。
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.• 你的瀏覽器是什麼?
Mozilla v5
• 請轉貼未翻譯的英文字句。 建議將此錯誤的螢幕截圖上傳到 Imgur.com 並轉貼連結。
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.• 這些文字存在於 翻譯系統 中嗎?若為真,其是否已被翻譯超過 24 小時?
• 你的瀏覽器是什麼?
Mozilla v5
• 請簡明精確地解釋你的建議,以便讓人一目了然。
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.• 你的瀏覽器是什麼?
Mozilla v5
案件沿革
2022年 9月 3日 12:35 • thoun • 此建議尚未被開發者分析過:
I know it was posted for King of Tokyo. For Arena, I make sure it is fixed to Disabled before releasing a new option, but every dev must ask admins to do that so they are some miss.
When an option is fixed for arena before activation, itwould be nice to set this settings to all tournaments created before the activation.
When an option is fixed for arena before activation, itwould be nice to set this settings to all tournaments created before the activation.
為本案件添加內容
任何可能重現這項錯誤或了解你的建議之相關資訊,都請在此填寫:
- 其他同樣狀況的桌號/步數
- 按 F5 是否解決了這個問題?
- 問題是否發生了好幾次?每次都發生?時好時壞?
- 建議將此錯誤的螢幕截圖上傳到 Imgur.com 並轉貼連結。
更改案件狀態為:
bug?id=71158