> For the complete documentation index, see [llms.txt](https://omori-modding.gitbook.io/wiki/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://omori-modding.gitbook.io/wiki/rpgmaker/event-plugin-commands.md).

# Event Plugin Commands

This page will document important Plugin Commands used in OMORI, and their functions. These can be used by selecting the Plugin Command option in the Rpgmaker event block, and then typing in the commands below. **USAGE OF THESE COMMANDS REQUIRES RPGMAKER MV**

![plugin](https://user-images.githubusercontent.com/87251065/204021804-74aa7d1d-8054-426e-84f8-8979893a9991.PNG)

### Dialogue

*<mark style="color:red;">NOTE: Dialogue in OMORI is stored in yaml files in the languages folder, and are organized by message numbers (usually). A template yaml can be found in the decrypted game files or</mark>* [*<mark style="color:red;">here</mark>*](https://github.com/saikedemon/omori-modding/blob/main/00_template.yaml) *<mark style="color:red;">if you are struggling to figure it out.</mark>*

`ShowMessage file.messageId` - This will display a dialogue box with the selected message.\
EXAMPLE: "ShowMessage dw\_boss\_rush.message\_1" will show the message "message\_1" in the dw\_boss\_rush.yaml file.

### Choices

`AddChoice file.messageId Label` - This will add a choice with the text of the selected message, and jumping to the Label "Label" when selected.

EXAMPLE: `AddChoice XX_GENERAL.message_4` Label1 will add a choice displaying the text "YES", jumping to the label "Label1" when selected.

*<mark style="color:red;">NOTE: Labels are another option in RPGMaker's event block menu. I would advise familiarizing yourself with how they work before attempting usage of this command and the ShowChoices command below.</mark>*

`ShowChoices [AMOUNT]` - This will show choices that were created using the AddChoice command, up to a set amount. This is needed to make the choices selectable. The amount starts from 0 and goes up.

EXAMPLE: ShowChoices 1 will show up to 2 choices created, rather than 1.

{% hint style="info" %}
Extra Note for Choices: **`XX_GENERAL.message_4`** will always be "YES" and **`XX_GENERAL.message_5`** will always be "NO", unless manually modified.
{% endhint %}

### Camera Movement

*<mark style="color:red;">NOTE: \[SPEED] is an extra parameter for a number representing how fast the camera moves. 800 is the default, lower numbers increase the speed while higher numbers decrease it. If you choose to not include the parameter entirely, it will be set to its default, 800.</mark>*

`CAM PLAYER [SPEED]` - Focuses the camera onto the player.\
EXAMPLE: "CAM PLAYER" Moves the camera to the player at the default speed.

`CAM EVENT ID [SPEED]` - Moves the camera to an event. The event ID is the number at the bottom right of the screen after selecting an event.\
EXAMPLE: "CAM EVENT 7" Moves the camera to event 7 at the default speed.

`CAM X Y [SPEED]` - Moves the camera to the x and y coordinates set. Self explanatory.\
EXAMPLE: "CAM 5 9" Moves the camera to the position \[5, 9] at the default speed.

`CAM DISABLE` - Disables custom camera movement, returning it to rpgmaker default (the camera follows the player).


---

# 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://omori-modding.gitbook.io/wiki/rpgmaker/event-plugin-commands.md?ask=<question>&goal=<endgoal>
```

`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.