# Core Concepts *** ## Action The base class for all actions. Each action is a serializable data object that defines: * **Enabled** — Toggle to enable/disable the action * **Description** — Optional description that replaces the action type name in the inspector header * **Delay** — Time to wait before executing * **Duration** — How long the action takes (used by some actions) *** ## ActionFlow A container that holds a list of actions. The FlowPlayer executes actions in this flow sequentially. *** ## FlowPlayer The MonoBehaviour component that manages and executes an ActionFlow. It provides playback controls and events. *** ## Triggers MonoBehaviour components that automatically play a FlowPlayer when specific conditions are met (collisions, input, timers, etc.). See the [Triggers](/beelabs-docs/flow-of-action/triggers.md) page for details. --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## 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://beelabs-dev.gitbook.io/beelabs-docs/flow-of-action/core-concepts.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.