> ## Documentation Index
> Fetch the complete documentation index at: https://lationscripts.com/docs/llms.txt
> Use this file to discover all available pages before exploring further.

# Interact - Installation

> Step by step instructions to install this resource

<Steps>
  <Step title="Add to 'resources' directory" stepNumber={1}>
    Extract the `lation_interact` zip folder directly into the root `resources` directory of your server.

    <Warning>
      Do not place this resource in a `[subfolder]` - it should be placed directly in the root.
    </Warning>
  </Step>

  <Step title="Update server.cfg" stepNumber={2}>
    Open your `server.cfg` and add `ensure lation_interact` **after** your framework core and inventory, and **before** every resource that uses targeting - it reads the framework for job and item checks, and any script that registers targets must start after it.

    If you use [Modern UI](/docs/modern-ui/install), `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.

    ```text theme={null}
    ensure lation_ui         # optional - first of all, before ox_lib
    ensure ox_lib
    ensure qbx_core          # your framework core (qb-core, es_extended, ox_core)
    ensure ox_inventory      # your inventory
    ensure lation_interact
    ensure [standalone]      # everything that registers targets
    .. etc
    ```

    <Warning>
      Starting `lation_interact` before your framework core throws `No such export GetPlayerData` errors on join - the framework's exports don't exist yet.
    </Warning>
  </Step>

  <Step title="Replacing ox_target or qb-target" stepNumber={3}>
    <Info>
      This step is only required if you're replacing an existing target resource.
    </Info>

    Remove (or stop) the real `ox_target` or `qb-target` - your existing scripts keep working without editing. See [Compatibility](/docs/interact/compat/ox-target) for the details.

    Bridged targets render nothing until you look at them. If you'd rather they get a grain (an ambient point of light marking them from a distance), set `Config.Reveal.bridged = 'ambient'` in `config.lua`.
  </Step>

  <Step title="Restart server" stepNumber={4}>
    Finally, perform a full server restart. Failure to perform a full restart after installation will cause errors.

    <Note>
      When **updating** an existing install on a live server, run `refresh` in the server console before restarting the resource.
    </Note>
  </Step>
</Steps>