Alle rapporter
Tash-Kalar rapporterer
#6440: "Game log shows duplicate actions"
wontfix: Denne fejl vil ikke blive rettet
1
Hvad handler denne rapport om?
Hvad skete der? Vær venlig og vælg nedenunder
Visningfejl: nogle spilinformationer blev vist forkert (uden nogen særlig konsekvens for spillet)
Detaljeret beskrivelse
• Venligst beskriv display problemet. Hvis du har et skærmbillede af denne fejl (god øvelse), kan du bruge Imgur.com til at uploade den og kopiere/indsætte linket her.
The game log shows my opponent's actions multiple times. This appears to be related to undo; the undone actions aren't being removed from the game log properly. Replaying from the beginning of my opponent's turn (action 129) to see what actually happened leaves the game log looking correct. However, this sometimes triggers #2483, leaving the board displaying a green legend in place of my blue legend on g7. I strongly suspect both of these bugs are related to undo.• Hvilken browser bruger du?
Firefox 50.1.0
Rapporthistorik
28. dec 2016 17:43 • Zahariel • Fejlen er ikke blevet reproduceret af udviklere endnu:
I've noticed this problem in other games of Tash-Kalar too but I don't have game numbers handy.
12. jan 2017 9:58 • Quinarbre • Denne fejl vil ikke blive rettet:
Yes, the game log shows duplicates, and that's deeply connected to the way undo works (I'm abusing the way moves work to allow for undo). This can't be changed, but at least the replay is correct (and complete).
Thanks for your ideas to help with bug #2483, but that one is more related to the way pieces move, rather than undo.
Thanks for your ideas to help with bug #2483, but that one is more related to the way pieces move, rather than undo.
2. sep 2020 14:17 • Leonius • Denne fejl vil ikke blive rettet:
Too bad they didn't fix it.
Repeated here:
boardgamearena.com/1/tashkalar?table=110074183&replayFrom=136
Repeated here:
boardgamearena.com/1/tashkalar?table=110074183&replayFrom=136
17. jun 2024 3:07 • smci • Denne fejl vil ikke blive rettet:
"Game log shows duplicate actions, including undone actions" would be a more accurate title.
This isn't necessarily a bug, and for (turn-based) Tash-Kalar games it's very useful to inspect your opponent's what-if moves and undoes, to infer/guess what faction-cards, legend cards and flares they might be holding(/not holding). So you only want to not see the second-and-subsequent move and undo.
Hard to see BGA implementing a game-specific change on logs just for Tash-Kalar and only to remove the 2nd or subsequent undone move... also including the (nested) case where opponent does move A, move B, undoes move B, undoes move A. Even harder in the corner-case where they have 3+ actions due to a flare/faction-card giving extra action/EverFrost frozen effect.
This isn't necessarily a bug, and for (turn-based) Tash-Kalar games it's very useful to inspect your opponent's what-if moves and undoes, to infer/guess what faction-cards, legend cards and flares they might be holding(/not holding). So you only want to not see the second-and-subsequent move and undo.
Hard to see BGA implementing a game-specific change on logs just for Tash-Kalar and only to remove the 2nd or subsequent undone move... also including the (nested) case where opponent does move A, move B, undoes move B, undoes move A. Even harder in the corner-case where they have 3+ actions due to a flare/faction-card giving extra action/EverFrost frozen effect.
Tilføj noget til denne rapport
Vær sød at tilføje, det du finder relevant for at vi kan løse fejlen i spillet eller forstå dit forslag:
- Et andet bord-ID / træk ID
- Løste F5 problemet?
- Skete problemet flere gange? Hver gang? Tilfældigt?
- Hvis du har et skærmbillede af denne fejl (god øvelse), kan du bruge Imgur.com til at uploade den og kopiere/indsætte linket her.
