Search Results

Network Admin The first active account in a new installation receives the global network_admin role. Network administrators can access platform-level administrative functions such as: Platform overview Maintenance mode User administration Workspace administra...

Maintenance & Backups Nord Forge includes platform maintenance and backup functionality. Maintenance mode When maintenance mode is enabled, normal users can be blocked from logging in while network_admin users retain administrative access. Backups The admin a...

Customer Troubleshooting Product is not in My Products Check that: The purchase or grant completed successfully. The license is active. You are signed into the correct Nord Forge account. Resource says server is not registered Add the server's sv_licenseKey i...

Developer Troubleshooting Product cannot be published A published release with a file is required. Create the release first, then publish the product. Release cannot be created Every release upload requires a file. Customer has a valid Forge Key but the produc...

Production Checklist Use this checklist before releasing Nord Forge publicly. Platform Change NORD_FORGE_SECRET. Change NORD_FORGE_CRYPTO_SECRET. Configure the public HTTPS URL. Configure database/storage paths. Verify backups. Verify reverse proxy and SSL. ...

FiveM Integration Quick Reference Required customer configuration setr nord_license "FG-XXXX-XXXX-XXXX-XXXX" setr nord_keymaster "cfxk_xxxxxxxxxxxxxxxxx" sv_licenseKey "cfxk_xxxxxxxxxxxxxxxxx" Register the server Before starting a protected product: Customer P...

Nord Vehicle Keys is a server-authoritative vehicle access system for FiveM. It combines physical vehicle keys, vehicle locking, theft gameplay, temporary stolen keys, recovery NPCs and a modular bridge layer for frameworks, inventories and UI providers. Main ...

Requirements Requirement Status FiveM server Required OneSync Required for authoritative entity checks oxmysql Required when persistence/ownership tables are used QBCore / QBX / ESX Optional nord_inventory Recommended for native physical-key metadata ox_invent...

After installation, verify these points before opening the server to players. oxmysql is started before Nord Vehicle Keys. The selected framework bridge is detected correctly. The selected inventory bridge is available. OneSync is enabled. No SQL or Lua errors...

The resource is intentionally split so integrations can be changed without editing the core logic. nord_vehiclekeys/ ├─ config/ │ ├─ bridges.lua │ └─ main.lua ├─ client/ │ ├─ bridge/ │ │ ├─ framework.lua │ │ ├─ inventory.lua │ │ ├─ notify.lua │ │ ├─...

The primary configuration file is: config/main.lua Common options: Config.Debug = false Config.Locale = 'en' Config.Keybinds = { Lock = 'L', Hotwire = 'H' } Distances are controlled separately: Config.Distances = { ToggleLock = 18.0, Action = 7...

Physical-key behaviour is configured under Config.PhysicalKeys. Config.PhysicalKeys = { Enabled = true, Item = 'vehicle_key', SyncWithAccess = true, ItemGrantsAccess = true, RequirePhysicalItemForAccess = true, OwnerAccessWithoutPhysic...

Using a physical vehicle_key can open the built-in vehicle remote. Config.PhysicalKeys.Remote = { Enabled = true, Range = 25.0, RefreshMs = 250, AllowTrunk = true, CloseOnAction = false, TrunkDoors = {}, } The remote supports: Lock Unl...

Key sharing Config.ShareKeys = { Enabled = true, AllowReshare = false, DefaultDurationSeconds = 3600, PersistTemporaryKeys = true, } Player commands: /givekey [server id] /revokekey [server id] The player must use the current vehicle or a nearb...