> 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/unreal-engine/guides/actions-guide/stage-1-default-actions/moves-to.md). # Moves To This action enables a character to move to certain objects/characters present in its environment {% hint style="info" %} By default, Convai Characters possess knowledge about the presence of other Convai characters within their environment. {% endhint %} ### 1. Use Moves to with other Convai Characters present in the Environment. Let's assume there are two Convai characters present in the virtual environment. We can ask one of the characters to move to the other character as shown here.

Convai Character moves to the other character.

### 2. Use Moves To with other objects present in environment. Steps: - * Click on your Convai character in present in scene. * In `Outliner` go to `Convai Info` section and then Click on the `+` icon near `Objects`.

* Click on `Pick Actor from Scene` tool

* Select any object from the scene and give it a `Name` and `Description` of choice.

* Save the changes and ask your Convai character to move to the object your named.

* The Convai character finally move to the object you added to its object list.

--- # 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/unreal-engine/guides/actions-guide/stage-1-default-actions/moves-to.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.