lrc-horsethief

Mission flow

Language

Config.Lang = 'en'  -- 'en' or 'ro'

Switches all in-game notification text and UI strings between English and Romanian. The locale strings themselves live in locale_init.lua — do not edit that file directly unless you are adding a new language.

Contact NPC — Config.ContactNPCs

Config.ContactNPCs = {
    {
        model  = 'MP_LM_STEALHORSE_BUYERS_01',
        coords = vector4(1242.2626, -437.9520, 89.4799, 60.3918),
    },
    -- add more entries here if needed
}

Each entry in this table spawns one contact NPC in the world. You can have multiple NPCs — each one opens the same mission menu independently. This is useful if you want to place the contact in more than one location on the map.

Prompt & proximity — Config.PromptRange

Config.PromptRange  = 2.5           -- metres from the NPC before the prompt appears
Config.PromptTitle  = 'Horse Thief'  -- title shown above the prompt hint
Config.PromptAction = 'Interact'     -- label on the prompt button

NPC blip — Config.ShowNPCBlip

Config.ShowNPCBlip = false                 -- set true to show the NPC on the minimap
Config.BlipSprite  = 'blip_ambient_horse'  -- blip icon hash name
Config.BlipLabel   = 'Horse Thief'         -- text shown when hovering the blip
Config.BlipScale   = 0.35                  -- size of the blip icon

When ShowNPCBlip is false, the NPC exists in the world but does not appear on the minimap — players must find them through other means (server lore, signage, etc.). Set it to true to show a minimap marker.

BlipSprite accepts any valid RedM blip hash name. BlipScale controls the size — 0.35 is small and unobtrusive; 0.6–1.0 is more prominent.

Delivery blip — shown during horse return

Config.DeliveryBlipSprite = 'blip_saddle'
Config.DeliveryBlipLabel  = 'Deliver Horse'
Config.DeliveryBlipScale  = 0.35
Config.DeliveryRadius     = 10.0   -- metres from NPC to trigger mission completion

Once a horse is calmed, a delivery blip appears on the NPC's position. DeliveryRadius is the proximity (in metres) within which the mission auto-completes and rewards are paid. Increase it if players are finding the detection too tight; decrease it for a more precise delivery zone.

Mission area radii

Config.CircleRadius  = 35.0   -- size of the visual circle drawn on the map
Config.TriggerRadius = 70.0   -- entering this range spawns enemies and the horse
Config.SpawnRadius   = 25.0   -- enemies and horse spawn within this range of the center

Enemy models, weapons & accuracy

Config.EnemyModels = {
    'g_m_m_uniafricanamericangang_01',
    'u_m_m_odriscollbrawler_01',
    -- add or remove ped model names here
}

Config.EnemyAccuracy = {
    easy    = 20,   -- 0 = completely blind, 100 = perfect aim
    default = 35,
    hard    = 55,
}

Config.EnemyWeapons = {
    easy = {
        'weapon_revolver_cattleman',
        'weapon_revolver_doubleaction',
    },
    default = {
        'weapon_revolver_cattleman',
        'weapon_repeater_winchester',
        'weapon_shotgun_doublebarrel',
    },
    hard = {
        'weapon_rifle_springfield',
        'weapon_rifle_boltaction',
        'weapon_shotgun_semiauto',
    },
}

EnemyModels is a shared pool — every spawned enemy picks a random model from this list regardless of mission difficulty. EnemyWeapons and EnemyAccuracy are keyed by difficulty type ('easy', 'default', 'hard'), which is set per-mission inside configmissions.lua.

Full mission structure

[1] = {
    type = 'default',  -- 'easy' | 'default' | 'hard'

    ui = {
        image   = 'assets/images/m1.png',
        label   = 'MISSION 1 [Morgan]',
        warning = 'This horse is protected by armed gangs!',
        details = 'A sturdy Morgan Gelding...\n\nGo steal it.',
    },

    horselocation = {
        vec3(1549.1113, 1073.8922, 181.2135),
        vec3(1769.6315, 950.4037,  119.5529),  -- optional extra location
    },

    horse   = { model = 'a_c_horse_morgan_bayroan' },
    enemies = { count = 8 },

    rewards = {
        enabled = true,
        cash    = 50,
        -- item   = 'horse_deed',  -- single item (optional)
        -- amount = 1,
        -- items  = {              -- multiple items (optional)
        --     { item = 'horse_deed',      amount = 1 },
        --     { item = 'aged_pirate_rum', amount = 2 },
        -- },
    },
},

Field reference

Naming convention

Images are named m1.png through mN.png and stored in ui/assets/images/. Each file maps directly to the mission at the same index — m1.png is shown for [1], m2.png for [2], and so on. The path is set per-mission in the ui.image field inside configmissions.lua, so you can also use a completely different filename or subfolder if you prefer.

Replacing an existing image

Simply replace the file at the same path with your new image. No config change is needed — the path is already declared in the mission entry. Recommended dimensions are roughly 400 × 260 px, landscape orientation.

Adding an image for a new mission

Save your image as ui/assets/images/mN.png where N is the new mission index, then reference it in the ui.image field of your new mission entry. The file is served via fxmanifest's wildcard declaration and does not need to be declared manually.

Config.CooldownEnabled = true
Config.CooldownMinutes = 10

How it works

When a player successfully completes a mission, the server records a timestamp for that player + mission combination. If the player tries to start the same mission again before CooldownMinutes has elapsed, they receive a notification telling them how much time remains and the mission does not start.

Cooldowns are tracked in memory on the server — they reset if the server restarts. If you need persistent cooldowns across restarts, that would require a database integration not included in this resource.

Disabling cooldowns

Set Config.CooldownEnabled = false to remove all cooldown restrictions. Players will be able to repeat any mission immediately after completing it.

Adjusting the duration

Change Config.CooldownMinutes to any whole number. A value of 0 with CooldownEnabled = true is the same as disabling — the cooldown expires instantly. Recommended range is 5–30 minutes depending on your server's economy pace.

Mission unlock threshold — Config.CompletionsToUnlock

Config.CompletionsToUnlock = 1   -- completions of mission N needed to unlock mission N+1

This is separate from the cooldown. It controls the progression gate — how many times a player must successfully complete Mission N before Mission N+1 becomes available. The default of 1 means one completion unlocks the next mission. Set it to 3 to require three completions, and so on.

Config.Levels = {
    { threshold = 0,   level = 1 },  -- 0–49 total completions → Level 1
    { threshold = 50,  level = 2 },  -- 50–99                 → Level 2
    { threshold = 100, level = 3 },  -- 100–149               → Level 3
    { threshold = 150, level = 4 },  -- 150–199               → Level 4
    { threshold = 200, level = 5 },  -- 200+                  → Level 5
}
Config.CashBonusPerLevel = 5  -- $ added per level above 1

How it works

The server tracks a player's total completions across all missions (not per-mission). When a mission is completed, the player's level is checked against the thresholds in Config.Levels. Their level is the highest entry whose threshold is less than or equal to their total completions.

The cash bonus is calculated as (level - 1) × CashBonusPerLevel. At Level 1 there is no bonus. At Level 2 the bonus is +$5. At Level 5 the bonus is +$20 (on top of whatever the mission's base cash reward is).

Customising levels

You can add more levels, change the thresholds, or raise the bonus amount freely. Each entry needs a threshold (minimum total completions to reach that level) and a level number. Keep the entries in ascending threshold order.

Config.EnableDeathFail = true

How it works

When true, a watcher thread starts the moment a mission is approved. It runs for the entire mission lifetime — travel to the area, the ambush phase, calming the horse, and delivery — and triggers a mission failure the instant IsEntityDead returns true for the local player.

On death, the mission is cancelled server-side (same as any other failure path), all spawned enemies and the target horse are cleaned up, and the player receives an 'error' notification.

Disabling

Set Config.EnableDeathFail = false to turn the feature off entirely. No watcher thread is created and dying during a mission has no effect on its state — the mission continues when the player respawns.

Default behaviour

The resource auto-detects the running framework at startup. On RSG-Core it uses ox_lib if available, otherwise falling back to RSGCore:Notify. On VORP-Core it uses vorp:TipRight. You do not need to configure anything for either of these to work.

Notification types

Throughout the resource, notifications are called with a ntype argument. The values used are:

• 'success' — mission completed, horse calmed, delivery confirmed
• 'error' — mission failed, horse killed, cooldown active, already in a mission
• 'primary' / 'inform' — neutral information (e.g. mount the horse, return to horse)

When replacing the notification system, map these type strings to whatever your target script expects.

Structure overview

The file defines four internal setup functions — one client and one server function for each framework — and then auto-detects which framework is running to call the right one. Each setup function assigns implementations to the LRCfw table.

local function setupClientRSG()
    LRCfw.notifyLocal = function(msg, ntype, duration)
        -- ← edit this to change client notifications on RSG
    end
end

local function setupClientVORP()
    LRCfw.notifyLocal = function(msg, ntype, duration)
        -- ← edit this to change client notifications on VORP
    end
end

local function setupServerRSG()
    LRCfw.notify = function(src, msg, ntype, duration)
        -- ← edit this to change server→client notifications on RSG
    end
end

local function setupServerVORP()
    LRCfw.notify = function(src, msg, ntype, duration)
        -- ← edit this to change server→client notifications on VORP
    end
end

Example — replacing with a custom notification script

Say you use a script called my-notify that exposes a client export exports['my-notify']:Send(msg, type, duration) and a server-side client event 'my-notify:client:show'. Here is how you would swap it in:

LRCfw.notifyLocal = function(msg, ntype, duration)
    exports['my-notify']:Send(msg, ntype, duration or 5000)
end

LRCfw.notify = function(src, msg, ntype, duration)
    TriggerClientEvent('my-notify:client:show', src, msg, ntype, duration or 5000)
end

Apply the same change to both RSG and VORP setup functions if you want it consistent on both frameworks, or only edit the one that applies to your server.

Other functions in fw_func.lua

Beyond notifications, the file also wires up money and item rewards. These are framework-specific and generally do not need changing unless you use a custom inventory or economy script.

What's included

Every purchase comes with full support — installation help, configuration questions, and bug fixes. Join the Discord and open a ticket, and 1973 will get back to you directly.