Configuration
ESX Compatibility Mode
If you are using ESX and want to use your server's ESX tables directly, you can use the ESX Compatibility Mode option database.esxCompat: true.
If you are using ESX and want to use your server's ESX tables directly, you can use the ESX Compatibility Mode option database.esxCompat: true.
You must ensure that the tables and columns are the same as the ones listed below.
You should preferably use the DBSync to be independent of your gameserver's and FiveNet's database structure.
You must ensure that the collation of your database, tables and columns is the same!A difference in collation between tables can occur, e.g., when the database server has been switched. The database server defines the "default collation" used unless otherwise specified.
If the collation is not the same across at least the tables listed below, FiveNet's database migrations have a very high likely hood of failing due to that.Please see Database Basics for more information.
Tables
The below database/table structure is only needed when wanting to use your server's ESX tables directly.In case of using the dbsync, you can ignore these instructions.
jobs Table
namelabel
job_grades Table
job_namegradelabel
licenses Table
typelabel
owned_vehicles Table
owner-varchar(64) NOT NULLplatetypemodel(Optional, can be overriden viadatabase.custom.columns.vehicles.modelconfig option)
users Table
id-int(11) NOT NULL AUTO_INCREMENTidentifier-varchar(64) NOT NULLgroupfirstnamelastnamedateofbirthjobjob_gradesexheightphone_numbervisum(Optional, can be overriden viadatabase.custom.columns.user.visumconfig option)playtime(Optional, can be overriden viadatabase.custom.columns.user.playtimeconfig option)
user_licenses Table
typeowner-varchar(64) NOT NULL