> For the complete documentation index, see [llms.txt](https://stalk.gitbook.io/documentation-stalk/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://stalk.gitbook.io/documentation-stalk/go-fast-system/installation-guide.md).

# Installation Guide

The installation process for **STALK GO-FAST** has been designed to be quick and simple to set up on your server.

`stalk_gofast` is a premium Go-Fast mission system built for roleplay servers. It includes multiple contract levels, dirty money payments, vehicle deliveries, lockpick missions, police alerts, progression statistics, cooldowns, NPC interactions, a modern NUI menu, and support for ESX or QBCore.

Most of the configuration can be modified directly through the `shared/config.lua` file.

***

## Step 1 : Resource Installation

Start by dragging the `stalk_gofast` folder into your server’s `resources` directory.

Once the folder has been added, open your `server.cfg` file and add the following line:

```
ensure stalk_gofast
```

After saving the changes, restart your server.

***

## Step 2 : Required Dependencies

Before starting the resource, make sure the following dependencies are installed on your server:

```
ox_libox_targetoxmysql
```

The script uses `ox_lib` for utility functions, `ox_target` for NPC and mission interactions, and `oxmysql` for saving player statistics and cooldowns.

***

## Step 3 : Database Installation

The resource includes an SQL file located here:

```
stalk_gofast/sql/stalk_gofast.sql
```

You can import this file manually into your database using phpMyAdmin, HeidiSQL, or any MySQL manager.

The script also automatically creates the required tables on startup if they do not already exist.

The database stores player GO-FAST statistics and cooldown data using the following tables:

```
stalk_gofast_statsstalk_gofast_cooldowns
```

***

## Step 4 : Main Configuration

All main configuration settings are located inside:

```
stalk_gofast/shared/config.lua
```

From this file, you can configure the framework, inventory system, language, mission timeout, cooldowns, progression requirements, payments, NPCs, vehicles, mission levels, police alerts, and interface behavior.

By default, the script is configured like this:

```
Config.Framework = 'esx'Config.Inventory = 'ox'Config.Language = 'en'
```

You can change the framework depending on your server setup:

```
Config.Framework = 'esx'
```

or

```
Config.Framework = 'qb'
```

The inventory system can also be changed depending on what your server uses:

```
Config.Inventory = 'ox'
```

```
Config.Inventory = 'esx'
```

```
Config.Inventory = 'qb'
```

***

## Step 5 : Language Configuration

The script includes multiple language files.

Available languages are:

```
frende
```

You can change the language here:

```
Config.Language = 'en'
```

If you want the script in French, use:

```
Config.Language = 'fr'
```

If you want the script in German, use:

```
Config.Language = 'de'
```

***

## Step 6 : Main NPC Configuration

The GO-FAST menu is started through an NPC.

You can configure the NPC here:

```
Config.Ped = {    enabled = true,    alwaysActive = true,    model = 'a_m_m_salton_03',    coords = vec4(1586.3280, -1691.7880, 88.1238, 188.6927),    activeFrom = 20,    activeTo = 0}
```

You can change the NPC model, position, heading, and activity hours.

If `alwaysActive` is set to `true`, the NPC will always be available. If you set it to `false`, the NPC will only be available between the configured hours.

***

## Step 7 : Vehicle Spawn Configuration

The vehicle used for GO-FAST missions is spawned at the configured spawn point.

```
Config.VehicleSpawn = vec4(1578.1814, -1697.1786, 88.1560, 29.2738)
```

You can move this position to any valid location on your server.

Make sure the spawn area has enough space for mission vehicles.

***

## Step 8 : Mission Prices

Each GO-FAST level has its own entry price.

```
Config.MenuPrices = {    [1] = { min = 750, max = 750 },    [2] = { min = 1500, max = 2600 },    [3] = { min = 3500, max = 5500 },    [4] = { min = 6500, max = 9500 },    [5] = { min = 12000, max = 18000 }}
```

The script randomly selects a price between the minimum and maximum values.

Players must have enough dirty money to start the selected contract.

***

## Step 9 : Dirty Money Configuration

The script supports dirty money payments for both ESX and QBCore.

```
Config.CurrencyAccount = {    esxDirty = 'black_money',    qbDirty = 'markedbills',    qbRewardAccount = 'cash'}
```

For ESX, the script uses the `black_money` account by default.

For QBCore, the script can use marked bills as an item:

```
Config.QBDirtyAsItem = true
```

If you want QBCore to use a money account instead, you can disable this option and configure the account name.

***

## Step 10 : Required Item Configuration

Some missions require a lockpick.

```
Config.RequiredItem = 'lockpick'
```

You can change this item name if your server uses a custom lockpick item.

The mission levels that require a lockpick are controlled individually inside `Config.Levels`.

Example:

```
requiresLockpick = true
```

***

## Step 11 : Mission Levels

The script includes five different GO-FAST mission levels.

Each level has its own label, risk, vehicle list, mission type, delivery points, and reward behavior.

Example:

```
Config.Levels = {    [1] = {        label = 'PASSEUR',        subtitle = 'Grosse passe rapide à vélo',        risk = 'FAIBLE',        requiresLockpick = false,        image = 'bmx.png',        vehicles = { 'bmx', 'cruiser', 'scorcher' },        minDistance = 2500    }}
```

You can customize each level by changing its vehicles, delivery points, distances, labels, risk text, images, and mission logic values.

***

## Step 12 : Reward Configuration

Mission rewards are calculated using base rewards, distance multipliers, and entry price return multipliers.

```
Config.RewardMultipliers = {    [1] = { base = 1800, perKm = 650, priceBack = 1.15 },    [2] = { base = 5000, perKm = 900, priceBack = 1.25 },    [3] = { base = 12000, perKm = 1250, priceBack = 1.35 },    [4] = { base = 21000, perKm = 1600, priceBack = 1.45 },    [5] = { base = 42000, perKm = 2100, priceBack = 1.60 }}
```

You can increase or decrease these values depending on your server economy.

Higher levels are designed to be riskier and more profitable.

***

## Step 13 : Cooldown Configuration

The script includes an optional player cooldown system.

```
Config.PlayerCooldown = {    enabled = false,    minutes = 30}
```

If enabled, a player will not be able to start another GO-FAST before the cooldown ends.

This is useful if you want to limit mission farming.

***

## Step 14 : Level Progression

The script includes an optional progression system.

```
Config.LevelProgression = {    enabled = false,    requirements = {        [2] = { requiredLevel = 1, requiredSuccess = 10 },        [3] = { requiredLevel = 2, requiredSuccess = 10 },        [4] = { requiredLevel = 3, requiredSuccess = 10 },        [5] = { requiredLevel = 4, requiredSuccess = 10 }    }}
```

If enabled, players must complete lower-level missions before unlocking higher-level contracts.

For example, level 2 can require 10 successful missions from level 1.

***

## Step 15 : Mission Timeout

The script includes a mission timeout system.

```
Config.MissionTimeoutMinutes = 30
```

If a player takes too long to complete a mission, the mission will automatically fail and clean up the active entities.

This helps prevent abandoned missions from staying active on the server.

***

## Step 16 : Police Alert Configuration

The script can automatically alert police jobs during GO-FAST activity.

```
Config.PoliceAlert = {    enabled = true,    delay = 30,    displayTime = 3000,    jobs = { 'police', 'lspd', 'sheriff' }}
```

You can enable or disable police alerts, change the delay, change the display duration, and configure which jobs receive alerts.

***

## Step 17 : Backpack Configuration

The script includes an optional backpack prop during missions.

```
Config.Backpack = {    enabled = true,    model = 'p_michael_backpack_s',    bone = 24818,    offset = vec3(0.07, -0.17, 0.02),    rotation = vec3(0.0, 90.0, 180.0)}
```

You can disable the backpack or change the prop model, bone, position, and rotation.

***

## Step 18 : Commands

The resource includes useful commands for testing and menu handling.

```
/stalkgofastmenu
```

This command requests and opens the GO-FAST menu.

```
/stalkgofastclose
```

This command closes the NUI menu.

```
/stalkgofastnotif
```

This command can be used to test notifications.

***

## Step 19 : Custom Text Messages

Some basic text messages can be customized inside the config.

```
Config.Text = {    noDirty = 'Tu n’as pas assez d’argent sale pour lancer ce contrat.',    noLockpick = 'Tu dois avoir un lockpick pour cette étape.',    alreadyActive = 'Tu as déjà un GO-FAST en cours.',    wrongVehicle = 'Tu dois utiliser le véhicule fourni pour cette mission.',    success = 'Mission terminée. Paiement reçu.',    menuClosed = 'Contrats mis à jour à la prochaine ouverture.'}
```

You can translate or rewrite these messages to match your server style.

For deeper translations, you can also edit the locale files located inside:

```
stalk_gofast/locales/
```

***

## Important

Before updating the resource or modifying important settings, we strongly recommend creating a full backup of your server and database.

Even though the script is optimized and tested before release, backups remain essential to avoid issues caused by incorrect configuration, missing dependencies, database errors, or external conflicts.

***

## AI / Documentation Queries

If some information is not directly available on this page, you can dynamically query the documentation using the `ask` parameter.

Example:

```
GET https://docs.stalk.dev/stalk-gofast/installation-guide.md?ask=<your-question>
```

You can ask questions such as how to change the GO-FAST NPC position, how to configure mission rewards, how to enable level progression, how to modify police alerts, how to change required items, or how to adjust mission cooldowns.

The system will automatically return a direct answer along with the most relevant documentation sections.
