Liam Dormon

I think it would be easier if you seperated all of your changes onto different branches in seperate pull requests, you've added vehicle bone stuff, some other player job changes...

@harryfen this is expected behaviour. It doesn't trigger events with arguments.

If you restart the bt-target resource before your host resource (the one with the exports) this should destroy the zone.

Show the full error, and show where you're calling the export, you've probably not configured properly.

That sounds like an ESX issue then.

https://github.com/brentN5/bt-target/blob/dd22aa78bc22479c82e8f7750896ec4fd9d12b64/bt-target/client/main.lua#L19 If you're using ESX and you have Config.ESX enabled then this will fetch your job, if it doesn't use a different version of ESX. If it still doesn't work...

I think it's better practice to just secure your events, this won't stop a hacker with an executor from exploiting it. Add server side callbacks to all of your events...

Don't do it in a while true loop, every time you interate your config you're overwriting the polyzone. Try changing the name to "abrirTaquilla"..i, you're also using a table for...

> The thing is that it works, but not everytime :/ You're doing it completely wrong. You only need to loop once, you can't have two poly zones with the...

Just keep it as ```lua for k, vin pairs(Config.PoliceStations) do for i = 1, #v.Cloakrooms, 1 do name = "Cloakrooms"..i exports["bt-target"]:AddBoxZone(name, vector3(v.Cloakrooms[i].x, v.Cloakrooms[i].y, v.Cloakrooms[i].z), 0.5, 2.0 { name = name,...