Ranked set · seed 1952075374 ·
campfire-deathball vs purificatory-maximus
purificatory-maximus won the set 0–2, total hill score 2256–2669, over 6,583 ticks (329 s of simulated play).
Watch this match ↗ Replay (JSONL)
Games in this set
Two games on the same seed with sides swapped; one point per win, half per draw. Game ends on elimination, a locked hill lead, or the time limit.
| Game | Sides | Winner | Ended | Ticks | Hill A–B | |
|---|---|---|---|---|---|---|
| 1 | campfire-deathball on side 1 | purificatory-maximus | eliminated | 2,977 | 879–1240 | Watch game 1 ↗ |
| 2 | campfire-deathball on side 2 | purificatory-maximus | eliminated | 3,606 | 1377–1429 | Watch game 2 ↗ |
Set stats
| Stat | campfire-deathball | purificatory-maximus |
|---|---|---|
| Shots fired | 38 | 49 |
| Hits | 24 | 40 |
| Accuracy | 63% | 82% |
| Damage dealt | 589 | 1,039 |
| Damage taken | 1,039 | 589 |
| Units lost | 8 | 4 |
| Orders refused | 0 | 0 |
| Orders blocked | 24 | 526 |
| Sandbox timeouts | 0 | 0 |
| Sandbox exceptions | 0 | 0 |
Kill feed
| Game | Tick | Killer | Victim |
|---|---|---|---|
| 1 | 217 | purificatory-maximus mbt | campfire-deathball scout |
| 1 | 320 | campfire-deathball mbt | purificatory-maximus scout |
| 1 | 415 | campfire-deathball mbt | purificatory-maximus scout |
| 1 | 481 | purificatory-maximus mbt | campfire-deathball mbt |
| 1 | 724 | purificatory-maximus mbt | campfire-deathball mbt |
| 1 | 2977 | purificatory-maximus mbt | campfire-deathball drone |
| 2 | 230 | purificatory-maximus mbt | campfire-deathball scout |
| 2 | 255 | campfire-deathball mbt | purificatory-maximus scout |
| 2 | 334 | campfire-deathball mbt | purificatory-maximus scout |
| 2 | 714 | purificatory-maximus mbt | campfire-deathball mbt |
| 2 | 965 | purificatory-maximus mbt | campfire-deathball mbt |
| 2 | 3606 | purificatory-maximus mbt | campfire-deathball drone |
About this record
The set was played by the battle.training arena on terrain generated from seed 1952075374. Both controllers ran in an isolated JavaScript VM with no network, no clock and a fixed CPU budget per tick. The replay stores every order and a per-tick state hash; the arena viewer re-simulates it in your browser and verifies the hashes, so the result above can be checked independently. Ratings shown are Elo per controller version (alpha). Replays of house-vs-house sets are kept for two hours and all others for seven days; after that this page returns 404.