Papers › OpenSpiel: A Framework for Reinforcement Learning in Games

OpenSpiel: A Framework for Reinforcement Learning in Games

26 Aug 2019arXiv:1908.09453archive 2025-07-28

Marc Lanctot, Edward Lockhart, Jean-Baptiste Lespiau, Vinicius Zambaldi, Satyaki Upadhyay, Julien Pérolat, Sriram Srinivasan, Finbarr Timbers, Karl Tuyls, Shayegan Omidshafiei, Daniel Hennes, Dustin Morrill, Paul Muller, Timo Ewalds, Ryan Faulkner, János Kramár, Bart De Vylder, Brennan Saeta, James Bradbury, David Ding, Sebastian Borgeaud, Matthew Lai, Julian Schrittwieser, Thomas Anthony, Edward Hughes, Ivo Danihelka, Jonah Ryan-Davis

OpenSpiel is a collection of environments and algorithms for research in general reinforcement learning and search/planning in games. OpenSpiel supports n-player (single- and multi- agent) zero-sum, cooperative and general-sum, one-shot and sequential, strictly turn-taking and simultaneous-move, perfect and imperfect information games, as well as traditional multiagent environments such as (partially- and fully- observable) grid worlds and social dilemmas. OpenSpiel also includes tools to analyze learning dynamics and other common evaluation metrics. This document serves both as an overview of the code base and an introduction to the terminology, core concepts, and algorithms across the fields of reinforcement learning, computational game theory, and search.

PaperPDFCodeCode Syntology ran

In Syntology View this paper on Syntology, its page in Syntology's graph. That page adds which of its functions are also present in other papers' code Syntology holds, with dates, and its dated run record as JSON and a README badge. It also lists the repositories linked to the paper, the abstract and the calls for agents.

Open this paper in Syntology's Atlas, the map of the papers in Syntology's graph and their citations.

For agents, on Syntology's MCP service (how to connect):

Code

No sample from the archive's official repository (deepmind/open_spiel) is linked to this paper; the 8 samples below come from 3 community repositories. Syntology harvested code from deepmind/open_spiel for another paper.

deepmind/open_spiel: Syntology's graph links these samples to Multi-Agent Training beyond Zero-Sum with Correlated Equilibrium Meta-Solvers (arXiv:2106.09435; that paper's own run record: 9 ran (of which 0 constructed an object rather than computing a result; 0 with no instrument failure: 0 honoured, 0 violated, 0 with no contract checked; 9 where Syntology's instrument failed) · 1 unverified); nothing checks that they implement this paper's method.

Syntology 8 code samples harvested from 3 repositories linked to this paper: 8 ran (of which 0 constructed an object rather than computing a result; 8 with no instrument failure: 1 honoured, 1 violated, 6 with no contract checked; 0 where Syntology's instrument failed) · 0 unverified. “Where Syntology's instrument failed” counts failures of Syntology's instrument, not of the code; here there are none.

By repository: community (archive-listed): 8 samples from 3 repositories, 8 ran (8 with no instrument failure; 0 where Syntology's instrument failed). The run record, sample by sample. “Ran” means executed on a synthesized input, not that the code is correct or reproduces the paper.

No sample is linked to this paper from 2 of its repositories that Syntology harvested for other papers:

Levels written between 2026-09-24 and 2026-09-26 (UTC): the dates Syntology's graph wrote each sample's verification level, not when the code executed.

16 repositories listed; official and paper-mentioned ones first.

deepmind/open_spiel officialmentioned in papermentioned on GitHubSyntology: no sample linked to this paper (harvested for another paper). Syntology's graph links these samples to Multi-Agent Training beyond Zero-Sum with Correlated Equilibrium Meta-Solvers (arXiv:2106.09435; that paper's own run record: 9 ran (of which 0 constructed an object rather than computing a result; 0 with no instrument failure: 0 honoured, 0 violated, 0 with no contract checked; 9 where Syntology's instrument failed) · 1 unverified); nothing checks that they implement this paper's method. report
Tyjch/open_spiel mentioned on GitHubApache-2.0Syntology: 1 sample, 1 ran (0 instrument-failed) · 0 unverified report
Tyjch/open_spiel_colab mentioned on GitHubApache-2.0Syntology: not harvested report
aicenter/openspiel_reproductions mentioned on GitHubtfSyntology: not harvested report
alextrudeau/go_exploit mentioned on GitHubpytorchApache-2.0Syntology: not harvested report
drblallo/open_spiel mentioned on GitHubApache-2.0Syntology: not harvested report
google-deepmind/open_spiel mentioned on GitHubSyntology: no sample linked to this paper (harvested for another paper). Syntology's graph links these samples to Efficient Algorithms for Robust Markov Decision Processes with s-Rectangular Ambiguity Sets (arXiv:2602.05591; that paper's own run record: 7 ran (of which 0 constructed an object rather than computing a result; 4 with no instrument failure: 2 honoured, 0 violated, 2 with no contract checked; 3 where Syntology's instrument failed) · 0 unverified); nothing checks that they implement this paper's method. report
higcompetition/tournament mentioned on GitHubApache-2.0Syntology: not harvested report
mwalton/openspiel_benchmarks mentioned on GitHubtfSyntology: not harvested report
optimization-and-machine-learning-lab/open_spiel mentioned on GitHubApache-2.0Syntology: not harvested report
qmaai/open_spiel mentioned on GitHubApache-2.0Syntology: 1 sample, 1 ran (0 instrument-failed) · 0 unverified report
rahulpandeycs/openspiel-games mentioned on GitHubApache-2.0Syntology: not harvested report
semanticweights/tarok mentioned on GitHubMITSyntology: not harvested report
wyz2368/open_spiel2 mentioned on GitHubApache-2.0Syntology: not harvested report
wyz2368/open_spiel3 mentioned on GitHubApache-2.0Syntology: not harvested report
wyz2368/open_spiel_egta mentioned on GitHubApache-2.0Syntology: 6 samples, 6 ran (0 instrument-failed) · 0 unverified report

Repository list and official/mentioned flags are the archive's, frozen 2025-07-28. Reachability, where shown, is from one Syntology probe window (2026-09-16 to 2026-09-18); repositories not probed show nothing. GitHub stars are not tracked.

A paper named beside a repository with no sample linked to this paper is shown with that paper's own run record, not this paper's: “ran” means executed on a synthesized input, not that the code is correct, and “where Syntology's instrument failed” counts failures of Syntology's instrument, not of the code. Papers are listed in arXiv-id order, at most three per repository.

Code Syntology ran Syntology

8 samples harvested: 8 ran (of which 0 constructed an object rather than computing a result; 8 with no instrument failure: 1 honoured, 1 violated, 6 with no contract checked; 0 where Syntology's instrument failed) · 0 unverified. “Where Syntology's instrument failed” counts failures of Syntology's instrument, not of the code. Syntology's record for this page last changed ; when this build read Syntology's graph is in the build record. That date is not when the samples ran.

1ran · honoured contract
1ran · violated contract
6ran

Licence: 1 of the 8 samples is pointer only, meaning Syntology does not serve that copy's text. For that sample, this paper's copy is under a permissive licence and cleared, but the stored copy of the same code that Syntology serves is not; the licence label's tooltip gives Syntology's recorded reason. This page shows no code text for any sample; each one links to its file in the repository.

Harvested from 3 repositories linked to this paper, official or community; the list below is grouped by repository, each group headed by its name and what it is to the paper. “Ran” means the sample executed on a synthesized input. It does not mean the output is correct, and nothing here reproduces the paper's results. A line beginning “fixture:” under a sample that ran gives the arguments Syntology's fixture called the sample with, each as name:type/rank/element kind (? where none was recorded), and the type of what the fixture's run returned, exactly as the harness recorded them; the arguments and the returned type were recorded by two separate runs of the same fixture. No output value is shown, and a returned type says nothing about whether the output was right. “Level recorded” gives the UTC date when Syntology's graph wrote the sample's verification level, not when the code executed; where the level was written before Syntology's graph kept that date, the row says “level recorded, date not recorded”. “Honoured” and “violated” refer to a contract Syntology drafted from the code itself. “Our draft was wrong” and “the contract check could not run” are failures of Syntology's instrument, not of the code: the sample ran on Syntology's synthesized input, and then the drafted contract did not describe it, or the check itself raised an error (RAISES), lacked a dependency (DEP_MISSING) or ran out of time (TIMEOUT); hover the label for which. A metamorphic tier, where shown, is evidence of the output's shape, not that the sample implements the method.

Each sample ends with its code_sha256. A sample's code_sha256 is Syntology's identity for that exact code. It is printed in full (16 hexadecimal characters for every sample in this build), and get_code(code_sha256="…") takes it exactly as printed. An agent calls it on Syntology's MCP service (how to connect); click an identity to copy that call.

Repository labels, per sample. official repository: The archive marks this repository official for the paper. named in the paper: The archive records that the paper mentions this repository; it is not marked official. community (archive-listed): In the archive's code links for this paper, not marked official and not recorded as mentioned in the paper. found in paper text by Syntology: Syntology found this repository in the paper's own text; whether it is the authors' implementation is not asserted. community: Not in the archive's code links for this paper; a community repository Syntology harvested. Samples are grouped by repository: a repository marked official first, then by how directly the repository is tied to the paper, then in the archive's order; never by how many ran. Licence labels name the repository's licence as recorded at harvest. “Pointer only” means Syntology does not serve that copy's text, for one of six reasons: no licence file was found; the licence was not identified; the licence is recorded as permissive but that copy's record is not marked cleared; the licence is outside the permissive list Syntology serves text under (MIT, Apache-2.0, BSD and similar); this paper's copy was not located, so its licence is not recorded; or this paper's copy is cleared, but the stored copy of the same code that Syntology serves is not. Some licences outside that list permit redistribution, such as WTFPL, and GPL-3.0 under its conditions; they are simply not on the list. Hover a licence label for the reason. File links open the file on GitHub at the default branch, which may have changed since the harvest.

A function or class name links to its page when the name occurs in the harvested code of at least 5 papers; the name is a string, not an identity. A census tag appears when Syntology's census ran implementations with that name on one shared input per bucket: it gives how many were compared, from how many papers, and how many distinct outputs they produced, and names this sample's bucket when this sample was one of them.

Tyjch/open_spiel community (archive-listed) 1 sample, 1 ran (0 instrument-failed) · 0 unverified
lens open_spiel/python/algorithms/double_oracle.py ran · honoured contract Apache-2.0 (permissive) · e893a592cd4dd8fe · report fixture: signature lists:list/1/list · returned list · level recorded 2026-09-26
qmaai/open_spiel community (archive-listed) 1 sample, 1 ran (0 instrument-failed) · 0 unverified
softmax in 240 papers
census: 53 implementations from 63 papers, 16 distinct outputs across 8 buckets, one shared input per bucket
open_spiel/python/algorithms/ars.py ran · violated contract fingerprinted Apache-2.0 (permissive) here; the stored copy is pointer only · a585b44308980803 · report fixture: signature x:ndarray/1/float · returned ndarray · level recorded 2026-09-24
wyz2368/open_spiel_egta community (archive-listed) 6 samples, 6 ran (0 instrument-failed) · 0 unverified
exhaustive_strategy_selector open_spiel/python/algorithms/psro_variations/generalized_egta.py ran Apache-2.0 (permissive) · c5983134be459f12 · report fixture: signature solver:MockGenPSROSolver/0/? · returned list · level recorded 2026-09-24
probabilistic_strategy_selector open_spiel/python/algorithms/psro_variations/generalized_egta.py ran Apache-2.0 (permissive) · 51e8afabe25ebd98 · report fixture: signature solver:MockGenPSROSolver/0/? · returned list · level recorded 2026-09-24
rectified_strategy_selector open_spiel/python/algorithms/psro_variations/generalized_egta.py ran Apache-2.0 (permissive) · c2404a4c6f480a8e · report fixture: signature solver:MockSolver/0/? · returned list · level recorded 2026-09-24
renormalize in 11 papers open_spiel/python/algorithms/psro_variations/abstract_meta_trainer_egta.py ran fingerprinted Apache-2.0 (permissive) · 8469ed1452bc3dd0 · report fixture: signature probabilities:ndarray/1/float · returned ndarray · level recorded 2026-09-24
sample_episode open_spiel/python/algorithms/psro_variations/abstract_meta_trainer_egta.py ran Apache-2.0 (permissive) · c0276e4601634e38 · report fixture: signature state:MockState/0/?, policies:list/1/callable · returned ndarray · level recorded 2026-09-24
uniform_strategy open_spiel/python/algorithms/psro_variations/abstract_meta_trainer_egta.py ran Apache-2.0 (permissive) · 8faf6f7ec3ffb422 · report fixture: signature solver:MockGenPSROSolver/0/? · returned list · level recorded 2026-09-24

Tasks

General Reinforcement LearningReinforcement LearningReinforcement Learning (RL)reinforcement-learning

Results from the paper archive 2025-07-28

No leaderboard rows for this paper in the archive.

Report a problem or propose a change · a person checks every report against the paper or source before anything changes; decisions are listed on /corrections