[PAID] [VORP/RedEM:RP/Any] Multiplayer Bounty Hunt + Party system by Ren

d4ff0b9310fbcd6a7b9758be4b3437805a2729dc

Video: [VORP/REDEM/Any] Multiplayer Bounty Hunt + Party script - YouTube
Buy bounty & party script (40€): here
Buy just party script(20€): here

A fully functional solo & multiplayer bounty hunt script along with a party HUD system.
Give your players the ability to go on exciting bounty hunts with their friends and reap the rewards.

Features:

  • Solo & Multiplayer bounty hunt missions.
  • Fully configurable missions, add as many as you want (with as many enemies as you want), the script picks one randomly and two groups cannot have the same mission at the same time.
  • Both scripts are fully standalone and can be used with ANY framework (vorp/redem:rp etc)
  • Really good performance (0.01ms inactive).
  • Party HUD + party member nametag with distance.
  • Fully controllable party system (kick members, lock group, disband, leave etc).
  • Extensive and well written config file. You can choose to disable HUD permanently, enable it before missions, after missions, pick the bounty boss peds etc.
  • Lifetime support + requests for future features.
  • Ability to buy JUST the party system without the bounty system for a smaller price.

Dependencies:

  • Warmenu by warxander (included in the script files, don’t need to do anything)

Config file:

--Missions can not be edited on the fly while in play these settings are predetermined!
--This scripts comes with a missions I made in Armadilo but it is best to remove it in order
--to ensure the locations you choose will not conflict server's establishments as well as
--NPC models to fit the asthetics of your composed environment for increased immersion!

--Basic table structure must be applied
--Table key will distribute values to appropriate mission
--consider this as [1] equals for Mission 1, [2] will equal for Mission 2 and so on...
--with this structure you can build as many missions as you like

--DO NOT forget to leave empty keys to avoid snails
--for example if you have Radius[1] = 200.0 then BossModelHash[1] must not be skipped
--Comma ` , ` next to a value separates Missions


--This Event Handler will trigger the ammount of set reward
AddEventHandler('PassRewards', function (PlayerIDs, MissionNumber, DeadOrAlive)
    local unpack = PlayerIDs
    local reward = Config.Mission.Reward[MissionNumber]
    local boolean = DeadOrAlive --true euqals Alive // false equals Dead
    for id,player in pairs(unpack) do
        --Trigger your reward for each player ID that successfully completed a bounty
        --it is advised to remove my demo 'sendmessage' Event
        if boolean then
            TriggerServerEvent('sendmessage', unpack[id], reward.Alive)
        else
            TriggerServerEvent('sendmessage', unpack[id], reward.Dead)
        end
    end
end)

--This will be your fuction to return the player's in-game name instead of Steam's
--for this custom HUD it is advised not skip this function since it's a core element
--it reflects server side; should not be used for client side scripting
PlayerName = function(ID)
    return GetPlayerName(ID) --chenage this native
end

Config = {}

--Toggle this feature for anyone in the server; Group system is a core element of this script
--anyone who interacts with the bounty prompt will eventually have access to it
Config.GroupSystem = true

--This will toggle display HUD components
--it will always display HUD if players are in mission
Config.DisplayHUD = true

--The locations for the player to interact with a prompt in order to browse the menu
Config.SignPosters = {
    vector3(-3627.91, -2608.8, -13.73)
}

--The locations for the player to deliver his/her bounty
Config.Prisons = {
    vector3(-3619.88, -2605.13, -13.33),
    vector3(-3621.31, -2601.04, -13.34)
}

--Leave this empty
Config.Mission = {}

-----------------------------------------------------------------------------------------------------
--Reward[1][1]/Reward[1][2] = will be your set ammount of reward for each mission 
--depending on difficulty you created and from a dead or alive status
Config.Mission.Reward = {
    {
        Alive = 'Nothing to collect except justice',
        Dead = 'Nothing to collect except vigilance'
    }
}

--Radius[1] = distance before triggering event, map blip will always be slightly larger
Config.Mission.Radius = {
    200.0
}

--DistanceFromTarget[1] = distance in which players must not surpass and are way outside of target's reach
Config.Mission.DistanceFromTarget = {
    400.0
}

--BossModelHashes[1] = model hash variation
Config.Mission.BossModelHashes = {
    'U_M_M_BHT_BANDITOMINE'
}
--EnforcementsModelHashes[1] = model hash variation
Config.Mission.EnforcementsModelHashes = {
    'G_M_M_UniBanditos_01'
}

--BossWeaponHash[1] = weapon name
Config.Mission.BossWeaponHash = {
    'WEAPON_REPEATER_CARBINE'
}
--EnforcementsWeapon[1] = weapon name
Config.Mission.EnforcementsWeaponHash = {
    'WEAPON_REPEATER_CARBINE'
}

--BossCombatAbility[1] = 1/2/3 Poor/Avarage/Pro
Config.Mission.BossCombatAbility = {
    3
}
--EnforcementsCombatAbility[1] = 1/2/3 Poor/Avarage/Pro
Config.Mission.EnforcementsCombatAbility = {
    1
}

--BossSeeingRange[1] = 100.0 must be float
Config.Mission.BossSeeingRange = {
    200.0
}
--EnforcementsSeeingRange[1] = 100.0 must be float
Config.Mission.EnforcementsSeeingRange = {
    200.0
}

--BossHearingRange[1] = 80.0 must be float
Config.Mission.BossHearingRange = {
    140.0
}
--EnforcementsHearingRange[1] = 80.0 must be float
Config.Mission.EnforcementsHearingRange = {
    140.0
}

--ETC
--AreaCoordinates[1] = destination for mission 1 (will blip)
Config.Mission.AreaCoordinates = {
    vector3(-3963.87, -2145.29, -5.62)
}

--vector4
--(x, y, z, Heading)
-----------------------------------------------------------
--ETC
--BossCoordinates[1] = spawn the target for mission 1
Config.Mission.BossCoordinates = {
    vector4(-3969.61, -2135.47, -5.53, 144)
}

--ETC
--EnforcementsCoordinates[1][1] = spawn npcs for mission 1
Config.Mission.EnforcementsCoordinates = {
    {
        vector4(-3974.17, -2134.77, -5.82, 208),
        vector4(-3967.73, -2138.78, -5.43, 78),
        vector4(-3969.69, -2141.18, -5.58, 32),
        vector4(-3972.24, -2142.12, -5.70, 349),
        vector4(-3974.50, -2141.00, -5.75, 302),
        vector4(-3968.42, -2156.00, -6.63, 132),
        vector4(-3970.76, -2152.35, -6.51, 134),
        vector4(-3970.52, -2148.41, -6.25, 127),
        vector4(-3975.39, -2146.93, -6.16, 163),
        vector4(-3979.29, -2147.01, -6.35, 170),
        vector4(-3961.42, -2151.94, -5.68, 47),
        vector4(-3962.72, -2148.59, -5.78, 175),
        vector4(-3959.19, -2149.26, -5.46, 98),
        vector4(-3961.23, -2144.30, -5.40, 102),
        vector4(-3956.99, -2145.85, -5.33, 67),
        vector4(-3959.67, -2136.69, -4.97, 342),
        vector4(-3958.46, -2132.50, -4.64, 180),
        vector4(-3962.10, -2130.31, -4.84, 177),
        vector4(-3966.31, -2134.09, -5.26, 203),
        vector4(-3969.00, -2127.25, -5.30, 62),
        vector4(-3968.96, -2117.11, -5.11, 340),
        vector4(-3973.94, -2121.92, -5.61, 43),
        vector4(-3979.63, -2132.03, -5.85, 210),
        vector4(-3983.03, -2137.44, -6.40, 102),
        vector4(-3985.82, -2143.15, -6.44, 139)
    }
}
1 Like

Absolutely NO support for the script, no updates, no accessible config for translations. I’ve been waiting since the end of december for support in the ticket and i got absolutely NO replies. Horrible

1 Like

OP request