Alle Meldungen
Flügelschlag Meldungen
#121445: "Cancelling move causes custom deck ordering to get break"
wontfix: Dieser Fehler wird nicht behoben werden
1
Worum geht es bei dieser Meldung?
Was ist passiert? Bitte wähle unten aus
Anzeigefehler: Irgendeine Information zum Spiel wurde falsch angezeigt (ohne starke Beeinträchtigung des Spiels)
Detaillierte Beschreibung
• Bitte beschreibe die Anzeigeschwierigkeiten. Falls du einen Screenshot dieses Fehlers hast (optimale Vorgehensweise), kannst du ihn bei Imgur.com hochladen, den Link kopieren und hier einfügen.
You can rearrange the birds in your hand to strategize about what specific birds you want to play cache etc. I usually use the bonus cards as a sort of marker for the same. But if anyone cancels a move, the bonus card goes back to the end and the card order gets disrupted.• Welchen Browser benutzt du?
Mozilla v5
Meldungshistorie
18. Apr 2024 22:53 • karanr • Der Fehler wurde von den Entwicklern noch nicht nachvollzogen:
Using F5 to refresh also breaks the order. So that could be fixed too. It appears everytime someone cancels their turn if you have a custom order.
19. Apr 2024 0:05 • paramesis • Dieser Fehler wird nicht behoben werden:
Addressing the F5 issue first:
After you rearrange cards in your hand, the interface waits 5 seconds before sending them to the server, unless you rearrange your cards further, in which case the timer resets to 5 seconds. This minimizes the number and frequency of transactions by inactive players, reducing the risk of race conditions. If a player closes the page or refreshes before that 5 seconds has passed, the new card order is not saved to the server.
Addressing the Undo:
I anticipated this could be a potential annoyance with the way I had set up this feature, but the probability that players are affected by it is very low, given that this is the first report I've gotten about it since the feature was deployed about 5 months ago (same with the delayed database transaction). When another player cancels their move, the entire game state is restored to a save point, and if that save point was created before your cards were rearranged, the order is reset as well. If the player does anything that creates a new save point, such as rolling dice, drawing a card, or ending their turn, the updated card order will be part of that new save point. There isn't really a way to fix this - that is, preserve the card order through another player's undo - that wouldn't dramatically increase the likelihood of serious errors or incompatibilities with BGA framework updates.
I plan on adding a feature in a future update to allow you to rearrange cards on your turn, which would be the best way of preventing this from being an annoyance, but until that is ready, hopefully it helps to understand what is happening under the hood.
After you rearrange cards in your hand, the interface waits 5 seconds before sending them to the server, unless you rearrange your cards further, in which case the timer resets to 5 seconds. This minimizes the number and frequency of transactions by inactive players, reducing the risk of race conditions. If a player closes the page or refreshes before that 5 seconds has passed, the new card order is not saved to the server.
Addressing the Undo:
I anticipated this could be a potential annoyance with the way I had set up this feature, but the probability that players are affected by it is very low, given that this is the first report I've gotten about it since the feature was deployed about 5 months ago (same with the delayed database transaction). When another player cancels their move, the entire game state is restored to a save point, and if that save point was created before your cards were rearranged, the order is reset as well. If the player does anything that creates a new save point, such as rolling dice, drawing a card, or ending their turn, the updated card order will be part of that new save point. There isn't really a way to fix this - that is, preserve the card order through another player's undo - that wouldn't dramatically increase the likelihood of serious errors or incompatibilities with BGA framework updates.
I plan on adding a feature in a future update to allow you to rearrange cards on your turn, which would be the best way of preventing this from being an annoyance, but until that is ready, hopefully it helps to understand what is happening under the hood.
Ergänze diese Meldung
Bitte erwähne hier alles, was bedeutsam sein könnte, um diesen Fehler nachzuvollziehen oder deinen Vorschlag zu verstehen:
- Eine weitere Tisch-ID/Zug-ID
- Konnte F5 das Problem lösen?
- Trat das Problem öfter auf? Jedes Mal? Zufällig?
- Falls du einen Screenshot dieses Fehlers hast (optimale Vorgehensweise), kannst du ihn bei Imgur.com hochladen, den Link kopieren und hier einfügen.
