Troubleshooting Guide

Solutions for common issues and error messages.

Error Codes

Info

If you encounter an error code not listed below, please open a support ticket in the Codesign Discord for assistance.

Server

7854 - You are pressing E to interact with a door, but no doors are nearby. It's possible you are out of range of the door, so get closer.

3001 - You are pressing E to interact with a door, but no doors have been created/imported yet.

Client

4387 - You are pressing E to interact with a door, but your job/identifier does not match the job/identifier required to interact with this door.

7854 - You are pressing E to interact with a door, but no doors are nearby.

3001 - You are pressing E to interact with a door, but no doors have been created/imported yet.

---

Common Issues

Please check out our Self Debugging Guide before contacting our support.

🔔 Folder Name Make sure the name of the folder is cd_doorlock.

🔔 Encrypted Files Do not edit the encrypted files in any way.

Can't select a new door to add?

Example: If you try to create a new door, the target eye icon appears but the door does not highlight.

Reason: This is common with garage doors or gates. The door is either larger or smaller than the default set Config.DoorValidationDimensions.

Solution: Edit the minimum and maximum values used for door detection.

If you enable Config.Debug, the system will display the actual size of the door you are looking at in F8. Use these values to correctly adjust the min and max settings for accurate detection.

F8 prints with Config.Debug enabled.

A simpler option is to just set all the min to 0.0 and all the max to 20.0. But the target system will think every object is a door while creating new doors.

Config.DoorValidationDimensions = {
    normal = {
        max_height = 20.0,
        min_height = 0.0,

        max_width = 20.0,
        min_width = 0.0,

        max_depth = 20.0,
        min_depth = 0.0,
    },

    garage = {
        max_height = 20.0,
        min_height = 0.0,

        max_width = 20.0,
        min_width = 0.0,

        max_depth = 20.0,
        min_depth = 0.0,
    },

    gate = {
        max_height = 20.0,
        min_height = 0.0,

        max_width = 20.0,
        min_width = 0.0,

        max_depth = 20.0,
        min_depth = 0.0,
    }
}

All Config.AdminAccess options disabled

Example: By default, all of the admin access options inside Config.AdminAccess, such as the Identifiers, AcePerms & Discord are set to false.

Reason: You need to enable at least 1 of these to allow admins to create new doors.

Solution: Enable at least 1 methods in Config.AdminAccess.

On the UI only 2 tab’s are showing not 6? (no admin perms)

Example: You are an admin but only the Control and Settings tab are visible on the UI; but it should show all 6 tabs (Create/Edit, Control, Import, Export, Convert & Settings). So you are unable to create new doors or import doors.

Reason: This is because you don’t have admin permissions set up correctly on your server. There could be multiple reasons for this.

1. The Config.AdminAccess in the config.lua has not been configured correctly for your server.

2. If you use ESX, QBCORE or QBOX your players permissions are set up incorrectly through your framework.

3. If you are using the Standalone framework option, and you have enabled Ace Perms; the ace perms are most likely not set up correctly in your server.cfg. To confirm this is the issue you can change the script to use the "command" ace perm and if the doors work then this is your issue, as the "command" ace perm gives every player access.

4. If you are using the Standalone framework option, and you have enabled Discord Perms; badger discord perms is required and it must be named [Badger_Discord_API].

Solution: If you are not able to figure it out from the above options open a ticket on discord.

New doors don’t save (using ZAP-Hosting)?

Example: If you use ZAP-Hosting, and you create new doors but they don’t save after a script/server restart.

Reason: This is because data is not being written to JSON file’s due to permission issues. (Only for people using zap-hosting).

Solution:

1. Stop the server.

2. Move the files to your server using filezilla or winscp.

3. Set the permissions for all JSON files to read write and execute for owner, group and user - https://www.pipeten.com/support/scripting/changing-file-permissions-using-filezilla/.

4. Then start the server.