> For the complete documentation index, see [llms.txt](https://wiki.vortexdevelopment.net/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://wiki.vortexdevelopment.net/projects/fallingstars/commands-and-permissions.md).

# 📜 Commands & Permissions

FallingStars provides a robust set of commands to manage stars, events, and player data. Most commands can be used via the base command `/fallingstars` or its alias `/fs`.

### 🛠️ Administrative Commands

These commands require specific permission nodes and are intended for server administrators.

| Command                                 | Description                                                    | Permission                           |
| --------------------------------------- | -------------------------------------------------------------- | ------------------------------------ |
| `/fs reload`                            | Reloads the plugin configuration and all star/event files.     | `fallingstars.command.reload`        |
| `/fs summon <type> [player]`            | Summons a specific star at the target player's location.       | `fallingstars.command.summon`        |
| `/fs list`                              | Lists all loaded star types currently available.               | `fallingstars.command.list`          |
| `/fs clear`                             | Immediately removes all active falling stars from the world.   | `fallingstars.command.clear`         |
| `/fs stars`                             | Opens the **Star Management GUI** to edit star properties.     | `fallingstars.command.stars`         |
| `/fs events`                            | Opens the **Event Management GUI** to manage scheduled events. | `fallingstars.command.events`        |
| `/fs randomspawn`                       | Opens the **Random Spawn Configuration GUI**.                  | `fallingstars.command.randomspawn`   |
| `/fs setstars <player> <type> <amount>` | Directly set a player's collected count for a specific star.   | `fallingstars.command.setstars`      |
| `/fs resetstars <player> [type]`        | Resets a player's collection data (optionally for one type).   | `fallingstars.command.resetstars`    |
| `/fs resetdatabase confirm`             | **Wipes the entire player database.** Requires confirmation.   | `fallingstars.command.resetdatabase` |

### 📅 Event Management

Manage dynamic events with these sub-commands. All require `fallingstars.command.event`.

| Command                                   | Description                                                      |
| ----------------------------------------- | ---------------------------------------------------------------- |
| `/fs event list`                          | Lists all defined event configurations.                          |
| `/fs event start <id> [duration]`         | Manually triggers an event for a specific duration (e.g., `1h`). |
| `/fs event stop <id>`                     | Forcefully terminates a running event.                           |
| `/fs event clear`                         | Stops all currently running events.                              |
| `/fs event setcenter <id>`                | Sets the center point of a `CENTER` event to your location.      |
| `/fs event reset-cooldowns <player> [id]` | Resets event trigger cooldowns for a player.                     |

### 👤 Player Commands

These commands are generally available to players by default.

| Command              | Description                                              |
| -------------------- | -------------------------------------------------------- |
| `/fs stats [player]` | View your own or another player's collection statistics. |
| `/fs top [type]`     | Displays the leaderboard for the most stars collected.   |

{% hint style="info" %}
**Pro Tip**: You can use tab-completion for all star types, event IDs, and player names to speed up your workflow!
{% 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://wiki.vortexdevelopment.net/projects/fallingstars/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.