Talos docs

critic.play

Since next

The playtester walks each goal entity in order with the real controller: per goal reached, stuck, fell-out, softlock, navmesh coverage.

Plain text

No player: presses its actions or walks its menus. feel: true adds scored verdict.feel probes (animation, controls, camera, audio). Answers a summary; page/section read the rest. Run before you stop. Own engine (minutes); needs the Node CLI.

TitlePlaytester
Modedisk
Token costabout 473 tokens (in the default list, paid on every call)
Toolsetcore

Arguments

ArgumentTypeRequiredDefaultAllowed valuesDescription
agentstringnoThe name of the agent making the call, when several agents share one connection: each named agent is its own actor and plays its own game. Leave it out when there is one agent.
feelnotrue: a feel error fails the run. Probe names (animation, controls, camera, audio, motion, response, movement, actions, impact): only those, no walk
fromnoStart here: a goal or entity id, or [x, y, z]
fullbooleannotrue returns every finding.
goalsstring[]noOnly these, in this order
headlessbooleannotrue
kindenumnoauto, walk, drive, actions, menuDriver; auto picks
motionMoversintegerno48
pageintegernoA page of the last findings, counted from 0, read without running the check again.
profilestringnomelee-duel|third-person-action|platformer-3d|platformer-2d|kart-racer|auto: scores feel
rerunbooleannoRun again; else page, section and full reread the newest kept run of these files and arguments
scenestringnoThe scene file to act on. The open scene when absent.
sectionstringnoOne of sections, e.g. feel.controls
seedintegerno1
speednumberno10Time scale of a realtime run
startstring[]noStart button texts or ids, if not Start/Play
timeoutintegerno120Simulated seconds

Example

An MCP tools/call with the required arguments (placeholders in angle brackets).

{
  "name": "critic.play",
  "arguments": {}
}