• Калі ласка, скапіруйце тэкст памылкі, якую вы бачыце на экране (калі яна ёсць).

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.

• Калі ласка, растлумачце, што вы хацелі зрабіць, што вы зрабілі і што здарылася

• Якім браўзэрам вы карыстаецеся?

• Калі ласка, скапіруйце тэкст на англійскай замест перакладу на ваш мову. If you have a screenshot of this bug (good practice), you can use a picture hosting service of your choice (snipboard.io for example) to upload it and copy/paste the link here. Дзе можна знайсьці гэты тэкст у сістэме перакладу? Калі так, ці быў ён перакладзены больш за 24 гадзін таму?

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.

• Якім браўзэрам вы карыстаецеся?

• Калі ласка, дакладна і коратка апішыце сваю прапанову, каб зрабіць яе найбольш даступнай для разумення.

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.

• Якім браўзэрам вы карыстаецеся?

• Што было намалявана на экране, калі вас заблакавала? (Пусты экран? Частка гульнявога стала? Паведамленне пра памылку?)

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.

• Якім браўзэрам вы карыстаецеся?

• Якая частка правілаў не выкананая ў версіі BGA

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.

• Ці відаць парушэнне правілаў у паўторы гульні? Калі так, то на якім хаду?

• Якім браўзэрам вы карыстаецеся?

• Якое гульнявое дзеянне вы хацелі зрабіць?

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.

• Што вы спрабавалі зрабіць, каб выканаць гэтае гульнявое дзеянне?

• Што адбылося, калі вы паспрабавалі зрабіць гэта (паведамленне пра памылку, паведамленне ў радку стану гульні ...)?

• Якім браўзэрам вы карыстаецеся?

• На якім кроку гульні адбылася праблема (якая была інструкцыя ў той момант у гульні)?

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.

• Што адбылося, калі вы паспрабавалі здзейсніць гульнявое дзеянне (паведамленне пра памылку, паведамленне ў радку стану гульні ...)?

• Якім браўзэрам вы карыстаецеся?

• Калі ласка, апішыце памылку адлюстравання. If you have a screenshot of this bug (good practice), you can use a picture hosting service of your choice (snipboard.io for example) to upload it and copy/paste the link here.

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.

• Якім браўзэрам вы карыстаецеся?

• Калі ласка, скапіруйце тэкст на англійскай замест перакладу на ваш мову. If you have a screenshot of this bug (good practice), you can use a picture hosting service of your choice (snipboard.io for example) to upload it and copy/paste the link here. Дзе можна знайсьці гэты тэкст у сістэме перакладу? Калі так, ці быў ён перакладзены больш за 24 гадзін таму?

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.

• Якім браўзэрам вы карыстаецеся?

• Калі ласка, дакладна і коратка апішыце сваю прапанову, каб зрабіць яе найбольш даступнай для разумення.

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.

• Якім браўзэрам вы карыстаецеся?