D&D5E NPC STAT BLOCK

The D&D5E NPC STAT BLOCK node is where you actually write your NPC. The other two nodes in this pack render the card and build the action list, but this one is the data-entry form: ~45 fields in, one JSON string out, and that string is what the Sheet Generator prints. Think of it as a stat block form that happens to live inside ComfyUI - ugly to look at, exactly what you need.

How it works. When you hit run, it gathers every input into a dictionary and json.dumps it with indentation. The keys matter because the card layout looks fields up by name: NAME, RACE, CR, HP, AC, SPEED, the six ability scores plus saves, the skill modifiers, IMMUNITY, RESISTENCE, WEAKNESS, SPELLCASTING, RESOURCES, DESCRIPTION, and an ACTIONS array. Everything goes into the JSON as strings (even the numbers, so HP 50 prints fine), and the output is a multiline STRING you wire straight into the Sheet Generator's i_s_npc_json input.

The node is long, so the author added cosmetic ====== STRENGTH ====== separator widgets between each ability block. Those are pure UI decoration - they're defined as inputs so the widget stays visible in the node, but the code never reads them. Ignore them, or don't touch them; they change nothing.

Inputs worth knowing. The top handful are obvious - name, race, cr, hp, ac, speed. Two details:

• cr is a STRING, not a number, which is a small godsend: D&D challenge ratings like "1/2" or "1/4" work as-is.
• image_prompt is metadata, not an instruction - it's the prompt you used (or will use) to generate the portrait, stored in the JSON so the card carries a record of how the art was made. Pair it with whatever you feed the portrait generator to keep the picture matching the sheet.

Below that come the six ability scores with their saves and skills. There are two gotchas here, and both are in the shipped source, not rumors:

• ATHLETICS is silently ignored. The node defines the input, but the code writes "ATHLETICS": -2 into the JSON no matter what you type. If Athletics on your NPC matters, edit the node file (cl_orso_character_sheet_generator_comfyui_bindings.py, one line where "ATHLETICS" is set) or accept the -2.
• "RESISTENCE" is misspelled - deliberately consistent typo that the layout also uses. Leave it.

The ability optional input is how the third node in this pack plugs in: feed it the chained abilities JSON and it merges them into ACTIONS.

Where this sits in the pipeline. ComfyUI is mostly plumbing - this whole node is a glorified "build a string" value node with a D&D skin, and that's fine, because it's the source of truth for the card. Run it as part of your normal generation graph (the front-of-card portrait and this node can run in parallel; nothing waits on anything). Change a stat, hit run, and you're re-printing the card. If you'd rather keep the graph tidy, you can paste the whole JSON into the Sheet Generator by hand - the output is just text.

Install. Same as the rest of the pack - ComfyUI Manager search comfyui-orso-character-sheet-generator, or:

cd ComfyUI/custom_nodes
git clone https://github.com/OrsoEric/comfyui-orso-character-sheet-generator

Restart, and the three nodes show up under dnd5e-orso. No model downloads, no extra Python packages - the pack leans entirely on Pillow and torch, both already in ComfyUI. The one failure mode to expect is feeding the output somewhere that wants valid JSON and getting a multiline string instead - it's a STRING output, not a magic type, so wire it to another STRING input, not a JSON-loaded node.