Installation

Follow these steps to add Navix to your server. The app installs like any lb-phone app, inside the [phone] folder of your resources.

Prerequisites

Item	Detail
lb-phone	Required, installed and working
ox_lib	Required
oxmysql	Required (data persistence)
OneSync	Must be enabled on the server

WARNING

Navix uses OneSync to detect nearby players and broadcast alerts to them. Without OneSync enabled, alert sharing will not work correctly.

1. Add the resource

Place the lo_navix folder in resources/[phone]/:

resources/
└── [phone]/
    └── lo_navix/
        ├── fxmanifest.lua
        ├── shared/
        │   ├── config.lua
        │   └── utils.lua
        ├── client/client.lua
        ├── server/server.lua
        ├── locales/          ← 25 language files
        └── ui/
            └── dist/         ← pre-built interface

2. Start order

In server.cfg, start Navix after its dependencies:

ensure oxmysql
ensure ox_lib
ensure lb-phone
ensure lo_navix

WARNING

If lo_navix starts before lb-phone, the app will not register in the phone. Respect the order: oxmysql → ox_lib → lb-phone → lo_navix.

3. Database

The schema is created automatically on first start through oxmysql — no manual action is required. Navix creates all of its tables (user preferences, favorites, recent searches, alerts, confirmations and cooldown tracking), along with the necessary indexes.

NOTE

Tables are prefixed with phone_navix_. The system also handles automatic cleanup of expired data and a server-side cache to limit queries.

4. Interface (UI)

The interface is already built: the ui/dist/ folder is provided and served to the phone by fxmanifest.lua. No compilation is required to use the app.

TIP

There is nothing to do here in the standard case: the shipped UI is ready to use.

Verification

1. Start the server (or ensure lo_navix on the fly).
2. Check the console: the phone_navix_* tables should be created without error on first launch.
3. On the in-game phone, open the App Store: Navix should appear there, ready to be downloaded.
4. Install it, run a test navigation and report an alert to validate real-time sharing.

Once installation is validated, fine-tune the behavior via the Configuration.