#134364: "See only confirmed moves!"
What is this report about?
What happened ? Please select from below
What happened ? Please select from below
Please check if there is already a report on the same subject
If yes, please VOTE for this report. Reports with the most votes are taken care of in PRIORITY!
# | Status | Votes | Game | Type | Title | Last update |
---|
Detailed description
• Please copy/paste the error message you see on your screen, if any.
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.
• Please explains what you wanted to do, what you do and what happened
• What is your browser?
Google Chrome v127
• Please copy/paste the text displayed in English instead of your language. If you have a screenshot of this bug (good practice), you can use Imgur.com to upload it and copy/paste the link here.
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.
• Is this text available in the translation system? If yes, has it been translated for more than 24 hours?
• What is your browser?
Google Chrome v127
• Please explain your suggestion precisely and concisely so that it's as easy as possible to understand what you mean.
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.
• What is your browser?
Google Chrome v127
• What was displayed on the screen when you were blocked (Blank screen? Part of the game interface? Error message?)
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.
• What is your browser?
Google Chrome v127
• Which part of the rules was not respected by the BGA adaptation
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.
• Is the rules violation visible on game replay? If yes, at which move number?
• What is your browser?
Google Chrome v127
• Which was the game action you wanted to do?
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.
• What do you try to do to trigger this game action?
• What happened when you try to do this (error message, game status bar message, ...)?
• What is your browser?
Google Chrome v127
• At which step of the game did the problem occurs (what was the current game instruction)?
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.
• What happened when you try to do a game action (error message, game status bar message, ...)?
• What is your browser?
Google Chrome v127
• Please describe the display issue. If you have a screenshot of this bug (good practice), you can use Imgur.com to upload it and copy/paste the link here.
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.
• What is your browser?
Google Chrome v127
• Please copy/paste the text displayed in English instead of your language. If you have a screenshot of this bug (good practice), you can use Imgur.com to upload it and copy/paste the link here.
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.
• Is this text available in the translation system? If yes, has it been translated for more than 24 hours?
• What is your browser?
Google Chrome v127
• Please explain your suggestion precisely and concisely so that it's as easy as possible to understand what you mean.
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.
• What is your browser?
Google Chrome v127
Report history
Move #71
(It's just one exemple)
Add something to this report
- Another table ID / move ID
- Did F5 solve the problem?
- Did the problem appears several time? Everytime? Randomly?
- If you have a screenshot of this bug (good practice), you can use Imgur.com to upload it and copy/paste the link here.