> For the complete documentation index, see [llms.txt](https://ss3d.gitbook.io/art-guide/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://ss3d.gitbook.io/art-guide/3d/modeling/formatting/variants.md).

# Variants

Many objects in SS3D will have variants to go with them, such as light bulbs and their broken counterparts, or different stages of construction, crafting, or consumption.

![](https://lh5.googleusercontent.com/6VPdq7Fdu9esszryzoZhQdxiTYuCAt8R_4E_D7tdz8mYIWVlwvU5LQUksnH7fcpZhHFXiAjolZvocjYZY54Qf1v0EfgF-k-WUobbanqG5XUcGXAR_XFAE0FJMnO-APy9NEuYlry7xIit5DqgDDaBPA)

For a clean in-game transition from one variant to the next, it is important that all variants of an item have their origins in the same exact relative location.&#x20;

And while all variants of an item can technically be saved as different files, it is best that all variants of the same item are stored within the same .FBX file to decrease clutter within folders.&#x20;

When opening the .FBX files, the multiple objects can be distinguished within Unity.


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://ss3d.gitbook.io/art-guide/3d/modeling/formatting/variants.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.
