#142674: "Path score chopped when half a path width covered by a card (not a diagonal situation this time)"
Despre ce este vorba acest raport?
Ce s-a întâmplat? Te rugăm alege de mai jos
Ce s-a întâmplat? Te rugăm alege de mai jos
Verificați dacă există deja un raport privind același subiect
Dacă da, te rugăm VOTEAZĂ pentru acest raport. Rapoartele cu cele mai multe voturi au PRIORITATE!
| # | Status | Votes | Game | Type | Title | Last update |
|---|
Descriere detaliată
-
• Te rugăm copiază/lipeşte mesajul erorii pe care îl vezi pe ecran, dacă apare vreunul.
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. -
• Explică, te rugăm, ce ai vrut să faci, ce ai făcut, și ce s-a întâmplat
34
• Care e browserul tău?
Google Chrome v128
-
• Va rugam copiati/lipiti textul afisat in engleza in locul limbii dumneavoastra. Dacă ai o captură de ecran cu acest bug (ceea ce îți sugerăm), poți folosi Imgur.com pentru încărcarea imaginii și pentru a pune link-ul aici.
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. -
• Este textul acesta disponibil în sistemul de traduceri? Dacă da, a fost tradus mai recent de 24 de ore?
34
• Care e browserul tău?
Google Chrome v128
-
• Vă rugăm să explicați sugestia exact și concis, astfel încât să fie cât mai ușor de înțeles.
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. • Care e browserul tău?
Google Chrome v128
-
• Ce a fost afișat pe ecran atunci când ai fost blocat (Ecran gol? O parte din interfața jocului? Mesaj de eroare?)
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. • Care e browserul tău?
Google Chrome v128
-
• Care parte din reguli nu a fost respectată de adaptarea 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. -
• Se observă frauda când derulați reluarea? Dacă da, la a câta mutare?
34
• Care e browserul tău?
Google Chrome v128
-
• Care a fost acțiunea pe care ai vrut să o faci?
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. -
• Ce ai făcut de ai produs această reacție/eroare?
34
-
• Ce se întâmplă atunci când vrei să faci asta (apare o eroare, un mesaj din partea jocului in partea de sus a ecranului, ...)?
• Care e browserul tău?
Google Chrome v128
-
• În ce etapă a jocului a apărut eroarea (care era instrucțiunea din acel moment) ?
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. -
• Ce se întâmplă atunci când vrei să acționezi în joc (apare o eroare, un mesaj din partea jocului in partea de sus a ecranului, ...)?
34
• Care e browserul tău?
Google Chrome v128
-
• Descrieți, vă rugăm, problema de afișaj. Dacă ai o captură de ecran cu acest bug (ceea ce îți sugerăm), poți folosi Imgur.com pentru încărcarea imaginii și pentru a pune link-ul aici.
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. • Care e browserul tău?
Google Chrome v128
-
• Va rugam copiati/lipiti textul afisat in engleza in locul limbii dumneavoastra. Dacă ai o captură de ecran cu acest bug (ceea ce îți sugerăm), poți folosi Imgur.com pentru încărcarea imaginii și pentru a pune link-ul aici.
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. -
• Este textul acesta disponibil în sistemul de traduceri? Dacă da, a fost tradus mai recent de 24 de ore?
34
• Care e browserul tău?
Google Chrome v128
-
• Vă rugăm să explicați sugestia exact și concis, astfel încât să fie cât mai ușor de înțeles.
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. • Care e browserul tău?
Google Chrome v128
Raportează istoric
Adaugă ceva la acest raport
- Alt identificator de masă / de mutare
- A rezolvat F5 problema?
- Această problemă a apărut de mai multe ori? De fiecare dată? Ocazional?
- Dacă ai o captură de ecran cu acest bug (ceea ce îți sugerăm), poți folosi Imgur.com pentru încărcarea imaginii și pentru a pune link-ul aici.
