• Si us plau, copia i enganxa el missatge d'error que veus a la pantalla, si és que n'hi ha algun.

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.

• Si us plau, què volies fer, què vas fer i que va succeir

• Quin és el meu navegador?

• Si us plau, copieu/enganxeu el text mostrat en anglès en comptes del teu idioma. Si tens una captura de pantalla d'aquest error (bona pràctica), pots utilitzar Imgur.com per pujar-ho i copiar i enganxar el link aquí.

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.

• És aquest text disponible al sistema de traducció? Si és així, ha sigut traduït fa més de 24 hores?

• Quin és el meu navegador?

• Si us plau, expliqueu el vostre suggeriment de manera precisa i concisa, per que sigui el més fàcil d'entendre possible.

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.

• Quin és el meu navegador?

• Què es mostrava a la pantalla quan estaves bloquejat (pantalla en blanc? Part de la interfície del joc? Missatge d'error?)

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.

• Quin és el meu navegador?

• Quina part de les regles no s'han respectat per l'adaptació de BGA

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.

• És visible la violació de les normes durant la repetició de la partida? Si es així, en quin número de moviment?

• Quin és el meu navegador?

• Quina va ser l'acció del joc que volies fer?

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.

• Què intentes fer per dur a terme aquesta acció del joc?

• Què va passar quan ho vas intentar fer (missatge d'error, missatge de la barra d'estat de la partida, ...)?

• Quin és el meu navegador?

• A quina fase del joc va passar l'error (quina era la ordre en curs)?

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.

• Què va passar quan vas intentar dur a terme l'acció del joc (missatge d'error, missatge de la barra d'estat del joc, ...)?

• Quin és el meu navegador?

• Si us plau, descriviu el problema de visualització. Si tens una captura de pantalla d'aquest error (bona pràctica), pots utilitzar Imgur.com per pujar-ho i copiar i enganxar el link aquí.

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.

• Quin és el meu navegador?

• Si us plau, copieu/enganxeu el text mostrat en anglès en comptes del teu idioma. Si tens una captura de pantalla d'aquest error (bona pràctica), pots utilitzar Imgur.com per pujar-ho i copiar i enganxar el link aquí.

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.

• És aquest text disponible al sistema de traducció? Si és així, ha sigut traduït fa més de 24 hores?

• Quin és el meu navegador?

• Si us plau, expliqueu el vostre suggeriment de manera precisa i concisa, per que sigui el més fàcil d'entendre possible.

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.

• Quin és el meu navegador?