hanabi-live
hanabi-live copied to clipboard
Game ends while in replay, use shared turns, play stacks disappear and deck becomes b3. No errors in console
for any of the players or just the spectator?
just spectator it seems like
I still have the tab open if you want me to run any commands.
As the review progresses, cards are going onto the disappeared play stacks so now they look normal. Also the deck returned to not being b3
tim says he can't repro so not sure what to do about this
i think this might have been an unrelated bug that has since been fixed. reopen if it happens again
happened again in up and down. different circumstances
no errors?
no errors
I moved forward and back a bit and the play stack placeholders reappear after a card is played and then rewound. also after like 7 turns the i3 changed to a y3. want me to run any commands with the tab open?
not really. i assume you were a spectator when the game ended? use json import and try to reproduce the problem
this time I was spectating the review for a while and then when the leader rewound to the beginning of the game the cards were glitched (I don't remember how exactly) and then when I moved forward a turn they all flew into different places and the deck became i3
I can use JSON import to try to reproduce
just trying by using the same shared replay. I'm doing similar things with no luck. a common theme in the two natural occurences though seems to be being teleported to the first turn of a shared replay of Up or Down.
and in both cases I was taken to the first turn of the game by means outside of my control. either the leader or the game ending while I was in a side replay
It happened again. This time not an up or down game. I was spectating, then the game ended, when the replay was taken back to the beginning at first all of the hands disappeared and the clue arrows were pointing at the 5's play stacks, and then all the cards snapped into place, the play stack placeholders were wrong, and the deck looked like a normal card
Status of this?
Timo, has still happened in the near present, or is this solved?
i'll close for now