Learning project for MCTS. This code aims for some efficiency and is strong enough to play well or better against other libraries. I use it in my Nego project.
Current features:
- UCT / UCB1Tuned
- RAVE/GRAVE
- MAST
- Decisive Moves
- Transposition tables
- Hyperparameter tuning with SMAC3
- Arena allocation (just a
Vec, inspired by indextree) - Preliminary benchmarking tools
- A growing number of game implementations
Some things I would like to explore:
- Better testability, ergonomics, safety
- More simulation strategies, selection improvements, etc.
- Online tuning
Other alternatives in Rust:
- minimax-rs: lock-free tree parallel implementation. Better for low branching factor tactical games due to use of full node expansion strategy and reliance on MCTS-Solver.
- ggpf: implements a lot of stuff, including AlphaZero and MuZero TF integration. Supports RAVE, PUCT, etc.
- zxqfl/mcts: some pretty clean looking code with lots of atomics and support for transposition tables. From the author of TabNine. I think it has a lot of good ideas on how to parameterize and mix different strategies.
- recon_mcts: mostly focused on parallelism, with some clever strategies to combine tree results.
- arbor: vanilla MCTS, but with a focus on single threaded efficiency, uses hand maintained arena. Has some transposition support, but says it is experimental. I haven't looked deeply because the project doesn't provide a LICENSE.
- OxyMcts: seems to be a vanilla UCT client
Some code and general approaches come from minimax-rs which has an MCTS strategy.
Not sure if this will become a published library, but it is improving and PRs are welcome.
A browser UI (SolidJS + Vite, ui/) for the games in games/,
backed by the stateless API in server/.
Quick start:
(cd ui && pnpm install && pnpm build)
cargo build --release
cargo run --release -p server
Then open http://127.0.0.1:7878. (The game binaries are compiled as part of the workspace build — the server communicates with them as child processes over JSON-line stdin/stdout pipes.)
The bench binary must be compiled separately (cargo build --release -p bench)
because it is a separate target — the server spawns it as a child process
for round-robin benchmarking runs.
For UI development with hot reload, run pnpm dev (from ui/) alongside
cargo run --release -p server instead of pnpm build — it serves the app
on http://localhost:5173 with /api/* proxied to the Rust server. Other
ui/ commands: pnpm typecheck, pnpm lint, pnpm test.