Alle rapporter
zuuli_displayed rapporter
#100596: "I can "steal" opponents cards during development phase"
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
I shouldn't be getting any extra cards from my opponent, or scoring them!• Er regelbruddet tydelig i spilloggen? Hvis ja, Hvilket trekknummer?
It is visible that I obtained more cards, but not how. Move #46.• Hvilken nettleser bruker du?
Google Chrome v116
Rapporthistorikk
okt. 6 th 2023 23:42 • sonyaswan • Feilen har ikke blitt reprodusert av utviklerne enda:
I was looking to try and calculate my opponent's score while I was in my development phase, to see if I could beat them (I couldn't, they were doing very well!), and tapped on a card to get a closer look. I then noticed the blue box appear around my park and hand, which allowed me to "take" the card from them. I could tell they were not my cards as they appeared smaller than my cards.
I had thought that maybe this was just a cosmetic issue, but I informed my opponent in the chat that I found a bug, started a screen recording, then confirmed my placed cards (including some of theirs). When the game scored, it scored the cards I had "taken" as if they were my own, but scored my opponent with their correct score (including their original cards).
Refreshing during the development phase reset the board (as it does normally), but I was still able to "take" my opponent's cards, and refreshing after scoring brought the images of my opponent's cards back, but the cards I had "taken" were still in my park- the cards seem to have duplicated themselves!
I screen recorded after having told my opponent I was about to do something stupid: youtu.be/oXU1GKAcSJw
You'll notice that I started with 20 cards at the beginning of the development phase, but ended up with 23 cards during scoring, and all of the ones I had placed in my park stuck around even after a refresh.
I first noticed this on mobile (Android, Chrome browser) but switched to a Chromebook to see if there was already a bug report for this, and I recorded on the Chromebook. I have yet to see if it happens again, but I will update this if I can do it again in another development phase.
I had thought that maybe this was just a cosmetic issue, but I informed my opponent in the chat that I found a bug, started a screen recording, then confirmed my placed cards (including some of theirs). When the game scored, it scored the cards I had "taken" as if they were my own, but scored my opponent with their correct score (including their original cards).
Refreshing during the development phase reset the board (as it does normally), but I was still able to "take" my opponent's cards, and refreshing after scoring brought the images of my opponent's cards back, but the cards I had "taken" were still in my park- the cards seem to have duplicated themselves!
I screen recorded after having told my opponent I was about to do something stupid: youtu.be/oXU1GKAcSJw
You'll notice that I started with 20 cards at the beginning of the development phase, but ended up with 23 cards during scoring, and all of the ones I had placed in my park stuck around even after a refresh.
I first noticed this on mobile (Android, Chrome browser) but switched to a Chromebook to see if there was already a bug report for this, and I recorded on the Chromebook. I have yet to see if it happens again, but I will update this if I can do it again in another development phase.
okt. 7 th 2023 8:21 • n_e_s_s_u_n_o • Feilen har blitt fikset:
Fixed thank you.
And Thank you for the very good report, rich of details.
And Thank you for the very good report, rich of details.
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.
