> For the complete documentation index, see [llms.txt](https://docs.fullscreen.no/info/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.fullscreen.no/info/game-creator-2-assets/herobridge/instructions/generate-sidekick-part-icons-and-buttons.md).

# Generate Sidekick Part Icons and Buttons

The **Generate Sidekick Part Icons and Buttons** instruction automatically generates preview icons for parts of a specific category on a Sidekick Character and creates corresponding UI buttons. These buttons can be used in menus to select parts, including an optional "None" button for removing parts.

***

#### **Inside the Instruction**

**Part Type**\
Select the category of the part you want to generate previews for.\
There are 38 categories available, such as:

* Head
* Hair
* Torso
* Hips
* Attachments\
  … and more.

**Button Prefab**\
The prefab of the button that will be instantiated for each part.

* Inside this prefab, there should be a child named **Icon**.
* The generated preview for each part will be applied to this icon.

**Empty Button Prefab** *(Optional)*\
If you provide a prefab for an empty button, this will be generated last and used for removing parts (setting the part to none).

* If extra parts are included, the icon inside this button will display them (for example, a bald character if Hair is the main Part Type but Torso and Head are in Extra Parts).
* If this is left empty, no "None" button will be generated.

**Buttons Parent**\
The parent GameObject where all generated buttons will be placed in the hierarchy.

**Center Part Type**\
Select the category of the part to center the camera on for consistent icon previews.

* Example: When generating hair icons, you may want to center on the Head to ensure the hair is positioned correctly in the icon.

**Extra Parts** *(Optional)*\
Add any additional parts to include in the preview icons.

* Useful for adding facial features, body parts, or accessories to make the icon more descriptive.
* Part names must match the catalog format, e.g., `SK_HUMN_BASE_01_01HEAD_HU01`.
* To find part names: use the **Set Part** instruction part's dropdown (Right-click copy and paste) or reference Synty’s Dex.

**Use Matching Parts**\
When enabled, automatically applies symmetrical elements.

* Example: If a left eyebrow is applied, the corresponding right eyebrow will also be applied if available.

**Icon Resolution**\
Sets the resolution of the generated preview icon.

* Lower resolutions generate faster and use less RAM but reduce quality.
* Find a balance depending on icon size in the UI.

**Rotation Offset**\
Apply a rotation to the camera for the preview.

* Allows taking snapshots from the front, side, or back.

**Vertical Offset**\
Move the camera up or down relative to the centered part.

* Helps position parts correctly within the icon frame.

**Horizontal Offset**\
Move the camera left or right relative to the centered part.

**Zoom Modifier**\
Adjust the camera zoom to make parts appear closer or further away in the icon.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.fullscreen.no/info/game-creator-2-assets/herobridge/instructions/generate-sidekick-part-icons-and-buttons.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.