#36423: "The new distress signal UX needs improvement"
รายงานนี้เกี่ยวกับอะไร?
เกิดอะไรขึ้น? กรุณาเลือกจากด้านล่าง
เกิดอะไรขึ้น? กรุณาเลือกจากด้านล่าง
โปรดตรวจสอบว่ามีรายงานในหัวข้อเดียวกันอยู่แล้ว
ถ้าใช่โปรดโหวตสำหรับรายงานนี้ รายงานที่ได้รับคะแนนโหวตมากที่สุดจะได้รับลำดับความสำคัญสูง!
# | Status | Votes | Game | Type | Title | Last update |
---|
คำอธิบายโดยละเอียด
• โปรดคัดลอก / วางข้อความแสดงข้อผิดพลาดที่คุณเห็นบนหน้าจอหากมี
When the game asks whether I want to use the distress signal and I click "No", my clock stops counting and I have no reason to believe that any more interaction with the question is required. It confused me greatly when the clock started counting again, and I thought that there must have been a communication problem with the server.
Moreover, even when people understand what's going on with the UI, there are situations where consensus is not reached. At the end of the linked game, we went through a lot of rounds of pressing buttons and arguing in the chat: you can see in the log that it skips from move 126 to move 144 (and I'm not entirely sure that the misplay by one of the players in the first trick wasn't a deliberate way of expressing dissatisfaction).
The idea of having a standardised and localised method to handle the discussion rather than just relying on chat is a good one, but I think that the implementation would be better in a simple three-phase process:
Phase 1: the current question: "Do you want to use the distress signal?" with options "No", "Clockwise", "Anticlockwise". If everyone says "No", skip phases 2 and 3.
Phase 2: those who said "No" get a message "Other players want to use the distress signal. What do you think is best?" with options "Clockwise", "Anticlockwise", "Either", "Please don't".
Phase 3: the commander decides.
It's less democratic, but it's finite. You can't win the argument by having more time on your clock.• โปรดอธิบายสิ่งที่คุณต้องการจะทำสิ่งที่คุณทำและสิ่งที่เกิดขึ้น
• คุณใช้เบราว์เซอร์อะไร?
Google Chrome v79
• โปรดคัดลอก / วางข้อความที่แสดงเป็นภาษาอังกฤษแทนภาษาของคุณ หากคุณมีภาพหน้าจอของข้อบกพร่องนี้ (แนวปฏิบัติที่ดี) คุณสามารถใช้ Imgur.com เพื่ออัปโหลดและคัดลอก / วางลิงค์ที่นี่
When the game asks whether I want to use the distress signal and I click "No", my clock stops counting and I have no reason to believe that any more interaction with the question is required. It confused me greatly when the clock started counting again, and I thought that there must have been a communication problem with the server.
Moreover, even when people understand what's going on with the UI, there are situations where consensus is not reached. At the end of the linked game, we went through a lot of rounds of pressing buttons and arguing in the chat: you can see in the log that it skips from move 126 to move 144 (and I'm not entirely sure that the misplay by one of the players in the first trick wasn't a deliberate way of expressing dissatisfaction).
The idea of having a standardised and localised method to handle the discussion rather than just relying on chat is a good one, but I think that the implementation would be better in a simple three-phase process:
Phase 1: the current question: "Do you want to use the distress signal?" with options "No", "Clockwise", "Anticlockwise". If everyone says "No", skip phases 2 and 3.
Phase 2: those who said "No" get a message "Other players want to use the distress signal. What do you think is best?" with options "Clockwise", "Anticlockwise", "Either", "Please don't".
Phase 3: the commander decides.
It's less democratic, but it's finite. You can't win the argument by having more time on your clock.• ข้อความนี้มีอยู่ใน ระบบการแปล หรือไม่? ถ้าใช่มันแปลมานานกว่า 24 ชั่วโมงแล้วหรือยัง?
• คุณใช้เบราว์เซอร์อะไร?
Google Chrome v79
• โปรดอธิบายข้อเสนอแนะของคุณอย่างแม่นยำและรัดกุมเพื่อให้ง่ายที่สุดที่จะเข้าใจสิ่งที่คุณหมายถึง
When the game asks whether I want to use the distress signal and I click "No", my clock stops counting and I have no reason to believe that any more interaction with the question is required. It confused me greatly when the clock started counting again, and I thought that there must have been a communication problem with the server.
Moreover, even when people understand what's going on with the UI, there are situations where consensus is not reached. At the end of the linked game, we went through a lot of rounds of pressing buttons and arguing in the chat: you can see in the log that it skips from move 126 to move 144 (and I'm not entirely sure that the misplay by one of the players in the first trick wasn't a deliberate way of expressing dissatisfaction).
The idea of having a standardised and localised method to handle the discussion rather than just relying on chat is a good one, but I think that the implementation would be better in a simple three-phase process:
Phase 1: the current question: "Do you want to use the distress signal?" with options "No", "Clockwise", "Anticlockwise". If everyone says "No", skip phases 2 and 3.
Phase 2: those who said "No" get a message "Other players want to use the distress signal. What do you think is best?" with options "Clockwise", "Anticlockwise", "Either", "Please don't".
Phase 3: the commander decides.
It's less democratic, but it's finite. You can't win the argument by having more time on your clock.• คุณใช้เบราว์เซอร์อะไร?
Google Chrome v79
• สิ่งที่ปรากฏบนหน้าจอเมื่อคุณถูกบล็อก (หน้าจอว่างเปล่าส่วนหนึ่งของอินเตอร์เฟซเกมข้อความผิดพลาด?)
When the game asks whether I want to use the distress signal and I click "No", my clock stops counting and I have no reason to believe that any more interaction with the question is required. It confused me greatly when the clock started counting again, and I thought that there must have been a communication problem with the server.
Moreover, even when people understand what's going on with the UI, there are situations where consensus is not reached. At the end of the linked game, we went through a lot of rounds of pressing buttons and arguing in the chat: you can see in the log that it skips from move 126 to move 144 (and I'm not entirely sure that the misplay by one of the players in the first trick wasn't a deliberate way of expressing dissatisfaction).
The idea of having a standardised and localised method to handle the discussion rather than just relying on chat is a good one, but I think that the implementation would be better in a simple three-phase process:
Phase 1: the current question: "Do you want to use the distress signal?" with options "No", "Clockwise", "Anticlockwise". If everyone says "No", skip phases 2 and 3.
Phase 2: those who said "No" get a message "Other players want to use the distress signal. What do you think is best?" with options "Clockwise", "Anticlockwise", "Either", "Please don't".
Phase 3: the commander decides.
It's less democratic, but it's finite. You can't win the argument by having more time on your clock.• คุณใช้เบราว์เซอร์อะไร?
Google Chrome v79
• ส่วนใดของกฎที่ไม่ได้รับความเคารพจากการปรับตัวด้วย BGA
When the game asks whether I want to use the distress signal and I click "No", my clock stops counting and I have no reason to believe that any more interaction with the question is required. It confused me greatly when the clock started counting again, and I thought that there must have been a communication problem with the server.
Moreover, even when people understand what's going on with the UI, there are situations where consensus is not reached. At the end of the linked game, we went through a lot of rounds of pressing buttons and arguing in the chat: you can see in the log that it skips from move 126 to move 144 (and I'm not entirely sure that the misplay by one of the players in the first trick wasn't a deliberate way of expressing dissatisfaction).
The idea of having a standardised and localised method to handle the discussion rather than just relying on chat is a good one, but I think that the implementation would be better in a simple three-phase process:
Phase 1: the current question: "Do you want to use the distress signal?" with options "No", "Clockwise", "Anticlockwise". If everyone says "No", skip phases 2 and 3.
Phase 2: those who said "No" get a message "Other players want to use the distress signal. What do you think is best?" with options "Clockwise", "Anticlockwise", "Either", "Please don't".
Phase 3: the commander decides.
It's less democratic, but it's finite. You can't win the argument by having more time on your clock.• การละเมิดกฎสามารถมองเห็นได้ในการเล่นซ้ำเกมหรือไม่ ถ้าใช่จะย้ายเบอร์ไหน
• คุณใช้เบราว์เซอร์อะไร?
Google Chrome v79
• แอคชั่นเกมใดที่คุณอยากใช้งาน?
When the game asks whether I want to use the distress signal and I click "No", my clock stops counting and I have no reason to believe that any more interaction with the question is required. It confused me greatly when the clock started counting again, and I thought that there must have been a communication problem with the server.
Moreover, even when people understand what's going on with the UI, there are situations where consensus is not reached. At the end of the linked game, we went through a lot of rounds of pressing buttons and arguing in the chat: you can see in the log that it skips from move 126 to move 144 (and I'm not entirely sure that the misplay by one of the players in the first trick wasn't a deliberate way of expressing dissatisfaction).
The idea of having a standardised and localised method to handle the discussion rather than just relying on chat is a good one, but I think that the implementation would be better in a simple three-phase process:
Phase 1: the current question: "Do you want to use the distress signal?" with options "No", "Clockwise", "Anticlockwise". If everyone says "No", skip phases 2 and 3.
Phase 2: those who said "No" get a message "Other players want to use the distress signal. What do you think is best?" with options "Clockwise", "Anticlockwise", "Either", "Please don't".
Phase 3: the commander decides.
It's less democratic, but it's finite. You can't win the argument by having more time on your clock.• คุณพยายามทำอะไรเพื่อกระตุ้นการกระทำของเกมนี้?
• เกิดอะไรขึ้นเมื่อคุณพยายามทำสิ่งนี้ (ข้อความแสดงข้อผิดพลาดข้อความแถบสถานะของเกม ... )?
• คุณใช้เบราว์เซอร์อะไร?
Google Chrome v79
• ปัญหาเกิดขึ้นที่ขั้นตอนใดของเกม (คำสั่งเกมปัจจุบันคืออะไร)
When the game asks whether I want to use the distress signal and I click "No", my clock stops counting and I have no reason to believe that any more interaction with the question is required. It confused me greatly when the clock started counting again, and I thought that there must have been a communication problem with the server.
Moreover, even when people understand what's going on with the UI, there are situations where consensus is not reached. At the end of the linked game, we went through a lot of rounds of pressing buttons and arguing in the chat: you can see in the log that it skips from move 126 to move 144 (and I'm not entirely sure that the misplay by one of the players in the first trick wasn't a deliberate way of expressing dissatisfaction).
The idea of having a standardised and localised method to handle the discussion rather than just relying on chat is a good one, but I think that the implementation would be better in a simple three-phase process:
Phase 1: the current question: "Do you want to use the distress signal?" with options "No", "Clockwise", "Anticlockwise". If everyone says "No", skip phases 2 and 3.
Phase 2: those who said "No" get a message "Other players want to use the distress signal. What do you think is best?" with options "Clockwise", "Anticlockwise", "Either", "Please don't".
Phase 3: the commander decides.
It's less democratic, but it's finite. You can't win the argument by having more time on your clock.• เกิดอะไรขึ้นเมื่อคุณพยายามทำการกระทำของเกม (ข้อความแสดงข้อผิดพลาดข้อความแถบสถานะเกม, ... )
• คุณใช้เบราว์เซอร์อะไร?
Google Chrome v79
• โปรดอธิบายปัญหาการแสดงผล หากคุณมีภาพหน้าจอของข้อบกพร่องนี้ (แนวปฏิบัติที่ดี) คุณสามารถใช้ Imgur.com เพื่ออัปโหลดและคัดลอก / วางลิงค์ที่นี่
When the game asks whether I want to use the distress signal and I click "No", my clock stops counting and I have no reason to believe that any more interaction with the question is required. It confused me greatly when the clock started counting again, and I thought that there must have been a communication problem with the server.
Moreover, even when people understand what's going on with the UI, there are situations where consensus is not reached. At the end of the linked game, we went through a lot of rounds of pressing buttons and arguing in the chat: you can see in the log that it skips from move 126 to move 144 (and I'm not entirely sure that the misplay by one of the players in the first trick wasn't a deliberate way of expressing dissatisfaction).
The idea of having a standardised and localised method to handle the discussion rather than just relying on chat is a good one, but I think that the implementation would be better in a simple three-phase process:
Phase 1: the current question: "Do you want to use the distress signal?" with options "No", "Clockwise", "Anticlockwise". If everyone says "No", skip phases 2 and 3.
Phase 2: those who said "No" get a message "Other players want to use the distress signal. What do you think is best?" with options "Clockwise", "Anticlockwise", "Either", "Please don't".
Phase 3: the commander decides.
It's less democratic, but it's finite. You can't win the argument by having more time on your clock.• คุณใช้เบราว์เซอร์อะไร?
Google Chrome v79
• โปรดคัดลอก / วางข้อความที่แสดงเป็นภาษาอังกฤษแทนภาษาของคุณ หากคุณมีภาพหน้าจอของข้อบกพร่องนี้ (แนวปฏิบัติที่ดี) คุณสามารถใช้ Imgur.com เพื่ออัปโหลดและคัดลอก / วางลิงค์ที่นี่
When the game asks whether I want to use the distress signal and I click "No", my clock stops counting and I have no reason to believe that any more interaction with the question is required. It confused me greatly when the clock started counting again, and I thought that there must have been a communication problem with the server.
Moreover, even when people understand what's going on with the UI, there are situations where consensus is not reached. At the end of the linked game, we went through a lot of rounds of pressing buttons and arguing in the chat: you can see in the log that it skips from move 126 to move 144 (and I'm not entirely sure that the misplay by one of the players in the first trick wasn't a deliberate way of expressing dissatisfaction).
The idea of having a standardised and localised method to handle the discussion rather than just relying on chat is a good one, but I think that the implementation would be better in a simple three-phase process:
Phase 1: the current question: "Do you want to use the distress signal?" with options "No", "Clockwise", "Anticlockwise". If everyone says "No", skip phases 2 and 3.
Phase 2: those who said "No" get a message "Other players want to use the distress signal. What do you think is best?" with options "Clockwise", "Anticlockwise", "Either", "Please don't".
Phase 3: the commander decides.
It's less democratic, but it's finite. You can't win the argument by having more time on your clock.• ข้อความนี้มีอยู่ใน ระบบการแปล หรือไม่? ถ้าใช่มันแปลมานานกว่า 24 ชั่วโมงแล้วหรือยัง?
• คุณใช้เบราว์เซอร์อะไร?
Google Chrome v79
• โปรดอธิบายข้อเสนอแนะของคุณอย่างแม่นยำและรัดกุมเพื่อให้ง่ายที่สุดที่จะเข้าใจสิ่งที่คุณหมายถึง
When the game asks whether I want to use the distress signal and I click "No", my clock stops counting and I have no reason to believe that any more interaction with the question is required. It confused me greatly when the clock started counting again, and I thought that there must have been a communication problem with the server.
Moreover, even when people understand what's going on with the UI, there are situations where consensus is not reached. At the end of the linked game, we went through a lot of rounds of pressing buttons and arguing in the chat: you can see in the log that it skips from move 126 to move 144 (and I'm not entirely sure that the misplay by one of the players in the first trick wasn't a deliberate way of expressing dissatisfaction).
The idea of having a standardised and localised method to handle the discussion rather than just relying on chat is a good one, but I think that the implementation would be better in a simple three-phase process:
Phase 1: the current question: "Do you want to use the distress signal?" with options "No", "Clockwise", "Anticlockwise". If everyone says "No", skip phases 2 and 3.
Phase 2: those who said "No" get a message "Other players want to use the distress signal. What do you think is best?" with options "Clockwise", "Anticlockwise", "Either", "Please don't".
Phase 3: the commander decides.
It's less democratic, but it's finite. You can't win the argument by having more time on your clock.• คุณใช้เบราว์เซอร์อะไร?
Google Chrome v79
ประวัติการรายงาน
The Crew is a cooperative game, that's precisely the point of the game to discuss and debate.
I wish that the help button on the title line leads to a description, how the implementation works.
I believe that option 'distress yes, either direction' is useful.
It is a rather rude and implies dismissiveness, as if you don't care: www.thefreedictionary.com/whatever. It's also quite hated: www.huffpost.com/entry/most-annoying-word-_n_4474607
Better alternatives would be "Abstain", "Neutral" or "No opinion".
I've submitted "No opinion".
เพิ่มการร้องเรียน
- ID ของโต๊ะอื่น / ID ของตาเดิน
- การกด F5 แก้ไขปัญหาหรือไม่
- ปัญหาเกิดขึ้นหลายครั้งหรือไม่ ทุกเวลา? สุ่ม?
- หากคุณมีภาพหน้าจอของข้อบกพร่องนี้ (แนวปฏิบัติที่ดี) คุณสามารถใช้ Imgur.com เพื่ออัปโหลดและคัดลอก / วางลิงค์ที่นี่