> For the complete documentation index, see [llms.txt](https://code-after-sex.gitbook.io/script-documentation/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://code-after-sex.gitbook.io/script-documentation/cas-weddingvenue/commands.md).

# Commands and Permissions

Commands and permissions in CAS Wedding Venue: the staff venue commands, the developer tools and ACE permissions.

## Staff commands

| Command                                                 | What it does                                                                             |
| ------------------------------------------------------- | ---------------------------------------------------------------------------------------- |
| `/wedding_venue on` / `off`                             | Shows or hides the venue for everyone. With no argument, tells you whether it is showing |
| `/wedding_crowd all` / `ceremony` / `reception` / `off` | Fills the venue with NPC guests for everyone nearby, or sends them home                  |
| `/wedding_clap [seconds]`                               | The NPC guests applaud, 8 seconds by default, 60 at most                                 |
| `/wedding_confetti`                                     | Confetti over the altar. `fireworks` adds fireworks, `all` adds fireworks and applause   |

All four also work from the server console. The answer appears in the chat, or in the console when run from there.

`/wedding_venue` and `/wedding_crowd` last until the next restart. After that the venue and the guests go back to `Config.Venue.EnabledByDefault` and `Config.Crowd.startMode`.

## Keys

| Where          | Key        | Action      |
| -------------- | ---------- | ----------- |
| At a free seat | Hold **E** | Sit Down    |
| While seated   | Hold **E** | Stand Up    |
| While seated   | Hold **R** | Change Pose |

## Developer tools

These help you fine-tune the venue. They do nothing unless `Config.DevTools = true`. Keep it `false` on a live server.

| Command                   | What it does                                                                                                                      |
| ------------------------- | --------------------------------------------------------------------------------------------------------------------------------- |
| `/wedding_where`          | Prints your position in venue-local metres and the nearest prop. Use it to place NPC guest spots                                  |
| `/wedding_seat [x y z h]` | While seated, prints that seat's offset, or moves it live                                                                         |
| `/wedding_scan`           | Surveys the ground and objects around the venue and saves `scan_<date>.json` in the resource folder. Needs `command.wedding_scan` |

## Permissions

Players need no permission to see the venue or to sit.

The staff commands use standard ACE permissions. With `Config.StaffOnlyCommands = true` (the default), a player needs `command.<name>`, or `command`, which covers every command:

```cfg
add_ace group.admin command allow
```

or only the venue commands:

```cfg
add_ace group.admin command.wedding_venue allow
add_ace group.admin command.wedding_crowd allow
add_ace group.admin command.wedding_clap allow
add_ace group.admin command.wedding_confetti allow
```

Change `group.admin` to whichever group your staff is in. To give the permission to one person:

```cfg
add_principal identifier.license:YOUR_LICENSE group.admin
```

Setting `Config.StaffOnlyCommands = false` lets every player use the commands. Use that only while testing.

{% hint style="info" %}
The resource checks ACE only, so it works the same on VORP, RSG Core or any other framework. If your staff are already in an ACE group such as `group.admin`, the line above is all you need.
{% endhint %}