Skip to main content

Papersseum

A real-time, multi-agent territory-capture tournament. Write an agent, submit it, and watch it fight four others for the map.

Five agents drop into a bounded circular arena for 180 seconds. Leave your land and you draw a trail behind you. Close the loop and everything you enclosed becomes yours. Cut a rival's trail and you don't just kill them, you take their whole territory and get a short speed burst to go after the next one. Whoever owns the most of the map when the clock runs out wins.

Anyone can enter. Your agent can be a few lines of rules, a trained neural net, a search routine, or anything in between. The server runs ladder rounds of random 5-agent lobbies, rates agents by how they place, and a final round sets the leaderboard. Every match is deterministic from its seed and action log, so any game can be replayed and any dispute settled by running it again.

The name is paper plus colosseum: an arena where paper-thin territories are fought over to the last tick.

The game

  • Arena. Circular, 11,304 playable cells on a 120x120 grid. The wall is solid. Steer into it and you slide along the edge instead of dying.
  • Match. Five players, 180 seconds. Everyone starts with a small disc worth 1% of the map. The engine runs at 30 ticks per second; agents decide 10 times per second.
  • Movement. Three actions: 0 straight, 1 left, 2 right. You move faster the more land you hold (+1 cell per second for every 5% of the map), and you get a 1.5x burst for 5 seconds after a kill. Speed is capped so you never move more than one cell per tick.
  • Capture. Re-enter your own land with an open trail and everything the loop encloses becomes yours, including other players' land.
  • Death. Two bots never share a cell: run into a bot's head on its trail and you cut it; otherwise one waits a tick. You can cross your own trail freely. Get cut by a rival, lose a head-on, or get caught inside a loop a rival closes, and the killer takes all your land. A bot's land is always one connected piece: separate pieces are joined by a thin one-cell strip over empty ground. You respawn with a fresh 1% patch on empty ground.
  • Score. Your share of the map at the end. Ties break on time-averaged coverage, then fewer deaths.

A few rules (taking territory on a kill, the kill speed burst, solid walls) are intentional changes from a stock paper.io-style game.

What your agent sees

Every decision, your agent gets a view built from its own point of view. There are 16 channels: your territory, trail, and head, the same three for each of the four opponents, and the arena mask.

  • Global view, shape (16, 120, 120). The whole arena, north up. Use it for planning.
  • Local view, shape (16, 31, 31). Cropped on your head and rotated so your heading points up, so "straight", "left", and "right" always mean the same pixels. Use it for quick reactions.
  • Scalars: your coverage, rank, speed, boost remaining, time left, and each opponent's coverage, speed, and alive flag.

Using the library

pip install -U papersseum        # Python 3.11+; the only dependency is NumPy
papersseum version               # library version and engine hash (must match the server's)
Command What it does
papersseum new my_agent.py Write a starter agent
papersseum play my_agent.py --vs greedy,hunter Play one match against baselines (--render out.mp4 needs ffmpeg)
papersseum eval my_agent.py --games 30 Benchmark over many matches: placements, win rate, coverage, rating
papersseum validate my_agent.py The platform's upload check, run locally
papersseum pack model.pt --into my_agent.py Embed trained weights in a single-file agent
papersseum render game.jsonl.gz out.mp4 Render a saved replay

From Python:

import papersseum

result = papersseum.play("my_agent.py", vs=["greedy", "hunter"], seed=7)
print(result["placements"])

env = papersseum.PapersseumEnv(seed=7)       # a multi-agent environment for training
obs = env.reset()                            # {player: observation}

An agent is one .py file defining Agent with reset(config) and act(obs) -> int (0 straight, 1 left, 2 right). Four baselines (random, greedy, safe_expander, hunter) ship in papersseum/agents/, and examples/ has a starter and a neural-network agent.

Everything else (upload rules, time limits, scoring, deep-learning recipe) is in COMPETITION.md.

Metadata

Release files for papersseum 0.6.3

For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.

Source distribution (sdist)

Source distribution for papersseum 0.6.3
File Size Uploaded
papersseum-0.6.3.tar.gz 66.6 kB Details

Built distribution (wheel)

Table of built distributions (wheels) for papersseum 0.6.3
File Interpreter ABI Platform
papersseum-0.6.3-py3-none-any.whl Python 3 none any Details

Total release size: 124.6 kB

Release files / papersseum-0.6.3.tar.gz

Download URL papersseum-0.6.3.tar.gz
Size 66.6 kB
Tags Source
SHA-256 checksum
How to use checksums
2e10f64af2b7cd42e127bb934084b8d38011c12074f0324577637109b71d874f
BLAKE2b-256 checksum
How to use checksums
e3ee39e7b3df8d42a9a75c039cdef614191141654c9f733558b663fffa6bd092
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/7.0.0 CPython/3.13.14

Provenance

Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.

PyPI Publish Attestation

PyPI verified that this artifact, at this checksum, originated from the publisher listed below.

Signed by GitHub Actions, verified by PyPI on Oct 16, 2026.

Transparency log

Release files / papersseum-0.6.3-py3-none-any.whl

Download URL papersseum-0.6.3-py3-none-any.whl
Size 58.0 kB
Tags Python 3
SHA-256 checksum
How to use checksums
c2e0f1be8171414e1642643e6bea27d832491a4bd2d6016fd6eadfaad9db4268
BLAKE2b-256 checksum
How to use checksums
bc3019ee2d4474b6cd927fd202653491cd5a018ae37251401c4e1e9927160a3c
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/7.0.0 CPython/3.13.14

Provenance

Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.

PyPI Publish Attestation

PyPI verified that this artifact, at this checksum, originated from the publisher listed below.

Signed by GitHub Actions, verified by PyPI on Oct 16, 2026.

Transparency log

Release history Release notifications | RSS feed

0.6.4

2 release files

This release

0.6.3 This release

2 release files

0.6.2

2 release files

0.6.1

2 release files

0.6.0

2 release files

0.5.1

2 release files

Anthropic, PBC Visionary sponsor Bloomberg Visionary sponsor Hudson River Trading Visionary sponsor Meta Visionary sponsor NVIDIA Visionary sponsor Microsoft Sustainability sponsor Depot Continuous Integration AWS Cloud computing and Security Sponsor Datadog Monitoring Fastly CDN Google Download Analytics Sentry Error logging StatusPage Status page