#77267: "Do more actions in the front-end interface instead of the back-end"
Vad handlar denna rapport om?
Vad hände? Välj från alternativen nedan
Vad hände? Välj från alternativen nedan
Vänligen kontrollera om det redan finns en rapport om samma ämne
Om detta stämmer, RÖSTA på denna rapport. Rapporterna med flest röster har PRIORITET!
| # | Status | Votes | Game | Type | Title | Last update |
|---|
Detaljerad beskrivning
-
• Var vänlig klipp och klistra in felmeddelandet du ser på skärmen, om något.
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. -
• Varsågod och förklara vad du ville göra, vad du gjorde och vad som hände
• Vad har du för webbläsare?
Mozilla v5
-
• Var vänlig kopiera/klistra in texten på engelska istället för ditt eget språk. Om du har en skärmdump av den här buggen (bra vana att ta en), så kan du använda en programvara (snipboard.io som till exempel) för att ladda upp bilden och klistra in länken här. Är denna text tillgänglig i översättningssystemet? I så fall, var det mer än 24 timmar sedan den översattes?
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. • Vad har du för webbläsare?
Mozilla v5
-
• Vänligen förklara ditt förslag exakt och koncist så att det är så enkelt som möjligt att förstå vad du menar.
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. • Vad har du för webbläsare?
Mozilla v5
-
• Vad visades på skärmen när du blockerades (Blank skärm? Del av spelets användargränssnitt? Felmeddelande?)?
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. • Vad har du för webbläsare?
Mozilla v5
-
• Vilken del av reglerna respekterades inte av BGA-adaptionen?
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. -
• Är regelbrottet synligt i återuppspelning? Om ja, vilket nummer är det på draget?
• Vad har du för webbläsare?
Mozilla v5
-
• Vilken spelhandling ville du göra?
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. -
• Vad försöker du göra för att sätta igång denna spelmekaniken?
-
• Vad hände när du försökte göra det här (felmeddelande, meddelande i spelstatusrad, ...)?
• Vad har du för webbläsare?
Mozilla v5
-
• På vilket steg i spelet kom felet (vad var den aktuella instruktionen från spelet)?
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. -
• Vad hände när du försökte utföra en spelhandling (felmeddelande, meddelande i spelstatusrad, ...)?
• Vad har du för webbläsare?
Mozilla v5
-
• Vänligen beskriv visningsproblemet. Om du har en skärmdump av den här buggen (bra vana att ta en), så kan du använda en programvara (snipboard.io som till exempel) för att ladda upp bilden och klistra in länken här.
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. • Vad har du för webbläsare?
Mozilla v5
-
• Var vänlig kopiera/klistra in texten på engelska istället för ditt eget språk. Om du har en skärmdump av den här buggen (bra vana att ta en), så kan du använda en programvara (snipboard.io som till exempel) för att ladda upp bilden och klistra in länken här. Är denna text tillgänglig i översättningssystemet? I så fall, var det mer än 24 timmar sedan den översattes?
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. • Vad har du för webbläsare?
Mozilla v5
-
• Vänligen förklara ditt förslag exakt och koncist så att det är så enkelt som möjligt att förstå vad du menar.
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. • Vad har du för webbläsare?
Mozilla v5
Rapporthistorik
Lägg till något till denna rapport
- Ett annat spelbords-ID / drag-ID
- Löste F5 problemet?
- Uppträdde problemet flera gånger? Varje gång? Slumpmässigt?
- Om du har en skärmdump av den här buggen (bra vana att ta en), så kan du använda en programvara (snipboard.io som till exempel) för att ladda upp bilden och klistra in länken här.
