Burve Character Race Details

Burve Character Planner handles the human base - body, age, hair, skin - but it has a gap: it doesn't describe non-human anatomy in detail. That's this node's job. It packages up fantasy race traits - ears, horns, wings, tail, legs and feet, skin surface, head features, hands and arms - into a CHARACTER_RACE_PIPE that you plug straight into the planner's race_override_pipe input.

Think of it as a swap-in module for the character workflow. You build your human base in the planner, connect this node, and the race traits ride along as overrides. Leave it disconnected and the planner behaves exactly like before - a regular human character, no fantasy baggage. It's a clean way to keep the two concerns separate: body shape in the planner, monster bits here.

How it works

Each trait is a dropdown with none as the default "don't select" option, plus an adjacent custom text field. Fill the custom field and it overrides the dropdown for that trait - so wings can be "dragon_membrane" from the list, or "translucent owl wings, slightly tattered" if you type it yourself. extra_notes is a free-text slot for anything the dropdowns can't express. Everything resolves into a JSON payload that the node emits three ways: the race_override_pipe for the planner, race_override_json for debugging, and summary for a quick human-readable readout of the resolved traits.

The inputs

The trait list: race_name (or custom_race_name), ears, horns, wings, tail, legs_feet, skin_surface, head_features, hands_arms - each with its matching custom field - and extra_notes. The choices are genuinely thorough: horns range from small_curved to crown_horns to broken_horn; tails go from feline to mer_tail; legs include digitigrade and serpentine_lower_body. The custom fields are the escape hatch for anything missing.

Outputs

Three of them: race_override_pipe (CHARACTER_RACE_PIPE), race_override_json (a string), and summary (a string). You only need to wire the first one, into Burve Character Planner's race_override_pipe. The other two are inspect-only.

Gotchas

The planner validates its own overrides, so if you try to send something contradictory it'll refuse rather than guess - that's a feature. And there's a sequencing quirk to know: the race name here can override the planner's own race dropdown, so if the planner says "elf" but this node says race_name: none, the pipe's value wins for the traits it covers. It's a straightforward text-and-pipe node, so install is just the pack itself - no models, no keys. It only matters inside a Burve character workflow, and that's fine; it's not trying to be a general-purpose tool.