• Prosím skopíruj a vlož chybové hlásenie, ktoré si videl na obrazovke, ak sa nejaké vyskytlo.

For Seasons, there are many cases where it would make sense to do more in the front-end instead of in the back-end. Especially when activating a card, all choices (which effect to use if there are multiple, paying the cost for the effect) should be handled at once in the front-end. Then this combined data could be sent at once to the back-end.

This would allow implementing Undo/Cancel in some cases and would generally make Seasons more user friendly.

A good example where this already partially happens is Amulet of Time: the user can select/unselect multiple cards to discard before confirming.

• Prosím vysvetli, čo si chcel/a spraviť, čo si spravil/a a čo sa stalo

• Aký prehliadač používaš?

• Skopíruj/vlož text zobrazený v angličtine namiesto tvojho jazyka. Ak máš screenshot (dobrý zvyk), môžeš použiť Imgur.com na jeho nahranie a skopírovať sem odkaz na neho.

For Seasons, there are many cases where it would make sense to do more in the front-end instead of in the back-end. Especially when activating a card, all choices (which effect to use if there are multiple, paying the cost for the effect) should be handled at once in the front-end. Then this combined data could be sent at once to the back-end.

This would allow implementing Undo/Cancel in some cases and would generally make Seasons more user friendly.

A good example where this already partially happens is Amulet of Time: the user can select/unselect multiple cards to discard before confirming.

• Je tento text dostupný v prekladovom systéme? Ak áno, bol preložený po dlhšie ako 24 hodín?

• Aký prehliadač používaš?

• Prosím presne a stručne vysvetli svoj podnet, aby bolo čo najjednoduchšie pochopiť, ako to myslíš.

For Seasons, there are many cases where it would make sense to do more in the front-end instead of in the back-end. Especially when activating a card, all choices (which effect to use if there are multiple, paying the cost for the effect) should be handled at once in the front-end. Then this combined data could be sent at once to the back-end.

This would allow implementing Undo/Cancel in some cases and would generally make Seasons more user friendly.

A good example where this already partially happens is Amulet of Time: the user can select/unselect multiple cards to discard before confirming.

• Aký prehliadač používaš?

• Čo sa objavilo na obrazovke, keď si bol zablokovaný (Prázdna obrazovka? Časť herného rozhrania? Chybové hlásenie?)?

For Seasons, there are many cases where it would make sense to do more in the front-end instead of in the back-end. Especially when activating a card, all choices (which effect to use if there are multiple, paying the cost for the effect) should be handled at once in the front-end. Then this combined data could be sent at once to the back-end.

This would allow implementing Undo/Cancel in some cases and would generally make Seasons more user friendly.

A good example where this already partially happens is Amulet of Time: the user can select/unselect multiple cards to discard before confirming.

• Aký prehliadač používaš?

• Ktorá časť pravidiel nebola dodržaná v BGA adaptácii?

For Seasons, there are many cases where it would make sense to do more in the front-end instead of in the back-end. Especially when activating a card, all choices (which effect to use if there are multiple, paying the cost for the effect) should be handled at once in the front-end. Then this combined data could be sent at once to the back-end.

This would allow implementing Undo/Cancel in some cases and would generally make Seasons more user friendly.

A good example where this already partially happens is Amulet of Time: the user can select/unselect multiple cards to discard before confirming.

• Je možné vidieť porušenie pravidiel na zázname z hry? Ak áno, aké je číslo ťahu?

• Aký prehliadač používaš?

• Aký herný ťah si chcel urobiť?

For Seasons, there are many cases where it would make sense to do more in the front-end instead of in the back-end. Especially when activating a card, all choices (which effect to use if there are multiple, paying the cost for the effect) should be handled at once in the front-end. Then this combined data could be sent at once to the back-end.

This would allow implementing Undo/Cancel in some cases and would generally make Seasons more user friendly.

A good example where this already partially happens is Amulet of Time: the user can select/unselect multiple cards to discard before confirming.

• Čo si skúsil aby si vyvolal túto akciu?

• Čo sa stalo keď si spravil túto hernú akciu (chybové hlásenie, hlásenie v stavovom pruhu, ...)?

• Aký prehliadač používaš?

• Kedy v priebehu hry sa problém vyskytol (aká bola prebiehajúca herná inštrukcia)?

For Seasons, there are many cases where it would make sense to do more in the front-end instead of in the back-end. Especially when activating a card, all choices (which effect to use if there are multiple, paying the cost for the effect) should be handled at once in the front-end. Then this combined data could be sent at once to the back-end.

This would allow implementing Undo/Cancel in some cases and would generally make Seasons more user friendly.

A good example where this already partially happens is Amulet of Time: the user can select/unselect multiple cards to discard before confirming.

• Čo sa stalo keď si spravil túto hernú akciu (chybové hlásenie, hlásenie v stavovom pruhu, ...)?

• Aký prehliadač používaš?

• Prosím popíš viditeľný problém. Ak máš screenshot (dobrý zvyk), môžeš použiť Imgur.com na jeho nahranie a skopírovať sem odkaz na neho.

For Seasons, there are many cases where it would make sense to do more in the front-end instead of in the back-end. Especially when activating a card, all choices (which effect to use if there are multiple, paying the cost for the effect) should be handled at once in the front-end. Then this combined data could be sent at once to the back-end.

This would allow implementing Undo/Cancel in some cases and would generally make Seasons more user friendly.

A good example where this already partially happens is Amulet of Time: the user can select/unselect multiple cards to discard before confirming.

• Aký prehliadač používaš?

• Skopíruj/vlož text zobrazený v angličtine namiesto tvojho jazyka. Ak máš screenshot (dobrý zvyk), môžeš použiť Imgur.com na jeho nahranie a skopírovať sem odkaz na neho.

For Seasons, there are many cases where it would make sense to do more in the front-end instead of in the back-end. Especially when activating a card, all choices (which effect to use if there are multiple, paying the cost for the effect) should be handled at once in the front-end. Then this combined data could be sent at once to the back-end.

This would allow implementing Undo/Cancel in some cases and would generally make Seasons more user friendly.

A good example where this already partially happens is Amulet of Time: the user can select/unselect multiple cards to discard before confirming.

• Je tento text dostupný v prekladovom systéme? Ak áno, bol preložený po dlhšie ako 24 hodín?

• Aký prehliadač používaš?

• Prosím presne a stručne vysvetli svoj podnet, aby bolo čo najjednoduchšie pochopiť, ako to myslíš.

For Seasons, there are many cases where it would make sense to do more in the front-end instead of in the back-end. Especially when activating a card, all choices (which effect to use if there are multiple, paying the cost for the effect) should be handled at once in the front-end. Then this combined data could be sent at once to the back-end.

This would allow implementing Undo/Cancel in some cases and would generally make Seasons more user friendly.

A good example where this already partially happens is Amulet of Time: the user can select/unselect multiple cards to discard before confirming.

• Aký prehliadač používaš?