• Lūdzu nokopē/ielīmē kļūdas ziņu, ko redzi ekrānā, ja tāda ir.

Here are before and after screenshots. Total score went from 34 to 32, but the played card (bottom right with the gravel and 3 flowers) should be neutral as far as I can tell - no net changes to elements.

imgur.com/a/FDooCWf

While there is a path diagonal on the board (upper right), and the scored 12 points makes it look like the algorithm is using that way on the path, the path legally forks off before that below it for 14.

Before my play the fork to the right (below the upper right diagonal) was a double wide path, but is now single, so perhaps only half the width was counting before and that is the side of the path width that I covered up with this card.

There are several ways to count 14, but the path calc seems to be stopping at the upper right diagonal (12 length reported for longPath) and ignoring the fork option below it forking off to the right side.

• Lūdzu paskaidro, ko Tu vēlējies darīt, ko Tu izdarīji un kas notika

34

• Kāda ir Tava pārlūkprogramma?

• Lūdzu iekopē tekstu, kas redzams angļu, nevis tavā valodā. If you have a screenshot of this bug (good practice), you can use a picture hosting service of your choice (snipboard.io for example) to upload it and copy/paste the link here. Vai šis teksts ir pieejams tulkošanas sistēmā? Ja jā, vai tas ir ticis tulkots pēdējo 24 stundu laikā?

Here are before and after screenshots. Total score went from 34 to 32, but the played card (bottom right with the gravel and 3 flowers) should be neutral as far as I can tell - no net changes to elements.

imgur.com/a/FDooCWf

While there is a path diagonal on the board (upper right), and the scored 12 points makes it look like the algorithm is using that way on the path, the path legally forks off before that below it for 14.

Before my play the fork to the right (below the upper right diagonal) was a double wide path, but is now single, so perhaps only half the width was counting before and that is the side of the path width that I covered up with this card.

There are several ways to count 14, but the path calc seems to be stopping at the upper right diagonal (12 length reported for longPath) and ignoring the fork option below it forking off to the right side.

• Kāda ir Tava pārlūkprogramma?

• Lūdzu, paskaidrojiet savu ieteikumu precīzi un kodolīgi, lai tas būtu pēc iespējas vieglāk saprotams.

Here are before and after screenshots. Total score went from 34 to 32, but the played card (bottom right with the gravel and 3 flowers) should be neutral as far as I can tell - no net changes to elements.

imgur.com/a/FDooCWf

While there is a path diagonal on the board (upper right), and the scored 12 points makes it look like the algorithm is using that way on the path, the path legally forks off before that below it for 14.

Before my play the fork to the right (below the upper right diagonal) was a double wide path, but is now single, so perhaps only half the width was counting before and that is the side of the path width that I covered up with this card.

There are several ways to count 14, but the path calc seems to be stopping at the upper right diagonal (12 length reported for longPath) and ignoring the fork option below it forking off to the right side.

• Kāda ir Tava pārlūkprogramma?

• Kas tika attēlots ekrānā, kad Tu tiki bloķēts (tukšs ekrāns? Daļa no spēles interfeisa? Ziņa par kļūdu?)?

Here are before and after screenshots. Total score went from 34 to 32, but the played card (bottom right with the gravel and 3 flowers) should be neutral as far as I can tell - no net changes to elements.

imgur.com/a/FDooCWf

While there is a path diagonal on the board (upper right), and the scored 12 points makes it look like the algorithm is using that way on the path, the path legally forks off before that below it for 14.

Before my play the fork to the right (below the upper right diagonal) was a double wide path, but is now single, so perhaps only half the width was counting before and that is the side of the path width that I covered up with this card.

There are several ways to count 14, but the path calc seems to be stopping at the upper right diagonal (12 length reported for longPath) and ignoring the fork option below it forking off to the right side.

• Kāda ir Tava pārlūkprogramma?

• Kura noteikumu daļa netika ņemta vērā BGA versijā?

Here are before and after screenshots. Total score went from 34 to 32, but the played card (bottom right with the gravel and 3 flowers) should be neutral as far as I can tell - no net changes to elements.

imgur.com/a/FDooCWf

While there is a path diagonal on the board (upper right), and the scored 12 points makes it look like the algorithm is using that way on the path, the path legally forks off before that below it for 14.

Before my play the fork to the right (below the upper right diagonal) was a double wide path, but is now single, so perhaps only half the width was counting before and that is the side of the path width that I covered up with this card.

There are several ways to count 14, but the path calc seems to be stopping at the upper right diagonal (12 length reported for longPath) and ignoring the fork option below it forking off to the right side.

• Vai noteikumu pārkāpums ir redzams spēles atkārtojumā? Ja jā, tad kurā gājienā?

34

• Kāda ir Tava pārlūkprogramma?

• Kādu spēles darbību Tu vēlējies veikt?

Here are before and after screenshots. Total score went from 34 to 32, but the played card (bottom right with the gravel and 3 flowers) should be neutral as far as I can tell - no net changes to elements.

imgur.com/a/FDooCWf

While there is a path diagonal on the board (upper right), and the scored 12 points makes it look like the algorithm is using that way on the path, the path legally forks off before that below it for 14.

Before my play the fork to the right (below the upper right diagonal) was a double wide path, but is now single, so perhaps only half the width was counting before and that is the side of the path width that I covered up with this card.

There are several ways to count 14, but the path calc seems to be stopping at the upper right diagonal (12 length reported for longPath) and ignoring the fork option below it forking off to the right side.

• Ko tu dari, lai panāktu šo spēles darbību?

34

• Kas notika, kad veicāt šo darbību (kļūdas paziņojums, spēles informācijas paziņojums,...)?

• Kāda ir Tava pārlūkprogramma?

• Kurā spēles solī problēma parādījās (kas bija tā brīža spēles instrukcija)?

Here are before and after screenshots. Total score went from 34 to 32, but the played card (bottom right with the gravel and 3 flowers) should be neutral as far as I can tell - no net changes to elements.

imgur.com/a/FDooCWf

While there is a path diagonal on the board (upper right), and the scored 12 points makes it look like the algorithm is using that way on the path, the path legally forks off before that below it for 14.

Before my play the fork to the right (below the upper right diagonal) was a double wide path, but is now single, so perhaps only half the width was counting before and that is the side of the path width that I covered up with this card.

There are several ways to count 14, but the path calc seems to be stopping at the upper right diagonal (12 length reported for longPath) and ignoring the fork option below it forking off to the right side.

• Kas notika, kad mēģinājāt veikt spēles darbību (kļūdas paziņojums, spēles informācijas paziņojums,...)?

34

• Kāda ir Tava pārlūkprogramma?

• Lūdzu aprakstiet radušos problēmu. If you have a screenshot of this bug (good practice), you can use a picture hosting service of your choice (snipboard.io for example) to upload it and copy/paste the link here.

Here are before and after screenshots. Total score went from 34 to 32, but the played card (bottom right with the gravel and 3 flowers) should be neutral as far as I can tell - no net changes to elements.

imgur.com/a/FDooCWf

While there is a path diagonal on the board (upper right), and the scored 12 points makes it look like the algorithm is using that way on the path, the path legally forks off before that below it for 14.

Before my play the fork to the right (below the upper right diagonal) was a double wide path, but is now single, so perhaps only half the width was counting before and that is the side of the path width that I covered up with this card.

There are several ways to count 14, but the path calc seems to be stopping at the upper right diagonal (12 length reported for longPath) and ignoring the fork option below it forking off to the right side.

• Kāda ir Tava pārlūkprogramma?

• Lūdzu iekopē tekstu, kas redzams angļu, nevis tavā valodā. If you have a screenshot of this bug (good practice), you can use a picture hosting service of your choice (snipboard.io for example) to upload it and copy/paste the link here. Vai šis teksts ir pieejams tulkošanas sistēmā? Ja jā, vai tas ir ticis tulkots pēdējo 24 stundu laikā?

Here are before and after screenshots. Total score went from 34 to 32, but the played card (bottom right with the gravel and 3 flowers) should be neutral as far as I can tell - no net changes to elements.

imgur.com/a/FDooCWf

While there is a path diagonal on the board (upper right), and the scored 12 points makes it look like the algorithm is using that way on the path, the path legally forks off before that below it for 14.

Before my play the fork to the right (below the upper right diagonal) was a double wide path, but is now single, so perhaps only half the width was counting before and that is the side of the path width that I covered up with this card.

There are several ways to count 14, but the path calc seems to be stopping at the upper right diagonal (12 length reported for longPath) and ignoring the fork option below it forking off to the right side.

• Kāda ir Tava pārlūkprogramma?

• Lūdzu, paskaidrojiet savu ieteikumu precīzi un kodolīgi, lai tas būtu pēc iespējas vieglāk saprotams.

Here are before and after screenshots. Total score went from 34 to 32, but the played card (bottom right with the gravel and 3 flowers) should be neutral as far as I can tell - no net changes to elements.

imgur.com/a/FDooCWf

While there is a path diagonal on the board (upper right), and the scored 12 points makes it look like the algorithm is using that way on the path, the path legally forks off before that below it for 14.

Before my play the fork to the right (below the upper right diagonal) was a double wide path, but is now single, so perhaps only half the width was counting before and that is the side of the path width that I covered up with this card.

There are several ways to count 14, but the path calc seems to be stopping at the upper right diagonal (12 length reported for longPath) and ignoring the fork option below it forking off to the right side.

• Kāda ir Tava pārlūkprogramma?