Alle Meldungen
Space Base Meldungen
#98302: "double stacked cards in shipyard"
notupdated: Die Meldung wurde automatisch geschlossen, weil es lange Zeit keine Stimmen / Kommentare dazu gab
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.
Screenshot here: imgur.com/vqmdbu5
Several cards in the second and third rows of shipyard had other cards tucked behind them. It looked like the tucked cards came from the row above? Eg, a card from row 1 would migrate down and tuck behind a card in row 2, etc. This effect was not present at the start of the game but appeared at some point early on, I'm not sure when. The number of double stacked cards varied. Every time someone bought a card in a row with tucked cards, one or more of the tucked cards would migrate to the end of the row and then back to their tucked places again.
This was distracting enough that I misclicked a couple of times and bought a card that I did not mean to. It's possible it let me buy one of the tucked cards at least once? I'm not 100% sure, it was confusing, and I spent most of the game trying to figure out what was wrong with the display or if I'd forgotten a rule or something.• Welchen Browser benutzt du?
Google Chrome v116
Meldungshistorie
12. Sep 2023 2:34 • emilindy • Der Fehler wurde von den Entwicklern noch nicht nachvollzogen:
I'm on a chromebook with a smaller than average screen (a Lenovo Duet). However, zooming out did not fix it, nor did enabling the option to display the cards with smaller numbers. Reloading did not change anything.
12. Sep 2023 3:10 • Shazzypaz • Die Entwickler brauchen mehr Informationen, um den Fehler nachzuvollziehen:
Strange. I went through the replay and didn't see any problems. Does the issue show when you go through the replay on your chromebook, and on a non chromebrook? (In replay, use "go to end of game" and let it play through to the end). If you see the issue either in the replay or during another game - are there any errors in the browser's javascript console? In Chrome you would find that in View -> Developer.
13. Sep 2023 1:37 • emilindy • Die Entwickler brauchen mehr Informationen, um den Fehler nachzuvollziehen:
Today I'm unable to reproduce it on any device, including the one from yesterday, neither in the replay nor in a new game... maybe it was a one-off? If it happens again I'll check the javascript.
13. Sep 2023 1:58 • Shazzypaz • Die Entwickler brauchen mehr Informationen, um den Fehler nachzuvollziehen:
Very odd! Thanks for trying.
14. Okt 2024 12:16 • Sourisdudesert • Die Meldung wurde automatisch geschlossen, weil es lange Zeit keine Stimmen / Kommentare dazu gab:
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.
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.
