Installation

Keep the resource named finals_UI: integrations and calling scripts reference that name. Back up your selected dependencies before first installation.

1. Download and place the folder

Extract the complete purchased Cfx/Tebex asset into resources/[finals]/finals_UI/. Keep the assets, build, client, data, integrations, interaction, server and shared directories together with config.lua, fxmanifest.lua and init.lua. Retain the hidden .fxap file and all protected files in an escrowed download.

Check build/index.html and build/world/index.html. The customer package does not need an npm build or a Node.js installation.

2. Select integrations

Edit the existing table in config.lua:

Config.Installer = {
    enabled = true,
    oxLib = true,
    qbCore = false, -- true only for stock qb-core UI APIs
    esx = false,    -- true for es_extended UI APIs
    target = false -- 'auto', 'ox_target', 'qb-target', or false
}

Choose one framework adapter. Qbox generally uses ox_lib; keep qbCore=false for qbx_core. This table routes supported UI calls, not framework gameplay. HUD player-data detection is separately controlled by Config.Framework.

3. Grant selected filesystem permissions

Add only the matching lines before ensure commands in server.cfg:

add_filesystem_permission finals_UI write ox_lib
# Only when qbCore = true:
# add_filesystem_permission finals_UI write qb-core
# Only when esx = true:
# add_filesystem_permission finals_UI write es_extended
# Select your installed target, if used:
# add_filesystem_permission finals_UI write ox_target
# add_filesystem_permission finals_UI write qb-target

FiveM does not allow a resource to grant itself these permissions. Changes to server.cfg require a full server restart; a resource restart does not execute server.cfg again.

4. Start order

Start ox_lib first and Finals before resources calling its UI/chat exports. Example Qbox order:

ensure ox_lib
ensure finals_UI
ensure qbx_core
ensure ox_target
ensure [qbx]

Keep your framework's other prerequisites, such as oxmysql, before that framework. Follow the framework-specific child guide. Review old HUD/chat ensures to avoid duplicate interfaces or providers; do not stop unrelated framework essentials.

5. Complete the first installation

Watch the server console. A successful first installation prints a prominent restart instruction. Perform that full restart so patched resources load their bridges. A completion marker prevents the installer repeating on every reload.

On failure the installer reports the selected file/resource, attempts rollback and writes no success marker. Correct the cause, then run fuiinstall in the server console, or restart the server. This is not an F8 client command. Recognized stock layouts are supported; modified forks can fail preflight instead of being overwritten.

6. Verify real gameplay

• Check HUD, chat and minimap after login.
• Open /hudedit, save a preset, reconnect and check persistence.
• Trigger a real notification/menu through your selected bridge.
• Select a target/world option if configured.
• Drive, repair and switch vehicles; verify fuel, belt and holographic telemetry.
• Open/close pause, then test its links and update cards.

Config edits require a resource restart. Filesystem permissions and first-time patched integration loading require the full restart above. See Troubleshooting if old UI remains.