Reported from multiplayer playtesting (v0.8.0.9), one human against 3 bots: the turn chart's "waiting on" always names the viewing player, even while it is visibly another seat's turn.
Cause, found in the code: the server plays every bot move the moment the human's turn ends (driveBots), so the LIVE game is almost always waiting on the human. The screen then replays those bot moves step by step (v0.8.0's watchable table), but the turn chart and the Division map's "their move" marker read the live Frame.actor (currentActorOfState), not the actor of the step being shown. The playback row does say who is acting; the chart contradicts it.
Proposed fix: while the board is catching up, the turn chart and the map's move marker name the actor of the step on screen.
Reported from multiplayer playtesting (v0.8.0.9), one human against 3 bots: the turn chart's "waiting on" always names the viewing player, even while it is visibly another seat's turn.
**Cause, found in the code:** the server plays every bot move the moment the human's turn ends (`driveBots`), so the LIVE game is almost always waiting on the human. The screen then replays those bot moves step by step (v0.8.0's watchable table), but the turn chart and the Division map's "their move" marker read the live `Frame.actor` (`currentActorOfState`), not the actor of the step being shown. The playback row does say who is acting; the chart contradicts it.
Proposed fix: while the board is catching up, the turn chart and the map's move marker name the actor of the step on screen.
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
Reported from multiplayer playtesting (v0.8.0.9), one human against 3 bots: the turn chart's "waiting on" always names the viewing player, even while it is visibly another seat's turn.
Cause, found in the code: the server plays every bot move the moment the human's turn ends (
driveBots), so the LIVE game is almost always waiting on the human. The screen then replays those bot moves step by step (v0.8.0's watchable table), but the turn chart and the Division map's "their move" marker read the liveFrame.actor(currentActorOfState), not the actor of the step being shown. The playback row does say who is acting; the chart contradicts it.Proposed fix: while the board is catching up, the turn chart and the map's move marker name the actor of the step on screen.