Skip to main content
Get Jaksam Identity up and running on your FiveM server.

Requirements

The script creates and updates its own database tables on start. Back up your database before installing and before every update.

Install the resource

There is one version for ESX and one for QBCore and Qbox (it finds out which of the two runs). Take the one for your framework.
1

Download Jaksam Identity

Download the ESX version and extract the jksm_identity folder into your server’s resources folder.
2

Configure server.cfg

Start it after everything it needs, for example:
3

Database

Nothing to do: the tables are created and updated on start (jksm_identity_schema holds the version).install/install.sql is only for databases where the script is not allowed to create tables.
4

Add the items

Add the items to your inventory, see Add the items below.
5

config/main.lua

  • Config.Bridge: inventory ('jaksam' or 'ox_inventory'), notifications ('esx' or 'ox_lib'), phone ('roadphone' or 'none') and menus
  • Config.Locale: 'en' or 'de'
  • Config.AdminGroups / Config.AdminAce: who may use the admin command
  • Config.Debug = false on a live server
esx_dmvschool: its event esx_dmvschool:addLicense is not checked on the server, so a cheating client can grant itself any licence with it. Jaksam Identity trusts the licences in the database and, with Config.DmvSchool on, issues the driver licence after that event. Secure the event in esx_dmvschool, or set Config.DmvSchool.enabled = false, on a live server.

Add the items

1

Add the item entries

Add the entries of install/jaksam_items.lua to jaksam_inventory_data/items.lua, inside the table after return { }.
2

Add the item types

Copy install/jaksam_item_types.lua as it is to jaksam_inventory_data/_data/jksm_identity.lua. It adds the right-click actions View, Show and Copy number. Nothing to paste: files in that folder survive inventory updates.
3

Copy the images

Copy install/images/*.webp to jaksam_inventory_data/_images/.
4

Restart the inventory

Restart jaksam_inventory once.
See Items from shops or admin gives for the metadata block every document item must keep.

Items from shops or admin gives

When the script issues a document it passes the metadata itself. When a document item comes into existence another way (a jaksam shop, an admin give), the metadata templates fill it. The entries in install/jaksam_items.lua already carry this block, keep it on every document item:
The templates are registered on start and again whenever jaksam_inventory restarts. A template-made document is registered (real), unless its jaksam rarity is listed in Config.UnregisteredRarities (default illegal).

Configure

1

config/documents.lua

The document types, their items, validity and themes. Any licence your framework knows can become a document: add the item and one entry here. See Documents and register.
2

config/office.lua

The starter documents (Config.Starter, by default the ID card) and the citizen offices (Config.Offices): places, NPC models, which documents each office handles, fees, cash or bank. See Citizen offices.
3

config/forgery.lua

List the forgery workshops in Config.Forgery.workshops (entrance outside, price, the jobs that may own it), or add them in game with /documents config. No workshop is configured out of the box: the forgery side stays invisible until you add one. See Forgery workshops.
4

config/raid.lua

The forces that raid workshops (your police jobs, from which rank) and where the evidence locker of each force stands. Without a locker nothing can be seized. Config.Raid.enabled = false turns raids off. See Raids.
Most of these settings, places included, can be changed in game with /documents config, without editing files or restarting. See Settings in game.

Verification

Start the server and read the console. A missing resource or a bridge without a file is named in red. No red line means the start checks passed (with Config.Debug = true it also prints start checks passed). In game, open /documents as an admin: without a subcommand it lists all the available ones.