Feel Lab

Feel Lab

An FPS feel checklist, measured: every interaction a player has, checked from what the game really did.

[license: MIT] [Python 3.10+] [PyPI: feellab-mcp] [MCP Registry: feellab-mcp] [checklist: 82 interactions] [tools: 6] [timeline contract: v1]

Game feel is what a player feels between pressing a key and seeing the world answer. A shot should flash, sound and kick on the same frame; a round striking a wall should throw dust, make a sound and leave a hole; a hit taken should jerk the view and show where it came from; a blast nearby should shake the screen more than one far away. When one answer is missing or late, the game feels floaty or cheap, and nobody can say why.

Feel Lab turns that into checks. Your game's probe plays standard scenes and writes a timeline: the camera every frame, and every sound, effect, mark and damage event with its time. Feel Lab measures latency, kick, shake, presence, match and smoothness from it, and judges each item of an 82-item checklist. It never runs your game: any engine can write the timeline (docs/TIMELINE.md).

The checklist

Items no timeline can show (a colour-blind option, a reload cancel's timing) are left for a person, with what to look for. feellab checklist prints them all.

What it measures

Every rule names its source. A range from game practice rather than evidence is marked as an estimate.

Try it

pip install feellab-mcpfeellab demo demofeellab judge demo

The demo writes timelines for two made-up games: "Juicy" passes every measured item; "Bare" (a debug dot where a round lands, no shake, silent steps) fails 17.

Use it in your game

1. Have your probe play the scenes in src/feellab/data/scenes.json and write one timeline each (docs/TIMELINE.md). Wrap the calls that start sounds and effects so each is recorded with its time; note the moments with no sound or effect of their own (a shot, an impact, a hit marker, damage, a flinch).
2. Record a camera frame before the scene's cause (a shot, a hit, a blast): kick and flinch are measured from it.
3. Tag what you can ("tags": ["muzzle"]). Where your asset names do not say what a sound or effect is for, put a feel_rules.json beside the timelines: {"dry": "slidelock"} tells Feel Lab that a sound named after a slide lock is the click of an empty gun.
4. feellab judge <folder>, or gate_rows for a gate.

The first game to use it (ToangTown) found 52 failing cases on four guns: a debug dot where a round lands, no shake anywhere, no blood, no footsteps, a climb that never comes back, a stall on the first shot.

Tools

{"mcpServers": {"feellab": {"command": "feellab-mcp"}}}

FEELLAB_OUT is the only folder Feel Lab writes to (its reports); ~/.feellab by default.

Where it came from

Feel Lab was built for ToangTown, an Unreal 5.8 co-op zombie FPS, next to Weapon Lab (weaponlab-mcp), whose Gate can judge Feel Lab's rows as cases.

License

MIT