• Kopirajte / prilepite sporočilo o napaki, ki ga vidite na zaslonu, če ga imate.

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.

• Prosim, pojasnite, kaj ste hoteli storiti, kaj ste naredili in kaj se je zgodilo

• Kateri brskalnik uporabljaš?

• Kopirajte / prilepite besedilo, prikazano v angleščini, namesto v vašem jeziku. Če imate sliko zaslona te napake (dobra praksa), lahko uporabite Imgur.com za nalaganje in kopirate/prilepite povezavo do slike tukaj.

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.

• Je ta tekst dosegljiv v prevajalnem sistemu? Če ja, ali je bil preveden več kot 24 ur nazaj?

• Kateri brskalnik uporabljaš?

• Natančno in jedrnato pojasnite svoj predlog, da bo čim lažje razumeti, kaj mislite.

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.

• Kateri brskalnik uporabljaš?

• Kaj je bilo prikazano na zaslonu, ko ste bili blokirani (prazen zaslon? Del vmesnika za igro? Sporočilo o napaki?)

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.

• Kateri brskalnik uporabljaš?

• Kateri del pravil ni bil upoštevan pri priredbi za 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.

• Je kršitev pravil vidna na seznamu potez? Če je, pri kateri številki poteze?

• Kateri brskalnik uporabljaš?

• Katero potezo ste želeli narediti v igri?

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.

• Kaj ste poskušali narediti, da bi izvedli to potezo v igri?

• Kaj se je zgodilo, ko ste poskusili to storiti (sporočilo o napaki, sporočilo v vrstici stanja, ...)?

• Kateri brskalnik uporabljaš?

• Na kateri točki v igri se je težava pojavila (katera navodila so bila prikazana)

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.

• Kaj se je zgodilo, ko ste poskušali narediti to potezo v igri (sporočilo o napaki, sporočilo v vrstici stanja, ...)?

• Kateri brskalnik uporabljaš?

• Prosim opiši problem s prikazom. Če imate sliko zaslona te napake (dobra praksa), lahko uporabite Imgur.com za nalaganje in kopirate/prilepite povezavo do slike tukaj.

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.

• Kateri brskalnik uporabljaš?

• Kopirajte / prilepite besedilo, prikazano v angleščini, namesto v vašem jeziku. Če imate sliko zaslona te napake (dobra praksa), lahko uporabite Imgur.com za nalaganje in kopirate/prilepite povezavo do slike tukaj.

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.

• Je ta tekst dosegljiv v prevajalnem sistemu? Če ja, ali je bil preveden več kot 24 ur nazaj?

• Kateri brskalnik uporabljaš?

• Natančno in jedrnato pojasnite svoj predlog, da bo čim lažje razumeti, kaj mislite.

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.

• Kateri brskalnik uporabljaš?