Alle rapporter
Framework rapporter
#100413: "One of the tiles which should have scored did not score"
fixed: Feilen har blitt fikset
1
Hva handler denne rapporten om?
Hva har skjedd, eller hva gjelder det? Vennligst velg
Regler: en regel i spillet har ikke blitt respektert
Detaljert beskrivelse
-
• Hvilken del av reglene ble ikke respektert av BGA-tilpasningen
The yellow frame, 3 red task tile did not score even though there are 5 red frames chained to it.
-
• Er regelbruddet tydelig i spilloggen? Hvis ja, Hvilket trekknummer?
Move 61, and persisted to the end. See screenshot with arrow to mark it.
imgur.com/a/3tPdEyg • Hvilken nettleser bruker du?
Google Chrome v117
Rapporthistorikk
Oct 5 th 2023 5:57 • lefalaf • Feilen har ikke blitt reprodusert av utviklerne enda:
May just be a display bug. My final score was 1 greater than the number of visible tokens indicating as much.
I tried to go back with replay to check move 61, but replay isn't able to find the game right now.
I tried to go back with replay to check move 61, but replay isn't able to find the game right now.
Oct 5 th 2023 6:24 • lefalaf • Feilen har ikke blitt reprodusert av utviklerne enda:
I just saw this happen again (right score, missing token) in boardgamearena.com/2/framework?table=424836575
Frame Red 3x brown - tile just able the triple frame in the bottom of my (lefalaf) board.
After the game, I refreshed the browser and it added the missing token.
Frame Red 3x brown - tile just able the triple frame in the bottom of my (lefalaf) board.
After the game, I refreshed the browser and it added the missing token.
Oct 5 th 2023 17:34 • vurtan • Feil har blitt bekreftet av utviklerne:
Was interesting to debug that. But I can confirm, that this is only a visual bug.
The placed token one tile gets the same ID as a temporary helper element to slide a new token on another tile.
This results in the movement of the token. You can observe that in the game on turn #50. Before that the token is correclty and then it moves in lightspeed :)
Of course that will be fixed asap :)
The placed token one tile gets the same ID as a temporary helper element to slide a new token on another tile.
This results in the movement of the token. You can observe that in the game on turn #50. Before that the token is correclty and then it moves in lightspeed :)
Of course that will be fixed asap :)
Oct 7 th 2023 6:48 • lefalaf • Feil har blitt bekreftet av utviklerne:
I just replayed to turn 50. That was funny. It was like the other token just scooped it up and said, "Come here, I have a better tile for you!" :-)
Thanks for your efforts on the game! Cheers.
Thanks for your efforts on the game! Cheers.
Oct 7 th 2023 13:21 • vurtan • Feilen har blitt fikset:
Love your appreciation of the bug :)
Just deployed the new version which fixed the issue.
Just deployed the new version which fixed the issue.
Legg til noe i denne rapporten
Legg til her noe som synes relevant for å reprodusere denne feilen eller forstå forslaget ditt:
- En annen bord ID / flytt ID
- Løste F5 problemet?
- Oppstod problemet gjentatte ganger? Hver gang? Tilfeldig?
- Hvis du har et skjermbilde av denne feilen (alltid lurt) kan du bruke Imgur.com for å laste det opp og kopiere inn lenken til bildet her.
