# Loaders

The **Loaders** section enables users to manage executable files (**loaders**) within their applications. Loaders are crucial for initializing, updating, and executing various tools that enhance your application's functionality. With the provided commands, users can add, modify, delete, rename, and update the status of loaders efficiently.

## **1. /status**

Displays the current status & numbers of all loaders associated with your application.

**Basic Command:**

<figure><img src="/files/eTSTQX8ghl3SNeZlNZdN" alt=""><figcaption></figcaption></figure>

**Result:**\
An embedded message listing all loaders categorized appropriately, showing their names and current statuses:

* 🟢 **Online**
* 🟠 **Updating**
* 🔴 **Offline**

**Example Output:**

<figure><img src="/files/0BMIkNFtgVPkkfUBv4ob" alt=""><figcaption></figcaption></figure>

***

## **2. /add\_loader**

Adds a new loader to a specified category or creates a new category if it doesn't exist.

**Basic Command:**

<figure><img src="/files/7eqV3wXj709wWpgPrwAc" alt=""><figcaption></figcaption></figure>

**Parameters Explained:**

1. **loader\_name** (String)
   * **Description:** The name of the loader to add.
   * **Example:** `TOOL v1`
2. **loader\_link** (URL)
   * **Description:** The URL where the loader executable is hosted. Must end with `.exe`, `.bat`, or similar executable formats.
   * **Example:** `https://example.com/tool_v1.exe`
3. **category** (Choice)
   * **Description:** The category under which the loader will be organized.
   * **Available Categories:** `BO6`, `MW3`, `MW2`, `MW19`, `FIVEM`, `SPOOFERS`, `VALORANT`, `R6`, `CS2`, `FORTNITE`, `RUST`, `APEX`, `HLL`, `DAYLIGHT`
4. **loader\_status** (Choice, Optional)
   * **Description:** The initial status of the loader.
   * **Available Statuses:** `🟢 online`, `🟠 updating`, `🔴 offline`
   * **Default:** `🟢 online`

**Usage Example:**

<figure><img src="/files/l1BkwXzovDN41kIFg3FU" alt=""><figcaption></figcaption></figure>

**Result:**\
Adds the `TOOL v1` loader to the `MW19` category with an initial status of `online`. If the `MW19` category does not exist, it will be created automatically.

***

## **3. /update\_loader**

Updates the link and increments the version of an existing loader based on its assigned number.

**Basic Command:**

<figure><img src="/files/jRdwsj6Mvq1M1903udcr" alt=""><figcaption></figcaption></figure>

**Parameters Explained:**

1. **loader\_number** (Integer)
   * **Description:** The unique number assigned to the loader you wish to update (from the `/status` command).
   * **Example:** `2`
2. **new\_link** (URL)
   * **Description:** The new URL for the loader executable. Must end with `.exe`, `.bat`, or similar executable formats.
   * **Example:** `https://example.com/tool_v2.exe`

**Usage Example:**

<figure><img src="/files/vIlW4MB4XJUpgvtFxrAL" alt=""><figcaption></figcaption></figure>

**Result:**\
Updates the `TOOL v2` loader's link to `https://tool_v2.exe` and increments its version number automatically.

***

## **4. /rename\_loader**

Renames an existing loader based on its assigned number.

**Basic Command:**

<figure><img src="/files/Uejj2RkmjDq0UPY6uVY9" alt=""><figcaption></figcaption></figure>

**Parameters Explained:**

1. **loader\_number** (Integer)
   * **Description:** The unique number assigned to the loader you wish to rename.
   * **Example:** `3`
2. **new\_name** (String)
   * **Description:** The new name for the loader.
   * **Example:** `Delta Chair 2`

**Usage Example:**

<figure><img src="/files/694jx1Mi6zxz2Xe9lxmy" alt=""><figcaption></figcaption></figure>

**Result:**\
Renames the loader numbered `3` from `TOOL v3` to `Delta Chair 2`.

***

## **5. /update\_status**

Updates the status of multiple loaders simultaneously based on their assigned numbers.

**Basic Command:**

<figure><img src="/files/p8VOSu1h0Mlfu1vfPDcJ" alt=""><figcaption></figcaption></figure>

**Parameters Explained:**

1. **tool\_numbers** (String)
   * **Description:** A space-separated or comma-separated list of loader numbers you wish to update.
   * **Format:** Numbers can be separated by spaces or commas.
   * **Example:** `1 3 5` or `1,3,5`
2. **status** (Choice)
   * **Description:** The new status to assign to the selected loaders.
   * **Available Statuses:** `🟢 online`, `🟠 updating`, `🔴 offline`

**Usage Example:**

<figure><img src="/files/kY0KdZqmFEhphJHeRZbg" alt=""><figcaption></figcaption></figure>

**Result:**\
Updates the status of loaders numbered `1`, `3`, and `5` to `updating`.

***

## **6. /delete**

Deletes a loader or an entire category from your application.

**Basic Command:**

<figure><img src="/files/3Buzt9EFRVYaZbXr0ysc" alt=""><figcaption></figcaption></figure>

**Parameters Explained:**

1. **item\_type** (Choice)
   * **Description:** Specifies whether you want to delete a `Loader` or a `Category`.
   * **Available Options:** `Loader`, `Category`
2. **loader\_number** (Integer, Required if `item_type` is `Loader`)
   * **Description:** The unique number assigned to the loader you wish to delete.
   * **Example:** `4`
3. **category\_name** (String, Required if `item_type` is `Category`)
   * **Description:** The name of the category you wish to delete.
   * **Example:** `BO6`

**Usage Examples:**

* **Deleting a Loader:**

<figure><img src="/files/vH0WlAZNnD3fClIo39WA" alt=""><figcaption></figcaption></figure>

* **Deleting a Category:**

<figure><img src="/files/Mr2fzzoVY2suO6W02Yd8" alt=""><figcaption></figcaption></figure>

**Result:**

* **Loader Deletion:** Removes the specified loader from its category.
* **Category Deletion:** Removes the entire category and all associated loaders.

***

## **Best Practices**

* **Consistent Naming:**\
  Use clear and descriptive names for loaders and categories to simplify management and enhance clarity.
* **Reliable Hosting:**\
  Ensure all loader URLs are hosted on reliable and accessible platforms to prevent issues with loader execution.
* **Regular Reviews:**\
  Periodically review the statuses and configurations of your loaders using the `/status` command to maintain users updated.


---

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

```
GET https://av0.gitbook.io/av/applications/multiloader-s1/discord-integration/loaders.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.