• Пожалуйста, скопируйте/вставьте текст ошибки, которую вы видите на экране (если она есть).

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.

• Какой браузер вы используете?

• Какая часть правил не соблюдена в версии БГА

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.

• Какой браузер вы используете?