#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
היסטוריית דיווחים
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 כדי להעלות אותו להדביק קישור לכאן.