> For the complete documentation index, see [llms.txt](https://docs.convai.com/api-docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.convai.com/api-docs/plugins-and-integrations/convai-unity-sdk/features.md). # Features Index of the Convai Unity SDK feature modules: actions, dynamic context, long-term memory, multi-character sessions, narrative design, scene metadata, vision. Features are the SDK's AI-powered capability modules. Each feature connects to Convai for a specific purpose — executing in-scene behaviors, expressing emotions, remembering users across sessions, following narrative graphs, or seeing the world through a camera. Features have dedicated module systems, ScriptableObject profiles, and their own Convai integration. Select a feature to get started:


Actions Let characters perform in-scene behaviors — move, pick up, animate, trigger events — in response to natural language commands.	Character actions
Dynamic Context Feed live runtime state — environment conditions, player status, simulation events — directly into a character's awareness mid-conversation.	Dynamic context
Scene Metadata Automatically register scene objects with Convai so characters understand the physical world around them without manual context injection.	Scene metadata
Long-Term Memory Give characters cross-session recall — they remember individual users, facts, and past interactions over time.	Long-term memory
Multi-Character Sessions Run several characters in one shared room and control which character the player is addressing at any moment.	Multi-character sessions
Narrative Design Structure conversations around authored story graphs with section-based behavior changes and trigger-driven progression.	Narrative design
Vision Stream live video from scene cameras or webcams to Convai, enabling characters to see and respond to real-time visual input.	Vision

--- # 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 by asking a question. Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters: ``` GET https://docs.convai.com/api-docs/plugins-and-integrations/convai-unity-sdk/features.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case. 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.