#97826: "Add newly played tree cards at the end of the row as default (grouping tree species as option)"
Hvad handler denne rapport om?
Hvad skete der? Vær venlig og vælg nedenunder
Hvad skete der? Vær venlig og vælg nedenunder
Vær sød at undersøge, om der allerede er sendt en besked om emnet
Hvis ja, venligst STEM for denne rapport. Rapporter med flest stemmer er dem der får PRIORITET!
| # | Status | Votes | Game | Type | Title | Last update |
|---|
Detaljeret beskrivelse
-
• Venligst kopier/indsæt fejlmeddelelsen du ser på din skærm, hvis der er en.
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. -
• Venligst forklar hvad du ønsker at gøre, hvad du gjorde og hvad der skete
• Hvilken browser bruger du?
Mozilla v5
-
• Venligst kopier/indsæt tekst vist på engelsk i stedet for dit sprog. Hvis du har et skærmbillede af denne fejl (god øvelse), kan du bruge Imgur.com til at uploade den og kopiere/indsætte linket her.
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. -
• er der adgang til denne tekst i oversættelsessystem? Hvis ja, er det blevet oversat inden for 24 timer?
• Hvilken browser bruger du?
Mozilla v5
-
• Forklar venligst dit forslag præcist og sammenfattende, så det er så let som muligt at forstå, hvad du mener.
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. • Hvilken browser bruger du?
Mozilla v5
-
• Hvad blev der vist på skærmen, da du blev blokeret (Blank skærm? Noget af spilbrugerfladen? Fejlmeddelelse?)
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. • Hvilken browser bruger du?
Mozilla v5
-
• Hvilken del af reglerne blev ikke respekteret ved BGA-tilpasningen
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. -
• Er regel-brudddet synligt i e
• Hvilken browser bruger du?
Mozilla v5
-
• Hvad var den spilhandling du ønskede at udføre?
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. -
• Hvad forsøgte du at gøre for at udløse denne spilhandling?
-
• Hvad skete der, da du forsøgre at gøre dette (fejlmeddelelse, meddelelsesstatusbjælke, ...)?
• Hvilken browser bruger du?
Mozilla v5
-
• I hvilket stadie af spillet opstod problemet (hvad var den daværende spilinstruktion)?
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. -
• Hvad skete der, da du forsøgte at udføre denne spilhandling (fejlmeddelelse, meddelelsesstatusbjælke, ...)?
• Hvilken browser bruger du?
Mozilla v5
-
• Venligst beskriv display problemet. Hvis du har et skærmbillede af denne fejl (god øvelse), kan du bruge Imgur.com til at uploade den og kopiere/indsætte linket her.
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. • Hvilken browser bruger du?
Mozilla v5
-
• Venligst kopier/indsæt tekst vist på engelsk i stedet for dit sprog. Hvis du har et skærmbillede af denne fejl (god øvelse), kan du bruge Imgur.com til at uploade den og kopiere/indsætte linket her.
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. -
• er der adgang til denne tekst i oversættelsessystem? Hvis ja, er det blevet oversat inden for 24 timer?
• Hvilken browser bruger du?
Mozilla v5
-
• Forklar venligst dit forslag præcist og sammenfattende, så det er så let som muligt at forstå, hvad du mener.
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. • Hvilken browser bruger du?
Mozilla v5
Rapporthistorik
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.
Tilføj noget til denne rapport
- Et andet bord-ID / træk ID
- Løste F5 problemet?
- Skete problemet flere gange? Hver gang? Tilfældigt?
- Hvis du har et skærmbillede af denne fejl (god øvelse), kan du bruge Imgur.com til at uploade den og kopiere/indsætte linket her.
