#97826: "Add newly played tree cards at the end of the row as default (grouping tree species as option)"
Waarover gaat dit rapport?
Wat is er gebeurd? Selecteer uit het onderstaande
Wat is er gebeurd? Selecteer uit het onderstaande
Controleer of er al een rapport is over hetzelfde onderwerp
Zo ja, gelieve dan voor dit rapport te STEMMEN. Rapporten met de meeste stemmen krijgen VOORRANG!
| # | Status | Votes | Game | Type | Title | Last update |
|---|
Gedetailleerde beschrijving
-
• Kopieer en plak alsjeblieft de foutboodschap die je op je scherm ziet, indien van toepassing.
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. -
• Leg uit wat je wilde doen, wat je deed en wat er gebeurde
• Welke browser gebruik je?
Mozilla v5
-
• Kopieer en plak alsjeblieft de tekst die in het Engels wordt getoond in plaats van in jouw taal. Als je een schermkopie van deze bug hebt (goede gewoonte), kun je een hosting-service voor afbeeldingen naar keuze gebruiken (bijvoorbeeld snipboard.io) om deze te uploaden en de link hier te kopiëren/plakken. Is deze tekst beschikbaar in het vertaalsysteem? Zo ja, is deze meer dan 24 uur geleden vertaald?
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. • Welke browser gebruik je?
Mozilla v5
-
• Gelieve jouw suggestie precies en beknopt uit te leggen zodat het zo makkelijk mogelijk is om te begrijpen wat je bedoelt.
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. • Welke browser gebruik je?
Mozilla v5
-
• Wat stond op het scherm toen je geblokkeerd was (Leeg scherm? Een deel van de spelinterface? Foutboodschap?)
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. • Welke browser gebruik je?
Mozilla v5
-
• Met welk onderdeel van de regels is geen rekening gehouden bij de BGA-versie?
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. -
• Is de inbreuk op de spelregels zichtbaar in de spelherhaling? Indien ja, bij welk zetnummer?
• Welke browser gebruik je?
Mozilla v5
-
• Welke spelactie wilde je uitvoeren?
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. -
• Wat probeerde je te doen om deze spelactie te laten optreden?
-
• Wat gebeurde er toen je dit probeerde te doen (foutboodschap, melding op de statusbalk van het spel, ...)?
• Welke browser gebruik je?
Mozilla v5
-
• In welke fase van het spel deed het probleem zich voor (wat was de huidige spelinstructie)?
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. -
• Wat gebeurde toen je deze spelactie probeerde (foutboodschap, melding op de statusbalk van het spel, ...)?
• Welke browser gebruik je?
Mozilla v5
-
• Beschrijf alsjeblieft het probleem met de beeldweergave. Als je een schermkopie van deze bug hebt (goede gewoonte), kun je een hosting-service voor afbeeldingen naar keuze gebruiken (bijvoorbeeld snipboard.io) om deze te uploaden en de link hier te kopiëren/plakken.
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. • Welke browser gebruik je?
Mozilla v5
-
• Kopieer en plak alsjeblieft de tekst die in het Engels wordt getoond in plaats van in jouw taal. Als je een schermkopie van deze bug hebt (goede gewoonte), kun je een hosting-service voor afbeeldingen naar keuze gebruiken (bijvoorbeeld snipboard.io) om deze te uploaden en de link hier te kopiëren/plakken. Is deze tekst beschikbaar in het vertaalsysteem? Zo ja, is deze meer dan 24 uur geleden vertaald?
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. • Welke browser gebruik je?
Mozilla v5
-
• Gelieve jouw suggestie precies en beknopt uit te leggen zodat het zo makkelijk mogelijk is om te begrijpen wat je bedoelt.
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. • Welke browser gebruik je?
Mozilla v5
Rapportgeschiedenis
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.
Dit rapport aanvullen
- Andere tafel ID / zet ID
- Loste F5 het probleem op?
- Kwam het probleem meerdere keren voor? Altijd? Willekeurig?
- Als je een schermkopie van deze bug hebt (goede gewoonte), kun je een hosting-service voor afbeeldingen naar keuze gebruiken (bijvoorbeeld snipboard.io) om deze te uploaden en de link hier te kopiëren/plakken.
