# Startup Purge

**Admin Commands:**

1. **/purge**\
   Activates the survival event. This command should be used to signal the beginning of the event.
2. **/startpurge**\
   Starts the survival phase. The event will officially begin, and players will be immersed in the competition.
3. **/endpurge**\
   Ends the event and resets the server to normal gameplay. Players will return to their regular activities.

**Player Command:**

1. **/joinpurge**\
   Allows players to enter the event before it begins. Once the event starts, they will not be able to join.
   * **Important**: Players will lose any weapons they had before entering the event. They should choose their loadout carefully!

***

#### **Requirements**

* **OX Inventory** or **QB Inventory** *(Optional)*
* **ESX Framework** or **QBcore Framework**
* **Xsound** *(Required for sound effects)*
* **Cayo Perico** *(Required map for the event)*
* **Okok Notify** *(Optional for notifications)*

***

#### **Admin Permissions**

To allow an admin to control the event, you must add them to the server's permissions configuration.

* **Permission Command**:\
  Add the following line to your `server.cfg` to give an admin control over the event:

```bash
add_ace identifier.steam:[SteamID] purge allow
```

Replace `[SteamID]` with the actual Steam ID of the admin you want to grant permissions to.

***

#### **Installation**

Download the Purge Script and place it in your server’s resources folder.


---

# 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://startup-documentation.gitbook.io/startup-documentation/documentation/publish-your-docs.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.