Save 4 hours! We auto-setup your workflow! Free!

Drop your workflow.json — we handle every dependency, custom node, and model. Just open the link and run.

Auto-Setup Workflow Json (Free) Now!
ComfyUI > Nodes > MOSS-Image Character Sheet Designer > _MOSSComposeScopedSheet

ComfyUI Node: _MOSSComposeScopedSheet

Class Name

_MOSSComposeScopedSheet

Category
_internal/MOSS-Image
Author
ukr8b3g-cmyk (Account age: 400days)
Extension
MOSS-Image Character Sheet Designer
Latest Updated
2026-11-01
Github Stars
0.01K

How to Install MOSS-Image Character Sheet Designer

Install this extension via the ComfyUI Manager by searching for MOSS-Image Character Sheet Designer
  • 1. Click the Manager button in the main menu
  • 2. Select Custom Nodes Manager button
  • 3. Enter MOSS-Image Character Sheet Designer in the search bar
After installation, click the Restart button to restart ComfyUI. Then, manually refresh your browser to clear the cache and access the updated list of nodes.

Visit ComfyUI Online for ready-to-use ComfyUI environment

  • Free trial available
  • 16GB VRAM to 80GB VRAM GPU machines
  • 400+ preloaded models/nodes
  • Freedom to upload custom models/nodes
  • 200+ ready-to-run workflows
  • 100% private workspace with up to 200GB storage
  • Dedicated Support

Run ComfyUI Online

_MOSSComposeScopedSheet Description

Composes view-specific character sheet prompts and canvas dimensions from validated JSON inputs.

_MOSSComposeScopedSheet:

_MOSSComposeScopedSheet composes a character reference-sheet prompt from a validated sheet specification and a set of appearance descriptions. It plans the arrangement and canvas size, then adapts the wording to the selected views. For example, a sheet made entirely of face views receives a close-up portrait summary, while a clothing-only sheet is described as laid-flat garments or blank space when no garment is specified. This helps you produce a prompt whose composition and descriptive details agree. The node is marked deprecated and is categorized under _internal/MOSS-Image, so treat it as an existing-workflow component rather than assuming it is the preferred choice for a new workflow.

_MOSSComposeScopedSheet Input Parameters:

state_json

A required STRING containing the complete sheet state as JSON. It controls which views appear, the character identity, optional per-part and per-view descriptions, appearance choices, style, background, prompt format, negative prompt, and canvas sizing. The parser checks the state’s schema and permitted values before the sheet is composed; it also puts selected views into its defined order rather than retaining an arbitrary input order. The supplied source requires schema_version to be the integer 1 and at least one unique, recognized view. Appearance options are hand_state: auto, bare, or gloved; clothing_type: auto, pants, or skirt_robe; and footwear_state: auto, shod, or unshod. Size mode is auto or manual; pixel_budget must be one of 1000000, 1500000, 2000000, or 4000000. Each of body_height, manual_width, and manual_height must be a multiple of 16 from 256 through the smaller of 16384 and the runtime resolution limit. prompt_format accepts auto, caption, or layout_json; in automatic mode, the preview chooses caption for one view and layout_json for multiple views. The complete state has a 65,536-byte UTF-8 limit. No default value for the state_json input, complete JSON template, or full set of view, style, and background options is established by the supplied source, so use a state generated by a compatible upstream component rather than constructing missing schema fields by guesswork.

features_json

A required STRING containing JSON appearance-analysis features. These descriptions refine the composed prompt: head details can describe face views, outfit details can describe clothing views, and hands and feet details can describe their corresponding views. A shared description can also supply style wording when the selected style has no predefined wording. The node validates this text against an expected set of feature fields, trims each accepted value, and limits each field to 1,500 characters; the raw text is checked against a 12,000-character limit. Clothing-only sheets can become a blank-background description when no outfit description or explicit garment is present. The supplied source does not show the contents of the required FIELDS set or a default value, so it does not support publishing a complete feature JSON template or claiming particular field names are optional. Supply features from the matching appearance-analysis stage.

_MOSSComposeScopedSheet Output Parameters:

string

The composed prompt as a STRING. It combines the planned sheet layout with the descriptions relevant to each selected view and renders the result in the state’s resolved prompt format. This is the value to pass to a downstream step that accepts the compiled prompt. Although the node also prepares status information for its interface, that status is not an additional output socket.

int (output 2)

The planned canvas width as an INT, measured in pixels. It is the first dimension of the sheet layout calculated from the state’s size settings. Use it as the width when configuring a downstream image-generation step so that the generated canvas matches the planned composition.

int (output 3)

The planned canvas height as an INT, measured in pixels. It is the second dimension of the calculated sheet layout. Use it with int (output 2) so that downstream image dimensions match the prompt’s planned arrangement.

_MOSSComposeScopedSheet Usage Tips:

  • Start with a complete state from the compatible upstream workflow. Set a nonblank character identity before compiling; the preview identifies an empty identity as E_IDENTITY_EMPTY, and this node continues into composition without checking that the preview is ready.
  • Choose only the views you need. A face-only selection receives a close-up portrait summary, while a clothing-only selection uses laid-flat garment wording when an outfit or explicit garment is supplied.
  • For a clothing-only sheet, provide an outfit description or explicitly specify garments when you want clothing depicted. Otherwise, the composition can describe blank background space.
  • Use size.mode set to auto when you do not need exact canvas dimensions. For manual sizing, keep width and height within the supported range and divisible by 16; the preview flags manual canvases above 4,000,000 pixels and unusually wide or tall aspect ratios as warnings.
  • Match prompt_format to the next step: auto resolves to caption for one view and layout_json for multiple views. Connect both integer outputs to the corresponding downstream width and height settings.

_MOSSComposeScopedSheet Common Errors and Solutions:

E_TYPE

  • Explanation: A supplied value has the wrong type. For example, state_json must be text containing a JSON object, views must be a list, and the checked size values must be integers rather than quoted numbers.
  • Solution: Check the reported field, provide valid JSON, and use the required value type. Write numeric sizes as numbers and schema_version as the integer 1.

E_UNICODE

  • Explanation: The state text cannot be encoded as valid UTF-8, so its byte length cannot be checked.
  • Solution: Remove malformed characters from state_json and export or regenerate the text as valid Unicode.

E_STATE_SIZE

  • Explanation: state_json exceeds its 65,536-byte UTF-8 limit.
  • Solution: Shorten unnecessary descriptions and remove redundant content while preserving the required state fields.

E_SCHEMA

  • Explanation: The state’s kind does not match the expected kind, or schema_version is not the integer 1.
  • Solution: Generate the state with a compatible upstream component and ensure its schema version is 1. The expected kind value is not included in the supplied source, so do not guess it.

E_VIEWS_EMPTY

  • Explanation: The views list is empty, leaving nothing to arrange on the sheet.
  • Solution: Select at least one supported view in the upstream state.

E_VIEWS_DUPLICATE

  • Explanation: The same view appears more than once in views.
  • Solution: Keep each selected view only once. Use the available distinct views for the perspectives you need.

E_ENUM

  • Explanation: A field contains a value outside its permitted options. This can affect a view, appearance choice, size mode, pixel budget, prompt format, style, or background.
  • Solution: Check the reported field and choose a supported value. For example, pixel_budget accepts only 1000000, 1500000, 2000000, or 4000000; prompt_format accepts auto, caption, or layout_json.

E_SIZE_RANGE

  • Explanation: body_height, manual_width, or manual_height is outside the supported range of 256 through the smaller of 16384 and the runtime resolution limit.
  • Solution: Set the reported size within that range, accounting for any lower limit imposed by your runtime.

E_SIZE_STEP

  • Explanation: A checked size is not a multiple of 16. - Solution: Change it to a nearby valid value, such as 1024 instead of 1025.

E_IDENTITY_EMPTY

  • Explanation: The preview marks an empty or whitespace-only character.identity as a blocking error. Because this node proceeds to feature composition after previewing, the failure you see during execution may instead refer to missing compiled layout data.
  • Solution: Add a meaningful, nonblank character identity to state_json before running the node again.

Invalid JSON or unexpected fields

  • Explanation: The supplied source validates both JSON inputs and checks their fields, but it does not provide the exact error codes or messages for every JSON or field-validation failure.
  • Solution: Confirm that both inputs contain valid JSON, use a complete compatible state and feature object, and remove unsupported fields. Use the reported field path, when available, to locate the problem.

dense_layout, many_views, high_resolution, or extreme_aspect_ratio

  • Explanation: These are preview warning codes, not documented fatal errors. They indicate, respectively, a low layout-density score, eight or more views, a manual canvas above 4,000,000 pixels, or a manual width-to-height ratio outside 0.45 through 2.5.
  • Solution: If the resulting sheet is hard to read or costly to generate, reduce the number of views, choose automatic sizing, lower manual dimensions, or use a less extreme canvas shape.

_MOSSComposeScopedSheet Related Nodes

Go back to the extension to check out more related nodes.
MOSS-Image Character Sheet Designer
RunComfy
Copyright 2025 RunComfy. All Rights Reserved.

RunComfy is the premier ComfyUI platform, offering ComfyUI online environment and services, along with ComfyUI workflows featuring stunning visuals. RunComfy also provides AI Models, enabling artists to harness the latest AI tools to create incredible art.

_MOSSComposeScopedSheet