Feel Lab

io.github.hpdkhoaPublished by GitHub account hpdkhoav0.1.0Updated Oct 24, 2026

An FPS feel checklist, measured from a timeline any game's probe can write

VerifiedSTDIODesktop onlyDeveloper ToolsData & Analytics

Overview

AI-generated overview

Judges FPS game feel from probe-written timelines, scoring an 82-item checklist of latency, kick, shake and sync.

What you can do
  • List the 82-item feel checklist by group, marking which items are measured and which are left for a person
  • List the standard scenes a game probe should play and the metrics with their units, rules and sources
  • Validate a timeline file against the expected contract
  • Judge a folder of timelines, returning each item's values and verdict plus a Markdown report
  • Export the metrics as rows for a gate in Weapon Lab's row format
When to use it
For teams building a first-person shooter who want objective, repeatable checks on how shooting, hits, damage, explosions and movement feel, instead of relying on subjective playtest impressions. Useful when a game already has a probe that can record camera frames and sound, effect and damage events.
Requirements
Runs locally as a Python package (pip install feellab-mcp) over stdio. It does not run the game itself; you need a probe that plays the standard scenes and writes timeline files, optionally with tags and a feel_rules.json. Writes reports only to the folder named by FEELLAB_OUT, defaulting to ~/.feellab.
Before you install
It reads timeline files and writes reports into the FEELLAB_OUT folder, so point that variable at a location you are comfortable having written to. Verdicts depend entirely on the quality of your probe's timeline data, and some checklist items are explicitly left to human review rather than measured.

Installation

In SourceWeft

  1. Open Feel Lab in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.

Other MCP clients

Follow the launch instructions in the repository.

README

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

GroupItemsMeasured from a timeline
A. Shooting (your own gun)199
B. Hitting (your bullets land)156
C. Getting hit (damage taken)94
D. Movement and the body112
E. Interacting with the world70
F. Enemies (zombies)50
G. Explosions, fire and the world51
H. Sound mix40
I. Screen and comfort40
J. Smoothness (feel breaks when the frame does)31

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

MeasureExample
Latencythe shot's flash and sound on the shot's frame; the hit marker within 50 ms of the hit
Syncthe shot's sound within 45 ms of its flash (ITU-R BT.1359)
Kickthe camera turns at least 0.3 degrees on a burst and settles within 0.6 s
Shakea blast 5 m away shakes the view; one 50 m away at least 3 times less
Presenceevery impact has an effect, a sound and a mark; every round fired ejects a case
Rhythmfootsteps at walking cadence (about 100 steps a minute and up); the head bobs
Smoothnessno frame twice the median length round a shot or a blast

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

Try it

bash
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

ToolWhat it does
list_checklistThe checklist by group: what the player should get, measured or for a person.
list_scenesThe standard scenes a probe plays.
list_metricsEvery metric: scene, unit, rule and source.
check_timelineA timeline file against the contract.
judge_folderA folder of timelines judged: each item's values and verdict, and a Markdown report.
gate_rowsThe metrics as rows for a gate (Weapon Lab's row format).
json
{"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

Source: README.md at commit 437580a

Tools

0
SourceWeft has not started this package in its sandbox yet, so its tools are not known.

Version history

1
  1. v0.1.0LatestOct 15, 2026

Score

50% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 days25 pts

    Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.

  • Auth declared10 pts

    Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.

  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts
  • License10 pts