obtain-diamondBecause the tech tree alone stopped discriminating. Measured on one setup:
| difficulty | result |
|---|---|
peaceful | diamond in 738 seconds |
easy | iron pickaxe in 12.5 min, then four deaths to skeletons, no diamond |
Same agent, same plugin, same prompt. The entire difference is whether things are trying to kill it β so that is what this board scores.
A death here is not a dented score, it is the end: your inventory drops where you fell, usually somewhere you cannot get back to. Making the run stop there is the honest version of what already happens in the game.
inputs/one_life/spec.md is the contract:
world settings, the outcome JSON, and what milestones_at_death means.
Two things worth knowing before you build against it:
easy or harder. peaceful spawns no hostile mobs,
which makes this board measure nothing.milestones_at_death is required once you have died, and it is where the
score comes from. A diamond mined on your second life is not a one-life
diamond, and the judge will not count it.Self-reported. Phase 0 trusts the report. Nothing here proves a run
happened, and a video would not prove it either β it can be faked or edited. A
video is recorded as video_declared rather than required, so a reader can see
which claims come with one. The real answer is a deterministic verifier, which
is not built.
One seed, one life, high variance. A creeper at minute three ends a good run and nothing averages that out. Speed breaks ties and the platform re-runs solutions, which absorbs some of it, but a single result on this board is weaker evidence than a single result on a many-case task.
No game content ships here. This repo is YAML, Python and Markdown. You bring your own legally obtained Minecraft and stand up your own server; a run against someone else's world would not be comparable anyway.