> For the complete documentation index, see [llms.txt](https://vinipistudios.gitbook.io/procedural-first-person-toolkit/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://vinipistudios.gitbook.io/procedural-first-person-toolkit/component-reference/procedural-motion-component/creating-custom-procedural-motions.md). # Creating Custom Procedural Motions A technical guide for developers on how to inherit from the **ProceduralMotionComponent** base class and override the necessary functions to create unique, project-specific movement logic. For this example, we are going to use the demo project and implementing Ready Or Not's ready/unready state, where by pressing a button the player lower's their equipment, allowing for faster movement. **Final Result:** {% embed url="" %} ### 1. Creating the Preset * Right click on an empty space inside the content browser. * Click **BlueprintClass.** * Select **ProceduralPreset** as the base class. Let's call it **BP\_ProceduralPreset\_Unready**.
* Create 4 variables, one for the Rotation and one For the Location offset, both for first and third person.
### 2. Creating the Component * Right click on an empty space inside the content browser. * Click **BlueprintClass.** * Select **ProceduralMotionComponent** as the base class.
Lets call it **B\_ProceduralUnreadyMotionComponent**. ### 3. The Procedural Motion Output * Inside your newly created component, override the function called **ComputeOutput**. * Create a **Bool** variable to define the current Ready/Unready state (make sure it's default value is true). * Create a **Float** variable to define the actual unready alpha.
* Create a new function called **RefreshAlpha**, passing in **DeltaTime** as a parameter * Use a simple **interpolation** algorithm to smoothly transition between ready/unready.
* Make sure **RefreshAlpha** is called inside **ComputeOutput**
* Call **GetPreset,** passing in the parent's **PresetData** variable and our newly created preset class, and promote the **ReturnValue** to a variable called **Preset.** connect the **IsValid** pin to a return node.
* Create a **Branch**, passing in **FirstPerson** (from the input) as the condition.
* From the **True** pin, call a return value, making a procedural output based on the FP location and rotation from our preset, passing in **UnreadyAlpha** as the **Weight**, and **Bone** as the **Space,** and **Additive** as the **Composition**.
* From the **False** pin, duplicate the previous code, this time passing in the **Third Person** values.
* Duplicate the **ReturnNode,** passing in Return Value as false if the preset is invalid.
This should be everything for the component. See the Final Code ### 4. Adding the Component For this example, let's add the component to our character blueprint. {% hint style="success" %} The component could also be added to the equipment, but to make things easier, let's add it to the character. {% endhint %} * Add **BP\_ProceduralUnreadyMotionComponent** to your character and select a **PresetData** containing the preset created previously, I'll be using the AK preset to speed things up, but you could create one for the character or each of the weapons.
* Swap the ready state based on input.
### 5. Final Result
Feel free to copy the values from the screenshot or find your own.