#97826: "Add newly played tree cards at the end of the row as default (grouping tree species as option)"
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.
Newly played tree cards are normally added at the end of the row of your trees. But if the new tree is the same species you already played, it is inserted into the row, grouping trees of the same species together.
It took me several games to figure out this exception rule, and I still find it confusing at times. I definitely lost some opportunities because of it. For example, when trying to optimize my forest to get 5 points per fully occupied tree for Beech Marten, I thought: "Didn't I have a tree almost occupied? No, I can't see it, so I didn't." Whereas in fact the tree almost occupied existed and just "jumped" unnoticed into the second row, now covered by my cards in hand.
So I think adding trees at the end of the row should be the default rule, with the option to switch to grouping tree species (which is also useful in some cases) and back to playing order. -
• 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 ?
Mozilla v5
-
• 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ñ.
Newly played tree cards are normally added at the end of the row of your trees. But if the new tree is the same species you already played, it is inserted into the row, grouping trees of the same species together.
It took me several games to figure out this exception rule, and I still find it confusing at times. I definitely lost some opportunities because of it. For example, when trying to optimize my forest to get 5 points per fully occupied tree for Beech Marten, I thought: "Didn't I have a tree almost occupied? No, I can't see it, so I didn't." Whereas in fact the tree almost occupied existed and just "jumped" unnoticed into the second row, now covered by my cards in hand.
So I think adding trees at the end of the row should be the default rule, with the option to switch to grouping tree species (which is also useful in some cases) and back to playing order. -
• 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 ?
Mozilla v5
-
• 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.
Newly played tree cards are normally added at the end of the row of your trees. But if the new tree is the same species you already played, it is inserted into the row, grouping trees of the same species together.
It took me several games to figure out this exception rule, and I still find it confusing at times. I definitely lost some opportunities because of it. For example, when trying to optimize my forest to get 5 points per fully occupied tree for Beech Marten, I thought: "Didn't I have a tree almost occupied? No, I can't see it, so I didn't." Whereas in fact the tree almost occupied existed and just "jumped" unnoticed into the second row, now covered by my cards in hand.
So I think adding trees at the end of the row should be the default rule, with the option to switch to grouping tree species (which is also useful in some cases) and back to playing order. • Peseurt merdeer eo hoc'h hini ?
Mozilla v5
-
• Petra oa diskouezet war ar skramm pa 'z oc'h chomet stanket (Skramm goullo ? Ul lodenn eus etrefas ar c'hoari ? Kemennadenn fazi ?)
Newly played tree cards are normally added at the end of the row of your trees. But if the new tree is the same species you already played, it is inserted into the row, grouping trees of the same species together.
It took me several games to figure out this exception rule, and I still find it confusing at times. I definitely lost some opportunities because of it. For example, when trying to optimize my forest to get 5 points per fully occupied tree for Beech Marten, I thought: "Didn't I have a tree almost occupied? No, I can't see it, so I didn't." Whereas in fact the tree almost occupied existed and just "jumped" unnoticed into the second row, now covered by my cards in hand.
So I think adding trees at the end of the row should be the default rule, with the option to switch to grouping tree species (which is also useful in some cases) and back to playing order. • Peseurt merdeer eo hoc'h hini ?
Mozilla v5
-
• Pesseurt reolenn n'eo ket doujet gant azasadenn ar c'hoari-mañ ?
Newly played tree cards are normally added at the end of the row of your trees. But if the new tree is the same species you already played, it is inserted into the row, grouping trees of the same species together.
It took me several games to figure out this exception rule, and I still find it confusing at times. I definitely lost some opportunities because of it. For example, when trying to optimize my forest to get 5 points per fully occupied tree for Beech Marten, I thought: "Didn't I have a tree almost occupied? No, I can't see it, so I didn't." Whereas in fact the tree almost occupied existed and just "jumped" unnoticed into the second row, now covered by my cards in hand.
So I think adding trees at the end of the row should be the default rule, with the option to switch to grouping tree species (which is also useful in some cases) and back to playing order. -
• 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 ?
Mozilla v5
-
• Peseurt taol ho peus c'hoant c'hoari ?
Newly played tree cards are normally added at the end of the row of your trees. But if the new tree is the same species you already played, it is inserted into the row, grouping trees of the same species together.
It took me several games to figure out this exception rule, and I still find it confusing at times. I definitely lost some opportunities because of it. For example, when trying to optimize my forest to get 5 points per fully occupied tree for Beech Marten, I thought: "Didn't I have a tree almost occupied? No, I can't see it, so I didn't." Whereas in fact the tree almost occupied existed and just "jumped" unnoticed into the second row, now covered by my cards in hand.
So I think adding trees at the end of the row should be the default rule, with the option to switch to grouping tree species (which is also useful in some cases) and back to playing order. -
• 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 ?
Mozilla v5
-
• Da be bazenn ar bartienn eo en em gavet ar gudenn (petra oa testenn kemenn ar c'hoari) ?
Newly played tree cards are normally added at the end of the row of your trees. But if the new tree is the same species you already played, it is inserted into the row, grouping trees of the same species together.
It took me several games to figure out this exception rule, and I still find it confusing at times. I definitely lost some opportunities because of it. For example, when trying to optimize my forest to get 5 points per fully occupied tree for Beech Marten, I thought: "Didn't I have a tree almost occupied? No, I can't see it, so I didn't." Whereas in fact the tree almost occupied existed and just "jumped" unnoticed into the second row, now covered by my cards in hand.
So I think adding trees at the end of the row should be the default rule, with the option to switch to grouping tree species (which is also useful in some cases) and back to playing order. -
• What happened when you try to do a game action (error message, game status bar message, ...)?
• Peseurt merdeer eo hoc'h hini ?
Mozilla v5
-
• 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ñ.
Newly played tree cards are normally added at the end of the row of your trees. But if the new tree is the same species you already played, it is inserted into the row, grouping trees of the same species together.
It took me several games to figure out this exception rule, and I still find it confusing at times. I definitely lost some opportunities because of it. For example, when trying to optimize my forest to get 5 points per fully occupied tree for Beech Marten, I thought: "Didn't I have a tree almost occupied? No, I can't see it, so I didn't." Whereas in fact the tree almost occupied existed and just "jumped" unnoticed into the second row, now covered by my cards in hand.
So I think adding trees at the end of the row should be the default rule, with the option to switch to grouping tree species (which is also useful in some cases) and back to playing order. • Peseurt merdeer eo hoc'h hini ?
Mozilla v5
-
• 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ñ.
Newly played tree cards are normally added at the end of the row of your trees. But if the new tree is the same species you already played, it is inserted into the row, grouping trees of the same species together.
It took me several games to figure out this exception rule, and I still find it confusing at times. I definitely lost some opportunities because of it. For example, when trying to optimize my forest to get 5 points per fully occupied tree for Beech Marten, I thought: "Didn't I have a tree almost occupied? No, I can't see it, so I didn't." Whereas in fact the tree almost occupied existed and just "jumped" unnoticed into the second row, now covered by my cards in hand.
So I think adding trees at the end of the row should be the default rule, with the option to switch to grouping tree species (which is also useful in some cases) and back to playing order. -
• 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 ?
Mozilla v5
-
• 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.
Newly played tree cards are normally added at the end of the row of your trees. But if the new tree is the same species you already played, it is inserted into the row, grouping trees of the same species together.
It took me several games to figure out this exception rule, and I still find it confusing at times. I definitely lost some opportunities because of it. For example, when trying to optimize my forest to get 5 points per fully occupied tree for Beech Marten, I thought: "Didn't I have a tree almost occupied? No, I can't see it, so I didn't." Whereas in fact the tree almost occupied existed and just "jumped" unnoticed into the second row, now covered by my cards in hand.
So I think adding trees at the end of the row should be the default rule, with the option to switch to grouping tree species (which is also useful in some cases) and back to playing order. • Peseurt merdeer eo hoc'h hini ?
Mozilla v5
Roll-istor an danevelloù bog
I had played 2 trees, the second tree, a Silver Fir, had a polecat on it and was on the right. I then played a Blackthorn bush and wanted to put a butterfly on it. Expecting the newly played bush-tree to be on the right, I clicked the right most tree.
Instead the game decided to put the Blackthorn on the far left and keep the Silver Fir on the far right, which in turn meant I clicked on it and my butterfly got put on the same tree as the polecat. If this game had a revert function this wouldn't be so bad but the game doesn't.
I had played 2 trees, the second tree, a Silver Fir, had a polecat on it and was on the right. I then played a Blackthorn bush and wanted to put a butterfly on it. Expecting the newly played bush-tree to be on the right, I clicked the right most tree.
Instead the game decided to put the Blackthorn on the far left and keep the Silver Fir on the far right, which in turn meant I clicked on it and my butterfly got put on the same tree as the polecat. If this game had a revert function this wouldn't be so bad but the game doesn't.
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ñ.
