#15242: "Always circle potential treasure locations, not just when there are 17 or fewer"
A che riguardo è la segnalazione?
Cos'è successo? Prego, seleziona tra le seguenti
Cos'è successo? Prego, seleziona tra le seguenti
Si prega di verificare se esiste già una segnalazione sullo stesso argomento
Se sì, per favore VOTA solo questa segnalazione. Segnalazioni con più voti hanno priorità di presa in carico!
| # | Status | Votes | Game | Type | Title | Last update |
|---|
Descrizione dettagliata
-
• Per favore copia/incolla il messaggio di errore visualizzato sullo schermo, se possibile.
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". -
• Per favore spiega cosa avresti voluto fare, cosa hai fatto e cosa è successo
• Qual è il tuo browser?
Firefox 74.0.1
-
• Per favore copia/incolla il testo visualizzato in inglese invece che nella tua lingua. Se hai una schermata di questo errore (cosa buona e giusta), puoi usare Imgur.com per caricarla e fare copia/incolla del link qui.
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". -
• Questo testo è disponibile nel sistema di traduzione? Se sì, è stato tradotto nell'arco di più di 24 ore?
• Qual è il tuo browser?
Firefox 74.0.1
-
• Spiega il tuo suggerimento in modo preciso e conciso in modo che sia il più semplice possibile per capire cosa intendi.
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". • Qual è il tuo browser?
Firefox 74.0.1
-
• Cosa era mostrato sullo schermo quando sei rimasto bloccato (schermo bianco? interfaccia di gioco parziale? messaggio di errore?)
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". • Qual è il tuo browser?
Firefox 74.0.1
-
• Quale parte delle regole non è stata rispettata dall'adattamento BGA
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". -
• La violazione delle regole è visibile nel replay della partita? Se sì, a che numero di mossa?
• Qual è il tuo browser?
Firefox 74.0.1
-
• Qual era l'azione di gioco che volevi fare?
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". -
• Cosa stai provando a fare per attivare questa azione di gioco?
-
• Cosa è successo quando hai provato a fare questo (messaggio di errore, messaggio nella barra di stato del gioco...)?
• Qual è il tuo browser?
Firefox 74.0.1
-
• In quale fase del gioco si è verificato il problema (qual era l'istruzione della partita in corso)?
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". -
• Cosa è successo quando hai provato a fare questa azione di gioco (messaggio di errore, messaggio nella barra di stato del gioco...)?
• Qual è il tuo browser?
Firefox 74.0.1
-
• Per favore descrivi il problema rilevato. Se hai una schermata di questo errore (cosa buona e giusta), puoi usare Imgur.com per caricarla e fare copia/incolla del link qui.
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". • Qual è il tuo browser?
Firefox 74.0.1
-
• Per favore copia/incolla il testo visualizzato in inglese invece che nella tua lingua. Se hai una schermata di questo errore (cosa buona e giusta), puoi usare Imgur.com per caricarla e fare copia/incolla del link qui.
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". -
• Questo testo è disponibile nel sistema di traduzione? Se sì, è stato tradotto nell'arco di più di 24 ore?
• Qual è il tuo browser?
Firefox 74.0.1
-
• Spiega il tuo suggerimento in modo preciso e conciso in modo che sia il più semplice possibile per capire cosa intendi.
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". • Qual è il tuo browser?
Firefox 74.0.1
Storico dei resoconti
Aggiungi qualcosa a questo report
- Un altro ID tavolo / ID mossa
- F5 ha risolto il problema?
- Il problema si verifica spesso? Ogni volta? Casualmente?
- Se hai una schermata di questo errore (cosa buona e giusta), puoi usare Imgur.com per caricarla e fare copia/incolla del link qui.
