• Kopieer en plak alsjeblieft de foutboodschap die je op je scherm ziet, indien van toepassing.

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.

• Leg uit wat je wilde doen, wat je deed en wat er gebeurde

34

• Welke browser gebruik je?

• Kopieer en plak alsjeblieft de tekst die in het Engels wordt getoond in plaats van in jouw taal. Als je een schermkopie van deze bug hebt (goede gewoonte), kun je een hosting-service voor afbeeldingen naar keuze gebruiken (bijvoorbeeld snipboard.io) om deze te uploaden en de link hier te kopiëren/plakken. Is deze tekst beschikbaar in het vertaalsysteem? Zo ja, is deze meer dan 24 uur geleden vertaald?

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.

• Welke browser gebruik je?

• Gelieve jouw suggestie precies en beknopt uit te leggen zodat het zo makkelijk mogelijk is om te begrijpen wat je bedoelt.

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.

• Welke browser gebruik je?

• Wat stond op het scherm toen je geblokkeerd was (Leeg scherm? Een deel van de spelinterface? Foutboodschap?)

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.

• Welke browser gebruik je?

• Met welk onderdeel van de regels is geen rekening gehouden bij de BGA-versie?

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.

• Is de inbreuk op de spelregels zichtbaar in de spelherhaling? Indien ja, bij welk zetnummer?

34

• Welke browser gebruik je?

• Welke spelactie wilde je uitvoeren?

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.

• Wat probeerde je te doen om deze spelactie te laten optreden?

34

• Wat gebeurde er toen je dit probeerde te doen (foutboodschap, melding op de statusbalk van het spel, ...)?

• Welke browser gebruik je?

• In welke fase van het spel deed het probleem zich voor (wat was de huidige spelinstructie)?

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.

• Wat gebeurde toen je deze spelactie probeerde (foutboodschap, melding op de statusbalk van het spel, ...)?

34

• Welke browser gebruik je?

• Beschrijf alsjeblieft het probleem met de beeldweergave. Als je een schermkopie van deze bug hebt (goede gewoonte), kun je een hosting-service voor afbeeldingen naar keuze gebruiken (bijvoorbeeld snipboard.io) om deze te uploaden en de link hier te kopiëren/plakken.

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.

• Welke browser gebruik je?

• Kopieer en plak alsjeblieft de tekst die in het Engels wordt getoond in plaats van in jouw taal. Als je een schermkopie van deze bug hebt (goede gewoonte), kun je een hosting-service voor afbeeldingen naar keuze gebruiken (bijvoorbeeld snipboard.io) om deze te uploaden en de link hier te kopiëren/plakken. Is deze tekst beschikbaar in het vertaalsysteem? Zo ja, is deze meer dan 24 uur geleden vertaald?

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.

• Welke browser gebruik je?

• Gelieve jouw suggestie precies en beknopt uit te leggen zodat het zo makkelijk mogelijk is om te begrijpen wat je bedoelt.

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.

• Welke browser gebruik je?