#71158: "Make new options more backwards-compatible (regarding default values for new games)"
Co się stało? Wybierz z poniższych opcji
Co się stało? Wybierz z poniższych opcji
Sprawdź, czy istnieje już zgłoszenie na ten sam temat
Jeśli tak, ZAGŁOSUJ na to zgłoszenie. Zgłoszenia z największą liczbą głosów mają najwyższy PRIORYTET!
# | Status | Votes | Game | Type | Title | Last update |
---|
Szczegółowy opis
• Proszę skopiować i wkleić treść błędu wyświetloną na ekranie, o ile jakaś się pojawia.
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.• Proszę opisać co chciałeś zrobić, co zrobiłeś i co się stało
• Jaką masz przeglądarkę?
Mozilla v5
• Proszę skopiować i wkleić tekst wyświetlany w języku angielskim zamiast w twoim języku. Jeżeli masz zrzut ekranu z tym błędem (dobry zwyczaj) możesz użyć Imgur.com, żeby wrzucić go do Internetu i potem skopiować łącze do niego tutaj.
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.• Czy ten tekst jest dostępny w systemie tłumaczeń? Jeśli tak, to czy został przetłumaczony więcej niż 24 godziny temu?
• Jaką masz przeglądarkę?
Mozilla v5
• Wyjaśnij swoją propozycję precyzyjnie i zwięźle, tak aby jak najłatwiej zrozumieć, co masz na myśli.
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.• Jaką masz przeglądarkę?
Mozilla v5
• Co wyświetlało się na ekranie kiedy zostałeś zablokowany (Pusty ekran? Część interfejsu gry? Komunikat o błędzie?)
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.• Jaką masz przeglądarkę?
Mozilla v5
• Która z zasad gry nie była przestrzegana w adaptacji 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.• Czy naruszenie zasad gry jest widoczne w powtórce rozgrywki? Jeżeli tak, to w ruchu o jakim numerze?
• Jaką masz przeglądarkę?
Mozilla v5
• Jaką akcję w grze chciałeś wykonać?
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.• Co starasz się zrobić by uruchomić tę akcję w grze?
• Co się stało kiedy próbowałeś to zrobić (komunikat o błędzie, komunikat na pasku stanu gry, ...)?
• Jaką masz przeglądarkę?
Mozilla v5
• W którym momencie gry pojawił się problem (jakie było aktualne polecenie w grze)?
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.• Co się stało kiedy próbowałeś wykonać akcję w grze (komunikat o błędzie, komunikat na pasku stanu gry, ...)?
• Jaką masz przeglądarkę?
Mozilla v5
• Proszę opisać problem z wyświetlaniem. Jeżeli masz zrzut ekranu z tym błędem (dobry zwyczaj) możesz użyć Imgur.com, żeby wrzucić go do Internetu i potem skopiować łącze do niego tutaj.
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.• Jaką masz przeglądarkę?
Mozilla v5
• Proszę skopiować i wkleić tekst wyświetlany w języku angielskim zamiast w twoim języku. Jeżeli masz zrzut ekranu z tym błędem (dobry zwyczaj) możesz użyć Imgur.com, żeby wrzucić go do Internetu i potem skopiować łącze do niego tutaj.
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.• Czy ten tekst jest dostępny w systemie tłumaczeń? Jeśli tak, to czy został przetłumaczony więcej niż 24 godziny temu?
• Jaką masz przeglądarkę?
Mozilla v5
• Wyjaśnij swoją propozycję precyzyjnie i zwięźle, tak aby jak najłatwiej zrozumieć, co masz na myśli.
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.• Jaką masz przeglądarkę?
Mozilla v5
Historia zgłoszeń
When an option is fixed for arena before activation, itwould be nice to set this settings to all tournaments created before the activation.
Dodaj coś do tego zgłoszenia
- Kolejne ID stołu / ID ruchu
- Czy F5 rozwiązało problem?
- Czy problem zdarzył się kilka razy? Za każdym razem? Losowo?
- Jeżeli masz zrzut ekranu z tym błędem (dobry zwyczaj) możesz użyć Imgur.com, żeby wrzucić go do Internetu i potem skopiować łącze do niego tutaj.