#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
-
• あなたの言語の代わりに、表示されている英語の文章をコピー&ペーストしてください。 もしこのバグのスクリーンショットがあれば(素晴らしい!)、Imgur.com等を使ってアップロードし、リンクをコピー&ペーストしてください。
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. -
• このテキストは翻訳ページで翻訳可能になっていますか?もしそうならば、24時間以上前に翻訳されていますか?
• あなたのブラウザは何ですか?
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
-
• 表示の問題を説明してください もしこのバグのスクリーンショットがあれば(素晴らしい!)、Imgur.com等を使ってアップロードし、リンクをコピー&ペーストしてください。
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
-
• あなたの言語の代わりに、表示されている英語の文章をコピー&ペーストしてください。 もしこのバグのスクリーンショットがあれば(素晴らしい!)、Imgur.com等を使ってアップロードし、リンクをコピー&ペーストしてください。
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. -
• このテキストは翻訳ページで翻訳可能になっていますか?もしそうならば、24時間以上前に翻訳されていますか?
• あなたのブラウザは何ですか?
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キー(ページの再読込)で問題は解決されましたか?
- 問題は何回も起こりましたか?毎回 起こりますか?ランダムに起きますか?
- もしこのバグのスクリーンショットがあれば(素晴らしい!)、Imgur.com等を使ってアップロードし、リンクをコピー&ペーストしてください。