> For the complete documentation index, see [llms.txt](https://m3ii0.gitbook.io/amazingtitles_core_1/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://m3ii0.gitbook.io/amazingtitles_core_1/integrations/cmi-integration.md).

# CMI Integration

{% hint style="info" %}
Plugin page on SpigotMC: <https://www.spigotmc.org/resources/3742/>
{% endhint %}

## Portal commands

```yaml
Portals: # Fired on CMI portal use event.
  PortalName1: # Portal Name
    Conditions: # If any of this condition is false, executions won't be executed
      - "permission::some.permission"
      - "world::some.world"
    Executions:
      - "yourcommand1" # {Player} - Player's name | {PortalName} - Portal's name
      - "yourcommand2" # {Player} - Player's name | {PortalName} - Portal's name
  PortalName2: # Portal Name
    Conditions: # If any of this condition is false, executions won't be executed
      - "permission::some.permission"
      - "world::some.world"
    Executions: # List of your commands without '/'
      - "yourcommand1" # {Player} - Player's name | {PortalName} - Portal's name
      - "yourcommand2" # {Player} - Player's name | {PortalName} - Portal's name
```

## Teleport Request

<pre class="language-yaml"><code class="lang-yaml">TeleportRequest:
  Conditions: # If any of this condition is false, executions won't be executed
    - "permission::some.permission"
    - "world::someWorld"
<strong>  Executions:
</strong>    - "yourcommand1" # {OfferingPlayer} - Offering player's name | {AcceptingPlayer} - Accenpting player's name
    - "yourcommand2" # {OfferingPlayer} - Offering player's name | {AcceptingPlayer} - Accenpting player's name
    
</code></pre>

## Teleport

```yaml
Teleport:
  Executions:
    - "yourcommand1" # {Player} - Player's name | {World} - World | {X} - X | {Y} - Y | {Z} - Z | {TeleportType} - Teleport type
    - "yourcommand2" # {Player} - Player's name | {World} - World | {X} - X | {Y} - Y | {Z} - Z | {TeleportType} - Teleport type
```

## Afk-Enter

```yaml
AfkEnter:
  Conditions: # If any of this condition is false, executions won't be executed
    - "permission::some.permission"
    - "world::someWorld"
  Executions:
    - "yourcommand1" # {Player} - Player's name
    - "yourcommand2" # {Player} - Player's name
```

## Afk-Leave

```yaml
AfkLeave:
  Conditions: # If any of this condition is false, executions won't be executed
    - "permission::some.permission"
    - "world::someWorld"
  Executions:
    - "yourcommand1" # {Player} - Player's name
    - "yourcommand2" # {Player} - Player's name
```

## Balance-Change

```yaml
BalanceChange:
  Conditions: # If any of this condition is false, executions won't be executed
    - "permission::some.permission"
    - "world::someWorld"
  Executions:
    - "yourcommand1" # {From} - Balance before | {To} - Balance after | {Player} - Player's name
    - "yourcommand2" # {From} - Balance before | {To} - Balance after | {Player} - Player's name
```

{% hint style="danger" %}
If you want add something into this integration, create a ticket on the Discord Server!\
Link: <https://discord.com/invite/Ms7uAAAtcT>
{% 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://m3ii0.gitbook.io/amazingtitles_core_1/integrations/cmi-integration.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.