> For the complete documentation index, see [llms.txt](https://epyk.gitbook.io/epyk-docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://epyk.gitbook.io/epyk-docs/pyplugins/pylms/commands-and-permissions.md).

# Commands & Permissions

Use `/lms` as the main pyLMS command. `/pylms` also works.

{% hint style="info" %}
Use `/lms` in guides and chat messages. It is shorter and easier to remember.
{% endhint %}

### Player commands

| Command     | Description                 | Permission   |
| ----------- | --------------------------- | ------------ |
| `/lms`      | Opens the pyLMS help menu.  | —            |
| `/lms help` | Shows available commands.   | —            |
| `/lms join` | Joins the active LMS event. | `pylms.join` |

{% hint style="warning" %}
Players need an empty inventory before joining. This prevents item loss and outside items entering the event.
{% endhint %}

### Admin commands

<table data-search="false"><thead><tr><th>Command</th><th>Description</th><th>Permission</th></tr></thead><tbody><tr><td><code>/lms start</code></td><td>Starts the LMS join phase. Alias: <code>/lms begin</code></td><td><code>pylms.start</code></td></tr><tr><td><code>/lms stop</code></td><td>Stops the active LMS event. Alias: <code>/lms end</code></td><td><code>pylms.stop</code></td></tr><tr><td><code>/lms set join</code></td><td>Sets the player join location.</td><td><code>pylms.set</code></td></tr><tr><td><code>/lms set spawn</code></td><td>Sets the return location after an event.</td><td><code>pylms.set</code></td></tr><tr><td><code>/lms set center [radius]</code></td><td>Sets the arena center and optional radius.</td><td><code>pylms.set</code></td></tr><tr><td><code>/lms listplayers</code></td><td>Lists LMS participants. Aliases: <code>/lms list</code>, <code>/lms players</code></td><td><code>pylms.listplayers</code></td></tr><tr><td><code>/lms reload</code></td><td>Reloads configuration, messages, schedules, and visual tasks. Alias: <code>/lms rl</code></td><td><code>pylms.reload</code></td></tr></tbody></table>

### Recovery and debug commands

Use these commands for staff recovery and troubleshooting only.

| Command                 | Description                                                                | Permission      |
| ----------------------- | -------------------------------------------------------------------------- | --------------- |
| `/lms fix <player>`     | Removes LMS-related invulnerability. Alias: `/lms fixplayer <player>`      | `pylms.fix`     |
| `/lms inspect <player>` | Shows a player's LMS safety information. Alias: `/lms infoplayer <player>` | `pylms.inspect` |

{% hint style="warning" %}
Use `/lms fix` only after an interrupted event, crash, forced stop, or similar issue.
{% endhint %}

### Permissions

<table data-search="false"><thead><tr><th>Permission</th><th>Allows</th><th>Default</th></tr></thead><tbody><tr><td><code>pylms.join</code></td><td>Joining LMS events</td><td>Everyone</td></tr><tr><td><code>pylms.start</code></td><td>Starting events manually</td><td>OP</td></tr><tr><td><code>pylms.stop</code></td><td>Stopping events manually</td><td>OP</td></tr><tr><td><code>pylms.set</code></td><td>Setting arena locations</td><td>OP</td></tr><tr><td><code>pylms.listplayers</code></td><td>Viewing LMS participants</td><td>OP</td></tr><tr><td><code>pylms.reload</code></td><td>Reloading pyLMS</td><td>OP</td></tr><tr><td><code>pylms.fix</code></td><td>Recovering affected players</td><td>OP</td></tr><tr><td><code>pylms.inspect</code></td><td>Viewing LMS safety information</td><td>OP</td></tr><tr><td><code>pylms.admin</code></td><td>Bypassing LMS command restrictions during an event</td><td>OP</td></tr></tbody></table>


---

# 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://epyk.gitbook.io/epyk-docs/pyplugins/pylms/commands-and-permissions.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.