Mysticky Bridge

What it controls

The bridge owns shared framework and provider detection so product resources stay focused on gameplay.

• Framework/player access and callbacks
• Inventory and SQL adapters
• Target interactions and Mysticky TextUI
• Notifications, progress, skill checks, dialogs, and shared NUI
• Dispatch, banking, vehicle keys, fuel, multijob, and garage selection

Recommended settings

Config.Framework = 'auto'
Config.Target = 'auto'
Config.Inventory = 'auto'
Config.Notifications = 'auto'
Config.Progress = 'auto'
Config.Skillbar = 'auto'
Config.Dialog = 'auto'
Config.Dispatch = 'auto'
Config.Banking = 'auto'
Config.VehicleKeys = 'auto'
Config.FuelSystem = 'auto'
Config.Multijob = 'auto'
Config.Garages = 'auto'
Config.HideWatermark = true

Interaction modes

Every product owns its UseTarget and fallback interaction setting.

• When target is enabled, the bridge uses the selected supported target provider.
• When target is disabled, a product can use the built-in Mysticky TextUI or native 3D text where documented.
• Changing one product’s interaction mode does not change other Mysticky resources.

Startup validation

The bridge validates providers when a consumer starts and prints the resolved integration summary.

• A missing or stopped bridge prevents dependent products from starting.
• Stopped providers invalidate immediately.
• New higher-priority providers are detected after the configured provider cache window.