Scene Entity - Horror

Optional node, and worth saying plainly: Scene Weaver - Horror already builds a complete scene with a fully-described subject. You only want Scene Entity when you need a second thing described just as deeply, or one monster you can reuse across a dozen scenes without it drifting into a different monster each render.

It describes exactly one entity - silhouette, material, colours, markings, close-range wear, appendages and how many, what glows and in what colour, weapons, how it watches, its aperture - and emits that as a payload a scene can consume.

What it gives you

Two outputs, and the split is the point:

• entity_text - the entity as it will read inside a scene, in prose. Wire it to a Show Text node to read it. No setting, no action.
• entity - a SCENE_ENTITY payload for one of the Scene Weaver's optional entity_1_in … entity_4_in sockets.

The absence is deliberate. No environment, no situation, no relations, because the scene owns all three. A wired entity that insisted on "crawling out of a well" would fight every scene you put it in. The scene decides where it is and what it's doing; the entity decides what it is.

That socket is genre-agnostic on purpose: a horror entity wires happily into a Fantasy or Sci-Fi Scene Weaver, and a sci-fi one wires into a haunted house. A cryptid built for a bog works fine standing in an elf glade, and the pack treats that as a feature. It's a dedicated socket type rather than a plain string, which is why you can't accidentally plug it into a text input and get silence.

How the vocabulary is scoped

Every field is Random / a value / None. kind governs the rest - it scopes the options and labels of everything beneath it - and horror's kinds are undead (ghoul, bog body, drowned revenant, walking skeleton), spirit (ghost, banshee, poltergeist, weeping apparition), cryptid (werewolf, antlered stalker, living scarecrow, moth-winged watcher), eldritch horror, mortal (hooded cultist, plague doctor, lantern-bearing warden), cursed object (porcelain doll, music box, spirit board) and haunted place (abandoned farmhouse, ruined chapel, derelict motel).

So a porcelain doll doesn't get a cleaver, and a manor doesn't get teeth. There's no gore filter on this node, deliberately: the gore setting belongs to the scene the entity lands in, not the entity, so No gore is set on the Weaver. Your own locks are still always kept.

What happens when you wire it in

• A field you locked is a choice. It beats that slot's own widgets and beats a coherence rule, and prompt_json._meta reports the rule and why it lost.
• A field left on Random is a draw. The scene picks a place that can hold the whole wired subject first, and re-draws a drawn field only when no place can - naming what it re-drew on the node face.
• Situation and relations never come from the entity. Those stay the scene's call.
• The wired slot gets the top detail allowance, but it's a promotion, not an exemption. A ghoul carries its whole component list; a haunted house only its silhouette, however many widgets you locked.
• Wiring a slot occupies it whatever entity_count says - connecting a node is the more explicit statement, and the count is raised to match.

The readout on this node shows exactly what it will contribute to a one-entity scene, so it works as a preview before you wire anything.

Why bother at all

Reuse. A diffusion model has no internal notion of this creature - there's no character identity hiding in the weights, just statistical patterns - so the only thing carrying your drowned revenant between scenes is the description. Lock the fields that made it work, fix the seed, and the creature comes back. Prompt-level consistency, no training required.

Install

Manager: search SceneWeaver, install, restart. Or:

cd ComfyUI/custom_nodes
git clone https://github.com/EnragedAntelope/comfyui-sceneweaver

Keep the directory named comfyui-sceneweaver. Zero dependencies - standard library only, no requirements.txt, nothing to build - but it needs ComfyUI 0.25.0+ (the newer comfy_api.latest node API) and Python 3.10+. Nodes land under conditioning/sceneweaver.

Horror vocabulary is extendable via a user_options.json beside the pack (gitignored, survives updates) with a "horror" section. Tags there interact with the scene's filter: conflict_only is what No gore hides.

python scripts/builtin_options.py subkind --kind cryptid --pack horror

Traps

Expecting the entity to supply an action. If you want the thing doing something, that's entity1_situation on the Weaver. The entity never provides it, whatever you wire.

Wiring it into a text encoder. entity_text goes there. The entity socket doesn't and can't - wrong type by design.

A locked, shrunken detail list on a building. A structure speaks only its silhouette in a scene, so a haunted house with every widget pinned still reads shorter than a ghoul with half of them locked. Budget, not bug.

Import errors on older ComfyUI. Below 0.25.0 you'll see comfy_api.latest fail at load rather than a node appearing.

_default pools for kind-scoped fields. form, material, surface_detail and markings are overridden by every kind, so a _default entry is never read. Put them under a kind name - the console warns you when they're in the wrong place.