> 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/2024.1/toolbox/plugins.md).

# Plugins

### Introduction

The **Plugins** **Nodes** appear once a **Logic Plugin** is activated. This process will be described in detail. They allow users to customize their **Logic**.

**Logic Plugins** allow the user to add their own customized **Nodes** to their **Projects**, expanding the capabilities of **Incari**. Below is just one example which ultimately provides one **Node** at the end of the process.

## Example

The example **Logic Plugin** is shipped with **Incari** and includes one **Node**: the [**Scale Vector Node**](/incari-studio/2024.1/toolbox/plugins/jsonscalevector.md). This **Node** appears after a particular process. The user requires access to the *Windows PowerShell* and the folder in which their **Incari Studio** appears, along with all its files. The user will also need to install [*CMake*](https://cmake.org/) and make sure it is added to PATH upon installation.

After clicking on the **Incari Studio** folder, its files should look something like this:

![Incari Studio Folder Example.](/files/CqJI2rxcnQoTLN6iNoYp)

Locate the `PluginExample` folder within the `sdk` folder. If you do not have administrative privileges, copy that to a folder where you have all permissions, such as `Documents`.

This is necessary if the user does not have permission to write to `C:/Program Files`. If the user has administrative rights and can use these when using the *Windows PowerShell* (more on that below), they do not have to copy anything over to `Documents` (or some other folder where they have permissions) and can follow this process in place. Similarly, if **Incari Studio** was installed somewhere that a non-administrative user has rights to, like the `Documents` folder, everything can be done in place as well.

![Locating and Copying the PluginExample Folder.](/files/f24wvRSCO5clV4KiUgls)

Once that is done, open the *Windows PowerShell* and choose the file path pointing to the `PluginExample\build` in `Documents` (or the folder where the files were copied to) as directory. This can be done by using the command `cd <directory>`, where `<directory>` is the location of the `build` folder.

Next, the user must use the following command:

`cmake .. -G "Visual Studio 17 2022" -A x64 -DINCARI_DIR="<file-path>"`

Here, copy everything exactly and replace `<file-path>` with the installation path of **Incari Studio**. This will likely be in the `Program Files` folder on your *Windows* device.

The resulting output of the above command is as follows:

![Output of First CMake Command.](/files/qo8QK0RXH8Srd1JdomP7)

The second crucial command to run is:

`cmake --build . --config Release`

When this command has finished running, the user can check back in the `PluginExample` folder that everything executed properly.

![Checking for output Folder.](/files/kVCgKpfteqyKqkZC11IV)

The contents of the `output` folder (`plugins`) needs to be copied into the installation folder of the user's **Incari Studio**. Please note that elevated rights might be required to do so (depending on the actual installation path).

![Copying the output Folder to the plugins Folder.](/files/FAMzJQMc7D7QYZIn1rbx)

Now it's time to open **Incari Studio**. When it's up and running, the user can check that the **Plugins** and the **Logic Editor** have the new data created during the previous process.

![Logic in Plugins.](/files/xueG9EGbCtyTJ64VEI18)

![New Node in Logic Editor.](/files/FWUSczaMGSTz0xf8K16f)

Following this process, the user will have successfully added the example **Plugin** to **Incari**. This **Plugin** includes the [**Scale Vector Node**](/incari-studio/2024.1/toolbox/plugins/jsonscalevector.md)

### Contents

* [**(JSON) Scale Vector**](/incari-studio/2024.1/toolbox/plugins/jsonscalevector.md)