• โปรดคัดลอก / วางข้อความแสดงข้อผิดพลาดที่คุณเห็นบนหน้าจอหากมี

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.

• โปรดอธิบายสิ่งที่คุณต้องการจะทำสิ่งที่คุณทำและสิ่งที่เกิดขึ้น

34

• คุณใช้เบราว์เซอร์อะไร?

• โปรดคัดลอก / วางข้อความที่แสดงเป็นภาษาอังกฤษแทนภาษาของคุณ 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. ข้อความนี้มีอยู่ใน ระบบการแปล หรือไม่? ถ้าใช่มันแปลมานานกว่า 24 ชั่วโมงแล้วหรือยัง?

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.

• คุณใช้เบราว์เซอร์อะไร?

• โปรดอธิบายข้อเสนอแนะของคุณอย่างแม่นยำและรัดกุมเพื่อให้ง่ายที่สุดที่จะเข้าใจสิ่งที่คุณหมายถึง

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.

• คุณใช้เบราว์เซอร์อะไร?

• สิ่งที่ปรากฏบนหน้าจอเมื่อคุณถูกบล็อก (หน้าจอว่างเปล่าส่วนหนึ่งของอินเตอร์เฟซเกมข้อความผิดพลาด?)

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.

• คุณใช้เบราว์เซอร์อะไร?

• ส่วนใดของกฎที่ไม่ได้รับความเคารพจากการปรับตัวด้วย BGA

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.

• การละเมิดกฎสามารถมองเห็นได้ในการเล่นซ้ำเกมหรือไม่ ถ้าใช่จะย้ายเบอร์ไหน

34

• คุณใช้เบราว์เซอร์อะไร?

• แอคชั่นเกมใดที่คุณอยากใช้งาน?

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.

• คุณพยายามทำอะไรเพื่อกระตุ้นการกระทำของเกมนี้?

34

• เกิดอะไรขึ้นเมื่อคุณพยายามทำสิ่งนี้ (ข้อความแสดงข้อผิดพลาดข้อความแถบสถานะของเกม ... )?

• คุณใช้เบราว์เซอร์อะไร?

• ปัญหาเกิดขึ้นที่ขั้นตอนใดของเกม (คำสั่งเกมปัจจุบันคืออะไร)

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.

• เกิดอะไรขึ้นเมื่อคุณพยายามทำการกระทำของเกม (ข้อความแสดงข้อผิดพลาดข้อความแถบสถานะเกม, ... )

34

• คุณใช้เบราว์เซอร์อะไร?

• โปรดอธิบายปัญหาการแสดงผล 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.

• คุณใช้เบราว์เซอร์อะไร?

• โปรดคัดลอก / วางข้อความที่แสดงเป็นภาษาอังกฤษแทนภาษาของคุณ 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. ข้อความนี้มีอยู่ใน ระบบการแปล หรือไม่? ถ้าใช่มันแปลมานานกว่า 24 ชั่วโมงแล้วหรือยัง?

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.

• คุณใช้เบราว์เซอร์อะไร?

• โปรดอธิบายข้อเสนอแนะของคุณอย่างแม่นยำและรัดกุมเพื่อให้ง่ายที่สุดที่จะเข้าใจสิ่งที่คุณหมายถึง

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.

• คุณใช้เบราว์เซอร์อะไร?