• Falls du eine Fehlermeldung auf dem Bildschirm siehst, bitte kopieren und einfügen.

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.

• Bitte erkläre, was du machen wolltest, was du dann getan hast und was dann passiert ist

• Welchen Browser benutzt du?

• Bitte kopiere den Text, der in Englisch anstatt in deiner Sprache angezeigt wird, und füge ihn hier ein. Falls du einen Screenshot dieses Fehlers hast (optimale Vorgehensweise), kannst du ihn bei Imgur.com hochladen, den Link kopieren und hier einfügen.

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.

• Ist dieser Text auf der Übersetzungsseite verfügbar? Wenn ja, wurde dieser vor mehr als 24 Stunden übersetzt?

• Welchen Browser benutzt du?

• Bitte erkläre deinen Vorschlag so präzise und genau wie möglich, damit er leicht zu verstehen ist.

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.

• Welchen Browser benutzt du?

• Was wurde auf dem Bildschirm angezeigt, als du blockiert wurdest (weißer Bildschirm? Teil der Spieloberfläche? Fehlermeldung?)

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.

• Welchen Browser benutzt du?

• Welcher Teil der Spielregel wurde durch die BGA-Adaption nicht beachtet?

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.

• Ist der Regelverstoß in der Spielwiederholung zu sehen? Falls ja, bei welcher Zugnummer?

• Welchen Browser benutzt du?

• Welche Spielaktion wolltest du durchführen?

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.

• Was versuchst du, um diese Spielaktion auszulösen?

• Was passiert, wenn du dies versuchst (Fehlermeldung, Statusmeldung des Spiels, ...)?

• Welchen Browser benutzt du?

• An welcher Stelle im Spiel ist das Problem aufgetreten? Was war die aktuelle Spielanweisung?

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.

• Was passiert, wenn du die Spielaktion ausführen möchtest (Fehlermeldung, Statusmeldung des Spiels, ...)?

• Welchen Browser benutzt du?

• Bitte beschreibe die Anzeigeschwierigkeiten. Falls du einen Screenshot dieses Fehlers hast (optimale Vorgehensweise), kannst du ihn bei Imgur.com hochladen, den Link kopieren und hier einfügen.

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.

• Welchen Browser benutzt du?

• Bitte kopiere den Text, der in Englisch anstatt in deiner Sprache angezeigt wird, und füge ihn hier ein. Falls du einen Screenshot dieses Fehlers hast (optimale Vorgehensweise), kannst du ihn bei Imgur.com hochladen, den Link kopieren und hier einfügen.

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.

• Ist dieser Text auf der Übersetzungsseite verfügbar? Wenn ja, wurde dieser vor mehr als 24 Stunden übersetzt?

• Welchen Browser benutzt du?

• Bitte erkläre deinen Vorschlag so präzise und genau wie möglich, damit er leicht zu verstehen ist.

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.

• Welchen Browser benutzt du?