#142674: "Path score chopped when half a path width covered by a card (not a diagonal situation this time)"
Sobre qué é este informe?
Qué aconteceu? Por favor selecciona debaixo
Qué aconteceu? Por favor selecciona debaixo
Por favor revisa se xa hai un informe sobre o mesmo tema
De ser afirmativo, por favor VOTA por este informe. Aos informes con máis votos se lles da PRIORIDADE!
| # | Status | Votes | Game | Type | Title | Last update |
|---|
Descrición detallada
-
• Por favor, copia e pega a mensaxe de erro que ves na túa pantalla, se houbera algú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. -
• Por favor, explica o que querías facer, o que fixeche e o que pasou
34
• Cal é o teu navegador?
Google Chrome v128
-
• Por favor, copia/pega o texto amosado en inglés no canto do teu idioma. Se tes unha captura de pantalla deste erro (boa práctica), podes usar un servizo de hospedaxe de imaxes da túa elección (snipboard.io, por exemplo) para subila e copiar/pegar o enlace aquí. É este o texto dispoñible no sistema de tradución? Se é así, foi traducido fai máis de 24 horas?
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. • Cal é o teu navegador?
Google Chrome v128
-
• Por favor explica a túa suxestión de maneira precisa e concisa para que sexa o máis sinxelo posible entender o que queres dicir.
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. • Cal é o teu navegador?
Google Chrome v128
-
• Qué había na pantalla cando se quedou bloqueado? (mensaxe de erro?, pantalla en blanco?, unha parte da interface do xogo?)
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. • Cal é o teu navegador?
Google Chrome v128
-
• Qué parte das regras non se cumpriron na adaptación da 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. -
• é visible a violación das regras na repetición? Se o é, en que número de movemento?
34
• Cal é o teu navegador?
Google Chrome v128
-
• Qué acción de xogo querías realizar?
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. -
• Qué é o que tratache de facer para activar esta acción do xogo?
34
-
• Qué sucedeu cando o fixeche (a mensaxe de erro, mensaxe na barra de estado do xogo, ...)?
• Cal é o teu navegador?
Google Chrome v128
-
• En que paso do xogo ocorreu o problema (cal foi a instrucción actual do xogo)?
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. -
• Qué sucedeu cando tratache de facer unha acción de xogo (mensaxe de erro, mensaxe na barra de estado do xogo, ...)?
34
• Cal é o teu navegador?
Google Chrome v128
-
• Por favor, describe o problema de visualización. Se tes unha captura de pantalla deste erro (boa práctica), podes usar un servizo de hospedaxe de imaxes da túa elección (snipboard.io, por exemplo) para subila e copiar/pegar o enlace aquí.
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. • Cal é o teu navegador?
Google Chrome v128
-
• Por favor, copia/pega o texto amosado en inglés no canto do teu idioma. Se tes unha captura de pantalla deste erro (boa práctica), podes usar un servizo de hospedaxe de imaxes da túa elección (snipboard.io, por exemplo) para subila e copiar/pegar o enlace aquí. É este o texto dispoñible no sistema de tradución? Se é así, foi traducido fai máis de 24 horas?
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. • Cal é o teu navegador?
Google Chrome v128
-
• Por favor explica a túa suxestión de maneira precisa e concisa para que sexa o máis sinxelo posible entender o que queres dicir.
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. • Cal é o teu navegador?
Google Chrome v128
Historial de informes
Engade a este informe
- Outro DI de mesa / ID de movemento
- Premer F5 resolveu o problema?
- Apareceu o problema varias veces? Tódalas veces? Aleatoriamente?
- Se tes unha captura de pantalla deste erro (boa práctica), podes usar un servizo de hospedaxe de imaxes da túa elección (snipboard.io, por exemplo) para subila e copiar/pegar o enlace aquí.
