#15242: "Always circle potential treasure locations, not just when there are 17 or fewer"
What is this report about?
What happened? Please select from below
What happened? Please select from below
Please check if there is already a report on the same subject
If yes, please VOTE for this report. Reports with the most votes are given PRIORITY!
| # | Status | Votes | Game | Type | Title | Last update |
|---|
Detailed description
-
• Please copy/paste the error message you see on your screen, if applicable.
Currently, when the cursor is placed over a "treasure map" (i.e. a pile of cubes), if there are cubes on the map for that treasure (which only happens if there are 17 or fewer possible locations), all of those spaces on the map are circled.
It would be much more useful to remove the "17 or fewer" condition: ALWAYS circle all potential spots on the map for that treasure type. The 17 is just a limitation from the physical board game, but there is no need for it in a computer version. (Also: it would be more useful for the number on the treasure pile to be the number of possible locations, not the number of cubes left in the pile -- i.e. 17 minus that number).
In addition, it would be helpful to indicate which of the 6 cards in the player's hand can currently be used for which treasure. For example, when the cursor is over a card, some text could say "cannot be used for any treasure" or "can be used for treasures A or B". -
• Please explain what you wanted to do, what you did and what happened
• Which browser are you using?
Firefox 74.0.1
-
• Please copy/paste the text displayed in English instead of your language. If you have a screenshot of this bug (good practice), you can use Imgur.com to upload it and copy/paste the link here.
Currently, when the cursor is placed over a "treasure map" (i.e. a pile of cubes), if there are cubes on the map for that treasure (which only happens if there are 17 or fewer possible locations), all of those spaces on the map are circled.
It would be much more useful to remove the "17 or fewer" condition: ALWAYS circle all potential spots on the map for that treasure type. The 17 is just a limitation from the physical board game, but there is no need for it in a computer version. (Also: it would be more useful for the number on the treasure pile to be the number of possible locations, not the number of cubes left in the pile -- i.e. 17 minus that number).
In addition, it would be helpful to indicate which of the 6 cards in the player's hand can currently be used for which treasure. For example, when the cursor is over a card, some text could say "cannot be used for any treasure" or "can be used for treasures A or B". -
• Is this text available in the translation system? If yes, has it been translated for more than 24 hours?
• Which browser are you using?
Firefox 74.0.1
-
• Please explain your suggestion precisely and concisely so that it's as easy as possible to understand what you mean.
Currently, when the cursor is placed over a "treasure map" (i.e. a pile of cubes), if there are cubes on the map for that treasure (which only happens if there are 17 or fewer possible locations), all of those spaces on the map are circled.
It would be much more useful to remove the "17 or fewer" condition: ALWAYS circle all potential spots on the map for that treasure type. The 17 is just a limitation from the physical board game, but there is no need for it in a computer version. (Also: it would be more useful for the number on the treasure pile to be the number of possible locations, not the number of cubes left in the pile -- i.e. 17 minus that number).
In addition, it would be helpful to indicate which of the 6 cards in the player's hand can currently be used for which treasure. For example, when the cursor is over a card, some text could say "cannot be used for any treasure" or "can be used for treasures A or B". • Which browser are you using?
Firefox 74.0.1
-
• What was displayed on the screen when you were blocked (Blank screen? Part of the game interface? Error message?)
Currently, when the cursor is placed over a "treasure map" (i.e. a pile of cubes), if there are cubes on the map for that treasure (which only happens if there are 17 or fewer possible locations), all of those spaces on the map are circled.
It would be much more useful to remove the "17 or fewer" condition: ALWAYS circle all potential spots on the map for that treasure type. The 17 is just a limitation from the physical board game, but there is no need for it in a computer version. (Also: it would be more useful for the number on the treasure pile to be the number of possible locations, not the number of cubes left in the pile -- i.e. 17 minus that number).
In addition, it would be helpful to indicate which of the 6 cards in the player's hand can currently be used for which treasure. For example, when the cursor is over a card, some text could say "cannot be used for any treasure" or "can be used for treasures A or B". • Which browser are you using?
Firefox 74.0.1
-
• Which part of the rules was not followed by the BGA adaptation?
Currently, when the cursor is placed over a "treasure map" (i.e. a pile of cubes), if there are cubes on the map for that treasure (which only happens if there are 17 or fewer possible locations), all of those spaces on the map are circled.
It would be much more useful to remove the "17 or fewer" condition: ALWAYS circle all potential spots on the map for that treasure type. The 17 is just a limitation from the physical board game, but there is no need for it in a computer version. (Also: it would be more useful for the number on the treasure pile to be the number of possible locations, not the number of cubes left in the pile -- i.e. 17 minus that number).
In addition, it would be helpful to indicate which of the 6 cards in the player's hand can currently be used for which treasure. For example, when the cursor is over a card, some text could say "cannot be used for any treasure" or "can be used for treasures A or B". -
• Is the rules violation visible on game replay? If yes, at which move number?
• Which browser are you using?
Firefox 74.0.1
-
• What was the game action you wanted to do?
Currently, when the cursor is placed over a "treasure map" (i.e. a pile of cubes), if there are cubes on the map for that treasure (which only happens if there are 17 or fewer possible locations), all of those spaces on the map are circled.
It would be much more useful to remove the "17 or fewer" condition: ALWAYS circle all potential spots on the map for that treasure type. The 17 is just a limitation from the physical board game, but there is no need for it in a computer version. (Also: it would be more useful for the number on the treasure pile to be the number of possible locations, not the number of cubes left in the pile -- i.e. 17 minus that number).
In addition, it would be helpful to indicate which of the 6 cards in the player's hand can currently be used for which treasure. For example, when the cursor is over a card, some text could say "cannot be used for any treasure" or "can be used for treasures A or B". -
• What did you try to do to trigger this game action?
-
• What happened when you tried to do this (error message, game status bar message, ...)?
• Which browser are you using?
Firefox 74.0.1
-
• At which step of the game did the problem occur? What was the current game instruction?
Currently, when the cursor is placed over a "treasure map" (i.e. a pile of cubes), if there are cubes on the map for that treasure (which only happens if there are 17 or fewer possible locations), all of those spaces on the map are circled.
It would be much more useful to remove the "17 or fewer" condition: ALWAYS circle all potential spots on the map for that treasure type. The 17 is just a limitation from the physical board game, but there is no need for it in a computer version. (Also: it would be more useful for the number on the treasure pile to be the number of possible locations, not the number of cubes left in the pile -- i.e. 17 minus that number).
In addition, it would be helpful to indicate which of the 6 cards in the player's hand can currently be used for which treasure. For example, when the cursor is over a card, some text could say "cannot be used for any treasure" or "can be used for treasures A or B". -
• What happened when you tried to do this game action (error message, game status bar message, ...)?
• Which browser are you using?
Firefox 74.0.1
-
• Please describe the display issue. If you have a screenshot of this bug (good practice), you can use Imgur.com to upload it and copy/paste the link here.
Currently, when the cursor is placed over a "treasure map" (i.e. a pile of cubes), if there are cubes on the map for that treasure (which only happens if there are 17 or fewer possible locations), all of those spaces on the map are circled.
It would be much more useful to remove the "17 or fewer" condition: ALWAYS circle all potential spots on the map for that treasure type. The 17 is just a limitation from the physical board game, but there is no need for it in a computer version. (Also: it would be more useful for the number on the treasure pile to be the number of possible locations, not the number of cubes left in the pile -- i.e. 17 minus that number).
In addition, it would be helpful to indicate which of the 6 cards in the player's hand can currently be used for which treasure. For example, when the cursor is over a card, some text could say "cannot be used for any treasure" or "can be used for treasures A or B". • Which browser are you using?
Firefox 74.0.1
-
• Please copy/paste the text displayed in English instead of your language. If you have a screenshot of this bug (good practice), you can use Imgur.com to upload it and copy/paste the link here.
Currently, when the cursor is placed over a "treasure map" (i.e. a pile of cubes), if there are cubes on the map for that treasure (which only happens if there are 17 or fewer possible locations), all of those spaces on the map are circled.
It would be much more useful to remove the "17 or fewer" condition: ALWAYS circle all potential spots on the map for that treasure type. The 17 is just a limitation from the physical board game, but there is no need for it in a computer version. (Also: it would be more useful for the number on the treasure pile to be the number of possible locations, not the number of cubes left in the pile -- i.e. 17 minus that number).
In addition, it would be helpful to indicate which of the 6 cards in the player's hand can currently be used for which treasure. For example, when the cursor is over a card, some text could say "cannot be used for any treasure" or "can be used for treasures A or B". -
• Is this text available in the translation system? If yes, has it been translated for more than 24 hours?
• Which browser are you using?
Firefox 74.0.1
-
• Please explain your suggestion precisely and concisely so that it's as easy as possible to understand what you mean.
Currently, when the cursor is placed over a "treasure map" (i.e. a pile of cubes), if there are cubes on the map for that treasure (which only happens if there are 17 or fewer possible locations), all of those spaces on the map are circled.
It would be much more useful to remove the "17 or fewer" condition: ALWAYS circle all potential spots on the map for that treasure type. The 17 is just a limitation from the physical board game, but there is no need for it in a computer version. (Also: it would be more useful for the number on the treasure pile to be the number of possible locations, not the number of cubes left in the pile -- i.e. 17 minus that number).
In addition, it would be helpful to indicate which of the 6 cards in the player's hand can currently be used for which treasure. For example, when the cursor is over a card, some text could say "cannot be used for any treasure" or "can be used for treasures A or B". • Which browser are you using?
Firefox 74.0.1
Report history
Add to this report
- Another table ID / move ID
- Did F5 solve the problem?
- Did the problem appear several times? Every time? Randomly?
- If you have a screenshot of this bug (good practice), you can use Imgur.com to upload it and copy/paste the link here.
