In Soulslike Framework, everything can be considered an Action. Provided with the project are multiple example Actions that you can inspect.
Actions work hand-to-hand with the [**Input Buffer Component**](/components-managers/player-specific-components/input-buffer.md)**.** That means they can be queued & consumed.
### Using the Utility Tools to Create/Edit Actions
1. Run the **Soulslike Action Creator** from the Soulslike Framework editor dropdown, or head into **/SoulslikeFramework/\_Utility/Creators** and right-click and Run Utility Widget -> **EUW\_ActionCreator:**
2. Fill in the details as you desire:
3. Click **Create Action** to generate the related assets.
4. Now, run the **Soulslike Action Browser** from the Soulslike Framework editor dropdown or head into **/SoulslikeFramework/\_Utility/Browsers** and right-click and Run Utility Widget -> **EUW\_ActionBrowser:**
3. Find your action and select it in the Browser. Double-check its properties to ensure everything is correct. Then click **"Open Logic"** to open the Action's logic asset:
6. If the assets opens in Data-Only mode, click the **Open Full Blueprint Editor** text.
7. Go to the **Functions** tab and override `ExecuteAction():`
8. (Optional) You can also add a new event graph and override the **Event** version of the method:
8. Next up, we need to let our [**Action Manager**](/components-managers/player-specific-components/action-manager.md) know that we want to initialize this new Action. Head inside **B\_Soulslike\_Character** and select **AC\_ActionManager:**
{% hint style="danger" %}
If you are using an **Override Table**, the **Actions map will be overridden.**
{% endhint %}
10. Create a new Gameplay Tag for your action. Then, add your new Action to either the **table** or the **Actions map** using the new Gameplay Tag & Action Data Asset:
11. Finally, using performing the Action **(Inside B\_Soulslike\_Character):**
---
# Agent Instructions: 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:
```
GET https://soulslike-framework.isik.vip/workflow/editor.md?ask=
```
The question should be specific, self-contained, and written in natural language.
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.