> For the complete documentation index, see [llms.txt](https://docs.engagevr.io/engage/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.engagevr.io/engage/experience-editor/working-with-objects/triggers/player-body-trigger.md).
# Player body trigger
A player body trigger is triggered when a player walks into it. You could use a player body trigger to play a sound or activate a video screen when a user enters an area.
A player body trigger is represented in the Experience Editor environment by a transparent cube with a grid material. However, the trigger is invisible when a user plays your experience.
The only effect options that you can set for a player body trigger are those described in [Effect options](/engage/experience-editor/working-with-objects/effect-options.md#common-effect-options) and [Triggers](/engage/experience-editor/working-with-objects/triggers.md#trigger-effect-options).
{% hint style="info" %}
To test your triggers while in the Experience Editor, select play (
) on the playback controls, and then minimize the editor panel. You can then move through the player body trigger.
{% endhint %}
---
# 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, and the optional `goal` query parameter:
```
GET https://docs.engagevr.io/engage/experience-editor/working-with-objects/triggers/player-body-trigger.md?ask=&goal=
```
`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.
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.