#134364: "See only confirmed moves!"
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.
I'm really glad to see this classic implemented here. Well done!
Unfortunately, one negative element should be corrected if possible. It's really unpleasant to see in the game log the color and square of a tile unofficially played by an opponent who then decides to undo his action. (I can't remember what it's like in real time, on the game board itself, as I play almost exclusively turn-based games, and I'm never in front of my screen when an opponent makes his move).
The identity of the tiles played should only be visible when the action is confirmed by the player - as implemented, for example, in Castles of Burgundy. (Incidentally, this implementation is of little importance in CoB, as players don't have a private, secret area). As it is, it's a bit like opponents sharing part of their hand every time they hesitate on a move, whereas the very essence of the game demands that the identity of our hand be constantly unknown to our opponents.
• Por favor explique o que queria fazer, o que fez e o que aconteceu
• Qual navegador você está usando?
Google Chrome v127
• 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.
I'm really glad to see this classic implemented here. Well done!
Unfortunately, one negative element should be corrected if possible. It's really unpleasant to see in the game log the color and square of a tile unofficially played by an opponent who then decides to undo his action. (I can't remember what it's like in real time, on the game board itself, as I play almost exclusively turn-based games, and I'm never in front of my screen when an opponent makes his move).
The identity of the tiles played should only be visible when the action is confirmed by the player - as implemented, for example, in Castles of Burgundy. (Incidentally, this implementation is of little importance in CoB, as players don't have a private, secret area). As it is, it's a bit like opponents sharing part of their hand every time they hesitate on a move, whereas the very essence of the game demands that the identity of our hand be constantly unknown to our opponents.
• Este texto está disponível no sistema de traduções? Se sim, foi traduzido há mais de 24 horas?
• Qual navegador você está usando?
Google Chrome v127
• 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.
I'm really glad to see this classic implemented here. Well done!
Unfortunately, one negative element should be corrected if possible. It's really unpleasant to see in the game log the color and square of a tile unofficially played by an opponent who then decides to undo his action. (I can't remember what it's like in real time, on the game board itself, as I play almost exclusively turn-based games, and I'm never in front of my screen when an opponent makes his move).
The identity of the tiles played should only be visible when the action is confirmed by the player - as implemented, for example, in Castles of Burgundy. (Incidentally, this implementation is of little importance in CoB, as players don't have a private, secret area). As it is, it's a bit like opponents sharing part of their hand every time they hesitate on a move, whereas the very essence of the game demands that the identity of our hand be constantly unknown to our opponents.
• Qual navegador você está usando?
Google Chrome v127
• O que estava presente na tela quando você estava bloqueado (tela em branco? Parte da imagem do jogo? Mensagem de erro?)
I'm really glad to see this classic implemented here. Well done!
Unfortunately, one negative element should be corrected if possible. It's really unpleasant to see in the game log the color and square of a tile unofficially played by an opponent who then decides to undo his action. (I can't remember what it's like in real time, on the game board itself, as I play almost exclusively turn-based games, and I'm never in front of my screen when an opponent makes his move).
The identity of the tiles played should only be visible when the action is confirmed by the player - as implemented, for example, in Castles of Burgundy. (Incidentally, this implementation is of little importance in CoB, as players don't have a private, secret area). As it is, it's a bit like opponents sharing part of their hand every time they hesitate on a move, whereas the very essence of the game demands that the identity of our hand be constantly unknown to our opponents.
• Qual navegador você está usando?
Google Chrome v127
• Que parte das regras não foi respeitada pela adaptação do BGA?
I'm really glad to see this classic implemented here. Well done!
Unfortunately, one negative element should be corrected if possible. It's really unpleasant to see in the game log the color and square of a tile unofficially played by an opponent who then decides to undo his action. (I can't remember what it's like in real time, on the game board itself, as I play almost exclusively turn-based games, and I'm never in front of my screen when an opponent makes his move).
The identity of the tiles played should only be visible when the action is confirmed by the player - as implemented, for example, in Castles of Burgundy. (Incidentally, this implementation is of little importance in CoB, as players don't have a private, secret area). As it is, it's a bit like opponents sharing part of their hand every time they hesitate on a move, whereas the very essence of the game demands that the identity of our hand be constantly unknown to our opponents.
• A violação de regras está visível na revisão do jogo? Se sim, em que número de jogada?
• Qual navegador você está usando?
Google Chrome v127
• Qual era a ação de jogo que queria fazer?
I'm really glad to see this classic implemented here. Well done!
Unfortunately, one negative element should be corrected if possible. It's really unpleasant to see in the game log the color and square of a tile unofficially played by an opponent who then decides to undo his action. (I can't remember what it's like in real time, on the game board itself, as I play almost exclusively turn-based games, and I'm never in front of my screen when an opponent makes his move).
The identity of the tiles played should only be visible when the action is confirmed by the player - as implemented, for example, in Castles of Burgundy. (Incidentally, this implementation is of little importance in CoB, as players don't have a private, secret area). As it is, it's a bit like opponents sharing part of their hand every time they hesitate on a move, whereas the very essence of the game demands that the identity of our hand be constantly unknown to our opponents.
• O que você tentou fazer para provocar esta ação de jogo?
• O que aconteceu quando tentou fazer isto(mensagem de erro, mensagem na barra de estado do jogo)?
• Qual navegador você está usando?
Google Chrome v127
• Em que passo do jogo ocorre o problema(qual era a instrução corrente do jogo)?
I'm really glad to see this classic implemented here. Well done!
Unfortunately, one negative element should be corrected if possible. It's really unpleasant to see in the game log the color and square of a tile unofficially played by an opponent who then decides to undo his action. (I can't remember what it's like in real time, on the game board itself, as I play almost exclusively turn-based games, and I'm never in front of my screen when an opponent makes his move).
The identity of the tiles played should only be visible when the action is confirmed by the player - as implemented, for example, in Castles of Burgundy. (Incidentally, this implementation is of little importance in CoB, as players don't have a private, secret area). As it is, it's a bit like opponents sharing part of their hand every time they hesitate on a move, whereas the very essence of the game demands that the identity of our hand be constantly unknown to our opponents.
• O que aconteceu quando tentou fazer essa ação de jogo (mensagem de erro, mensagem na barra de estado do jogo)?
• Qual navegador você está usando?
Google Chrome v127
• 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.
I'm really glad to see this classic implemented here. Well done!
Unfortunately, one negative element should be corrected if possible. It's really unpleasant to see in the game log the color and square of a tile unofficially played by an opponent who then decides to undo his action. (I can't remember what it's like in real time, on the game board itself, as I play almost exclusively turn-based games, and I'm never in front of my screen when an opponent makes his move).
The identity of the tiles played should only be visible when the action is confirmed by the player - as implemented, for example, in Castles of Burgundy. (Incidentally, this implementation is of little importance in CoB, as players don't have a private, secret area). As it is, it's a bit like opponents sharing part of their hand every time they hesitate on a move, whereas the very essence of the game demands that the identity of our hand be constantly unknown to our opponents.
• Qual navegador você está usando?
Google Chrome v127
• 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.
I'm really glad to see this classic implemented here. Well done!
Unfortunately, one negative element should be corrected if possible. It's really unpleasant to see in the game log the color and square of a tile unofficially played by an opponent who then decides to undo his action. (I can't remember what it's like in real time, on the game board itself, as I play almost exclusively turn-based games, and I'm never in front of my screen when an opponent makes his move).
The identity of the tiles played should only be visible when the action is confirmed by the player - as implemented, for example, in Castles of Burgundy. (Incidentally, this implementation is of little importance in CoB, as players don't have a private, secret area). As it is, it's a bit like opponents sharing part of their hand every time they hesitate on a move, whereas the very essence of the game demands that the identity of our hand be constantly unknown to our opponents.
• Este texto está disponível no sistema de traduções? Se sim, foi traduzido há mais de 24 horas?
• Qual navegador você está usando?
Google Chrome v127
• 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.
I'm really glad to see this classic implemented here. Well done!
Unfortunately, one negative element should be corrected if possible. It's really unpleasant to see in the game log the color and square of a tile unofficially played by an opponent who then decides to undo his action. (I can't remember what it's like in real time, on the game board itself, as I play almost exclusively turn-based games, and I'm never in front of my screen when an opponent makes his move).
The identity of the tiles played should only be visible when the action is confirmed by the player - as implemented, for example, in Castles of Burgundy. (Incidentally, this implementation is of little importance in CoB, as players don't have a private, secret area). As it is, it's a bit like opponents sharing part of their hand every time they hesitate on a move, whereas the very essence of the game demands that the identity of our hand be constantly unknown to our opponents.
• Qual navegador você está usando?
Google Chrome v127
Histórico do relatório
Move #71
(It's just one exemple)
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.