> For the complete documentation index, see [llms.txt](https://visualonecompany.gitbook.io/storyframeworkdocs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://visualonecompany.gitbook.io/storyframeworkdocs/core-components/cinematic-tooling/skill-checks-qtes.md).

# Skill Checks / QTE's

Out-of-the-box, SF includes 3 different types of Skill Checks that are generally designed to be used within sequencer but can also be used outside of sequencer. These are; `Simple Key Reaction`, `Timed Circular`, and `Timed Heartbeat`.

<figure><img src="https://2310584459-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FuiMQl6UzBr8OnuaoaiWO%2Fuploads%2FFTMcSiJFael9Uc6vX9qG%2FQTE's.png?alt=media&amp;token=ab4eb32e-4387-47e2-9b5b-1a226c5ca370" alt=""><figcaption></figcaption></figure>

All 3 types of Skill Checks have configurable difficulties values.

***

To create a new Skill Check, find (can be found in the SF editor drop-down towards the top of your editor) and open the `SkillCheckVault_DT` . This data table will hold any and all Skill Checks used throughout your project, all in one location for easier modification and reusability.\
\
Once that data table is opened, hit the "Add" button towards the top.

<div align="left"><figure><img src="https://2310584459-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FuiMQl6UzBr8OnuaoaiWO%2Fuploads%2Fl7afkMKdNCs6gVLEtIp0%2Fimage.png?alt=media&amp;token=987d2ff4-5ec4-4406-a3cf-b15ad6e96bc6" alt=""><figcaption></figcaption></figure></div>

Once a new Row appears, give your new Skill Check a unique Row Name and optionally, a unique `Skill Check ID` value.

<figure><img src="https://2310584459-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FuiMQl6UzBr8OnuaoaiWO%2Fuploads%2FMySzKaxeqdRZKzwC61i4%2Fimage.png?alt=media&amp;token=7c90dfb6-0ab4-432e-9f63-313689d92950" alt=""><figcaption></figcaption></figure>

Just below the skill check ID, you'll find a `Skill Check Data` field. This is where you will choose what type of skill check this row will be. Each skill check has its own set of data (hence the use of an instanced struct for the variable type). To find compatible structures, search for any structure ending in "Skill Check".

<div align="left"><figure><img src="https://2310584459-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FuiMQl6UzBr8OnuaoaiWO%2Fuploads%2FNC8L34KPLRj4VcBSkrI6%2Fimage.png?alt=media&amp;token=b93b57d9-f545-4823-8e2e-8992a975a3fa" alt=""><figcaption></figcaption></figure></div>

Descriptions covering individual skill check settings can be found below.

{% tabs %}
{% tab title="Simple Key Reaction" %}

<div align="left"><figure><img src="https://2310584459-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FuiMQl6UzBr8OnuaoaiWO%2Fuploads%2F5Pc4kDKX9NAygCTwTelD%2Fimage.png?alt=media&amp;token=bfd1bd8c-6747-4c0b-a0ce-c175b24d972f" alt=""><figcaption></figcaption></figure></div>

**Shrink Speed (Min & Max)**\ <sup><mark style="color:$info;">Define a min and max range for the speed at which the shrinking "press" indicator shrinks (a random speed is chosen within the defined range)<mark style="color:$info;"></sup>\
**Cycle Target Inputs**\ <sup><mark style="color:$info;">Enabling this option will present a chance to randomize the required input key for the Skill Check upon each successful press (Be default, the required input key is \[E]. With this option enabled, input keys will cycle between \[E], \[F], \[Q]. and \[C]).<mark style="color:$info;"></sup>
{% endtab %}

{% tab title="Timed Circular" %}

<figure><img src="https://2310584459-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FuiMQl6UzBr8OnuaoaiWO%2Fuploads%2FRZbMrZe2ZEDTvtE1Hiph%2Fimage.png?alt=media&amp;token=84d0b436-c595-4a06-9489-42f3f869e419" alt=""><figcaption></figcaption></figure>

**Rotation Speed**\ <sup><mark style="color:$info;">Determines the speed at which the small "press" indicator spins around the Skill Check circle (Recommended to keep this within the range of 50,0 - 325,0)<mark style="color:$info;"></sup>\
**Skill Check Scale**\ <sup><mark style="color:$info;">Determines the size of the segment that the small "press" indicator needs to land within to count an input press as "successfull" (Recommended to keep this within the range of 0.03 - 0.25)<mark style="color:$info;"></sup>\
**Cycle Target Inputs**\ <sup><mark style="color:$info;">Enabling this option will present a chance to randomize the required input key for the Skill Check upon each successful press (Be default, the required input key is \[E]. With this option enabled, input keys will cycle between \[E], \[F], \[Q]. and \[C]).<mark style="color:$info;"></sup>
{% endtab %}

{% tab title="Timed Heartbeat" %}

<figure><img src="https://2310584459-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FuiMQl6UzBr8OnuaoaiWO%2Fuploads%2FiX0RIU79H6e3nl06ZPWI%2Fimage.png?alt=media&amp;token=25e82d46-b2a3-4917-80c6-b011dae9bebb" alt=""><figcaption></figcaption></figure>

**Heartbeat Interval Sizes**\ <sup><mark style="color:$info;">Heartbeats are grouped into pairs of 2. This value determines the size of the gap between each pair (Recommended to keep this within the range of 150,0 - 1000,0).<mark style="color:$info;"></sup>\
**Heartbeat Speed**\ <sup><mark style="color:$info;">Determines the speed at which the Heartbeat pairs move across the screen (Recommended to keep this within the range of 100,0 - 425,0).<mark style="color:$info;"></sup>\
**Cycle Target Inputs**\ <sup><mark style="color:$info;">Enabling this option will present a chance to randomize the required input key for the Skill Check upon each successful press (Be default, the required input key is \[E]. With this option enabled, input keys will cycle between \[E], \[F], \[Q]. and \[C]).<mark style="color:$info;"></sup>
{% endtab %}
{% endtabs %}

Completing or failing a Skill Check starts by understanding how SF structures completion or failure. All Skill Checks are setup to be required to "complete" multiple times. Let's take the "Timed Circular" Skill Check as an example;\
\
This skill check contains a small "pin" like line that spins in a circle and requires the player to press the target input key when it is inside of a white colored zone / segment. This is classified as a "Correct Attempt".  If they press that same input key outside of the white colored zone / segment, then that counts as a "Failed Attempt".\
\
Setting the requirements that determine whether a Skill Check is completed or failed is done by configuring the `Min Num of Correct Attempts` & `Max Num of Failed Attempts` values.\
\
**Min Num of Correct Attempts**\ <sup><mark style="color:$info;">Minimum amount of "Correct Attempts" or input presses made by the player to classify the Skill Check as "successfull" when it finishes.<mark style="color:$info;"></sup>\
**Max Num of Failed Attempts**\ <sup><mark style="color:$info;">Maximum amount of "Failed Attempts" or input presses made by the player, at which point the Skill Check will immediately stop and produce a "Failed" result. Some Skill Checks might be more challenging then others. Defining a maximum number higher than 1 gives players more chances to continue with the Skill Check and "complete" it.<mark style="color:$info;"></sup>

<figure><img src="https://2310584459-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FuiMQl6UzBr8OnuaoaiWO%2Fuploads%2F5DaJ1zNtlFTvIQQBvtCc%2Fimage.png?alt=media&amp;token=465c89fd-e462-4874-8837-999ab9be4665" alt=""><figcaption></figcaption></figure>

If you're using these Skill Checks within sequencer, you can make use of the `Result Play Sequence` section / drop-down to play conditional subsequent sequences upon the player completing or failing the Skill Check (The current sequence will simply continue playing if the result of the Skill Check does not have a subsequent sequence set / is left empty).

<figure><img src="https://2310584459-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FuiMQl6UzBr8OnuaoaiWO%2Fuploads%2FUweNzXlCCL6aKmuNmDIy%2Fimage.png?alt=media&amp;token=00d8e80f-e281-4466-97f8-1c7ce2da6388" alt=""><figcaption></figcaption></figure>

***

Starting a Skill Check can be done in 2 different ways. First of which, is directly through blueprints by calling the `Create Skill Check` event from SF's sequence manager, feeding in a `Row Name` (the Row Name of your Skill Check within the `SkillCheckVault_DT` data table) and a `Duration` (how long in seconds should the Skill Check be active. After the delay / duration, the active Skill Check will determine a result depending on how well the player performed relative to the `Max Num of Failed Attempts` / `Min Num of Correct Attempts` values set)

<div align="left"><figure><img src="https://2310584459-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FuiMQl6UzBr8OnuaoaiWO%2Fuploads%2FC3hDyxScld6lcOBTT2RZ%2FCreateQTE.png?alt=media&amp;token=4a2cab7e-f525-4692-b932-8bf700df976c" alt=""><figcaption></figcaption></figure></div>

The 2nd way to create a Skill Check is done directly inside of sequencer by making use of the "Add Skill Check" [Custom Sequencer Track](https://visualonecompany.gitbook.io/storyframeworkdocs/core-components/cinematic-tooling/custom-sequencer-tracks.md).

***
