#71158: "Make new options more backwards-compatible (regarding default values for new games)"
Mi történt? Kérünk, válassz az alábbiakból
Mi történt? Kérünk, válassz az alábbiakból
Kérjük ellenőrizd, hogy nincs-e azonos tárggyal már jelentés!
Ha igen, kérjük SZAVAZZ erre a jelentésre! A legtöbb szavazattal rendelkező jelentéssel kiemelt PRIORITÁSSAL foglalkozunk
# | Status | Votes | Game | Type | Title | Last update |
---|
Részletes leírás
• Kérjük másold be a hiba üzenetet, amit kaptál, ha volt ilyen.
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.• Kérjük mondd el, hogy mit szerettél volna csinálni, mit csináltál és mi történt
• Milyen böngészőt használsz?
Mozilla v5
• Kérjük, másold az angolul megjelenített szöveget, ahelyett, hogy lefordítanád a Te nyelvedre! Ha van screenshot-od erről a bugról (ajánlott), használd a Imgur.com, hogy feltöltsd, majd másold be a linket.
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.• Létezik ez a szöveg a fordítási rendszerben? Ha igen, több mint 24 órája lett lefordítva?
• Milyen böngészőt használsz?
Mozilla v5
• Kérjük magyarázd el a javaslatodat pontosan és tömören, hogy amennyire lehet, könnyen érthető legyen, mire is gondolsz!
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.• Milyen böngészőt használsz?
Mozilla v5
• Mit láttál a képernyőn, amikor blokkolva lettél? (Üres képernyő? A játék felületének egy részét? Hiba üzenet?)
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.• Milyen böngészőt használsz?
Mozilla v5
• A szabályok melyik részét nem vette figyelembe a BGA adaptá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.• Ez a szabály áthágása látható a visszajátszásban? Ha igen, melyik lépésszámnál?
• Milyen böngészőt használsz?
Mozilla v5
• Melyik játékbeli akciót akartad csinálni, amikor a hiba előjött?
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 akartál csinálni, hogy ezt a játékbeli akciót elindíthasd?
• Mi történt amikor megpróbáltad ezt (hiba üzenet, játék státusz üzenet, ...)?
• Milyen böngészőt használsz?
Mozilla v5
• A játék melyik lépésénél lépett fel a probléma? (mi volt a kiírt utasítás?)
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.• Mi történt amikor megpróbáltad ezt az akciót (hiba üzenet, játék státusz üzenet, ...)?
• Milyen böngészőt használsz?
Mozilla v5
• Kérjük írd le a felületen talált hibát. Ha van screenshot-od erről a bugról (ajánlott), használd a Imgur.com, hogy feltöltsd, majd másold be a linket.
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.• Milyen böngészőt használsz?
Mozilla v5
• Kérjük, másold az angolul megjelenített szöveget, ahelyett, hogy lefordítanád a Te nyelvedre! Ha van screenshot-od erről a bugról (ajánlott), használd a Imgur.com, hogy feltöltsd, majd másold be a linket.
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.• Létezik ez a szöveg a fordítási rendszerben? Ha igen, több mint 24 órája lett lefordítva?
• Milyen böngészőt használsz?
Mozilla v5
• Kérjük magyarázd el a javaslatodat pontosan és tömören, hogy amennyire lehet, könnyen érthető legyen, mire is gondolsz!
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.• Milyen böngészőt használsz?
Mozilla v5
Bejelentés előzmények
When an option is fixed for arena before activation, itwould be nice to set this settings to all tournaments created before the activation.
Hozzáadni valamit a jelentéshez
- Másik asztal ID / lépés ID
- az F5 megoldotta a problémát?
- Milyen gyakran jön elő a probléma? Minden alkalommal? Véletlenszerűen?
- Ha van screenshot-od erről a bugról (ajánlott), használd a Imgur.com, hogy feltöltsd, majd másold be a linket.