VRP Prompt Combine:
VRPPromptCombine gathers your overall scene description and active regional descriptions into two separate text prompts: one describing what you want and another describing what you want to avoid. It places the overall description first, followed by regional descriptions in their existing order, making it useful when you want to reuse a regional composition as ordinary prompt text for another encoding or refinement step. You can preserve the text with line breaks or normalize its separators into a comma-separated list. Blank text is excluded, and regions with zero weight are skipped. Positive regional weights determine inclusion only; they do not add emphasis or strength notation to the text. This is a text-only utility: it does not generate images, encode text, apply masks, or preserve spatial control in the combined prompt.
VRP Prompt Combine Input Parameters:
formatting
A required selection that determines how the prompt text is joined. The available options are Newline and Commas; the method default is Newline, which is also the first listed option. Newline joins nonblank descriptions with a line break while preserving each description’s existing text, including internal line breaks and spacing. Commas splits descriptions at line breaks and unescaped commas, removes empty fragments, reduces repeated whitespace to a single space, trims each fragment, and joins the results with a comma followed by a space. Escaped literal commas are not treated as separators, and repeated tags and prompt-weight syntax are retained rather than deliberately removed or rewritten. Choose Newline for minimal changes to your wording and Commas when you want more consistent separators. Numeric minimum and maximum values do not apply.
vrp_region
An optional VRP_REGIONS connection supplying the regional descriptions to combine. Connect the Region chain directly, not Core. The node reads each region’s identity, positive text, negative text, and weight, then includes descriptions from regions whose weight is greater than zero, preserving their order in the bundle. Region weights must be finite numbers from 0 to 1 inclusive, but fractional values do not scale the combined text: a region weighted 0.2 contributes its text just as a region weighted 1 does. Every record must have a unique, nonblank text identifier and valid positive and negative strings, including records with zero weight. The default is None, meaning no regional descriptions are added and only the global descriptions are processed. The connection itself has no numeric minimum or maximum; the 0–1 restriction applies to weights inside its records.
global_prompt_positive
An optional STRING connection containing your overall positive scene description, such as the setting, visual style, or lighting shared across the image. Its text is placed before the positive descriptions from active regions. It is configured as a connection-only string input with multiline support, so you supply it from a compatible text source rather than relying on an inline text field on this node. The method default is None, which is treated as an empty string; blank or whitespace-only text contributes nothing to the combined result. No minimum or maximum text length is specified. If you leave this disconnected while supplying active regions, the positive result contains only their nonblank positive descriptions.
global_prompt_negative
An optional STRING connection containing the overall negative description: qualities or content you want to discourage, such as unwanted artifacts or visual traits. Its text is placed before the negative descriptions from active regions, independently of the positive text. Like the positive global description, this is a connection-only string input with multiline support. The method default is None, which is treated as an empty string, and blank or whitespace-only text is omitted. No minimum or maximum text length is specified. Leaving it disconnected does not disable regional negative descriptions; those are still combined when valid active regions are connected.
VRP Prompt Combine Output Parameters:
positive_combined
A STRING containing the global positive description followed by the positive descriptions of all active regions, in their original bundle order, joined using the selected formatting. Blank descriptions are omitted, and regions with zero weight do not contribute text. If no nonblank positive descriptions are available, the result is an empty string. You can pass this text to a compatible text encoder or another text-processing step, including a separate refinement workflow. It contains prompt text only—not encoded conditioning, masks, region coordinates, or automatically applied regional strength values—so combining regional descriptions does not itself keep those descriptions spatially restricted.
negative_combined
A STRING containing the global negative description followed by the negative descriptions of all active regions, in their original bundle order, using the same formatting selection as the positive result. Blank negative descriptions are omitted independently of positive descriptions, so a region can contribute to one result without contributing to the other. If no nonblank negative descriptions are available, the result is an empty string. This text can be passed to a compatible negative-prompt encoder where your workflow supports one. Once combined, regional negatives are ordinary text in a shared negative prompt; this output does not retain region-specific placement or apply regional negative conditioning by itself.
VRP Prompt Combine Usage Tips:
- Connect the Region chain directly to
vrp_region. Do not substitute a Core connection or aVRP_PROMPTSbundle, because this node expects the specificVRP_REGIONSstructure. - Choose
Newlinewhen you want to retain existing prompt spacing, internal line breaks, and punctuation as closely as possible. The node adds a line break between nonblank descriptions without otherwise normalizing their contents. - Choose
Commaswhen your source descriptions mix line breaks, extra spaces, or repeated comma separators. For example, descriptions containing “forest,, mist” and “soft light” are combined as “forest, mist, soft light”. - Set a region’s weight to 0 upstream to exclude both its positive and negative text. Do not lower its weight to a small positive value expecting weaker emphasis: every valid weight greater than zero includes the text without adding a weight modifier.
- Put shared scene information in the global descriptions and subject-specific details in the regional descriptions. This gives the combined text a consistent order: shared context first, then individual regional details.
- Leave
vrp_regiondisconnected when you only need to format your global positive and negative text. You can also leave either global description disconnected when you only want the corresponding regional descriptions. - Review repeated or conflicting phrases before sending the results to an encoder. The node does not remove duplicate tags, reconcile contradictory descriptions, or enforce an encoder’s text-length limits.
- Keep your original regional workflow connected separately if you need spatial control. These combined strings are useful for a separate text-encoding or refinement step, but they do not carry masks or region placement.
VRP Prompt Combine Common Errors and Solutions:
VRP Prompt Combine requires a VRP_REGIONS bundle
- Explanation: The regional connection is not a dictionary containing exactly the top-level fields
versionandregions. A different bundle type, a Core result, or a custom structure with extra top-level fields can trigger this error. - Solution: Connect the Region chain’s compatible
VRP_REGIONSoutput directly. If you only need global text, disconnectvrp_region. If you construct bundles yourself, use exactly the required top-level fields.
Unsupported VRP_REGIONS prompt bundle
- Explanation: The bundle has the expected top-level fields, but its
versionis not the integer 1, orregionsis not a list. A version written as text, such as"1", is not accepted. - Solution: Rebuild the bundle using compatible Region nodes. For custom integrations, supply integer version 1 and a list of region records, and ensure the nodes producing and consuming the bundle use compatible contracts.
Invalid VRP_REGION prompt record
- Explanation: An entry inside the region list is not a dictionary, or its record-level
versionis missing or is not the integer 1. Each region needs its own valid version field in addition to the bundle’s version. - Solution: Recreate the affected region using the Region chain. If you generate records programmatically, ensure every list entry is a dictionary with integer version 1.
Region prompt IDs must be nonempty and unique
- Explanation: A region’s
region_idis missing, is not a string, contains only whitespace, or duplicates another identifier in the bundle. This check also applies to regions with zero weight. - Solution: Give every region a distinct, nonblank text identifier upstream. When combining chains or duplicating region records, ensure their identifiers do not collide.
Region positive/negative prompts must be strings
- Explanation: A regional
positive_promptornegative_promptis missing or contains a value other than text. Both fields must be strings, even if you do not want to supply one of the descriptions. - Solution: Supply text for both regional prompt fields. Use an empty string for an unused positive or negative description instead of a missing field, a number, or
None.
Region prompt weight must be between 0 and 1
- Explanation: A region’s weight is missing, is not an integer or floating-point number, is nonfinite, or falls outside the inclusive range 0–1. Boolean values and numbers supplied as text are also rejected.
- Solution: Set each region’s weight to a valid numeric value such as 0, 0.5, or 1. Use 0 to exclude a region’s text, but remember that its other required fields must still be valid.
Prompt format must be Newline or Commas
- Explanation: The formatting value does not exactly match either supported option. This is most likely when calling the node through code or modifying a workflow outside the normal dropdown interface.
- Solution: Select
NewlineorCommasfrom the dropdown. For programmatic calls, use one of those exact strings, including capitalization.
Prompt inputs must be strings
- Explanation: A value passed to the text-joining step is not a string. In normal node use, this can indicate that a global prompt was supplied as an incompatible value; regional prompt types are checked separately before joining.
- Solution: Connect compatible
STRINGoutputs to the global prompt connections. Convert numbers or other data to text upstream if needed, or leave an unused global connection disconnected so it is treated as empty text.
