Skip to main content
1

Add to 'resources' directory

Extract the lation_interact zip folder directly into the root resources directory of your server.
Do not place this resource in a [subfolder] - it should be placed directly in the root.
2

Update server.cfg

Open your server.cfg and add ensure lation_interact after your framework core, and before your inventory and every resource that uses targeting - it reads the framework for job and item checks, and your inventory and any script that registers targets check at their own start whether a target resource is running, so lation_interact must already be started when they start.If you use Modern UI, lation_ui goes first of all - before ox_lib - and the interaction layer picks up your theme from it. This is optional - lation_interact runs standalone without it.
Starting lation_interact before your framework core throws No such export GetPlayerData errors on join - the framework’s exports don’t exist yet.
Starting ox_inventory before lation_interact makes ox_inventory switch its own target integration off, with an ox_target is not loaded warning - its shops, stashes, evidence lockers, dumpsters and trunks fall back to markers until the order is fixed.
3

Replacing ox_target or qb-target

This step is only required if you’re replacing an existing target resource.
Remove (or stop) the real ox_target, qb-target, or qtarget - your existing scripts keep working without editing. See Compatibility for the details.Bridged content renders nothing until you look at it. If you’d rather bridged zones get a grain (an ambient point of light marking them from a distance), set Config.Reveal.bridged = 'ambient' in config.lua.
4

Restart server

Finally, perform a full server restart. Failure to perform a full restart after installation will cause errors.
When updating an existing install on a live server, run refresh in the server console before restarting the resource.