# first setup

Use this checklist after installation and license activation.

## 1. Verify plugin status

Run:

```
/pb info
/pbadmin help
/pbadmin license
```

Expected result:

* `/pb info` shows PracticeBot and Citizens status.
* `/pbadmin help` lists admin commands.
* `/pbadmin license` shows a valid/unlocked status.

## 2. Test player bot spawning

As a player with spawn permissions:

```
/spawnbot
/spawnbot normal
/spawnbot crystal
```

Expected result:

* `/spawnbot` opens the spawn selection GUI.
* `/spawnbot normal` spawns a Normal PvP bot.
* `/spawnbot crystal` spawns a Crystal PvP bot.

> **Media placeholder:** Add a 5-8 second GIF of `/spawnbot` opening the spawn selector and spawning a Normal bot.

## 3. Test player bot GUI

Shift-right-click your bot.

Expected result:

* Normal bots open the player settings menu.
* CPvP bots open the Crystal PvP settings menu.
* Inventory/settings buttons work without console errors.

## 4. Test admin tools

Run:

```
/pbadmin inventory
/pbadmin egui
/pbadmin reload
```

Expected result:

* Default inventory editor opens.
* GUI editor opens.
* Reload completes without errors.

## 5. Test template workflow

Create a temporary template:

```
/pbadmin template create test_normal
```

Use the editor, then save or cancel. If saved, test spawning:

```
/pbadmin template spawn test_normal
```

Then remove it if needed:

```
/pbadmin template delete test_normal
```

## 6. Configure permissions

Before opening the plugin to public players, configure:

* `practicebot.spawn.normal`
* `practicebot.spawn.cpvp`
* `practicebot.admin`
* specific admin child permissions if you want split staff access

## 7. Production safety check

Before release, test:

* disabled worlds
* spawn limits
* death/respawn behavior
* CPvP behavior in your arena geometry
* template respawn delays
* command tab completion
* server restart persistence
* PlaceholderAPI output if used


---

# Agent Instructions: 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:

```
GET https://edelweiss-network.gitbook.io/practicebot/server-owner-guide/first-setup.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.