#134364: "See only confirmed moves!"
Hvad handler denne rapport om?
Hvad skete der? Vær venlig og vælg nedenunder
Hvad skete der? Vær venlig og vælg nedenunder
Vær sød at undersøge, om der allerede er sendt en besked om emnet
Hvis ja, venligst STEM for denne rapport. Rapporter med flest stemmer er dem der får PRIORITET!
| # | Status | Votes | Game | Type | Title | Last update |
|---|
Detaljeret beskrivelse
-
• Venligst kopier/indsæt fejlmeddelelsen du ser på din skærm, hvis der er en.
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.
-
• Venligst forklar hvad du ønsker at gøre, hvad du gjorde og hvad der skete
• Hvilken browser bruger du?
Google Chrome v127
-
• Venligst kopier/indsæt tekst vist på engelsk i stedet for dit sprog. Hvis du har et skærmbillede af denne fejl (god øvelse), kan du bruge Imgur.com til at uploade den og kopiere/indsætte linket her.
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.
-
• er der adgang til denne tekst i oversættelsessystem? Hvis ja, er det blevet oversat inden for 24 timer?
• Hvilken browser bruger du?
Google Chrome v127
-
• Forklar venligst dit forslag præcist og sammenfattende, så det er så let som muligt at forstå, hvad du mener.
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.
• Hvilken browser bruger du?
Google Chrome v127
-
• Hvad blev der vist på skærmen, da du blev blokeret (Blank skærm? Noget af spilbrugerfladen? Fejlmeddelelse?)
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.
• Hvilken browser bruger du?
Google Chrome v127
-
• Hvilken del af reglerne blev ikke respekteret ved BGA-tilpasningen
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.
-
• Er regel-brudddet synligt i e
• Hvilken browser bruger du?
Google Chrome v127
-
• Hvad var den spilhandling du ønskede at udføre?
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.
-
• Hvad forsøgte du at gøre for at udløse denne spilhandling?
-
• Hvad skete der, da du forsøgre at gøre dette (fejlmeddelelse, meddelelsesstatusbjælke, ...)?
• Hvilken browser bruger du?
Google Chrome v127
-
• I hvilket stadie af spillet opstod problemet (hvad var den daværende spilinstruktion)?
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.
-
• Hvad skete der, da du forsøgte at udføre denne spilhandling (fejlmeddelelse, meddelelsesstatusbjælke, ...)?
• Hvilken browser bruger du?
Google Chrome v127
-
• Venligst beskriv display problemet. Hvis du har et skærmbillede af denne fejl (god øvelse), kan du bruge Imgur.com til at uploade den og kopiere/indsætte linket her.
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.
• Hvilken browser bruger du?
Google Chrome v127
-
• Venligst kopier/indsæt tekst vist på engelsk i stedet for dit sprog. Hvis du har et skærmbillede af denne fejl (god øvelse), kan du bruge Imgur.com til at uploade den og kopiere/indsætte linket her.
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.
-
• er der adgang til denne tekst i oversættelsessystem? Hvis ja, er det blevet oversat inden for 24 timer?
• Hvilken browser bruger du?
Google Chrome v127
-
• Forklar venligst dit forslag præcist og sammenfattende, så det er så let som muligt at forstå, hvad du mener.
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.
• Hvilken browser bruger du?
Google Chrome v127
Rapporthistorik
Move #71
(It's just one exemple)
Tilføj noget til denne rapport
- Et andet bord-ID / træk ID
- Løste F5 problemet?
- Skete problemet flere gange? Hver gang? Tilfældigt?
- Hvis du har et skærmbillede af denne fejl (god øvelse), kan du bruge Imgur.com til at uploade den og kopiere/indsætte linket her.
