# Getting Started

{% embed url="<https://youtu.be/nF23ZduHJ30>" %}

### Importing BloodScreens Pro into Your Unity Project

Getting started with **BloodScreens Pro** is quick and straightforward. To begin, simply import the latest `.unitypackage` into your Unity project.\
\
![](https://3579135912-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F72StjR34vSJ02PW0cVH0%2Fuploads%2FPDMZuIGUv2UfWvPeA0mh%2Fimage.png?alt=media\&token=86a085f1-6af5-4a00-a967-73731f9adf16)

Create an empty BSP Manager or use pre-configured presets directly from the menu for quick setup and instant results.

```
GameObject > IronSami Studio > BloodScreensPro > Presets
```

<figure><img src="https://3579135912-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F72StjR34vSJ02PW0cVH0%2Fuploads%2FE0chDtrOsPr0glletHtc%2Fimage.png?alt=media&#x26;token=dbfe3c50-7a4e-4da1-8790-12c4827a650e" alt=""><figcaption><p>You can select the Empty BSP Manager or a ready preset</p></figcaption></figure>

\
\
Selecting this option will add the **BSP\_Manager** to your scene. This manager includes a built-in **Pooling System** to ensure optimal performance during runtime.

### Quick Testing with the debugger

To quickly test functionality at runtime, enable the **`BSP_Debugger`** object within the **BloodScreens Pro Manager** prefab.&#x20;

<figure><img src="https://3579135912-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F72StjR34vSJ02PW0cVH0%2Fuploads%2FihaBHWxPtWimSCg3IcPh%2Fimage.png?alt=media&#x26;token=e91cec86-de69-45cd-816b-ba6f47150ab9" alt=""><figcaption><p>Activate BSP_Debugger to try out the effects</p></figcaption></figure>

This will activate the built-in test script, allowing you to interact with the manager using keyboard shortcuts:<br>

* Press **X** to show a screen effect.
* Press **I** to start the effect cycle (e.g., low health).
* Press **U** to stop the effect cycle.
* Press **L** to activate manual flash.
* Press **K** to deactivate manual flash.

<figure><img src="https://3579135912-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F72StjR34vSJ02PW0cVH0%2Fuploads%2FOIgEYCo8vWbTDu83r2D2%2Fimage.png?alt=media&#x26;token=b102e860-9026-4233-8acf-327fecd04376" alt=""><figcaption><p>Try out the different effects using X in runtime when debugger is enabled</p></figcaption></figure>

You can also experiment with various settings directly in runtime. For example, disabling the **Procedural Effect** will switch the screen effect to a static mode, allowing you to preview different visual behaviors.
