Alle rapporter
crazyfarmers_displayed rapporter
#18889: "Double card when steeling opponents barn not occurring"
fixed: Feilen har blitt fikset
2
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
When claiming an opponents barn you should be awarded 2 cards.
-
• Er regelbruddet tydelig i spilloggen? Hvis ja, Hvilket trekknummer?
Move 169
• Hvilken nettleser bruker du?
Google Chrome v83
Rapporthistorikk
Jun 7 th 2020 21:12 • Kenners2k • Feilen har ikke blitt reprodusert av utviklerne enda:
When reclaiming an opponents barn after it has already been stolen off yourself, you are only awarded 1 card.
The first claiming of an opponents barn works correctly and 2 cards are awarded however subsequent reclaims of that barn are only awarded 1 card.
The first claiming of an opponents barn works correctly and 2 cards are awarded however subsequent reclaims of that barn are only awarded 1 card.
Jun 7 th 2020 21:17 • thinkb4coding • Feilen har ikke blitt reprodusert av utviklerne enda:
I'll check, the only reason I see for this is that you reached the end of the drawpile after the first card.
This would still be a bug
This would still be a bug
Jun 7 th 2020 21:19 • Chauff • Feilen har ikke blitt reprodusert av utviklerne enda:
I am the other player. I didn't figure at the moment, but this barn never gave two cards: I only got 1 when reclaiming this same central barn for the first time, at move 164
Jun 7 th 2020 21:20 • Chauff • Feilen har ikke blitt reprodusert av utviklerne enda:
At the moment I had 4 cards and Kenners 1, so I don't think we reached the end of the drawpile
Jun 7 th 2020 21:59 • thinkb4coding • Feilen har ikke blitt reprodusert av utviklerne enda:
hmm yes this is quite strange. I'll check the code tomorrow, bjutt there are few conditions there so I'm surprised it did not what is expected
Jun 8 th 2020 10:19 • thinkb4coding • Feil har blitt bekreftet av utviklerne:
I didn't know I could load the database in the studio.. and now it has been deleted. But looking closely at the game, the bug happened actually at move 135. When you look carefully at barns, there is 2 slightly different images when they are free or not. Free barns have small grass touches around, and Occupied barns don't have same because it looks not great on parcels colors.
At move 135, there is a 4 parcels takeover containing the central barn. There is correctly 1 card drawn. But the barn is still displayed with the small grass touches, which means it's still considered free...
That's strange, but it explains why, at move 164, the take over gave only 1 card.
At move 135, there is a 4 parcels takeover containing the central barn. There is correctly 1 card drawn. But the barn is still displayed with the small grass touches, which means it's still considered free...
That's strange, but it explains why, at move 164, the take over gave only 1 card.
Jun 8 th 2020 15:27 • thinkb4coding • Feil har blitt bekreftet av utviklerne:
Ok. I found it.
It was a problem happening when taking free barns *and* taking over opponents parcels. The computation of the resulting state was wrongly using initial barns and not recomputed barns... so the fact that the barns was now occupied was lost
It was a problem happening when taking free barns *and* taking over opponents parcels. The computation of the resulting state was wrongly using initial barns and not recomputed barns... so the fact that the barns was now occupied was lost
Jun 8 th 2020 15:33 • thinkb4coding • Feil har blitt bekreftet av utviklerne:
Hopefully the notifications contains all the moves from the game in the same way they are stored in the database.
So I could with a few lines of code rebuild state just before the move causing problems, then playing it and see why the code didn't return the expected result.
So I could with a few lines of code rebuild state just before the move causing problems, then playing it and see why the code didn't return the expected result.
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.
