• Kui näed ekraanil veateadet, kopeeri see siia.

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.

• Kirjelda, mida sa soovisid teha, mida sa tegid ja mis juhtus

• mis on sinu veebilehitseja?

• Palun kopeeri/kleebi kuvatud tekst inglise keeles, mitte sinu oma keeles. Kui sul on sellest veast ekraanipilt (hea tava), saad kasutada Imgur.com selle üleslaadimiseks ja lingi siia kopeerida.

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.

• Kas see tekst on kättesaadav tõlkesüsteemis ? Kui jah, kas see on tõlgitud rohkem kui 24 tundi tagasi?

• mis on sinu veebilehitseja?

• Palun selgita oma ettepanekut täpselt ja lühidalt, et oleks võimalikult lihtne mõista, mida silmas pead.

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.

• mis on sinu veebilehitseja?

• Mis oli ekraanil, kui sind blokeeriti? (Tühi ekraan? Osa mänguliidesest? Veateade?)

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.

• mis on sinu veebilehitseja?

• Millist osa BGA kohandamisest ei järgitud

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.

• Kas reeglite rikkumist on mängu taasesitusel näha? Kui jah, siis mitmendal käigul?

• mis on sinu veebilehitseja?

• Milline oli mängu tegevus, mida tahtsid sooritada?

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.

• Mida püüdsid teha, et seda mängu tegevust käivitada?

• Mis juhtus, kui seda proovisite (veateade, mängu olekuriba teade, ...)?

• mis on sinu veebilehitseja?

• Millises mängu etapis esines probleem (Mis oli selle mänguetapi instruktsioon)?

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.

• Mis juhtus, kui proovisite sooritada seda mängu käiku (veateade, mängu olekuriba sõnum, ...)?

• mis on sinu veebilehitseja?

• Kirjelda kuvamise probleemi. Kui sul on sellest veast ekraanipilt (hea tava), saad kasutada Imgur.com selle üleslaadimiseks ja lingi siia kopeerida.

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.

• mis on sinu veebilehitseja?

• Palun kopeeri/kleebi kuvatud tekst inglise keeles, mitte sinu oma keeles. Kui sul on sellest veast ekraanipilt (hea tava), saad kasutada Imgur.com selle üleslaadimiseks ja lingi siia kopeerida.

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.

• Kas see tekst on kättesaadav tõlkesüsteemis ? Kui jah, kas see on tõlgitud rohkem kui 24 tundi tagasi?

• mis on sinu veebilehitseja?

• Palun selgita oma ettepanekut täpselt ja lühidalt, et oleks võimalikult lihtne mõista, mida silmas pead.

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.

• mis on sinu veebilehitseja?