#97826: "Add newly played tree cards at the end of the row as default (grouping tree species as option)"
В какво се състои този доклад?
Какво се случи? Моля изберете от списъка по-долу
Какво се случи? Моля изберете от списъка по-долу
Моля, проверете дали вече има доклад по същия въпрос
Ако отговорът е „да“, моля, гласувайте за този доклад. Отчетите с най-много гласове са дадени ПРИОРИТЕТ!
| # | Status | Votes | Game | Type | Title | Last update |
|---|
Подробно описание
-
• Моля поставете тук съобщението за грешка което виждате, ако има такова
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. -
• Моля обяснете, какво искахте да направите, какво направихте и какво се случи
• Какъв е вашия браузър?
Mozilla v5
-
• Моля копирайте/поставете текстът показан на аглийски, вместо на Вашия език. 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. • Какъв е вашия браузър?
Mozilla v5
-
• Моля обяснете вашето придложение ясно и кратко така че да бъде възможно най-разбираемо.
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. • Какъв е вашия браузър?
Mozilla v5
-
• Какво е било показано на екрана, когато сте били блокирани (празен екран? Част от интерфейса на играта? Съобщение за грешка?)
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. • Какъв е вашия браузър?
Mozilla v5
-
• Коя част от правилата не е била спазена от 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. -
• Нарушенията на правилата видими ли са при повторение на играта? Ако да, на кой ход се случват?
• Какъв е вашия браузър?
Mozilla v5
-
• Какъв бе игровият ход, който се опитахте да извършите?
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. -
• Какво се опитвате да направите, за да задействате тази игра?
-
• Какво се случи, когато се опитахте да направите това (съобщение за грешка, съобщение за статуса на играта, ...)?
• Какъв е вашия браузър?
Mozilla v5
-
• В кой момент от играта се появи проблема (каква е била съответната инструкция в играта)?
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. -
• Какво се случи, когато се опитахте да извършите действието в играта (съобщение за грешка, съобщение за статуса на играта, ...)?
• Какъв е вашия браузър?
Mozilla v5
-
• Моля опишете грешката при изобразяването 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. • Какъв е вашия браузър?
Mozilla v5
-
• Моля копирайте/поставете текстът показан на аглийски, вместо на Вашия език. 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. • Какъв е вашия браузър?
Mozilla v5
-
• Моля обяснете вашето придложение ясно и кратко така че да бъде възможно най-разбираемо.
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. • Какъв е вашия браузър?
Mozilla v5
История на докладванията
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.
Добави нещо към този доклад
- Друга маса ID / Ход ID
- F5 реши ли проблема?
- Проблемът няколко пъти ли се е появил? Или всеки път? Или абсолютно случайно?
- 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.
