> 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/standalone-assets/herobridge-standalone/components/sidekick-save-load-applier.md).
# Sidekick Save Load Applier
The **Sidekick Save Load Applier** allows you to save and restore a Sidekick character’s appearance. This can be used when saving a game, switching scenes, or reapplying a character setup at runtime.
Add the **Sidekick Save Load Applier** component to a GameObject.
**Target**\
The Sidekick character whose appearance will be saved or loaded.
**Apply Mode** defines when the component runs:
* **On Enable** - Runs automatically when the GameObject is enabled
* **On Disable** - Runs when the GameObject is disabled
* **On Invoke** - Runs when triggered via code or events
* **On Button Press** - Runs when a Unity UI Button on the same GameObject is pressed
**Action**
* **Save** - Saves the current character parts, blendshapes and colors.
* **Load** - Loads a previously saved character parts, blendshapes and colors.
**Save Slot**\
Defines which save slot is used for saving or loading character data.
The **GameObject name** of the target character is used as the unique identifier when saving and loading. This allows multiple characters to be stored in the same save slot, as long as each character has a unique GameObject name.
When loading, the character GameObject name must match the name used during saving. Using consistent and unique names ensures that parts, colors, and blendshapes are correctly restored per character.
---
# 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/standalone-assets/herobridge-standalone/components/sidekick-save-load-applier.md?ask=&goal=
```
`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.