全ての報告
ウイングスパン(Wingspan)の報告
#121445: "Cancelling move causes custom deck ordering to get break"
wontfix: このバグが修正されることはありません
1
どういった内容ですか?
どうしましたか?以下から選んでください
表示バグ: 表示されるゲームの情報が間違っている(ゲーム上の重要事項を表示していない)
詳細
• 表示の問題を説明してください もしこのバグのスクリーンショットがあれば(素晴らしい!)、Imgur.com等を使ってアップロードし、リンクをコピー&ペーストしてください。
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.• あなたのブラウザは何ですか?
Mozilla v5
報告履歴
karanr • バグは未だ開発者によって再現できていません:
2024年 4月18日 22:53 • 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.
paramesis • このバグが修正されることはありません:
2024年 4月19日 0:05 • 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.
報告に書き加える
このバグを再現するため、またはあなたの提案を理解するために、ここに関連性があると思われるものを追加してください:
- 他のテーブルID/行動ID
- F5キー(ページの再読込)で問題は解決されましたか?
- 問題は何回も起こりましたか?毎回 起こりますか?ランダムに起きますか?
- もしこのバグのスクリーンショットがあれば(素晴らしい!)、Imgur.com等を使ってアップロードし、リンクをコピー&ペーストしてください。