> 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/2022.2/toolbox/array/remove-array-element.md).

# Remove Array Element

## Overview

![The Remove Array Element Node.](/files/Bqsde3qtNlWCqZQ6lmry)

The **Remove Array Element Node** deletes the element(s) of an **Array** at the specified index/indices.

For example, an **Array** is populated as follows: $$\[0,3,6,9,12]$$. If the *indices* $$1$$ and $$3$$ are given, the elements at those indices are deleted and the user is left with a new **Array**: $$\[0,6,12]$$.

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

## Attributes

![The Remove Array Element Node Attributes.](/files/l9oVgbBb4ZHytDgjbOJ9)

| Attribute   | Type          | Description                                                                                             |
| ----------- | ------------- | ------------------------------------------------------------------------------------------------------- |
| `Index [n]` | **Drop-down** | The index, or indices, of the element(s) to be removed, if one is not provided in the **Input Socket**. |

## Inputs

| Input             | Type      | Description                                                                                                |
| ----------------- | --------- | ---------------------------------------------------------------------------------------------------------- |
| *Pulse Input* (►) | **Pulse** | A standard **Input Pulse**, to trigger the execution of the **Node**.                                      |
| `Array`           | **Array** | The **Array** whose element(s) will be removed.                                                            |
| `Index (i)[n]`    | **Int**   | The index `i` where the element will be removed. `n` determines the number of **Input Sockets** available. |

## 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. |
| `Array`            | **Array** | The **Array** without the element(s) that were specified to be removed.                                                                |

## See Also

* [**Insert Array Element**](/incari-studio/2022.2/toolbox/array/insert-array-element.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/2022.2/toolbox/array/remove-array-element.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.