2023-05-24 10:34 • deBoerisTroef • De ontwikkelaars hebben deze bug niet kunnen reproduceren:
Tiny update: I managed to abandon game 379764171 by locally changing the javascript a bit. What was happening was that the tmpCardsSelectionForPlayer was called without a player_id for who to pick a card in its args; so it tried to get the name of the NULL player. Boom. I just changed that line to return "whut" in that case, which at least let the UI render (the button to give a card to 'whut' obviously didn't work, since player_id was still null). But this allowed me to press the abandon button and made my friends happy.
Hope the game and its state will stick around in the DB for a bit so you can check what was the case.

Thanks for reporting and already digging somewhat in the right direction :)
It is definitely a different bug from that boardgamearena.com/bug?id=65245, so please add any new info here.

Looking at your screenshots and info, I can definitely see the issue.

However, not sure if I will be able to solve this, as I have no idea where the 10 cards are coming from, and it is definitely not reproducible - Everybody Gets 1 has been played without problems in many 100.000 games by now.

Really strange indeed... I checked the replay and been searching through code a little, not even a beginning of an explanation of what happened here.
Game replay, game logs, deck counter all show that you drew only 4 cards to distribute with Everybody Gets 1 - as expected.

I can't find any reason why you would end up with client arguments having 10 cards to distribute and more players than there really are - which is the root cause for the javascript error.

I will leave this open for now, but unless it happens more often and we get some more info, it will probably get classified as a one time glitch...