Drag a picture to spin it, wheel to zoom. Both pictures move together.
Mark a problem:drag a box around the wrong spot on A or B, then say what is wrong.
A · moving
A
B · press Tab
B
Score 0 ApprenticeYour picks 0Everyone 0Consistency – (hidden "same picture" checks)Ready to apply – settings with 6+ picks and a clear winnersaving on this computer
What it has learned so far
Score = how often an option won, adjusted for what it was up against (a Bradley–Terry model fitted to every pick). Green = current favourite. "Now" marks what the games use today. A favourite means little before about 6 comparisons. Movement settings are only tested in Walk mode.
Current prescription for the engine and the games
The exact constants the games would use if we applied today's favourites. Settings without enough picks keep their current value.
tools/apply-look.py results.json --apply writes the shader ones into the engine; the rest are listed for the game builds.Analysis: upgrade or keep?
One line per setting. UPGRADE = enough picks and the favourite differs from what the games use now. KEEP = enough picks and today's value wins. MORE PICKS = not decided yet. The win counts are plain tallies of every pick.
Needs fixing
Two sources: the automatic geometry audit of every monster (parts found by the leg/arm rule, loose blocks that touch nothing, size) and the flags players raise under a picture (missing part, broken movement, floating blocks, too dark, colours off, clipping).
Rig fix for —:Move a slider, watch the monster re-rig (press Show rig to see the joints). Fixes are saved and sent to the lab.