#79532: "Enforce simultaneity"
ما هو هذا التقرير؟
ماذا حدث؟ يرجى اختيار من أدناه
ماذا حدث؟ يرجى اختيار من أدناه
يرجى التحقق مما إذا كان هناك بالفعل تقرير عن نفس الموضوع
إذا كانت الإجابة بنعم ، يرجى التصويت لهذا التقرير. يتم إعطاء التقارير ذات أكبر عدد من الأصوات الأولوية!
| # | Status | Votes | Game | Type | Title | Last update |
|---|
وصف مفصل
-
• يرجى نسخ / لصق رسالة الخطأ التي تراها على الشاشة ، إن وجدت.
This is between a suggestion and a bug.
As per the rules, players 2 to 6 are supposed to make their choice simultaneously and they add that if some people want to wait and see what the others are doing, then people should play in turn order.
I think that the best way to enforce simultaneity is to do as for Railroad Ink and make it so that you cannot see what other players (2 to 6) have done this round (both in log and by looking at their sheet, both before and after F5) until you have done your own round.
( And ensure that you don't get problems as in "It's a wonderful world" where players are interrupted in their actions and get weird refreshes when someone else is playing their turn. )
This kind of simultaneity usually requires some work on the architecture of the code and is best done (or at least foreseen) early in the development.
-
• يرجى توضيح ما تريد القيام به ، ماذا فعلت وما حدث
• ما هو متصفحك؟
Google Chrome v102
-
• يرجى نسخ / لصق النص المعروض باللغة الإنجليزية بدلاً من لغتك. إذا كان لديك لقطة شاشة لهذا الخطأ (ممارسة جيدة) ، يمكنك استخدام Imgur.com لتحميله ونسخ / لصق الرابط هنا.
This is between a suggestion and a bug.
As per the rules, players 2 to 6 are supposed to make their choice simultaneously and they add that if some people want to wait and see what the others are doing, then people should play in turn order.
I think that the best way to enforce simultaneity is to do as for Railroad Ink and make it so that you cannot see what other players (2 to 6) have done this round (both in log and by looking at their sheet, both before and after F5) until you have done your own round.
( And ensure that you don't get problems as in "It's a wonderful world" where players are interrupted in their actions and get weird refreshes when someone else is playing their turn. )
This kind of simultaneity usually requires some work on the architecture of the code and is best done (or at least foreseen) early in the development.
-
• هل هذا النص متاح في translation system ؟ إذا كانت الإجابة بنعم ، فهل تمت ترجمتها لأكثر من 24 ساعة؟
• ما هو متصفحك؟
Google Chrome v102
-
• يرجى توضيح اقتراحك بدقة وإيجاز بحيث يكون من السهل قدر الإمكان فهم ما تعنيه.
This is between a suggestion and a bug.
As per the rules, players 2 to 6 are supposed to make their choice simultaneously and they add that if some people want to wait and see what the others are doing, then people should play in turn order.
I think that the best way to enforce simultaneity is to do as for Railroad Ink and make it so that you cannot see what other players (2 to 6) have done this round (both in log and by looking at their sheet, both before and after F5) until you have done your own round.
( And ensure that you don't get problems as in "It's a wonderful world" where players are interrupted in their actions and get weird refreshes when someone else is playing their turn. )
This kind of simultaneity usually requires some work on the architecture of the code and is best done (or at least foreseen) early in the development.
• ما هو متصفحك؟
Google Chrome v102
-
• ما الذي تم عرضه على الشاشة عندما تم حظرك (شاشة فارغة؟ جزء من واجهة اللعبة؟ رسالة خطأ؟)
This is between a suggestion and a bug.
As per the rules, players 2 to 6 are supposed to make their choice simultaneously and they add that if some people want to wait and see what the others are doing, then people should play in turn order.
I think that the best way to enforce simultaneity is to do as for Railroad Ink and make it so that you cannot see what other players (2 to 6) have done this round (both in log and by looking at their sheet, both before and after F5) until you have done your own round.
( And ensure that you don't get problems as in "It's a wonderful world" where players are interrupted in their actions and get weird refreshes when someone else is playing their turn. )
This kind of simultaneity usually requires some work on the architecture of the code and is best done (or at least foreseen) early in the development.
• ما هو متصفحك؟
Google Chrome v102
-
• أي جزء من القواعد تم مخالفته في تصميم التبني لدى BGA
This is between a suggestion and a bug.
As per the rules, players 2 to 6 are supposed to make their choice simultaneously and they add that if some people want to wait and see what the others are doing, then people should play in turn order.
I think that the best way to enforce simultaneity is to do as for Railroad Ink and make it so that you cannot see what other players (2 to 6) have done this round (both in log and by looking at their sheet, both before and after F5) until you have done your own round.
( And ensure that you don't get problems as in "It's a wonderful world" where players are interrupted in their actions and get weird refreshes when someone else is playing their turn. )
This kind of simultaneity usually requires some work on the architecture of the code and is best done (or at least foreseen) early in the development.
-
• هل انتهاك القواعد مرئي عند إعادة اللعب؟ إذا كانت الإجابة بنعم ، فبأي رقم؟
• ما هو متصفحك؟
Google Chrome v102
-
• ما هو نشاط اللعبة الذي أردت القيام به؟
This is between a suggestion and a bug.
As per the rules, players 2 to 6 are supposed to make their choice simultaneously and they add that if some people want to wait and see what the others are doing, then people should play in turn order.
I think that the best way to enforce simultaneity is to do as for Railroad Ink and make it so that you cannot see what other players (2 to 6) have done this round (both in log and by looking at their sheet, both before and after F5) until you have done your own round.
( And ensure that you don't get problems as in "It's a wonderful world" where players are interrupted in their actions and get weird refreshes when someone else is playing their turn. )
This kind of simultaneity usually requires some work on the architecture of the code and is best done (or at least foreseen) early in the development.
-
• ماذا تحاول أن تفعل لتحريك هذا العمل اللعبة؟
-
• ماذا حدث عند محاولة القيام بهذا (رسالة خطأ ، رسالة شريط حالة اللعبة ، ...)؟
• ما هو متصفحك؟
Google Chrome v102
-
• في أي خطوة من اللعبة حدثت المشكلة (ما هو تعليمة اللعبة الحالية)؟
This is between a suggestion and a bug.
As per the rules, players 2 to 6 are supposed to make their choice simultaneously and they add that if some people want to wait and see what the others are doing, then people should play in turn order.
I think that the best way to enforce simultaneity is to do as for Railroad Ink and make it so that you cannot see what other players (2 to 6) have done this round (both in log and by looking at their sheet, both before and after F5) until you have done your own round.
( And ensure that you don't get problems as in "It's a wonderful world" where players are interrupted in their actions and get weird refreshes when someone else is playing their turn. )
This kind of simultaneity usually requires some work on the architecture of the code and is best done (or at least foreseen) early in the development.
-
• ماذا حدث عند محاولة إجراء هذه الحركة داخل اللعبة (رسالة خطأ ، رسالة شريط حالة اللعبة ، ...)؟
• ما هو متصفحك؟
Google Chrome v102
-
• يرجى وصف مشكلة العرض. إذا كان لديك لقطة شاشة لهذا الخطأ (ممارسة جيدة) ، يمكنك استخدام Imgur.com لتحميله ونسخ / لصق الرابط هنا.
This is between a suggestion and a bug.
As per the rules, players 2 to 6 are supposed to make their choice simultaneously and they add that if some people want to wait and see what the others are doing, then people should play in turn order.
I think that the best way to enforce simultaneity is to do as for Railroad Ink and make it so that you cannot see what other players (2 to 6) have done this round (both in log and by looking at their sheet, both before and after F5) until you have done your own round.
( And ensure that you don't get problems as in "It's a wonderful world" where players are interrupted in their actions and get weird refreshes when someone else is playing their turn. )
This kind of simultaneity usually requires some work on the architecture of the code and is best done (or at least foreseen) early in the development.
• ما هو متصفحك؟
Google Chrome v102
-
• يرجى نسخ / لصق النص المعروض باللغة الإنجليزية بدلاً من لغتك. إذا كان لديك لقطة شاشة لهذا الخطأ (ممارسة جيدة) ، يمكنك استخدام Imgur.com لتحميله ونسخ / لصق الرابط هنا.
This is between a suggestion and a bug.
As per the rules, players 2 to 6 are supposed to make their choice simultaneously and they add that if some people want to wait and see what the others are doing, then people should play in turn order.
I think that the best way to enforce simultaneity is to do as for Railroad Ink and make it so that you cannot see what other players (2 to 6) have done this round (both in log and by looking at their sheet, both before and after F5) until you have done your own round.
( And ensure that you don't get problems as in "It's a wonderful world" where players are interrupted in their actions and get weird refreshes when someone else is playing their turn. )
This kind of simultaneity usually requires some work on the architecture of the code and is best done (or at least foreseen) early in the development.
-
• هل هذا النص متاح في translation system ؟ إذا كانت الإجابة بنعم ، فهل تمت ترجمتها لأكثر من 24 ساعة؟
• ما هو متصفحك؟
Google Chrome v102
-
• يرجى توضيح اقتراحك بدقة وإيجاز بحيث يكون من السهل قدر الإمكان فهم ما تعنيه.
This is between a suggestion and a bug.
As per the rules, players 2 to 6 are supposed to make their choice simultaneously and they add that if some people want to wait and see what the others are doing, then people should play in turn order.
I think that the best way to enforce simultaneity is to do as for Railroad Ink and make it so that you cannot see what other players (2 to 6) have done this round (both in log and by looking at their sheet, both before and after F5) until you have done your own round.
( And ensure that you don't get problems as in "It's a wonderful world" where players are interrupted in their actions and get weird refreshes when someone else is playing their turn. )
This kind of simultaneity usually requires some work on the architecture of the code and is best done (or at least foreseen) early in the development.
• ما هو متصفحك؟
Google Chrome v102
سجل التاريخ
اضف لهذا البلاغ
- تعريف طاولة/تعريف حركة
- هل حلَت F5 المشكلة؟
- هل ظهرت المشكلة عدة مرات؟ كل مرة؟ بطريقة عشوائية؟
- إذا كان لديك لقطة شاشة لهذا الخطأ (ممارسة جيدة) ، يمكنك استخدام Imgur.com لتحميله ونسخ / لصق الرابط هنا.
