botc-release
botc-release copied to clipboard
[BUG] using the same script and the same seat assignments will assign the same characters
Description
When playing 2 games in a row, with the same script and the same seat positions (without gardener or shuffling seats), the same role will be assigned to the player in that seat if it is in play.
Steps to reproduce
- Have a group playing a game with a given script (e.g., Trouble Brewing).
- Keep the same players in the same seats for a second game, without using the gardener fabled.
- If any characters are in play from the previous game, the same player will be assigned that character (so if they were the imp in game 1, they will be the imp again).
Browser
Chrome
Operating System
Mac
Date and Time
May 2024 to present (repeatable)
Game Session
No response
Relevant console log output
No response
Hi Kelsey,
Is this something you're able to commonly repeat? If you could take a video, that'd be great. I've just tried doing it a few times and couldn't get it to repeat the all of the same characters in the same place.
Thanks, Patrick
Yes, it’s been a repeatable bug for a while - I will ask the ST to take a screencap the next time I play. I do think it requires players to be seated and it only happens when the same character is in play 2 games in a row - which will always happen when it’s a one-demon script for example. I’ll let you know when I can get that screencap!
On Sun, Oct 6, 2024 at 2:14 PM Patrick Campbell @.***> wrote:
Hi Kelsey,
Is this something you're able to commonly repeat? If you could take a video, that'd be great. I've just tried doing it a few times and couldn't get it to repeat the all of the same characters in the same place.
Thanks, Patrick
— Reply to this email directly, view it on GitHub https://github.com/ThePandemoniumInstitute/botc-release/issues/247#issuecomment-2395570668, or unsubscribe https://github.com/notifications/unsubscribe-auth/AQXJ2MQ3RIXAY2VI4KFEWL3Z2GKZZAVCNFSM6AAAAABPN4YKESVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDGOJVGU3TANRWHA . You are receiving this because you authored the thread.Message ID: @.***>
Do you happen to have a particular game session where this happened? If so, I'd need the session name and a rough timestamp for when it happened.
Closed due lack of feedback / being unable to reproduce.