> For the complete documentation index, see [llms.txt](https://docs.incari.com/incari-studio/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.incari.com/incari-studio/2023.2/toolbox/incari/object2d/getpaint.md).

# Get Paint

## Get Paint

This **Node** has different versions based on whether `Color` or `Image` is chosen in the **Attributes**.

{% tabs %}
{% tab title="Color" %}

### Overview

![The Get Paint Node with Fill Target and Color Paint Type.](/files/sd93GsLlkFYHrP5TCxx2)

The **Get Paint Node** returns the value of the fill or stroke's `Paint Type` selected in the **Attributes**.

[**Scope**](/incari-studio/2023.2/toolbox/overview.md#scopes): **Scene**, **Function**, **Prefab**.

### Attributes

![The Get Paint Node with Fill Target and Color Paint Type Attributes.](/files/ga2Z2H14UPgzZFOuMjth)

| Attribute    | Type         | Description                                                                                                                                                                              |
| ------------ | ------------ | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| `Target`     | **Dropdown** | Can be either `Fill` or `Stroke`. In the image above, `Fill` has been chosen.                                                                                                            |
| `Index`      | **Int**      | Determines the layer of the paint content, if one is not provided in the **Input Socket**. It works in a top to bottom way, where 0 is the top layer and increasing layers are below it. |
| `Paint Type` | **Dropdown** | The type of content that was used on the inputted **Object**. The choices are `Color`or `Image`. In this case, `Color` has been chosen.                                                  |

### Inputs

| Input             | Type         | Description                                                                                                    |
| ----------------- | ------------ | -------------------------------------------------------------------------------------------------------------- |
| *Pulse Input* (►) | **Pulse**    | A standard **Input Pulse**, to trigger the execution of the **Node**.                                          |
| `Object ID`       | **ObjectID** | The ID of the **Object** that will have its fill or stroke returned (depending on the `Target` **Attribute**). |
| `Index`           | **Int**      | The index of the fill or stroke’s layer.                                                                       |

### Outputs

| Output             | Type      | Description                                                                                                                            |
| ------------------ | --------- | -------------------------------------------------------------------------------------------------------------------------------------- |
| *Pulse Output* (►) | **Pulse** | A standard **Output Pulse**, to move onto the next **Node** along the **Logic Branch**, once this **Node** has finished its execution. |
| `Color`            | **Color** | The returned color of the chosen **Object's** fill or stroke.                                                                          |
| {% endtab %}       |           |                                                                                                                                        |

{% tab title="Image" %}

### Overview

![The Get Paint Node with Fill Target and Image Paint Type.](/files/DSRirUArwfzwHeRNSAjU)

The **Get Paint Node** returns the value of the fill or stroke's `Paint Type` selected in the **Attributes**.

[**Scope**](/incari-studio/2023.2/toolbox/overview.md#scopes): **Scene**, **Function**, **Prefab**.

### Attributes

![The Get Paint Node with Fill Target and Image Paint Type Attributes.](/files/2mjDfJz7AJ1TzK5TeRsC)

| Attribute    | Type         | Description                                                                                                                                                                              |
| ------------ | ------------ | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| `Target`     | **Dropdown** | Can be either `Fill` or `Stroke`. In the image above, `Fill` has been chosen.                                                                                                            |
| `Index`      | **Int**      | Determines the layer of the paint content, if one is not provided in the **Input Socket**. It works in a top to bottom way, where 0 is the top layer and increasing layers are below it. |
| `Paint Type` | **Dropdown** | The type of content that was used on the inputted **Object**. The choices are `Color`or `Image`. In this case, `Image` has been chosen.                                                  |

### Inputs

| Input             | Type         | Description                                                                                                    |
| ----------------- | ------------ | -------------------------------------------------------------------------------------------------------------- |
| *Pulse Input* (►) | **Pulse**    | A standard **Input Pulse**, to trigger the execution of the **Node**.                                          |
| `Object ID`       | **ObjectID** | The ID of the **Object** that will have its fill or stroke returned (depending on the `Target` **Attribute**). |
| `Index`           | **Int**      | The index of the fill or stroke’s layer.                                                                       |

### Outputs

| Output             | Type          | Description                                                                                                                            |
| ------------------ | ------------- | -------------------------------------------------------------------------------------------------------------------------------------- |
| *Pulse Output* (►) | **Pulse**     | A standard **Output Pulse**, to move onto the next **Node** along the **Logic Branch**, once this **Node** has finished its execution. |
| `Texture ID`       | **TextureID** | The ID of the returned image of the chosen **Object's** fill or stroke.                                                                |
| {% endtab %}       |               |                                                                                                                                        |
| {% endtabs %}      |               |                                                                                                                                        |

## See Also

* [**Set Paint**](/incari-studio/2023.2/toolbox/incari/object2d/setpaint.md)


---

# 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.incari.com/incari-studio/2023.2/toolbox/incari/object2d/getpaint.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.