• Por favor copie e cole a mensagem de erro que aparece na tela, se possível.

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.

• Por favor explique o que queria fazer, o que fez e o que aconteceu

• Qual navegador você está usando?

• Por favor copie/cole o texto em inglês em vez de sua língua. If you have a screenshot of this bug (good practice), you can use a picture hosting service of your choice (snipboard.io for example) to upload it and copy/paste the link here. Este texto está disponível no sistema de traduções? Se sim, foi traduzido há mais de 24 horas?

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.

• Qual navegador você está usando?

• Por favor, explique sua sugestão precisamente e de forma concisa, de forma que fique o mais fácil possível, entender o que você quer dizer.

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.

• Qual navegador você está usando?

• O que estava presente na tela quando você estava bloqueado (tela em branco? Parte da imagem do jogo? Mensagem de erro?)

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.

• Qual navegador você está usando?

• Que parte das regras não foi respeitada pela adaptação do 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.

• A violação de regras está visível na revisão do jogo? Se sim, em que número de jogada?

• Qual navegador você está usando?

• Qual era a ação de jogo que queria fazer?

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 que você tentou fazer para provocar esta ação de jogo?

• O que aconteceu quando tentou fazer isto(mensagem de erro, mensagem na barra de estado do jogo)?

• Qual navegador você está usando?

• Em que passo do jogo ocorre o problema(qual era a instrução corrente do jogo)?

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 que aconteceu quando tentou fazer essa ação de jogo (mensagem de erro, mensagem na barra de estado do jogo)?

• Qual navegador você está usando?

• Por favor descreva o problema de visualização. If you have a screenshot of this bug (good practice), you can use a picture hosting service of your choice (snipboard.io for example) to upload it and copy/paste the link here.

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.

• Qual navegador você está usando?

• Por favor copie/cole o texto em inglês em vez de sua língua. If you have a screenshot of this bug (good practice), you can use a picture hosting service of your choice (snipboard.io for example) to upload it and copy/paste the link here. Este texto está disponível no sistema de traduções? Se sim, foi traduzido há mais de 24 horas?

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.

• Qual navegador você está usando?

• Por favor, explique sua sugestão precisamente e de forma concisa, de forma que fique o mais fácil possível, entender o que você quer dizer.

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.

• Qual navegador você está usando?