All reports
skat_displayed reports
#102550: "Beim Skat darf man nicht auf alle Züge der Vergangenheit zugreifen"
notupdated: This report has been closed automatically because there was no vote/comment on it for a long time
2
What is this report about?
What happened ? Please select from below
Rules: a rule of the game has not been respected
Detailed description
• Which part of the rules was not respected by the BGA adaptation
Beim Skat darf man nicht auf alle Züge der Vergangenheit zugreifen
Die Züge sollten nur für den aktuellen Stich einsehbar sein
Wenn man das Spiel noch nicht bestimmt hat , dann darf man die Karten aus dem Skat nochmal aufnehmen.• Is the rules violation visible on game replay? If yes, at which move number?
s.o.• What is your browser?
Mozilla v5
Report history
28. Oct 2023 21:10 •
Technolizm • Bug has not been reproduced by delopers yet:
11. Apr 2024 11:12 • Wenn man alle Stiche sehen kann nimmmt es tatsächlich den Spielwitz - somit ist diese Umsetzung definitiv nicht gut.
Sourisdudesert • This report has been closed automatically because there was no vote/comment on it for a long time:
11. Apr 2025 12:16 • Report closed automatically because it has not been upvoted or commented for a while.
Your bug has probably been fixed already, or was linked to a temporary failure of BGA service.
In any case, when filling a bug report, make sure to have an explicit title linked to the incident (ex: with error message), so other players can recognize it and vote for it.
Your bug has probably been fixed already, or was linked to a temporary failure of BGA service.
In any case, when filling a bug report, make sure to have an explicit title linked to the incident (ex: with error message), so other players can recognize it and vote for it.
ribidilus • This report has been closed automatically because there was no vote/comment on it for a long time:
4. Jun 2025 10:39 • new bug, same issue: boardgamearena.com/bug?id=162980
Add something to this report
Please add here anything that seems relevant to reproduce this bug or understand your suggestion:
- Another table ID / move ID
- Did F5 solve the problem?
- Did the problem appears several time? Everytime? Randomly?
- If you have a screenshot of this bug (good practice), you can use Imgur.com to upload it and copy/paste the link here.