Installation

1. Download and extract DevMateCopy Anchor Link

Download the latest DevMate release from your Big Daddy Scripts account. Extract the archive into your server's resources directory.

The resource folder must be named exactly DevMate:

resources/
└── DevMate/
    ├── fxmanifest.lua
    ├── config.jsonc
    └── permissions.cfg

2. Add your license keyCopy Anchor Link

Open DevMate/config.jsonc and replace the placeholder in LicenseKey with the key from the Licenses section of your Big Daddy Scripts account.

{
  "$schema": "./schemas/config.schema.json",
  "ConfigVersion": 2,
  "MenuCommand": "devmate",
  "LicenseKey": "paste-your-license-key-here",
  // Keep the remaining settings from the included file.
}

Keep the license key private. Do not paste it into support messages, screenshots, or a public repository.

3. Update server.cfgCopy Anchor Link

Add the permissions file at the very top of server.cfg, before all other lines:

exec @DevMate/permissions.cfg

Then add DevMate to the resource startup section:

ensure DevMate

The bundled permissions file lets DevMate run the server commands used by Resource Manager and loads the generated filesystem rules used by Resource Explorer.

4. Give yourself accessCopy Anchor Link

DevMate enables permission checks by default. The included configuration defines admin, developer, and tester groups. Assign your FiveM identifier to one of them in server.cfg:

add_principal identifier.license:YOUR_LICENSE_IDENTIFIER group.admin

Replace the example identifier with your own. You can use any principal setup supported by FiveM; the group name only needs to match a group in config.jsonc.

See Configuration before granting Resource Explorer or Code Executor access.

5. Start the serverCopy Anchor Link

Start or fully restart the server. After DevMate reports that license validation passed, join the server and run:

/devmate

If the menu does not open, work through Troubleshooting.

Updating from v1Copy Anchor Link

We recommend a full wipe of the existing DevMate installation when updating from v1. Do not copy v2 over the existing resource or reuse the v1 configuration files.

1. Stop the server.
2. Remove the existing DevMate folder from your server's resources directory.
3. Extract a clean copy of the v2 DevMate folder into the resources directory without renaming it.
4. Configure v2 using the new config.jsonc file included with the resource.
5. Add exec @DevMate/permissions.cfg at the very top of server.cfg, before all other lines.
6. Confirm that ensure DevMate is present in the resource startup section.
7. Start the server, review the licensing messages in the server console, and verify your permission groups before allowing anyone to use the menu.

With AutomaticUpdates enabled, future resource updates are downloaded and verified automatically. Restart DevMate or the server when the console says an update was installed.