> For the complete documentation index, see [llms.txt](https://docs.deltarix.store/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.deltarix.store/paid-assets/mdt-v2/setup.md).

# Setup

{% hint style="info" %}
Welcome to the setup guide! I've crafted this guide to make the installation and configuration process as straightforward and smooth as possible. Just follow the steps outlined here, and you'll have everything up and running in no time. Embrace the simplicity of our setup, and let's get started!
{% endhint %}

***

#### Step 1: Ensure Dependencies

Ensure that all the necessary requirements for the dependencies are met. Refer to the [dependencies](/paid-assets/mdt-v2/dependencies.md) page to verify you have everything in place.

**Step 2: SQL File Management**

1. **Identify Your Database Collation:** Determine the collation your database uses. This will decide which folder of SQL files you need to import. You have two options:

   * `collate-utf8mb4_general_ci`
   * `collate-utf8mb4_unicode_ci`

   Each folder contains files optimized for their respective character sets and collation rules.
2. **Navigate to the Correct Folder:** Based on your collation type, navigate to the corresponding folder within the `sql` directory:
   * For UTF8MB4 General CI collation: `sql/collate-utf8mb4_general_ci`
   * For UTF8MB4 Unicode CI collation: `sql/collate-utf8mb4_unicode_ci`
3. **Import the Framework-Specific SQL Files:** Inside the chosen collation folder, you will find SQL files for different frameworks. Import the SQL files that correspond to the framework you are using:
   * For QBCore: `qb.sql`
   * For ESX: `esx.sql`
   * First, import the `import.sql` file before the framework-specific files.
4. **Import Standalone Data:** After importing the framework-specific and initial SQL files, proceed to import additional data for more extensive customization and setup:

   * Navigate to `sql/standalone_data`
   * Import the following files:
     * `cameras.sql`
     * `categories.sql`
     * `charges.sql`
     * `roles.sql`
     * `tags.sql`

   These files contain modifiable data which can also be adjusted within the game via the MDT (Mobile Data Terminal).
5. **Review and Customize SQL Files if Necessary:**
   * It's important to review the SQL files before importing them to ensure that they align with your specific setup and requirements. Make modifications if necessary to fit your environment or to enhance functionality.
6. **Final Checks:**
   * After importing all necessary SQL files, check your database to ensure that all data is correctly inserted and that there are no errors.
   * Ensure that all settings in the game and database are correctly configured to interact as expected.

#### Step 3: Initialize Officer Command

Run the command `drx_mdt_hire` **on the server-side console**. It's essential to note that this cannot be executed client-side.

* To use the `drx_mdt_hire` command, you'll need your `stateid`, which the MDT generates. Find this in your database table `drx_mdt_player_link`. Remember, this step is crucial when adding the first officer.

***

Once you've completed these steps, your setup should be complete. Dive in and enjoy the experience!