#77267: "Do more actions in the front-end interface instead of the back-end"
Čeho se toto hlášení týká?
Co se stalo? Prosím vyberte níže
Co se stalo? Prosím vyberte níže
Prosím zkontroluj, zda již neexistuje hlášení pro stejnou věc
Pokud ano, HLASUJ pro toto hlášení. Hlášení s nejvyšším počtem hlasů budou řešena PŘEDNOSTNĚ!
| # | Status | Votes | Game | Type | Title | Last update |
|---|
Detailní popis
-
• Prosím, zkopíruj a vlož hlášení o chybě, které vidíš na monitoru, pokud to lze.
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. -
• Prosím popiš, co jsi měl v úmyslu udělat, co jsi udělal a co se nakonec stalo
• Jaký prohlížeč používáte?
Mozilla v5
-
• Prosíme, zkopíruj/vlož text zobrazený v angličtině namísto tvého jazyka. Pokud máš snímek obrazvky zobrazující tuto chybu (doporučujeme!), můžeš použít Imgur.com pro nahrání obrázku a pak odkaz na tento obrázek na Imguru zkopírovat a vložit sem.
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 tento text k dispozici v systému pro překládání? Pokud ano, byl přeložen před více než 24 hodinami?
• Jaký prohlížeč používáte?
Mozilla v5
-
• Prosím popiš svůj návrh přesně a konzistentně, aby bylo snadné pochopit, co máš na mysli.
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. • Jaký prohlížeč používáte?
Mozilla v5
-
• Co bylo zobrazeno na monitoru, když došlo k tvému zablokování? (Černá obrazovka? Část herního prostředí? Hlášení o chybě?)
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. • Jaký prohlížeč používáte?
Mozilla v5
-
• Která část pravidel nebyla dodržena adaptací hry na 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 vidět porušení pravidel na záznamu hry? Pokud ano, ve kterém tahu?
• Jaký prohlížeč používáte?
Mozilla v5
-
• O jakou herní akci ses pokoušel/a?
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. -
• Co ses pokoušel/a udělat, abys spustil/a tuhle herní akci?
-
• Co se stalo, když ses o tuto akci pokusil/a (vyskočila chybová hláška, lišta ve hře, ...)?
• Jaký prohlížeč používáte?
Mozilla v5
-
• V jaké fázi hry problém nastal (jaký byl poslední herní pokyn)?
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. -
• Co se stalo, když ses pokusil/a udělat akci (chybová hláška, oznámení stavového řádku hry, ...)?
• Jaký prohlížeč používáte?
Mozilla v5
-
• Prosím popište vyobrazený problém. Pokud máš snímek obrazvky zobrazující tuto chybu (doporučujeme!), můžeš použít Imgur.com pro nahrání obrázku a pak odkaz na tento obrázek na Imguru zkopírovat a vložit sem.
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. • Jaký prohlížeč používáte?
Mozilla v5
-
• Prosíme, zkopíruj/vlož text zobrazený v angličtině namísto tvého jazyka. Pokud máš snímek obrazvky zobrazující tuto chybu (doporučujeme!), můžeš použít Imgur.com pro nahrání obrázku a pak odkaz na tento obrázek na Imguru zkopírovat a vložit sem.
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 tento text k dispozici v systému pro překládání? Pokud ano, byl přeložen před více než 24 hodinami?
• Jaký prohlížeč používáte?
Mozilla v5
-
• Prosím popiš svůj návrh přesně a konzistentně, aby bylo snadné pochopit, co máš na mysli.
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. • Jaký prohlížeč používáte?
Mozilla v5
Historie hlášení
Doplňte tuto zprávu
- ID dalšího stolu / ID tahu
- Byla chyba odstraněna stisknutím F5?
- Objevila se tato chyba častěji? Pokaždé? Náhodně?
- Pokud máš snímek obrazvky zobrazující tuto chybu (doporučujeme!), můžeš použít Imgur.com pro nahrání obrázku a pak odkaz na tento obrázek na Imguru zkopírovat a vložit sem.
