Skip to content

Troubleshooting

Most problems leave a message in the F8 console (client) or the server console, always starting with [sl_interact] and the name of the script involved. Look there first.

Interactions of my old target scripts don’t show

Section titled “Interactions of my old target scripts don’t show”
  • Check that ox_target, qb-target or qtarget is not running. If it is, SL-Interact prints ... is running: scripts that use it will talk to it in the server console. Remove it from server.cfg.
  • Check that ensure sl_interact comes before those scripts in server.cfg. On QBCore, put it above ensure [qb] and move qb-target out of [qb].
  • Restart the whole server, not only the resource.

Everything disappeared after restarting SL-Interact

Section titled “Everything disappeared after restarting SL-Interact”

When SL-Interact restarts, it forgets what other scripts gave it. Scripts that use the bridge (ox_target, qb-target, qtarget) don’t add their interactions again, and SL-Interact warns about it in the server console. Restart the whole server, or restart those scripts after SL-Interact.

For your own scripts, see if SL-Interact restarts.

Scripts that depend on SL-Interact (dependency 'sl_interact') are stopped by FiveM when it stops, and are not started again. ensure them again from the console.

A vehicle, a player or something else shows nothing

Section titled “A vehicle, a player or something else shows nothing”

Those points only show while holding Alt by default (Config.Reveal.globals and players). Hold it and aim at any part of the vehicle.

On purpose: from a vehicle only interactions with inVehicle = true show.

On purpose: points hide while running or sprinting and come back when walking.

  • Red for a moment when pressed: something refused it, and the reason is shown.
  • Dimmed: a condition fails (a job, an item…) and the script chose to show it anyway (showDisabled).
  • Missing: a condition fails and the script chose to hide it. Check the job, grade and items it needs in the interactions panel.

A player can’t use the panel or the style editor

Section titled “A player can’t use the panel or the style editor”

They need the ACE permission: add_ace group.admin sl_interact.style allow in server.cfg, or their identifier in Config.StyleEditor.admins. Without it they get You can’t open the interactions panel.

That’s the default mode since 1.0.1 ('hold', like ox_target): keep holding Alt while you choose and press the option’s key. If you’d rather keep the label open after letting go of Alt, set Config.Reveal.mode = 'toggle' in config.lua and restart the server. See the Alt key: hold or toggle.

I changed a key in config.lua and players still use the old one

Section titled “I changed a key in config.lua and players still use the old one”

FiveM only applies a new default key to players who never changed it. Each player can set it in Settings > Key Bindings > FiveM.

I changed config.lua and the look didn’t change

Section titled “I changed config.lua and the look didn’t change”

What is saved in the style editor wins over Config.Shape, Config.Colors, Config.Points and Config.Reveal (except Config.Reveal.mode, which is only set in config.lua). Use Back to the server values in the editor, or change it there.

SL-Interact checks every interaction it receives and prints what is wrong with the name of the resource that sent it:

Message Meaning
unknown field "x" A field SL-Interact doesn’t know, usually a typo
key "X" is not one of Config.Keys The option asks for a key that is not in Config.Keys
does nothing: give it onSelect, event, serverEvent or options The option has no action
icon "x" does not exist (yet) Register it with registerIcon first. A normal point shows meanwhile
has groups but there is no framework Job conditions need a framework; that option never shows
polygon zones are shown as a point in their center A target script used a polygon zone (see limits)