You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When we made uabc generic we lost support for a practice mode, as uabc no longer has access to game engines.
Since game servers are just npm packages, we could have uabc pull the appropriate game server using npm install, and act as a client in order to play games locally.
uabc checks if the uttt game server is available (we need to ensure consistent package names for this obviously)
a. If available, go to point 3.
b. If not available, try running npm install {game}-game-server
c. If that succeeds, go to 3.
Start the game server locally, start the two players, and have them play with the game server. This is already the way tournaments are played, with the handoff mechanism, so uabc will just need to be aware of some extra protocol logic (mainly around matches)
The text was updated successfully, but these errors were encountered:
When we made uabc generic we lost support for a practice mode, as uabc no longer has access to game engines.
Since game servers are just npm packages, we could have uabc pull the appropriate game server using npm install, and act as a client in order to play games locally.
The workflow would be:
uabc --practice uttt -f "python player.py" "python random.py"
uabc checks if the uttt game server is available (we need to ensure consistent package names for this obviously)
a. If available, go to point 3.
b. If not available, try running
npm install {game}-game-server
c. If that succeeds, go to 3.
Start the game server locally, start the two players, and have them play with the game server. This is already the way tournaments are played, with the handoff mechanism, so uabc will just need to be aware of some extra protocol logic (mainly around matches)
The text was updated successfully, but these errors were encountered: