You cannot download it yet: Blixye's FiveM framework, phone included, has not been released. This guide explains how it installs for when it is.
You cannot download it yet: Blixye's FiveM framework, phone included, has not been released. This guide explains how it installs for when it is.
NOTE
You cannot download it yet: Blixye's FiveM framework, phone included, has not been released. This guide explains how it installs for when it is.
On FiveM, Blixye is its own framework (core, characters, inventory, HUD, shops, garages, admin panel…) with the Blixye phone inside the game. It does not install on top of ESX or QBCore: it replaces them, and ships bridges so scripts written for them keep working untouched (ESX, QBCore and target bridges). The phone (blixye_telefono) needs the framework core: it does not run on its own on an ESX or QBCore server.
On FiveM, Blixye is its own framework (core, characters, inventory, HUD, shops, garages, admin panel…) with the Blixye phone inside the game. It does not install on top of ESX or QBCore: it replaces them, and ships bridges so scripts written for them keep working untouched (ESX, QBCore and target bridges). The phone (blixye_telefono) needs the framework core: it does not run on its own on an ESX or QBCore server.
NOTE
On FiveM, Blixye is its own framework (core, characters, inventory, HUD, shops, garages, admin panel…) with the Blixye phone inside the game. It does not install on top of ESX or QBCore: it replaces them, and ships bridges so scripts written for them keep working untouched (ESX, QBCore and target bridges). The phone (blixye_telefono) needs the framework core: it does not run on its own on an ESX or QBCore server.
Requirements
Requirements
NOTE
Requirements
NOTE
FXServer with OneSync on: several core features do not work without it.
MariaDB 10.9 or newer, with an empty database. The framework is tested against MariaDB 11.4.
oxmysql, started before anything from Blixye.
For the phone: a server created in Blixye and a game key for it (Game key and scopes).
Installation
Installation
NOTE
Installation
NOTE
Copy the resources/[blixye] folder into your server's resources.
Put the database connection and the ensure lines below, in that order, in your server.cfg (The server.cfg).
Start it. Migrations apply themselves when the core starts: there is no .sql to import by hand.
set mysql_connection_string "mysql://user:password@localhost/blixye?charset=utf8mb4"
ensure oxmysql
ensure blixye_loadscreen
ensure blixye_config
ensure blixye_lib
ensure blixye_core
ensure blixye_ui
ensure blixye_inventory
ensure blixye_hud
ensure blixye_admin
ensure blixye_characters
ensure blixye_aspecto
ensure blixye_store
ensure blixye_garage
ensure blixye_concesionario
ensure blixye_mapas
ensure blixye_jefe
ensure blixye_telefono
ensure skinchanger
ensure esx_skin
ensure qb-clothing
ensure es_extended
ensure qb-core
ensure blixye_target
ensure qb-target
ensure ox_target
set onesync on
set mysql_connection_string "mysql://user:password@localhost/blixye?charset=utf8mb4"
ensure oxmysql
ensure blixye_loadscreen
ensure blixye_config
ensure blixye_lib
ensure blixye_core
ensure blixye_ui
ensure blixye_inventory
ensure blixye_hud
ensure blixye_admin
ensure blixye_characters
ensure blixye_aspecto
ensure blixye_store
ensure blixye_garage
ensure blixye_concesionario
ensure blixye_mapas
ensure blixye_jefe
ensure blixye_telefono
ensure skinchanger
ensure esx_skin
ensure qb-clothing
ensure es_extended
ensure qb-core
ensure blixye_target
ensure qb-target
ensure ox_target
set onesync on
NOTE
set mysql_connection_string "mysql://user:password@localhost/blixye?charset=utf8mb4"
ensure oxmysql
ensure blixye_loadscreen
ensure blixye_config
ensure blixye_lib
ensure blixye_core
ensure blixye_ui
ensure blixye_inventory
ensure blixye_hud
ensure blixye_admin
ensure blixye_characters
ensure blixye_aspecto
ensure blixye_store
ensure blixye_garage
ensure blixye_concesionario
ensure blixye_mapas
ensure blixye_jefe
ensure blixye_telefono
ensure skinchanger
ensure esx_skin
ensure qb-clothing
ensure es_extended
ensure qb-core
ensure blixye_target
ensure qb-target
ensure ox_target
set onesync on
Why that order
Why that order
NOTE
Why that order
NOTE
oxmysql has to answer before blixye_core runs its migrations.
blixye_config goes before the core, which is what reads it.
blixye_ui goes before any screen: if it starts later, screens come up unstyled and without any error.
The phone goes after the core, which it depends on.
The bridges (skinchanger, esx_skin, qb-clothing, es_extended, qb-core, qb-target, ox_target) go after the core and before any third-party script: your ESX or QBCore scripts go last.
Checking the phone connects
Checking the phone connects
NOTE
Checking the phone connects
On start, blixye_telefono says in the console what it is missing. If none of these warnings show up, the key is set correctly:
On start, blixye_telefono says in the console what it is missing. If none of these warnings show up, the key is set correctly:
NOTE
On start, blixye_telefono says in the console what it is missing. If none of these warnings show up, the key is set correctly:
NOTE
«Falta la convar blixye_game_token»: there is no key in server.cfg; nobody will be able to open the phone.
«Blixye no contesta a la llave»: the key is not valid or the API does not answer; it retries every 30 seconds.
«La llave no tiene players.session»: the phone scope is missing.
«La llave no tiene jobs.read»: jobs stay with the framework, not with Blixye (Jobs).