Getting started

Before you install

Download purchased resources from the Cfx.re Portal. Extract each folder without renaming it.

• Confirm your framework and core providers are already running.
• Keep mysticky_bridge and each purchased resource in your resources directory.
• Back up your server configuration and database before adding a new production resource.

Start order

Providers must start before the bridge. Mysticky gameplay resources start after it.

ensure es_extended # or qb-core / qbx_core
ensure ox_inventory # or your supported inventory
ensure oxmysql # or your supported SQL provider
ensure ox_target # optional when target use is disabled

ensure mysticky_bridge
ensure mysticky_drugsystem
ensure mysticky_carrental
ensure mysticky_printer
ensure mysticky_robnpcs

Configure the bridge

Open mysticky_bridge/config.lua. The default auto values detect running supported providers. Use explicit resource names only when you need to override detection.

• Framework, inventory, target, SQL, notifications, progress, dialogs, dispatch, banking, vehicle keys, fuel, multijob, and garages are centralized here.
• Set Config.HideWatermark globally for built-in Mysticky interfaces.
• Leave BridgeConfig.Debug false in production unless support asks for logs.

Configure your product

Edit only the documented configuration files in the resource. Do not edit protected runtime logic.

• Printer: config.lua and its installation item definitions.
• Drug System: the split shared/config.*.lua files.
• Car Rental: shared/config.lua, shared/config.carrent.lua, and shared/config.starterpack.lua.
• Rob NPCs: config.lua plus the ziptie and scissors definitions in [install].

Restart and verify

Restart the bridge, then the changed product. Read the complete server console summary and test with a non-admin character.

• Check the interaction appears at the configured location.
• Verify required items exist in the selected inventory.
• Test payment, reward, job, and database behavior before opening to players.