#134364: "See only confirmed moves!"
Tentang apa laporan ini?
Apa yang terjadi? Pilih di bawah
Apa yang terjadi? Pilih di bawah
Silakan periksa apakah sudah ada laporan tentang hal yang sama
Jika ya, silakan VOTE untuk laporan ini. Laporan dengan suara terbanyak diberikan PRIORITAS!
# | Status | Votes | Game | Type | Title | Last update |
---|
Detil Deskripsi
• Mohon salin/tempel pesan error yang Anda lihat di layar, jika ada.
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.
• Mohon jelaskan apa yang ingin Anda lakukan, apa yang kemudian Anda lakukan, dan apa yang terjadi
• Apa browser yang Anda gunakan?
Google Chrome v127
• Harap salin/tempel teks yang ditampilkan dalam bahasa Inggris alih-alih bahasa anda. Jika Anda memiliki screenshot bug ini (disarankan), Anda dapat menggunakan Imgur.com untuk menguploadnya dan memberi tautannya di sini.
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.
• apakah teks ini tersedia dalam translation system? jika iya, itu bisa diartikan lebih dari 24 jam
• Apa browser yang Anda gunakan?
Google Chrome v127
• Tolong jelaskan saran Anda secara tepat dan ringkas sehingga semudah mungkin untuk memahami apa yang Anda maksud.
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.
• Apa browser yang Anda gunakan?
Google Chrome v127
• Apa yang tampil di layar ketika Anda tidak dapat berjalan (Layar kosong? Hanya tampil sebagian antar-muka? Pesan error?)
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.
• Apa browser yang Anda gunakan?
Google Chrome v127
• Bagian mana dari peraturan yang tidak diterapkan dengan tepat oleh 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.
• Apakah kesalahan peraturan dapat dilihat dari ulangan permainan? Jika ya, pada langkah ke berapa?
• Apa browser yang Anda gunakan?
Google Chrome v127
• Aksi permainan apa yang ingin Anda lakukan?
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.
• Apa yang Anda coba lakukan untuk memunculkan aksi permainan ini?
• Apa yang terjadi ketika Anda melakukannya (pesan error, pesan status permainan, ...)?
• Apa browser yang Anda gunakan?
Google Chrome v127
• Pada langkah ke berapa masalah tersebut muncul (apa petunjuk permainan saat itu)?
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.
• Apa yang terjadi ketika Anda mencoba untuk melakukan aksi permainan (pesan error, pesan status permainan, ...)?
• Apa browser yang Anda gunakan?
Google Chrome v127
• Mohon jelaskan masalah tampilannya. Jika Anda memiliki screenshot bug ini (disarankan), Anda dapat menggunakan Imgur.com untuk menguploadnya dan memberi tautannya di sini.
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.
• Apa browser yang Anda gunakan?
Google Chrome v127
• Harap salin/tempel teks yang ditampilkan dalam bahasa Inggris alih-alih bahasa anda. Jika Anda memiliki screenshot bug ini (disarankan), Anda dapat menggunakan Imgur.com untuk menguploadnya dan memberi tautannya di sini.
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.
• apakah teks ini tersedia dalam translation system? jika iya, itu bisa diartikan lebih dari 24 jam
• Apa browser yang Anda gunakan?
Google Chrome v127
• Tolong jelaskan saran Anda secara tepat dan ringkas sehingga semudah mungkin untuk memahami apa yang Anda maksud.
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.
• Apa browser yang Anda gunakan?
Google Chrome v127
Laporkan riwayat
Move #71
(It's just one exemple)
Tambahkan hal lain di laporan ini
- ID meja / nomor langkah lainnya
- Apakah F5 menyelesaikan masalah?
- Apakah masalah tersebut telah muncul beberapa kali? Setiap kali? Tidak tentu?
- Jika Anda memiliki screenshot bug ini (disarankan), Anda dapat menggunakan Imgur.com untuk menguploadnya dan memberi tautannya di sini.