Additional Informations

Page dedicated to Additional Informations about our Spawn Selector [V2].

Core Features

• Cinematic Engine: Utilizes native GTA V sky-cam transitions (SwitchOutPlayer, SwitchInPlayer) for a premium feel.

• Economic Integration: Charge players money to spawn in premium or strategic locations.

• Job Restriction: Keep faction-specific spawns (like PDs, Hospitals, Gang HQs) hidden from the general public.

• Audio Ambience: Built-in music player to maintain atmosphere during the selection phase.

Developer API (Events & Hooks)

The Spawn Selector exposes specific events allowing developers to manually trigger the UI, or execute logic the exact moment a player finalizes their spawn choice.

Client-Side Trigger

If you have a custom script (such as a tutorial sequence, unique login system, or custom character selection) and want to manually open the spawn selector UI, trigger this client-side event:

-- CLIENT-SIDE
-- Opens the spawn selector UI
-- @param isNew boolean - Indicates if the player is a brand new character.
-- (Set to true to filter out features like 'last location' and paid spawns for new characters)

local isNewCharacter = false
TriggerEvent('qf_spawnselector_v2:open', isNewCharacter)

Server-Side Hook

Once the player selects a location and the cinematic sequence concludes, the script registers and handles the spawn completion. If you want other server-side resources to listen to this event, hook into this Net Event:

-- SERVER-SIDE
-- Listen for player spawn selection completion
RegisterNetEvent('qf_spawnselector_v2:playerSpawned', function(spawnId)
    local src = source -- Server ID of the player who spawned
    
    -- 'spawnId' matches the 'id' field of the selected location (or "last-location")
    if spawnId == "last-location" then
        print(("Player %s resumed from their last known coordinates."):format(src))
    else
        print(("Player %s chose to spawn at: %s"):format(src, spawnId))
    end
    
    -- Example: Set custom routing bucket or give clothing items based on spawn choice
    SetPlayerRoutingBucket(src, 0)
    
    if spawnId == "lspd_hq" then
        -- Trigger job-uniform equip logic
    end
end)

Client-Side Hook

Fired locally once the ped has been placed, collision has streamed in and the player has control. In cinematic mode it fires after the camera flight, not before it — use it to decide when your HUD may come up.

-- CLIENT-SIDE
AddEventHandler('qf_spawnselector_v2:client:playerSpawned', function(spawnId)
    -- The player is now standing in the world and is in control.
    print(("Spawned at: %s"):format(spawnId))
end)

---

Frequently Asked Questions (Q&A)

Q: The camera gets stuck in the sky and never drops down. What is wrong? A: This happens when the framework (ESX/QBCore) fails to load the player's data in time, or another script is freezing the player entity. Press F8 to check for client-side errors. Ensure your framework is fully initialized before triggering the spawn sequence.

Q: How do I remove the cinematic sky-drop effect? A: Open config.lua and set Config.UseGTASwitch = false. The UI will simply fade out, and the player will instantly teleport to their selected coordinates.

Q: How do I restrict specific spawn points to factions or jobs? A: You can configure the jobs filter inside config/default_data.lua by specifying the required job names and minimum grades. Unallowed players will not see those spawn points in the UI.