#87310: "Burgle Bros - Loitering check"
เกิดอะไรขึ้น? กรุณาเลือกจากด้านล่าง
เกิดอะไรขึ้น? กรุณาเลือกจากด้านล่าง
โปรดตรวจสอบว่ามีรายงานในหัวข้อเดียวกันอยู่แล้ว
ถ้าใช่โปรดโหวตสำหรับรายงานนี้ รายงานที่ได้รับคะแนนโหวตมากที่สุดจะได้รับลำดับความสำคัญสูง!
# | Status | Votes | Game | Type | Title | Last update |
---|
คำอธิบายโดยละเอียด
• โปรดคัดลอก / วางข้อความแสดงข้อผิดพลาดที่คุณเห็นบนหน้าจอหากมี
Currently in Burgle Bros, the rules state you're not allowed to move "back and forth" in order to avoid drawing an event. However, it has been stated that this would be too difficult to code, and would result in false positives, and so (understandably), the devs focused on more productive things.
As a programmer myself, I spent some time analyzing the problem, as I knew I could tackle this, and I have the time to (unlike your devs :) ) and believe I have a draft solution which is a viable option as it:
1) doesn't result in false positives.
2) Simple coding logic changes to implement - nothing major, no redesign needed - you have all the info already, it's just a matter of gathering it up and using it properly.
3) flexible - so we can focus on the "simple"/obvious checks first .. and consider expanding to trickier ones later (if we want).
The logic is simple:
1) capture the current board "state" (everything, including tiles, hidden tiles, walls, player/guard positions, tools/loot positions, hack tokens .. alarms .. etc.) store it as a simple string (1 character per "item", ie Safe = "S", Walkway = "W", etc.)
2) boolean flag to indicate dice were rolled (ie safe, keypad, etc.) This provides a marker, as we won't compare board states beyond a dice roll. (think 1 move into a keypad, and failing the roll)
3) Compare latest board state with al previous ones up to a die roll event.
4) if any match, reject the move as "loitering" ..
• โปรดอธิบายสิ่งที่คุณต้องการจะทำสิ่งที่คุณทำและสิ่งที่เกิดขึ้น
• คุณใช้เบราว์เซอร์อะไร?
Google Chrome v112
• โปรดคัดลอก / วางข้อความที่แสดงเป็นภาษาอังกฤษแทนภาษาของคุณ หากคุณมีภาพหน้าจอของข้อบกพร่องนี้ (แนวปฏิบัติที่ดี) คุณสามารถใช้ Imgur.com เพื่ออัปโหลดและคัดลอก / วางลิงค์ที่นี่
Currently in Burgle Bros, the rules state you're not allowed to move "back and forth" in order to avoid drawing an event. However, it has been stated that this would be too difficult to code, and would result in false positives, and so (understandably), the devs focused on more productive things.
As a programmer myself, I spent some time analyzing the problem, as I knew I could tackle this, and I have the time to (unlike your devs :) ) and believe I have a draft solution which is a viable option as it:
1) doesn't result in false positives.
2) Simple coding logic changes to implement - nothing major, no redesign needed - you have all the info already, it's just a matter of gathering it up and using it properly.
3) flexible - so we can focus on the "simple"/obvious checks first .. and consider expanding to trickier ones later (if we want).
The logic is simple:
1) capture the current board "state" (everything, including tiles, hidden tiles, walls, player/guard positions, tools/loot positions, hack tokens .. alarms .. etc.) store it as a simple string (1 character per "item", ie Safe = "S", Walkway = "W", etc.)
2) boolean flag to indicate dice were rolled (ie safe, keypad, etc.) This provides a marker, as we won't compare board states beyond a dice roll. (think 1 move into a keypad, and failing the roll)
3) Compare latest board state with al previous ones up to a die roll event.
4) if any match, reject the move as "loitering" ..
• ข้อความนี้มีอยู่ใน ระบบการแปล หรือไม่? ถ้าใช่มันแปลมานานกว่า 24 ชั่วโมงแล้วหรือยัง?
• คุณใช้เบราว์เซอร์อะไร?
Google Chrome v112
• โปรดอธิบายข้อเสนอแนะของคุณอย่างแม่นยำและรัดกุมเพื่อให้ง่ายที่สุดที่จะเข้าใจสิ่งที่คุณหมายถึง
Currently in Burgle Bros, the rules state you're not allowed to move "back and forth" in order to avoid drawing an event. However, it has been stated that this would be too difficult to code, and would result in false positives, and so (understandably), the devs focused on more productive things.
As a programmer myself, I spent some time analyzing the problem, as I knew I could tackle this, and I have the time to (unlike your devs :) ) and believe I have a draft solution which is a viable option as it:
1) doesn't result in false positives.
2) Simple coding logic changes to implement - nothing major, no redesign needed - you have all the info already, it's just a matter of gathering it up and using it properly.
3) flexible - so we can focus on the "simple"/obvious checks first .. and consider expanding to trickier ones later (if we want).
The logic is simple:
1) capture the current board "state" (everything, including tiles, hidden tiles, walls, player/guard positions, tools/loot positions, hack tokens .. alarms .. etc.) store it as a simple string (1 character per "item", ie Safe = "S", Walkway = "W", etc.)
2) boolean flag to indicate dice were rolled (ie safe, keypad, etc.) This provides a marker, as we won't compare board states beyond a dice roll. (think 1 move into a keypad, and failing the roll)
3) Compare latest board state with al previous ones up to a die roll event.
4) if any match, reject the move as "loitering" ..
• คุณใช้เบราว์เซอร์อะไร?
Google Chrome v112
• สิ่งที่ปรากฏบนหน้าจอเมื่อคุณถูกบล็อก (หน้าจอว่างเปล่าส่วนหนึ่งของอินเตอร์เฟซเกมข้อความผิดพลาด?)
Currently in Burgle Bros, the rules state you're not allowed to move "back and forth" in order to avoid drawing an event. However, it has been stated that this would be too difficult to code, and would result in false positives, and so (understandably), the devs focused on more productive things.
As a programmer myself, I spent some time analyzing the problem, as I knew I could tackle this, and I have the time to (unlike your devs :) ) and believe I have a draft solution which is a viable option as it:
1) doesn't result in false positives.
2) Simple coding logic changes to implement - nothing major, no redesign needed - you have all the info already, it's just a matter of gathering it up and using it properly.
3) flexible - so we can focus on the "simple"/obvious checks first .. and consider expanding to trickier ones later (if we want).
The logic is simple:
1) capture the current board "state" (everything, including tiles, hidden tiles, walls, player/guard positions, tools/loot positions, hack tokens .. alarms .. etc.) store it as a simple string (1 character per "item", ie Safe = "S", Walkway = "W", etc.)
2) boolean flag to indicate dice were rolled (ie safe, keypad, etc.) This provides a marker, as we won't compare board states beyond a dice roll. (think 1 move into a keypad, and failing the roll)
3) Compare latest board state with al previous ones up to a die roll event.
4) if any match, reject the move as "loitering" ..
• คุณใช้เบราว์เซอร์อะไร?
Google Chrome v112
• ส่วนใดของกฎที่ไม่ได้รับความเคารพจากการปรับตัวด้วย BGA
Currently in Burgle Bros, the rules state you're not allowed to move "back and forth" in order to avoid drawing an event. However, it has been stated that this would be too difficult to code, and would result in false positives, and so (understandably), the devs focused on more productive things.
As a programmer myself, I spent some time analyzing the problem, as I knew I could tackle this, and I have the time to (unlike your devs :) ) and believe I have a draft solution which is a viable option as it:
1) doesn't result in false positives.
2) Simple coding logic changes to implement - nothing major, no redesign needed - you have all the info already, it's just a matter of gathering it up and using it properly.
3) flexible - so we can focus on the "simple"/obvious checks first .. and consider expanding to trickier ones later (if we want).
The logic is simple:
1) capture the current board "state" (everything, including tiles, hidden tiles, walls, player/guard positions, tools/loot positions, hack tokens .. alarms .. etc.) store it as a simple string (1 character per "item", ie Safe = "S", Walkway = "W", etc.)
2) boolean flag to indicate dice were rolled (ie safe, keypad, etc.) This provides a marker, as we won't compare board states beyond a dice roll. (think 1 move into a keypad, and failing the roll)
3) Compare latest board state with al previous ones up to a die roll event.
4) if any match, reject the move as "loitering" ..
• การละเมิดกฎสามารถมองเห็นได้ในการเล่นซ้ำเกมหรือไม่ ถ้าใช่จะย้ายเบอร์ไหน
• คุณใช้เบราว์เซอร์อะไร?
Google Chrome v112
• แอคชั่นเกมใดที่คุณอยากใช้งาน?
Currently in Burgle Bros, the rules state you're not allowed to move "back and forth" in order to avoid drawing an event. However, it has been stated that this would be too difficult to code, and would result in false positives, and so (understandably), the devs focused on more productive things.
As a programmer myself, I spent some time analyzing the problem, as I knew I could tackle this, and I have the time to (unlike your devs :) ) and believe I have a draft solution which is a viable option as it:
1) doesn't result in false positives.
2) Simple coding logic changes to implement - nothing major, no redesign needed - you have all the info already, it's just a matter of gathering it up and using it properly.
3) flexible - so we can focus on the "simple"/obvious checks first .. and consider expanding to trickier ones later (if we want).
The logic is simple:
1) capture the current board "state" (everything, including tiles, hidden tiles, walls, player/guard positions, tools/loot positions, hack tokens .. alarms .. etc.) store it as a simple string (1 character per "item", ie Safe = "S", Walkway = "W", etc.)
2) boolean flag to indicate dice were rolled (ie safe, keypad, etc.) This provides a marker, as we won't compare board states beyond a dice roll. (think 1 move into a keypad, and failing the roll)
3) Compare latest board state with al previous ones up to a die roll event.
4) if any match, reject the move as "loitering" ..
• คุณพยายามทำอะไรเพื่อกระตุ้นการกระทำของเกมนี้?
• เกิดอะไรขึ้นเมื่อคุณพยายามทำสิ่งนี้ (ข้อความแสดงข้อผิดพลาดข้อความแถบสถานะของเกม ... )?
• คุณใช้เบราว์เซอร์อะไร?
Google Chrome v112
• ปัญหาเกิดขึ้นที่ขั้นตอนใดของเกม (คำสั่งเกมปัจจุบันคืออะไร)
Currently in Burgle Bros, the rules state you're not allowed to move "back and forth" in order to avoid drawing an event. However, it has been stated that this would be too difficult to code, and would result in false positives, and so (understandably), the devs focused on more productive things.
As a programmer myself, I spent some time analyzing the problem, as I knew I could tackle this, and I have the time to (unlike your devs :) ) and believe I have a draft solution which is a viable option as it:
1) doesn't result in false positives.
2) Simple coding logic changes to implement - nothing major, no redesign needed - you have all the info already, it's just a matter of gathering it up and using it properly.
3) flexible - so we can focus on the "simple"/obvious checks first .. and consider expanding to trickier ones later (if we want).
The logic is simple:
1) capture the current board "state" (everything, including tiles, hidden tiles, walls, player/guard positions, tools/loot positions, hack tokens .. alarms .. etc.) store it as a simple string (1 character per "item", ie Safe = "S", Walkway = "W", etc.)
2) boolean flag to indicate dice were rolled (ie safe, keypad, etc.) This provides a marker, as we won't compare board states beyond a dice roll. (think 1 move into a keypad, and failing the roll)
3) Compare latest board state with al previous ones up to a die roll event.
4) if any match, reject the move as "loitering" ..
• เกิดอะไรขึ้นเมื่อคุณพยายามทำการกระทำของเกม (ข้อความแสดงข้อผิดพลาดข้อความแถบสถานะเกม, ... )
• คุณใช้เบราว์เซอร์อะไร?
Google Chrome v112
• โปรดอธิบายปัญหาการแสดงผล หากคุณมีภาพหน้าจอของข้อบกพร่องนี้ (แนวปฏิบัติที่ดี) คุณสามารถใช้ Imgur.com เพื่ออัปโหลดและคัดลอก / วางลิงค์ที่นี่
Currently in Burgle Bros, the rules state you're not allowed to move "back and forth" in order to avoid drawing an event. However, it has been stated that this would be too difficult to code, and would result in false positives, and so (understandably), the devs focused on more productive things.
As a programmer myself, I spent some time analyzing the problem, as I knew I could tackle this, and I have the time to (unlike your devs :) ) and believe I have a draft solution which is a viable option as it:
1) doesn't result in false positives.
2) Simple coding logic changes to implement - nothing major, no redesign needed - you have all the info already, it's just a matter of gathering it up and using it properly.
3) flexible - so we can focus on the "simple"/obvious checks first .. and consider expanding to trickier ones later (if we want).
The logic is simple:
1) capture the current board "state" (everything, including tiles, hidden tiles, walls, player/guard positions, tools/loot positions, hack tokens .. alarms .. etc.) store it as a simple string (1 character per "item", ie Safe = "S", Walkway = "W", etc.)
2) boolean flag to indicate dice were rolled (ie safe, keypad, etc.) This provides a marker, as we won't compare board states beyond a dice roll. (think 1 move into a keypad, and failing the roll)
3) Compare latest board state with al previous ones up to a die roll event.
4) if any match, reject the move as "loitering" ..
• คุณใช้เบราว์เซอร์อะไร?
Google Chrome v112
• โปรดคัดลอก / วางข้อความที่แสดงเป็นภาษาอังกฤษแทนภาษาของคุณ หากคุณมีภาพหน้าจอของข้อบกพร่องนี้ (แนวปฏิบัติที่ดี) คุณสามารถใช้ Imgur.com เพื่ออัปโหลดและคัดลอก / วางลิงค์ที่นี่
Currently in Burgle Bros, the rules state you're not allowed to move "back and forth" in order to avoid drawing an event. However, it has been stated that this would be too difficult to code, and would result in false positives, and so (understandably), the devs focused on more productive things.
As a programmer myself, I spent some time analyzing the problem, as I knew I could tackle this, and I have the time to (unlike your devs :) ) and believe I have a draft solution which is a viable option as it:
1) doesn't result in false positives.
2) Simple coding logic changes to implement - nothing major, no redesign needed - you have all the info already, it's just a matter of gathering it up and using it properly.
3) flexible - so we can focus on the "simple"/obvious checks first .. and consider expanding to trickier ones later (if we want).
The logic is simple:
1) capture the current board "state" (everything, including tiles, hidden tiles, walls, player/guard positions, tools/loot positions, hack tokens .. alarms .. etc.) store it as a simple string (1 character per "item", ie Safe = "S", Walkway = "W", etc.)
2) boolean flag to indicate dice were rolled (ie safe, keypad, etc.) This provides a marker, as we won't compare board states beyond a dice roll. (think 1 move into a keypad, and failing the roll)
3) Compare latest board state with al previous ones up to a die roll event.
4) if any match, reject the move as "loitering" ..
• ข้อความนี้มีอยู่ใน ระบบการแปล หรือไม่? ถ้าใช่มันแปลมานานกว่า 24 ชั่วโมงแล้วหรือยัง?
• คุณใช้เบราว์เซอร์อะไร?
Google Chrome v112
• โปรดอธิบายข้อเสนอแนะของคุณอย่างแม่นยำและรัดกุมเพื่อให้ง่ายที่สุดที่จะเข้าใจสิ่งที่คุณหมายถึง
Currently in Burgle Bros, the rules state you're not allowed to move "back and forth" in order to avoid drawing an event. However, it has been stated that this would be too difficult to code, and would result in false positives, and so (understandably), the devs focused on more productive things.
As a programmer myself, I spent some time analyzing the problem, as I knew I could tackle this, and I have the time to (unlike your devs :) ) and believe I have a draft solution which is a viable option as it:
1) doesn't result in false positives.
2) Simple coding logic changes to implement - nothing major, no redesign needed - you have all the info already, it's just a matter of gathering it up and using it properly.
3) flexible - so we can focus on the "simple"/obvious checks first .. and consider expanding to trickier ones later (if we want).
The logic is simple:
1) capture the current board "state" (everything, including tiles, hidden tiles, walls, player/guard positions, tools/loot positions, hack tokens .. alarms .. etc.) store it as a simple string (1 character per "item", ie Safe = "S", Walkway = "W", etc.)
2) boolean flag to indicate dice were rolled (ie safe, keypad, etc.) This provides a marker, as we won't compare board states beyond a dice roll. (think 1 move into a keypad, and failing the roll)
3) Compare latest board state with al previous ones up to a die roll event.
4) if any match, reject the move as "loitering" ..
• คุณใช้เบราว์เซอร์อะไร?
Google Chrome v112
ประวัติการรายงาน
boardgamearena.com/forum/viewtopic.php?t=30165
In the linked .zip is a flowchart showing the logic, and it should be reasonable easy to fit into, and after some additionally games. and review, I think it should be reasonable robust.
เพิ่มการร้องเรียน
- ID ของโต๊ะอื่น / ID ของตาเดิน
- การกด F5 แก้ไขปัญหาหรือไม่
- ปัญหาเกิดขึ้นหลายครั้งหรือไม่ ทุกเวลา? สุ่ม?
- หากคุณมีภาพหน้าจอของข้อบกพร่องนี้ (แนวปฏิบัติที่ดี) คุณสามารถใช้ Imgur.com เพื่ออัปโหลดและคัดลอก / วางลิงค์ที่นี่