Closed lukew3 closed 2 years ago
In receiveMove, you could check that the userId matches the userId of next up. Maybe check if the length of moves is even to determine who is next up. This might add more latency than it's worth.
In receiveMove, you could check that the userId matches the userId of next up. Maybe check if the length of moves is even to determine who is next up. This might add more latency than it's worth.
102 will fix this