#134364: "See only confirmed moves!"
Hva handler denne rapporten om?
Hva har skjedd, eller hva gjelder det? Vennligst velg
Hva har skjedd, eller hva gjelder det? Vennligst velg
Vennligst sjekk om det allerede er en rapport om samme emne
Hvis ja, vennligst STEM på denne rapporten. Rapporter med flest stemmer er gitt PRIORITET!
# | Status | Votes | Game | Type | Title | Last update |
---|
Detaljert beskrivelse
• Vennligst kopier/lim inn feilmeldingen du ser på skjermen, om mulig.
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.
• Vennligst forklar hva du ønsket å gjøre, samt hva du faktisk gjorde og hva som skjedde
• Hvilken nettleser bruker du?
Google Chrome v127
• Vennligst kopier / lim inn teksten som vises på engelsk i stedet for språket ditt. Hvis du har et skjermbilde av denne feilen (alltid lurt) kan du bruke Imgur.com for å laste det opp og kopiere inn lenken til bildet 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 denne teksten tilgjengelig i translation system? Hvis ja, har den blitt oversatt i mer enn 24 timer?
• Hvilken nettleser bruker du?
Google Chrome v127
• Vennligst forklar ditt forslag nøyaktig og konsistent slik at det er så enkelt som mulig å forstå hva 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 nettleser bruker du?
Google Chrome v127
• Hva ble vist på skjermen når du ble blokkert (Tom skjerm? Del av spillgrensesnittet? Feilmelding?)
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 nettleser bruker du?
Google Chrome v127
• Hvilken del av reglene ble ikke respektert av 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 regelbruddet tydelig i spilloggen? Hvis ja, Hvilket trekknummer?
• Hvilken nettleser bruker du?
Google Chrome v127
• Hva var spillhandlingen du ønsket å gjø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.
• Hva prøvde du å gjøre for å trigge denne spillhandlingen?
• Hva skjer når du prøver å gjøre dette (feilmelding, meldingsstatus for meldingsfelt, ...)?
• Hvilken nettleser bruker du?
Google Chrome v127
• På hvilket tidspunkt i spillet oppsto problemet (hva var den daværende spillinstruksjonen)?
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.
• Hva skjer når du forsøker å gjøre en spillhandling (feilmelding, spillstatusfeltmelding, ...)?
• Hvilken nettleser bruker du?
Google Chrome v127
• Vennligst beskriv visningsproblemet. Hvis du har et skjermbilde av denne feilen (alltid lurt) kan du bruke Imgur.com for å laste det opp og kopiere inn lenken til bildet 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 nettleser bruker du?
Google Chrome v127
• Vennligst kopier / lim inn teksten som vises på engelsk i stedet for språket ditt. Hvis du har et skjermbilde av denne feilen (alltid lurt) kan du bruke Imgur.com for å laste det opp og kopiere inn lenken til bildet 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 denne teksten tilgjengelig i translation system? Hvis ja, har den blitt oversatt i mer enn 24 timer?
• Hvilken nettleser bruker du?
Google Chrome v127
• Vennligst forklar ditt forslag nøyaktig og konsistent slik at det er så enkelt som mulig å forstå hva 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 nettleser bruker du?
Google Chrome v127
Rapporthistorikk
Move #71
(It's just one exemple)
Legg til noe i denne rapporten
- En annen bord ID / flytt ID
- Løste F5 problemet?
- Oppstod problemet gjentatte ganger? Hver gang? Tilfeldig?
- Hvis du har et skjermbilde av denne feilen (alltid lurt) kan du bruke Imgur.com for å laste det opp og kopiere inn lenken til bildet her.