Vcore-doorlocks
Business door groups are linked to the business job configured in Config.AuthGroups. Doorlocks reads the current owner CSN from the live business record, so door access updates automatically when a new owner is set in-game. doorconfig.lua assigns the door group's authGroup. The matching entry in config.lua contains the business jobs value and may also contain an owners list. The owners list is a fallback. Keep it updated when possible because any CSN listed there can receive access if the linked business record is unavailable. It should not be treated as the primary source of business ownership. Example: In this example, flowcustoms is the door authorization group and flowc is the business job name. The job name must exactly match the business created
Introduction
Business door groups are linked to the business job configured in Config.AuthGroups. Doorlocks reads the current owner CSN from the live business record, so door access updates automatically when a new owner is set in-game. doorconfig.lua assigns the door group's authGroup. The matching entry in config.lua contains the business jobs value and may also contain an owners list. The owners list is a fallback. Keep it updated when possible because any CSN listed there can receive access if the linked business record is unavailable. It should not be treated as the primary source of business ownership. Example: In this example, flowcustoms is the door authorization group and flowc is the business job name. The job name must exactly match the business created
No manifest UI page detected.
Dependencies & References
| Resource | Type | Package status |
|---|---|---|
core | Manifest dependency | Included in Base |
inventory | Manifest dependency | Included in Base |
oxmysql | Manifest dependency | External / prerequisite |
polyzone | Manifest dependency | Included in Base |
garages | Referenced resource | Included in Base |
logs | Referenced resource | Included in Base |
multichar | Referenced resource | Included in Base |
utils | Referenced resource | Included in Base |
Cross-resource export calls
| Resource | Functions called |
|---|---|
core | getCoreObject |
garages | RegisterGarageAccessProvider |
inventory | GetPlayerItems, OpenStash, RemoveItemAtSlot |
logs | Log |
multichar | RegisterCaseFileSpawnProvider |
utils | RegisterAdminAction |
Installation / Start Order
Install the resource with its required dependencies, then enable it in your resource start order.
ensure doorlocksConfiguration
Config files
config.luadoorconfig.lua
Top-level config keys
AuthGroupsDoorsSettingsEvents, Exports & Callbacks
Exports
Client exports1
IsNearLockpickableDoor
Server exports6
ExecuteUtilsAdminActionGetBusinessSpawnPointsGetDoorStateHasAccessSetDoorStatehasGarageAccess
Callbacks
Server callbacks2
doorlocks:server:canUsedoorlocks:server:getAccess
Registered network events
Client registered events4
doorlocks:client:inspectNearestdoorlocks:client:interactionAccepteddoorlocks:client:lockpickResultdoorlocks:client:useLockpick
Server registered events6
doorlocks:server:completeLockpickdoorlocks:server:grantAccessdoorlocks:server:openStashdoorlocks:server:openWardrobedoorlocks:server:revokeAccessdoorlocks:server:toggle
Commands
Client commands2
+-
Database / SQL
| File | Type |
|---|---|
sql/doorlocks.sql | Resource SQL file |
sql/legacy-doorlocklocations.sql | Resource SQL file |
doorlock_accessdoorlock_statesVcore also includes the consolidated VCORE_INSTALL.sql.
Source Layout
| Area | Files |
|---|---|
| Client Lua | 5 |
| Server Lua | 7 |
| Other/shared Lua | 4 |
| JavaScript | 0 |
| HTML | 0 |
| CSS | 0 |
| SQL | 2 |
Troubleshooting
- Confirm all manifest dependencies are started before
doorlocks. - Confirm the resource is enabled in the correct start order.
- If database queries fail, import the consolidated Base SQL and any resource-local SQL listed above.
- If the UI fails, verify the resource's NUI files and
ui_pagewhen one is declared.