#15242: "Always circle potential treasure locations, not just when there are 17 or fewer"
Petra a zo c'hoarvezet ? Trugarez evit dibab amañ dindan
Petra a zo c'hoarvezet ? Trugarez evit dibab amañ dindan
Gwiriit mar-plij ma n'eus ket dija un danevell evit an hevelep dodenn
M'oc'h a-du, VOTIT evit an danevell-mañ. An danevelloù gant ar muiañ a vouezhioù a vo studiet DA GENTAÑ !
| # | Status | Votes | Game | Type | Title | Last update |
|---|
Deskrivadur dre ar munud
-
• Mar-plij, eilit/pegit ar gemennadenn fazi a zo war ho skramm, ma zo unan.
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". -
• Displegit deomp, mar-plij, ar pezh ho poa c'hoant d'ober, ar pezh ho peus graet hag ar pezh a zo c'hoarvezet 'benn ar fin
• Peseurt merdeer eo hoc'h hini ?
Firefox 74.0.1
-
• Mar-plij, eilit/pegit an destenn e Saozneg ha n'eo ket en ho yezh. M'ho peus un dapadenn skramm eus ar gudenn (ho pezit soñj d'eus se !), gellout a rit implij Imgur.com evit e bellgargañ hag eilañ/pegañ al liamm amañ.
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". -
• Ha dibres eo an destenn-mañ er sistem treiñ? Ma ya, daoust ha troet eo bet ouzhpenn 24 eur 'zo ?
• Peseurt merdeer eo hoc'h hini ?
Firefox 74.0.1
-
• Displegit ho kinnig mar-plij, e berrgomzoù met en un doare resis, evit ma vefe an aesañ posupl kompren mat ar pezh ho peus c'hoant lâret.
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". • Peseurt merdeer eo hoc'h hini ?
Firefox 74.0.1
-
• Petra oa diskouezet war ar skramm pa 'z oc'h chomet stanket (Skramm goullo ? Ul lodenn eus etrefas ar c'hoari ? Kemennadenn fazi ?)
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". • Peseurt merdeer eo hoc'h hini ?
Firefox 74.0.1
-
• Pesseurt reolenn n'eo ket doujet gant azasadenn ar c'hoari-mañ ?
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". -
• Ha posupl eo gwelet torridigezh ar reolenn e replay ar bartienn ? Ma 'z eo ya, da be niverenn taol ?
• Peseurt merdeer eo hoc'h hini ?
Firefox 74.0.1
-
• Peseurt taol ho peus c'hoant c'hoari ?
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". -
• Petra emaoc'h o klask ober evit delankañ an ober c'hoari-mañ ?
-
• What happened when you try to do this (error message, game status bar message, ...)?
• Peseurt merdeer eo hoc'h hini ?
Firefox 74.0.1
-
• Da be bazenn ar bartienn eo en em gavet ar gudenn (petra oa testenn kemenn ar c'hoari) ?
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 try to do a game action (error message, game status bar message, ...)?
• Peseurt merdeer eo hoc'h hini ?
Firefox 74.0.1
-
• Mar-plij, diskrivit kudenn an diskwel. M'ho peus un dapadenn skramm eus ar gudenn (ho pezit soñj d'eus se !), gellout a rit implij Imgur.com evit e bellgargañ hag eilañ/pegañ al liamm amañ.
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". • Peseurt merdeer eo hoc'h hini ?
Firefox 74.0.1
-
• Mar-plij, eilit/pegit an destenn e Saozneg ha n'eo ket en ho yezh. M'ho peus un dapadenn skramm eus ar gudenn (ho pezit soñj d'eus se !), gellout a rit implij Imgur.com evit e bellgargañ hag eilañ/pegañ al liamm amañ.
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". -
• Ha dibres eo an destenn-mañ er sistem treiñ? Ma ya, daoust ha troet eo bet ouzhpenn 24 eur 'zo ?
• Peseurt merdeer eo hoc'h hini ?
Firefox 74.0.1
-
• Displegit ho kinnig mar-plij, e berrgomzoù met en un doare resis, evit ma vefe an aesañ posupl kompren mat ar pezh ho peus c'hoant lâret.
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". • Peseurt merdeer eo hoc'h hini ?
Firefox 74.0.1
Roll-istor an danevelloù bog
Ouzhpennañ un dra bennak d'an danevell-mañ
- Niverenn taol all / Niverenn ar fiñv
- Ha renket eo bet ar gudenn gant an douchenn F5 ?
- Ha c'hoarvezet eo ar gudenn meur a wech ? Bewech ? Cheñch-dicheñch ?
- M'ho peus un dapadenn skramm eus ar gudenn (ho pezit soñj d'eus se !), gellout a rit implij Imgur.com evit e bellgargañ hag eilañ/pegañ al liamm amañ.
