• Калі ласка, скапіруйце тэкст памылкі, якую вы бачыце на экране (калі яна ёсць).

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.

• Калі ласка, растлумачце, што вы хацелі зрабіць, што вы зрабілі і што здарылася

• Якім браўзэрам вы карыстаецеся?

• Калі ласка, скапіруйце тэкст на англійскай замест перакладу на ваш мову. Калі ў вас ёсць скрыншот гэтай памылкі (добрая звычка), вы можаце скарыстацца Imgur.com, каб загрузіць яго і ўставіць сюды спасылку.

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.

• Дзе можна знайсьці гэты тэкст у сістэме перакладу? Калі так, ці быў ён перакладзены больш за 24 гадзін таму?

• Якім браўзэрам вы карыстаецеся?

• Калі ласка, дакладна і коратка апішыце сваю прапанову, каб зрабіць яе найбольш даступнай для разумення.

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.

• Якім браўзэрам вы карыстаецеся?

• Што было намалявана на экране, калі вас заблакавала? (Пусты экран? Частка гульнявога стала? Паведамленне пра памылку?)

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.

• Якім браўзэрам вы карыстаецеся?

• Якая частка правілаў не выкананая ў версіі 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.

• Ці відаць парушэнне правілаў у паўторы гульні? Калі так, то на якім хаду?

• Якім браўзэрам вы карыстаецеся?

• Якое гульнявое дзеянне вы хацелі зрабіць?

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.

• Што вы спрабавалі зрабіць, каб выканаць гэтае гульнявое дзеянне?

• Што адбылося, калі вы паспрабавалі зрабіць гэта (паведамленне пра памылку, паведамленне ў радку стану гульні ...)?

• Якім браўзэрам вы карыстаецеся?

• На якім кроку гульні адбылася праблема (якая была інструкцыя ў той момант у гульні)?

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.

• Што адбылося, калі вы паспрабавалі здзейсніць гульнявое дзеянне (паведамленне пра памылку, паведамленне ў радку стану гульні ...)?

• Якім браўзэрам вы карыстаецеся?

• Калі ласка, апішыце памылку адлюстравання. Калі ў вас ёсць скрыншот гэтай памылкі (добрая звычка), вы можаце скарыстацца Imgur.com, каб загрузіць яго і ўставіць сюды спасылку.

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.

• Якім браўзэрам вы карыстаецеся?

• Калі ласка, скапіруйце тэкст на англійскай замест перакладу на ваш мову. Калі ў вас ёсць скрыншот гэтай памылкі (добрая звычка), вы можаце скарыстацца Imgur.com, каб загрузіць яго і ўставіць сюды спасылку.

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.

• Дзе можна знайсьці гэты тэкст у сістэме перакладу? Калі так, ці быў ён перакладзены больш за 24 гадзін таму?

• Якім браўзэрам вы карыстаецеся?

• Калі ласка, дакладна і коратка апішыце сваю прапанову, каб зрабіць яе найбольш даступнай для разумення.

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.

• Якім браўзэрам вы карыстаецеся?