So I installed esx_doorlock and added some doors. They are not lockable tho. Do I have to start esx_doorlock before or after something special? Or Am I missing something important?
Btw I am mostly talking about doors from addon buildings like Benny´s and new PD.
you must add the doors to the config for them to be lockable and unlockable without that the script is dormant until you add some names of models of doors
So since i am using codewalker to get all the coords the heading and hashes are written there. I think then I dont need that script. Point is, how exactly do I have to put heading and the hash in the config? You mean the doorlock config not server config, correct?
Yes Doorlock config i should have specified that
and personaly i use esx-community’s doorlock and it works like a charm if i need to add a door i just do /idgun get the object hash and coods/heading and add it to the config like so no need for programs all done ingame so it makes it much faster
Config.DoorList = {
--
-- Mission Row First Floor
--
-- Entrance Doors
{
textCoords = vector3(434.7, -982.0, 31.5),
authorizedJobs = {'police'},
locked = false,
maxDistance = 2.5,
doors = {
-- if u wanna use model names
{objHash = GetHashKey('v_ilev_ph_door01'), objHeading = 270.0, objCoords = vector3(434.7, -980.6, 30.8)},
--if u wanna use object hashes
{objHash = 1417577297, objHeading = 270.0, objCoords = vector3(434.7, -983.2, 30.8)}
}
},
}
Btw where is your doorlock located? Mine is in an extra “ESX” folder and i have an extra ESX.cfg but i really dont think thats the problem since i pushed it directly into resources and didnt work either