#142674: "Path score chopped when half a path width covered by a card (not a diagonal situation this time)"
על מה דוח זה?
מה קרה? אנא בחר מהרשימה מטה
מה קרה? אנא בחר מהרשימה מטה
בבקשה בדוק אם יש כבר דוח על אותו נושא
אם כן, הצביעו בעד הדיווח הזה, דיווחים עם הכי הרבה קולות נחקרים ראשונים
| # | Status | Votes | Game | Type | Title | Last update |
|---|
תיאור מפורט
-
• אנא העתק/הדבק את הודעת השגיאה המופיעה במסך, אם יש כזו.
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
• מה הדפדפן שלך?
Google Chrome v128
-
• בבקשה העתק והדבק את הטקסט המוצג באנגלית במקום בשפה שלך. 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. • מה הדפדפן שלך?
Google Chrome v128
-
• אנא הסבר את ההצעה שלך במדויק ותמצית כדי שיהיה קל ככל האפשר להבין למה אתה מתכוון.
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. • מה הדפדפן שלך?
Google Chrome v128
-
• מה הוצג על המסך כאשר נחסמה (מסך ריק? חלק ממשק המשחק? הודעת שגיאה?)
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. • מה הדפדפן שלך?
Google Chrome v128
-
• איזה חלק של הכללים לא היה מכובד על ידי עיבוד 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
• מה הדפדפן שלך?
Google Chrome v128
-
• מה היה המהלך במשחק שרצית לבצע?
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
-
• מה קרה כאשר את/ה מנסה לעשות את זה (הודעת שגיאה, הודעת פס סטטוס משחק, ...)?
• מה הדפדפן שלך?
Google Chrome v128
-
• באיזה שלב במשחק הבעייה קרתה (מה היו ההוראות הנכונות)
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
• מה הדפדפן שלך?
Google Chrome v128
-
• אנא תאר/י את הנושא המוצג. 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. • מה הדפדפן שלך?
Google Chrome v128
-
• בבקשה העתק והדבק את הטקסט המוצג באנגלית במקום בשפה שלך. 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. • מה הדפדפן שלך?
Google Chrome v128
-
• אנא הסבר את ההצעה שלך במדויק ותמצית כדי שיהיה קל ככל האפשר להבין למה אתה מתכוון.
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. • מה הדפדפן שלך?
Google Chrome v128
היסטוריית דיווחים
הוסף לדוח הזה
- מספר שולחן/מהלך אחר
- האם לחיצה על F5 פתר את הבעיה?
- האם הבעיה הופיע כמה פעמים? בכל פעם? באופן אקראי?
- 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.
