H3 Character Sheet Designer v1.2.2:
H3CharacterSheetDesignerReference13 prepares the instructions and optional visual layout guidance for an H3 character-sheet workflow using a 13-view design. It helps you organize a sheet around an existing character and use additional images of that same character to provide more visual context. Its main job is preparation rather than image generation: it translates a saved design configuration into generation instructions and sheet dimensions, and can create a layout guide to help communicate the intended arrangement to the downstream H3 generation workflow. This separates sheet planning from rendering, making it easier to maintain a consistent reference setup while adjusting the design. It prepares one sheet per execution, not a batch of individually generated views. The supplied implementation identifies this as version 1.2.2 and marks it as deprecated, so it is especially relevant when maintaining an existing workflow that already uses this node.
H3 Character Sheet Designer v1.2.2 Input Parameters:
state_json
A required STRING containing the character-sheet design configuration in JSON format. The node processes this configuration to prepare the generation prompt, determine the sheet width and height, and obtain the layout information needed when a guide is enabled. Treat this as structured design data rather than an ordinary text prompt: its contents must follow the format expected by the character-sheet designer. The field supports multiple lines and has dynamic prompt processing disabled, so its text is not configured for dynamic-prompt expansion. Its default is the package-provided DEFAULT_STATE_JSON; the supplied source does not show that constant’s contents, the supported JSON fields, or their individual ranges. No minimum or maximum string length is declared. Configuration validation uses the runtime maximum resolution, but the numerical limit is not shown in the provided code.
character_image
A required IMAGE providing the main character reference for the sheet. Use this to establish the character whose appearance you want the downstream generation workflow to follow. The node validates that a required reference image is present and acceptable, then passes that same image through without modifying it. This node does not analyze the image into a separate text description in the supplied implementation. Connect it from an image-producing node, such as an image loader, and route its corresponding output to H3’s first reference slot. No default image, minimum dimensions, maximum dimensions, or other image limits are declared in this class; the detailed checks performed by the image-validation helper are not included in the supplied context.
reference_image_1
An optional IMAGE supplying an additional reference of the same character. For example, you can use another angle or a clearer image of an important character detail to give the downstream model more visual context. When connected, it is validated, its presence is included when preparing the sheet instructions, and the original image is passed through unchanged. When omitted, its execution default is None, and the node accounts for its absence when assigning picture numbers in the instructions. There are no numerical minimum or maximum values, and no image-size limits are declared in this class. This reference is intended for H3’s ref_images.ref_image_2 slot.
reference_image_2
An optional IMAGE providing another same-character reference. It allows you to supplement the main image and first optional reference with additional visual evidence, such as a different view of clothing or character features. The node validates the connected image, records whether it is present when compiling the instructions, and returns it unchanged for downstream use. Its execution default is None, so you do not need to supply it when the existing references are sufficient. No minimum or maximum image dimensions are specified in this class. This reference is intended for H3’s ref_images.ref_image_3 slot.
reference_image_3
An optional IMAGE providing a third additional reference of the same character, allowing four character images in total when combined with the required main image. Like the other optional references, it is checked before processing, considered when preparing reference-picture numbering, and passed through without modification. Its execution default is None, and leaving it unconnected is supported. No numerical bounds or image-size limits are declared in this class. This reference is intended for H3’s ref_images.ref_image_4 slot; use a supporting image that adds useful information rather than introducing a conflicting character design.
use_layout_image
An optional BOOLEAN that controls whether the node creates a visual guide for the sheet arrangement. Its available values are False and True, with a default of False. When True, the node renders a guide from the compiled layout information and converts it into an IMAGE suitable for connection to the downstream H3 reference inputs. When False, the node does not render the guide and returns None for the layout image rather than a blank placeholder. This setting is also supplied to the configuration compiler, so it participates in preparing the sheet instructions. Enable it when you want to provide explicit visual layout guidance, while remembering that a guide is not a guarantee that the downstream model will reproduce the arrangement precisely.
style
An optional COMBO[STRING] that selects a style setting to use when preparing the sheet instructions. The default is none, and the available choices are taken from the keys of the package’s STYLE_PROMPTS collection. The supplied context does not include that collection, so the complete option list and the exact wording associated with each style cannot be documented here. Select from the choices offered by the node rather than entering an assumed style name. The selected value is used during both configuration validation and prompt compilation; it does not directly transform the supplied reference images, which are returned unchanged. Numerical minimum and maximum values do not apply.
H3 Character Sheet Designer v1.2.2 Output Parameters:
prompt
A STRING containing the compiled instructions for generating the character sheet. It is prepared from the design configuration, selected style, layout-guide setting, and the presence or absence of the optional character references. The node’s description specifies that picture numbers skip missing images, helping the instructions refer to the reference images actually supplied. Connect this text to the prompt input of your downstream H3 generation workflow. It is generation guidance, not a finished image or a guarantee of exact visual compliance.
width
An INT specifying the sheet width produced by configuration compilation. Use it as the width setting in the downstream generation workflow so the image size agrees with the prepared sheet design. This is the intended sheet width, not a measurement taken from the main character reference image. The supplied code does not expose a fixed default or numerical range; resolution validation is delegated to the configuration compiler using the runtime maximum resolution.
height
An INT specifying the sheet height produced by configuration compilation. Connect it to the downstream generation height setting alongside width to preserve the intended sheet proportions. It describes the planned sheet size rather than the height of any supplied reference image. As with width, the exact default and allowed numerical bounds are not shown in the supplied class, and the configuration is checked against the runtime resolution limit.
layout_image
An IMAGE containing the rendered sheet-layout guide when use_layout_image is True. The guide is created from the compiled geometry and semantic layout, then converted into a single-image batch with pixel values normalized to the 0–1 range. Connect it to H3’s ref_images.ref_image_1 slot to provide visual arrangement guidance. When layout guidance is disabled, this output is None despite the socket being declared as IMAGE, so the downstream reference handling must support an absent image. This output is a planning guide, not the generated character sheet.
character_image
The same IMAGE supplied as the required main character reference, returned without modification. Passing it through this node lets you keep the prepared instructions, layout guide, and reference connections organized together. Connect it to H3’s ref_images.ref_image_0 slot. It remains a source reference for downstream generation and is not a newly generated or restyled image.
reference_image_1
The unchanged first optional same-character reference IMAGE, or None if you did not provide one. Connect it to H3’s ref_images.ref_image_2 slot. Its purpose is to carry your supporting character reference into the generation workflow while keeping the image connections consistent with the compiled instructions.
reference_image_2
The unchanged second optional same-character reference IMAGE, or None when that input is absent. Connect it to H3’s ref_images.ref_image_3 slot. Like the other reference outputs, it contains no generated artwork or image adjustments; it preserves the reference you supplied for downstream interpretation.
reference_image_3
The unchanged third optional same-character reference IMAGE, or None when it is not connected. Connect it to H3’s ref_images.ref_image_4 slot. This provides the final additional character-reference connection supported by this node and should remain in the documented slot order so that the supplied images agree with the prepared reference instructions.
H3 Character Sheet Designer v1.2.2 Usage Tips:
- Start with the package’s default design configuration or a valid configuration produced by the designer interface. The supported JSON schema is not included in the supplied source, so avoid inventing field names or replacing the configuration with a plain-language prompt.
- Follow the documented H3 reference wiring:
character_imagetoref_images.ref_image_0,layout_imagetoref_images.ref_image_1, andreference_image_1,reference_image_2, andreference_image_3to slots 2, 3, and 4 respectively. Picture numbering in the instructions skips absent images; this does not mean you should manually rearrange the documented socket connections. - Connect both
widthandheightto the downstream generation settings. This helps prevent the rendered sheet’s proportions from disagreeing with the compiled design. - Set
use_layout_imagetoTruewhen arrangement guidance is important, and connect the resulting guide to the designated H3 slot. Leave itFalsewhen you do not want a guide; this avoids rendering one, but requires downstream handling that acceptsNone. - Choose additional references that show the same character consistently. Different angles or clearer details can be useful, while contradictory outfits, proportions, or identities can make the downstream result harder to control.
- Begin with
styleset tononewhen checking the basic configuration and reference wiring. After confirming that the workflow works, try the available style choices to evaluate their effect on the generated sheet. - Plan for one sheet per execution. This class has no
batch_outinput, filename-suffix output, or list-output declaration; do not apply the batching instructions supplied for other similarly named nodes. - Note the deprecated status when sharing or updating workflows. A separate
H3CharacterSheetDesignerReferenceV13class appears in the supplied context, but check its behavior and compatibility before replacing this older node.
H3 Character Sheet Designer v1.2.2 Common Errors and Solutions:
StateValidationError during configuration compilation
- Explanation: The node catches
StateValidationErrorduring input validation and returns the exception’s text as the validation message. This indicates that the configuration or a related compilation setting was rejected. The exact message strings and validation rules are not included in the supplied helper code. - Solution: Read the specific message shown in ComfyUI, restore a known-working configuration, and reapply changes gradually. Use the designer’s supported controls or configuration format rather than guessing JSON fields.
Invalid JSON or unsupported state configuration — descriptive label
- Explanation:
state_jsonis processed as a structured design configuration, not as a normal prompt. Malformed JSON or content that does not match the expected state format can prevent compilation; the exact error wording is not available in the supplied source. - Solution: Restore the package default or re-export a valid design state. If editing manually, check quotation marks, commas, and brackets, and avoid removing required configuration fields.
Required character image missing or rejected — descriptive label
- Explanation:
character_imageis mandatory and is explicitly validated with the required flag enabled. A missing image or an image value rejected by the validation helper prevents successful execution. The helper’s exact error strings and acceptance rules are not shown. - Solution: Connect a valid IMAGE output from an image loader or another image-producing node. Confirm that the upstream node successfully loads or produces the image rather than supplying text, a file path, or an empty result.
Optional reference image rejected — descriptive label
- Explanation: Each optional reference is validated when supplied. An incompatible value can therefore stop execution even though that reference is not required; exact validation messages are not provided in the available code.
- Solution: Disconnect the optional reference and test again. If the node then works, reload or replace that reference with a valid IMAGE output before reconnecting it.
Resolution rejected during state validation — descriptive label
- Explanation: Configuration compilation receives the runtime maximum resolution, so a sheet size outside the supported limits can cause validation to fail. The numerical limits and exact error text are not visible in the supplied class.
- Solution: Reduce the sheet dimensions using the supported design controls, or return to a known-working size. Use the actual validation message to identify the applicable limit rather than assuming a fixed maximum.
Downstream node rejects a missing layout or reference image — descriptive label
- Explanation: Disabling
use_layout_imageintentionally producesNoneforlayout_image, and unconnected optional references also returnNone. A downstream node that requires an image in every connected socket may reject these values; that failure occurs downstream rather than necessarily inside this designer. - Solution: Use H3 reference handling that supports absent images. Enable the layout guide if you need an actual guide image, and avoid sending absent optional references to inputs that require a real image.
Reference images do not match the prompt’s picture references — workflow symptom
- Explanation: The compiled instructions account for missing optional references, while the documented wiring assigns each output to a specific H3 slot. Reordering references or using a different set of images downstream can make the instructions and image sequence disagree without producing a validation error.
- Solution: Restore the documented slot mapping and pass through the same reference images used during compilation. Check the main character, guide, and all three optional reference connections together.
Generated sheet does not follow the layout precisely — workflow symptom
- Explanation: This node prepares instructions and an optional visual guide; it does not render the final character sheet or enforce the downstream model’s geometry. A successful execution therefore does not guarantee precise placement in the generated image.
- Solution: Confirm that layout guidance is enabled and connected, use the compiled width and height, and check that the downstream workflow receives the compiled prompt. If the arrangement is still unsuitable, adjust the design and regenerate rather than treating the guide as a strict placement constraint.
