• Jei ekrane matote kokį nors klaidos pranešimą, įklijuokite jį čia.

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.

• Prašome paaiškinti, ką norėjote padaryti, ką padarėte ir kas atsitiko

34

• Kokia tavo naršyklė?

• Prašome nukopijuoti / įklijuoti tekstą, rodomą anglų kalba, o ne savo kalba. 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. Ar šis tekstas yra translation system? Jei taip, ar jis buvo išverstas daugiau nei 24 valandas?

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.

• Kokia tavo naršyklė?

• Prašome paaiškinti siūlomą pakeitimą tiksliai ir glaustai, kad būtų kuo lengviau suprasti, ką jūs siūlote.

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.

• Kokia tavo naršyklė?

• Kas buvo pavaizduota ekrane, tave užblokavus (juodas ekranas? Nepilna žaidimo sąsaja? Klaidos pranešimas?)

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.

• Kokia tavo naršyklė?

• Į kurias taisykles neatsižvelgiama BGA žaidimo versijoje

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.

• Ar taisyklių pažeidimas matomas žaidimo atkartojime? Jeigu taip, kuris veiksmo numeris?

34

• Kokia tavo naršyklė?

• Kurį žaidimo veiksmą norėjai atlikti?

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ą reikia padaryti, kad iššauktum šį žaidimo veiksmą?

34

• Kas įvyko kai bandei tai padaryti (klaidos pranešimas, žaidimo būsenos pranešimas, ...)?

• Kokia tavo naršyklė?

• Kuriuo žaidimo metu problema atsirado (koks buvo tuometinis žaidimo nurodymas)?

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 įvyko kai bandei atlikti žaidimo veiksmą (klaidos pranešimas, žaidimo būsenos pranešimas, ...)?

34

• Kokia tavo naršyklė?

• Aprašykite rodomą problemą. 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.

• Kokia tavo naršyklė?

• Prašome nukopijuoti / įklijuoti tekstą, rodomą anglų kalba, o ne savo kalba. 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. Ar šis tekstas yra translation system? Jei taip, ar jis buvo išverstas daugiau nei 24 valandas?

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.

• Kokia tavo naršyklė?

• Prašome paaiškinti siūlomą pakeitimą tiksliai ir glaustai, kad būtų kuo lengviau suprasti, ką jūs siūlote.

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.

• Kokia tavo naršyklė?