#142674: "Path score chopped when half a path width covered by a card (not a diagonal situation this time)"
Sobre o que é este relatório?
O que aconteceu ? Por favor escolha abaixo
O que aconteceu ? Por favor escolha abaixo
Por favor, cheque se já há um report com o mesmo assunto
Se sim, por favor, VOTE para este report. Reports com mais votos recebem PRIORIDADE!
# | Status | Votes | Game | Type | Title | Last update |
---|
Descrição detalhada
-
• Por favor copie e cole a mensagem de erro que aparece na tela, se possível.
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 explique o que queria fazer, o que fez e o que aconteceu
34
• Qual navegador você está usando?
Google Chrome v128
-
• Por favor copie/cole o texto em inglês em vez de sua língua. Se tiver uma captura de ecrã/tela deste problema (boa prática), pode usar Imgur.com para carregá-la e copiar/colar o endereço aqui.
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 texto está disponível no sistema de traduções? Se sim, foi traduzido há mais de 24 horas?
34
• Qual navegador você está usando?
Google Chrome v128
-
• Por favor, explique sua sugestão precisamente e de forma concisa, de forma que fique o mais fácil possível, entender o que você quer dizer.
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. • Qual navegador você está usando?
Google Chrome v128
-
• O que estava presente na tela quando você estava bloqueado (tela em branco? Parte da imagem do jogo? Mensagem de erro?)
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. • Qual navegador você está usando?
Google Chrome v128
-
• Que parte das regras não foi respeitada pela adaptação do 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. -
• A violação de regras está visível na revisão do jogo? Se sim, em que número de jogada?
34
• Qual navegador você está usando?
Google Chrome v128
-
• Qual era a ação de jogo que queria fazer?
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. -
• O que você tentou fazer para provocar esta ação de jogo?
34
-
• O que aconteceu quando tentou fazer isto(mensagem de erro, mensagem na barra de estado do jogo)?
• Qual navegador você está usando?
Google Chrome v128
-
• Em que passo do jogo ocorre o problema(qual era a instrução corrente do jogo)?
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. -
• O que aconteceu quando tentou fazer essa ação de jogo (mensagem de erro, mensagem na barra de estado do jogo)?
34
• Qual navegador você está usando?
Google Chrome v128
-
• Por favor descreva o problema de visualização. Se tiver uma captura de ecrã/tela deste problema (boa prática), pode usar Imgur.com para carregá-la e copiar/colar o endereço aqui.
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. • Qual navegador você está usando?
Google Chrome v128
-
• Por favor copie/cole o texto em inglês em vez de sua língua. Se tiver uma captura de ecrã/tela deste problema (boa prática), pode usar Imgur.com para carregá-la e copiar/colar o endereço aqui.
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 texto está disponível no sistema de traduções? Se sim, foi traduzido há mais de 24 horas?
34
• Qual navegador você está usando?
Google Chrome v128
-
• Por favor, explique sua sugestão precisamente e de forma concisa, de forma que fique o mais fácil possível, entender o que você quer dizer.
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. • Qual navegador você está usando?
Google Chrome v128
Histórico do relatório
Adicione alguma coisa para este relatório
- Outro ID de mesa / ID de jogada
- Carregar em F5 resolveu o problema?
- O problema aparece várias vezes? Sempre? Imprevisivelmente?
- Se tiver uma captura de ecrã/tela deste problema (boa prática), pode usar Imgur.com para carregá-la e copiar/colar o endereço aqui.