所有案件
星際探險隊:深海任務 的案件
#49549: "Free choice: assign 'dark green' tasks to players automatiquely"
#49549: "Free choice: assign 'dark green' tasks to players automatiquely"
這是關於哪方面的案件?
發生什麼事? 請從下方選擇
建議:依我所見,有些調整將大幅增進遊戲完成度
發生什麼事? 請從下方選擇
建議:依我所見,有些調整將大幅增進遊戲完成度
請檢查是否已有同課題案件
若肯定,請「投票」給這樁案件。最高票的案件將「優先」處理!
# | Status | Votes | Game | Type | Title | Last update |
---|
細節描述
• 如果可以的話,請轉貼螢幕顯示的錯誤訊息。
Once everyone has clicked on 'Done', assign each task asked in solo in dark green to one of the player which asked that task (starting with commander).• 請說明你當時想做什麼,你做了什麼,然後發生了什麼事
• 你的瀏覽器是什麼?
Mozilla v5
• 請簡明精確地解釋你的建議,以便讓人一目了然。
Once everyone has clicked on 'Done', assign each task asked in solo in dark green to one of the player which asked that task (starting with commander).• 你的瀏覽器是什麼?
Mozilla v5
• 當你不能動作時,螢幕上顯示什麼?(螢幕全黑?部份遊戲介面?錯誤訊息?)
Once everyone has clicked on 'Done', assign each task asked in solo in dark green to one of the player which asked that task (starting with commander).• 你的瀏覽器是什麼?
Mozilla v5
• 遊戲規則的哪部分在 BGA 版本有所錯漏?
Once everyone has clicked on 'Done', assign each task asked in solo in dark green to one of the player which asked that task (starting with commander).• 這項違反規則之處可否在遊戲重播中看到?若可以是在哪步?(重播時左上角資訊)
• 你的瀏覽器是什麼?
Mozilla v5
• 你當時想採取哪個遊戲行動?
Once everyone has clicked on 'Done', assign each task asked in solo in dark green to one of the player which asked that task (starting with commander).• 你想觸發這個遊戲行動時做了什麼?
• 當你試著這麼做時發生了什麼(錯誤訊息、遊戲狀態條訊息...)?
• 你的瀏覽器是什麼?
Mozilla v5
• 問題發生在遊戲的哪一步?(當前遊戲指示是什麼)
Once everyone has clicked on 'Done', assign each task asked in solo in dark green to one of the player which asked that task (starting with commander).• 當你試著進行遊戲動作時發生了什麼(錯誤訊息、遊戲狀態條訊息...)?
• 你的瀏覽器是什麼?
Mozilla v5
• 請描述顯示問題。 建議將此錯誤的螢幕截圖上傳到 Imgur.com 並轉貼連結。
Once everyone has clicked on 'Done', assign each task asked in solo in dark green to one of the player which asked that task (starting with commander).• 你的瀏覽器是什麼?
Mozilla v5
• 請簡明精確地解釋你的建議,以便讓人一目了然。
Once everyone has clicked on 'Done', assign each task asked in solo in dark green to one of the player which asked that task (starting with commander).• 你的瀏覽器是什麼?
Mozilla v5
案件沿革
2021年 9月29日 18:07 • Romain672 • 此建議尚未被開發者分析過:
The goal is to make some automatisation which work most of the time.
If people aren't agree with it they should: refuse the task afterward/talk in chat/not put that task in dark green.
It's possible to extend it to 'light green' too (but not for worst, i would like the commander to manually choose).
If people aren't agree with it they should: refuse the task afterward/talk in chat/not put that task in dark green.
It's possible to extend it to 'light green' too (but not for worst, i would like the commander to manually choose).
2021年 9月29日 18:08 • Tisaac • 開發者需要更詳細的建議內容:
I don't like automation on the free alloc, there are always counter-example so you would solve usually with discussion.
2021年 9月29日 18:09 • Romain672 • 開發者需要更詳細的建議內容:
I think 95+% of the time, assign tasks for at least the dark green color wouldn't be bad.
And the 5% of task left can be changed by the players themselves.
And the 5% of task left can be changed by the players themselves.
2021年10月 2日 12:36 • Romain672 • 開發者需要更詳細的建議內容:
With more games in the bag, here is my suggestion without the 'random' part:
For each task:
- if a single player put a dark green opinion on it, give (=put the task in front of him, but still let the commander move it) automatiquely the task to him
- else, if no player put a dark green opinion on it, and if a single player put a light green opinion on it, give automatiquely the task to him
- else, leave the task to the middle
For each task:
- if a single player put a dark green opinion on it, give (=put the task in front of him, but still let the commander move it) automatiquely the task to him
- else, if no player put a dark green opinion on it, and if a single player put a light green opinion on it, give automatiquely the task to him
- else, leave the task to the middle
2021年10月 2日 14:12 • Romain672 • 開發者需要更詳細的建議內容:
Here is the good and bad links (please note no one know it would be automatic, if that was the case, you could slightly play for it): www.zupimages.net/up/21/39/idf8.jpg
On game 1, A & C don't work well. A should be cancelled because of ABCI (compared to my last post), and C is just... unlucky. Guess C should stay in the wrong, I should kindly ask in chat to change
On game 2, G is the only wrong. But it's like C on the previous game
On game 3, that 'ACH' ruin everything. If we change 'ACH' by 'A'+'C'+'H', we got everything which goes well and D not put to anyone....
On game 1, A & C don't work well. A should be cancelled because of ABCI (compared to my last post), and C is just... unlucky. Guess C should stay in the wrong, I should kindly ask in chat to change
On game 2, G is the only wrong. But it's like C on the previous game
On game 3, that 'ACH' ruin everything. If we change 'ACH' by 'A'+'C'+'H', we got everything which goes well and D not put to anyone....
2021年10月 2日 14:12 • Romain672 • 開發者需要更詳細的建議內容:
So, here is what I learned from those three games:
For each task taken individually:
- IF a player put a dark green opinion on it, AND others players did not put any bundle of tasks with that task in dark green
=> give automatiquely the task to him (=put the task in front of him, but still let the commander move it)
- else, if no player put any bundle of tasks with that task in dark green, AND if a single player put a light green opinion on it, AND others players did not put any bundle of tasks with that task in light green
=> give automatiquely the task to him
- else
=> leave the task to the middle
These rules seem to put lots of tasks in the middle but it’s not the case, there is lots of rules which instead of giving a task to a player will make the task stay in the middle.
For each task taken individually:
- IF a player put a dark green opinion on it, AND others players did not put any bundle of tasks with that task in dark green
=> give automatiquely the task to him (=put the task in front of him, but still let the commander move it)
- else, if no player put any bundle of tasks with that task in dark green, AND if a single player put a light green opinion on it, AND others players did not put any bundle of tasks with that task in light green
=> give automatiquely the task to him
- else
=> leave the task to the middle
These rules seem to put lots of tasks in the middle but it’s not the case, there is lots of rules which instead of giving a task to a player will make the task stay in the middle.
2021年10月 3日 0:51 • Romain672 • 開發者需要更詳細的建議內容:
Here is 11 more, included one bugged (I normally don't put the bugged one, but that was an interresting one): www.zupimages.net/up/21/39/cww1.jpg
So with those new rules, on the previous screenshot, we got (success-fail): 4-1, 6-1, 3-0 which give 13-2.
With those 11 more screenshots, we got:
3-0, 4-0, 4-0, 4-0, 4-0, 7-0, 1-0, 2-0.
And I guess the bugged game would give 3-2.
If I sum all that I obtain: 32-2.
If I sum both screenshots, I got 45-4, so 90.7% of tasks assigned automatiquely were right.
Still need to try more 4 players, and try 5 players, but that look an enough good number to me to do it :(
So with those new rules, on the previous screenshot, we got (success-fail): 4-1, 6-1, 3-0 which give 13-2.
With those 11 more screenshots, we got:
3-0, 4-0, 4-0, 4-0, 4-0, 7-0, 1-0, 2-0.
And I guess the bugged game would give 3-2.
If I sum all that I obtain: 32-2.
If I sum both screenshots, I got 45-4, so 90.7% of tasks assigned automatiquely were right.
Still need to try more 4 players, and try 5 players, but that look an enough good number to me to do it :(
2021年10月 3日 0:55 • Romain672 • 開發者需要更詳細的建議內容:
On 88 tasks:
- 45 were correctly automatised (51%)
- 4 were incorectly automatised (4.5%)
- 32 were not automatised (36%)
51% is pretty high. I suppose it would be lower with more 4/5 players games.
- 45 were correctly automatised (51%)
- 4 were incorectly automatised (4.5%)
- 32 were not automatised (36%)
51% is pretty high. I suppose it would be lower with more 4/5 players games.
2021年10月 3日 19:05 • Romain672 • 開發者需要更詳細的建議內容:
No one upvoted it, even if I put some publicity for it on my profile.
I find it really sad because I'm convinced it would be positive.
But fine, you can close it if you want.
I find it really sad because I'm convinced it would be positive.
But fine, you can close it if you want.
2021年11月 4日 4:08 • Tuut Tuut tis Luut • 開發者需要更詳細的建議內容:
I feel like this would be at best a very mild convenience in the cases where it's the desired move.
And endlessly frustrating any other time.
There are so many cases where despite a high rating from one crewmate, it's still better to give them to someone else for easier combo,s for example.
Or when someone rates one task high, but has another (incompatible) task rated just a bit lower that nobody else can do. Just a few examples of the top of my head.
And even in the cases where you're happy with the automated distribution. I doubt it would actually save all that much time. Commander will still have to read and think about all tasks to decide if it's the best distribution. Only now instead of having them all neatly in the middle, they're all already scattered around the table.
Thinking tends to take the most time, after that the time it takes you to click is negligible
And endlessly frustrating any other time.
There are so many cases where despite a high rating from one crewmate, it's still better to give them to someone else for easier combo,s for example.
Or when someone rates one task high, but has another (incompatible) task rated just a bit lower that nobody else can do. Just a few examples of the top of my head.
And even in the cases where you're happy with the automated distribution. I doubt it would actually save all that much time. Commander will still have to read and think about all tasks to decide if it's the best distribution. Only now instead of having them all neatly in the middle, they're all already scattered around the table.
Thinking tends to take the most time, after that the time it takes you to click is negligible
2021年12月 1日 12:11 • Romain672 • 開發者需要更詳細的建議內容:
I was looking at some more games at 4/5 players.
So remember that last time on my %, I took in purpose a game where the automatic way goes wrongly.
I took 4 more games, there was no mistakes, and about ~50% of automatisations.
"There are so many cases where despite a high rating from one crewmate, it's still better to give them to someone else for easier combo,s for example." => "So many" hum :D Yeah in theory, but in practice, this just work well most of the time.
The thing is, even on your case (which is rare I insist), after the automatisation, the task D appear to be taken by no one. AND someone put a bundle with task DE in light green or gray (if it was dark green, no task of that bundle would be assign automatiquely). AND someone else put the task E in dark green, or light green if before it was gray.
On this case, yeah the task E would be assign wrongly.
But that's just so much conditions...
So yeah, I'm now convinced this would be great.
Would it be worst the coding time? I mean, that doesn't look hard... I dunno, I'm way too much biaised.
So remember that last time on my %, I took in purpose a game where the automatic way goes wrongly.
I took 4 more games, there was no mistakes, and about ~50% of automatisations.
"There are so many cases where despite a high rating from one crewmate, it's still better to give them to someone else for easier combo,s for example." => "So many" hum :D Yeah in theory, but in practice, this just work well most of the time.
The thing is, even on your case (which is rare I insist), after the automatisation, the task D appear to be taken by no one. AND someone put a bundle with task DE in light green or gray (if it was dark green, no task of that bundle would be assign automatiquely). AND someone else put the task E in dark green, or light green if before it was gray.
On this case, yeah the task E would be assign wrongly.
But that's just so much conditions...
So yeah, I'm now convinced this would be great.
Would it be worst the coding time? I mean, that doesn't look hard... I dunno, I'm way too much biaised.
2021年12月 1日 12:13 • Romain672 • 開發者需要更詳細的建議內容:
Oh I forget a good part of my argument. Once the task D appear to be taken by no one, we immediately saw D is a problem. While, when you just assign tasks in order (like some? a lot? people do), this doesn't appear until D arise. That's even worst if the person assign tasks in dark green first, because D would then appear last.
為本案件添加內容
任何可能重現這項錯誤或了解你的建議之相關資訊,都請在此填寫:
- 其他同樣狀況的桌號/步數
- 按 F5 是否解決了這個問題?
- 問題是否發生了好幾次?每次都發生?時好時壞?
- 建議將此錯誤的螢幕截圖上傳到 Imgur.com 並轉貼連結。
更改案件狀態為:
bug?id=49549