Apply Rig Overrides

Automatic rigs get you most of the way and then lie to you about the rest. GameAssets_ApplyRigOverrides is the correction pass: you paste in a small JSON of the changes you want - move this pivot, reparent that bone - and it applies them to a GAME_ASSET_RIG while keeping everything else intact. Instead of regenerating the whole rig by hand, you nudge the parts that matter.

It's part of comfyui-game-assets-maker, quinteroac's pack shared on r/comfyui as a playground for game-asset pipelines. It slots in right after SeeThrough Parts Rig Probe or SeeThrough Parts Pose Rig produce their guess, and right before you export.

How it works

You give it the rig and a JSON object with two keys, parts and bones. Parts can be targeted three ways: by id ("face": {...}), by exact tag ("tag:front hair": {...}), or by tag prefix (a bare "tag" matches any part whose tag starts with that name - handy for left_arm vs right_arm if you want to hit both). Bones are matched by their id.

The README's example is the clearest shape of it:

{
  "parts": {
    "face": { "pivot": [653, 650] },
    "tag:front hair": { "pivot": [704, 526] }
  },
  "bones": {
    "face_bone": { "parent": "neck_bone" }
  }
}

The node merges your values into the existing parts and bones - it doesn't replace the rig, so anything you don't mention is untouched.

Inputs

Just two: rig (the GAME_ASSET_RIG, or its JSON as a string) and overrides_json (a multiline text field, defaulting to an empty {"parts": {}, "bones": {}}).

Outputs

• rig - the adjusted GAME_ASSET_RIG, wireable onward to Rig To SVG Preview or Rig To Spine Export.
• rig_json - the full updated rig as JSON, for inspection.
• report - exactly what changed: which parts and bones got overrides. If you typo'd an id, it'll show up here as "none" applied, which is your cue to fix the JSON.

Installing

ComfyUI Manager (search "comfyui-game-assets-maker") or:

cd ComfyUI/custom_nodes
git clone https://github.com/quinteroac/ComfyUI-GameAssetsMaker.git
cd ComfyUI-GameAssetsMaker
pip install -r requirements.txt

Restart after. Only opencv-python in the requirements, no models to download.

Where people get burned

Silent typos. Override an id that doesn't exist and the node won't error - it just won't apply anything, and the report is the only place you'll see it. The tag: prefix matching is also a footgun if you're not expecting it: a bare "front hair" matches parts whose tag starts with "front hair", which is usually what you want, but quote exact tags with tag:front hair when you need precision. And remember the override only changes what you wrote; rerun the generator and your hand-fixes are gone, so apply overrides late in the chain.