[Bug] Clients Unable to Spawn Mission Entities When SetRoutingBucketPopulationEnabled is false.

[k3yomi]

Summary

When SetRoutingBucketPopulationEnabled(0, false) is applied, clients are unable to spawn networked mission entities, even though disabling population should only prevent non mission entities from spawning. (Ex. "AI" peds and vehicles)

As a side note, using CreateVehicle RPC (Server) still works as intended. Setting SetRoutingBucketEntityLockdownMode to inactive has no effect on the issue. (Works as intended)

This affects all entities including pickups, peds, objects, and vehicles.

Issue type

Both / Unsure

Repro rate

Always

Server build version

FXServer-early-access b119 win32

OS

No response

CPU

No response

GPU

No response

RAM

No response

Storage type

None

Connection type

None

ISP and bandwidth

No response

DxDiag

No response

Network graph

No response

Platform

Windows

OS version / distribution

No response

CPU

No response

RAM

No response

Using txAdmin?

Yes

Hosting provider

Self-hosted

Machine type

Dedicated

/perf endpoint output

No response

DDoS protection

No response

ulimit -n value (Linux only)

No response

Docker Compose file (Docker only)

No response

Steps to Reproduce

1. Disable population spawning using the server side native SetRoutingBucketPopulationEnabled(0, false)
2. Use CreateVehicle or equivalent on the client (netMissionEntity, isNetwork as true)
3. Enable population for that specific bucket and it will allow you to spawn it back in.

Expected Behavior

SetRoutingBucketPopulationEnabled should only control the spawning of non mission entities within the specified bucket.

See: https://docs.fivem.net/natives/?_0xCE51AC2C

Actual Behavior

Setting SetRoutingBucketPopulationEnabled to false for a routing bucket, such as bucket 0, disables all client-side entity spawning. Client side spawning should instead be controlled by SetRoutingBucketEntityLockdownMode.

Evidence

2026-08-15.08-45-18_compressed.mp4

See Additional Context for command scripts

Additional Context

This is on a base server without any third party resources besides the reproduction script

Server (Repo Test)

SetRoutingBucketEntityLockdownMode(0, "inactive") -- Making sure this is set to inactive
RegisterCommand("population", function(source, args, rawCommand)
    if (source == -1) then
        print("This command can only be used by players.")
        return
    end
    local bucketId = GetPlayerRoutingBucket(source) -- should be 0 by default if not changed
    local enabled = args[1] == "true"
    SetRoutingBucketPopulationEnabled(bucketId, enabled)
    print("Routing bucket " .. bucketId .. " population enabled: " .. tostring(enabled))
end, false)

Client (Repo Test)

RegisterCommand("spawn", function(source, args, rawCommand)
    local playerPed = PlayerPedId()
    local playerCoords = GetEntityCoords(playerPed)
    local vehicleHash = GetHashKey("adder")
    while not HasModelLoaded(vehicleHash) do
        RequestModel(vehicleHash)
        Wait(100)
    end
    CreateVehicle(vehicleHash, playerCoords.x, playerCoords.y, playerCoords.z, GetEntityHeading(playerPed), true, true)
    print("Vehicle spawned.")
end, false)

RegisterCommand("object", function(source, args, rawCommand)
    local playerPed = PlayerPedId()
    local playerCoords = GetEntityCoords(playerPed)
    local objectHash = GetHashKey("p_spinning_anus_s")
    while not HasModelLoaded(objectHash) do
        RequestModel(objectHash)
        Wait(100)
    end
    CreateObject(objectHash, playerCoords.x, playerCoords.y, playerCoords.z, true, true, true)
    print("Object spawned.")
end, false)

[wolfram-cfx]

Thanks, we are looking into this.

[WLVF]

This is still happening on server b170 with the client on early-access b167. Legacy is fine with the same scripts.

One thing I found that might help: it isn't population being off that blocks client spawning. It's a player being in the bucket when it gets switched off. Players who enter the bucket after the change are fine.

• Players in a bucket whose population was already off before they entered can spawn networked entities normally.
• If it gets switched off while the player is in the bucket (like the original repro), or in the same tick they're moved in, that player can't create networked entities in that bucket.
• That player stays stuck for as long as they're in the bucket. Every new networked entity they create is lost, even minutes later.
• Moving the player to another bucket and back clears it, even though population is still off.

When it's stuck, the client creates the entity, networks it, gets a network ID and owns it. netobjviewer shows regular Last update sent / Last sent ack times, so the server keeps acking it. But entityCreating never fires, GetAllVehicles() doesn't list it, and NetworkGetEntityFromNetworkId returns 0. Like the original post says, SetRoutingBucketEntityLockdownMode(bucket, 'inactive') doesn't help.

I've personally hit this because our race system takes a bucket, switches its population off, and moves the racers in during the same tick. So every car created for a race never reaches the server to be networked for everyone in the bucket.

Repro

/repro control moves you to a new bucket and the server prints server received entity ... for the car. /repro does the same, but switches population off on the bucket right before moving you in. The car spawns on the client, but the server never receives it.

server.lua

local nextBucket = 40000

RegisterCommand('repro', function(source, args)
    local bucket = nextBucket
    nextBucket = nextBucket + 1

    if args[1] ~= 'control' then
        SetRoutingBucketPopulationEnabled(bucket, false)
    end
    SetPlayerRoutingBucket(source, bucket)

    print(('player moved to bucket %s (%s), spawning a car'):format(bucket, args[1] or 'population off'))
    TriggerClientEvent('repro:spawn', source)
end, false)

AddEventHandler('entityCreating', function(entity)
    print(('server received entity %s in bucket %s'):format(entity, GetEntityRoutingBucket(entity)))
end)

client.lua

RegisterNetEvent('repro:spawn', function()
    local model = `adder`
    RequestModel(model)
    while not HasModelLoaded(model) do Wait(0) end

    local coords = GetOffsetFromEntityInWorldCoords(PlayerPedId(), 0.0, 6.0, 0.5)
    local vehicle = CreateVehicle(model, coords.x, coords.y, coords.z, 0.0, true, false)
    Wait(1000)

    print(('[repro] client created vehicle netId=%s'):format(NetworkGetNetworkIdFromEntity(vehicle)))
end)

Workaround

Pre-assign each bucket's population before any player enters it.

In my server, I made it so that every bucket's population is disabled at resource start, then only call SetRoutingBucketPopulationEnabled on a bucket that needs population a tick before moving players into it.

[Gogsi]

Hello,
A fix for this issue has been implemented in November 11 patch for FiveM for GTAV Enhanced. Please try again and let us know if the issue persists. Thanks for your help!