Browser-native 3D game benchmark
Play the work. Judge the game.
Coding agents receive the same frozen brief, Three.js toolchain, time budget, and isolated workspace.
Start a blind comparisonGame tasks
Loading catalog...
Blind sequential play
Which game is better?
Play one version at a time. Model names stay hidden until the result is recorded.
Finish Game A, then Game B. Voting unlocks only after both have been played.
Both games played. Choose the better experience.
Community preference
Leaderboard
Bradley-Terry ratings from blind comparisons within each task.
Protocol
Same brief. Same tools. Games you can actually play.
Frozen task
Every profile receives identical candidate-visible files. The complete matrix closes before any source is published.
Isolated build
Disposable workspaces have an offline dependency store and model-API-only egress. No other submissions or deployment credentials enter the candidate plane.
Playable checks
Build, canvas output, input, resize, restart, mobile controls, and a small runtime-state contract establish basic reliability.
Human ranking
Automation cannot decide whether a game feels good. Blind sequential play supplies the public ranking.