# Permissions

**Version:** 1.0.0

Events has four player nodes, which are allowed by default, and one admin node. Command syntax is on the [Commands](./commands) page.

---

## Player nodes (allowed by default)

These nodes are **allowed unless you set them to `false`**. A player without one gets "You are not allowed to do that."

| Permission | Commands | In the window |
|------------|----------|---------------|
| `ks.events.user.open` | `/ksevent`, `/ksevent list`, `/ksevent remind`, `/ksevent help` | Opening the events window |
| `ks.events.user.join` | `/ksevent join`, `/ksevent leave` | **Join** and **Leave**. Without it the button says "Joining not allowed" |
| `ks.events.user.travel` | `/ksevent travel`, `/ksevent back` | **Travel there**, **To my plot** and **Back where I was** |
| `ks.events.user.vote` | `/ksevent vote` | **Rate** on the **Now** tab, the rating bar and its **Next plot** |

The window checks the same nodes as the commands. To keep a group away from events completely, set `ks.events.user.open` to `false`.

:::note[Who may rate]
`ks.events.user.vote` only opens the rating bar. Who may rate a contest is decided by the rule **Everyone on the field may rate** (see [Configuration](./configuration#voting)): by default everyone who signed up and everyone who stands on the field during the voting.
:::

---

## Admin node (not granted by default)

| Permission | What it unlocks |
|------------|-----------------|
| `ks.events.admin` | `/kseventadmin` with all its subcommands, the admin window (also from the **Events** tile in the `/ksadmin` hub), and seeing who built which plot before the ceremony |

- The admin window checks the node on every click and closes itself when it is gone.
- The `/ksadmin` hub needs Core's `ks.admin`; the **Events** tile in it also checks `ks.events.admin`.
- The server console may use every `/kseventadmin` command.

---

## Command rewards

| Permission | What it unlocks |
|------------|-----------------|
| `ks.core.admin.dialog.console` | Adding a **Command** reward to an event. Command rewards run as the console |

This node belongs to KyuubiSoft Core. Admins without it can still plan events with items, coins and titles; a new command reward is refused with "Command rewards need the permission ks.core.admin.dialog.console." Command rewards that are already in an event stay when someone without the node edits it.

---

## Protection of build fields

Building on a build field is not a permission. Events tells KyuubiSoft Claims who may build:

- **During the build time** of the contest on that field: only the owner of a plot, and only on that plot.
- **At any other time:** nobody. Building, containers and workbenches inside the field are blocked.

Players who may bypass claims in KyuubiSoft Claims are handled as Claims handles them.

`/kslang` has no permission.