Scene Weaver - Sci-Fi

Most prompt randomizers hand you a comma pile: starship, red, damaged, space, detailed, 8k. Words with no grammar, so the model guesses which adjective sticks to what - and when the pieces disagree, like a derelict with its engines firing, the picture becomes a negotiation. Scene Weaver - Sci-Fi draws from pools the same way but writes English: a place, up to four things in it, what each is doing, and how they relate.

Why you'd reach for it

You want variety without writing a prompt per image. The usual answer is the bracket trick - {brown|blonde|black} hair, batch it, cherry-pick - which buys variation at the cost of coherence. Coherence is the point here: a contradictory prompt averages to nothing, and attention is finite, so four fully-described entities never render whole.

How it works

The seed drives one random.Random, and everything downstream is that draw. Fields resolve in widget order from the pool their scope chain selects - which is why kind: gas giant narrows form live to sphere shapes instead of offering a spiral coil. Constraint rules then run to a fixed point before anything is written: what a place affords, how a shape holds itself up, which traits can't coexist on one body. A ring can't stand on its own ring because a stance rule excludes it, not because someone wrote that sentence.

Last comes the detail budget. Each occupied slot keeps a fixed allowance of optional fields and the whole scene is capped at 320 tokens: slot 1 speaks in full, later slots get their silhouette unless you promote them, and anything cut is written back to None in prompt_json too - no "resolved but unspoken" state, so the JSON never promises a detail the image wasn't asked for. A locked field is never cut.

The controls that matter

Every descriptive dropdown - fifty-plus once all four slots are revealed - defaults to Random, so an untouched node already generates complete scenes. The ones you'll touch:

• seed - the scene is a pure function of it. The control below defaults to randomize; flip it to fixed when you like something.
• entity_count - "1" to "4", and raising it reveals that slot's widgets. One has the highest hit rate, two is the sweet spot; three and four read as a crowd and models blend subjects. A wired Scene Entity occupies its slot regardless.
• scene_filter - Any, Peaceful, Conflict. Peaceful masks weapons and hostile actions out of the pools before the draw, rather than drawing a weapon and talking around it.
• set_all_fields - Randomize all / Clear all. It never touches a locked value and snaps back to Off: a one-shot action, not a mode.

The morphology fields - form, material, primary_color, markings, emitters, emitter_color, sensors - are where the depth lives, and form is what makes two ships genuinely different. Slots 2–4 expose only kind, subkind, scale, condition and situation; the relation_* pairs default to None on purpose.

Outputs

Two strings. prompt_text goes into any text encoder, and into a Show Text node so you can read what you got. prompt_json is the same scene as structured data. The node's face also shows a readout: scene contents, filter, counts, wired slots, and an approximate token count.

Install

ComfyUI Manager, search SceneWeaver, install, restart. Or:

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

Keep the folder named comfyui-sceneweaver. There are no dependencies - standard library only, so no requirements.txt step and nothing to build. It does need ComfyUI 0.25.0+ and Python 3.10+, since it's written against the newer node API (from comfy_api.latest import io) rather than the old NODE_CLASS_MAPPINGS style.

Where people get burned

There's no style in the output, on purpose. SceneWeaver never mentions lighting, lens, medium or mood, so a bare prompt is drawn as bare content. The maintainer's own graphs prefix every prompt with cinematic film-quality slightly-grainy analog film still. - one line, and the difference between flat and the README's gallery.

Locking beats rules, quietly. A locked field wins over a coherence rule, which is what you asked for - unless you locked condition: derelict and emitters: reactor flare yourself. Those decisions land in prompt_json._meta.warnings.

The seed trap is the usual ComfyUI one. control_after_generate fires after the run, so the seed left in the box isn't the one that made your image. Set "widget control mode" to Before, or set seed's control to fixed first.

Generic labels mean the JavaScript didn't load. The frontend relabels counts per kind (emitter_count is "Engine count" on a vessel, "Eye count" on a creature) and narrows pools live; plain labels mean a stale cache. Hard-refresh.

Custom vocabulary is a file, not a fork. A gitignored user_options.json beside the pack adds creature types, environments, situations. Write ion thruster, not an ion thruster - the engine composes articles and plurals.