#142674: "Path score chopped when half a path width covered by a card (not a diagonal situation this time)"
Bu rapor neyle alakali?
Ne oldu? Lütfen aşağıdan seçin
Ne oldu? Lütfen aşağıdan seçin
Lütfen aynı konuda bir rapor olup olmadığını kontrol edin
Eğer evet ise, lütfen bu rapor için oy verin. En çok oy alan raporlar ÖNCELİKLİ!
| # | Status | Votes | Game | Type | Title | Last update |
|---|
Detayli tanim
-
• Eğer varsa, lütfen ekranda gördüğünüz hata mesajını kopyalayın/yapıştırın.
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ütfen ne yapmak istediğini, ne yaptığını ve ne olduğunu açıkla.
34
• Hangi browseri kullaniyorsun?
Google Chrome v128
-
• Lütfen görüntülenen metni kendi diliniz yerine İngilizce olarak kopyalayın/yapıştırın. 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. Bu metin çeviri sisteminde mevcut mu? Evet ise 24 saatten fazla bir süredir tercüme edildi mi?
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. • Hangi browseri kullaniyorsun?
Google Chrome v128
-
• Lütfen önerinizi tam ve net olarak açıklayın, böylece ne demek istediğinizi mümkün olduğunca kolay anlayabiliriz.
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. • Hangi browseri kullaniyorsun?
Google Chrome v128
-
• Engellendiğinizde ekranda ne belirdi (Boş ekran? Oyun arayüzünün bir parçası mı? Hata mesajı?)
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. • Hangi browseri kullaniyorsun?
Google Chrome v128
-
• Kuralların hangi kısmına BGA adaptasyonu tarafından saygı gösterilmedi
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. -
• Kural ihlali oyun tekrarında görünür mü? Eğer evet ise, hangi hareket numarası?
34
• Hangi browseri kullaniyorsun?
Google Chrome v128
-
• Hangi oyun aksiyonu yapmak istedin?
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. -
• Bu oyun eylemini tetiklemek için ne yapmaya çalışıyorsun?
34
-
• Bunu yapmaya çalıştığınızda ne oldu (hata mesajı, oyun durum çubuğu mesajı, ...)?
• Hangi browseri kullaniyorsun?
Google Chrome v128
-
• Oyunun hangi aşamasında sorun oluştu (mevcut oyun talimatı neydi)?
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. -
• Oyunda bu hamleyi yapmaya çalıştığınızda ne oldu (hata mesajı, oyun durum çubuğu mesajı, ...)?
34
• Hangi browseri kullaniyorsun?
Google Chrome v128
-
• Lütfen görüntü sorununu açıklayın. 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. • Hangi browseri kullaniyorsun?
Google Chrome v128
-
• Lütfen görüntülenen metni kendi diliniz yerine İngilizce olarak kopyalayın/yapıştırın. 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. Bu metin çeviri sisteminde mevcut mu? Evet ise 24 saatten fazla bir süredir tercüme edildi mi?
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. • Hangi browseri kullaniyorsun?
Google Chrome v128
-
• Lütfen önerinizi tam ve net olarak açıklayın, böylece ne demek istediğinizi mümkün olduğunca kolay anlayabiliriz.
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. • Hangi browseri kullaniyorsun?
Google Chrome v128
Rapor geçmişi
Bu rapora ekleme yap
- Başka bir masa ID / hareket ID
- F5 sorunu çözdü mü?
- Bu sorun cok mu oluyor ? Her zaman mi ? Tesadüfen mi ?
- 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.
