> 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/conditions/has-part-type.md).
# Has Part Type
The **Has Part Type** condition checks if a character currently has **any part equipped** of a specific **part category**.
This is useful for applying logic based on whether a character has something equipped. For example, determining if they are wearing any kind of **helmet** or **hair piece**.
### Inside the Condition
#### Sidekick Character
The character you want to check.\
Supports both **Game Creator 2** and **non–Game Creator 2 characters**.
#### Part Type
Select the **category** of part to check for.\
There are **38 different categories**, including:
* Head
* Hair
* Torso
* Hips
* Attachments\
…and more.
This condition returns **true** if the character has *any* part equipped in the selected type.
***
### Example Use Case
When equipping a **helmet**, you can use the **Has Part Type** condition to check if the character has any **Hair** parts equipped.\
If true, you can remove the hair part to prevent **clipping through the helmet**.
---
# 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/conditions/has-part-type.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.