Interaction Methods
Choose one interaction method for everything or a different method for each interaction type
Use different methods for showroom, management and selling interactions when they use different types in the location creator.
Edit Config.InteractionMethod in config/config.lua. This controls how players use interactions placed in the location creator.
One method for everything
The default is a single string. Existing string configurations still work:
Config.InteractionMethod = "textui"Choose one of these methods:
| Value | How players interact | Provider setting |
|---|---|---|
textui | Read a screen prompt and press its key | Config.DrawText |
target | Use your targeting system | Config.Target |
3dtextui | Use a prompt near the entity or the point or zone centre | Config.DrawText3d |
radial | Select an entry in the radial menu while nearby | Config.RadialMenu |
A method for each type
Replace the string with a table to mix methods. This example uses key prompts for points and parking zones, targets for peds, 3D prompts for vehicles and radial menus for objects:
Config.InteractionMethod = {
point = "textui",
polyzone = "textui",
vehicle = "3dtextui",
ped = "target",
object = "radial"
}Every entry accepts textui, target, 3dtextui or radial. Missing entries use textui; an empty table also uses textui for everything. Unrecognised values fall back to textui.
| Key | Interaction type in the creator |
|---|---|
point | A point with a radius |
polyzone | A polygon area |
vehicle | An interaction attached to a placed vehicle |
ped | An interaction attached to a ped |
object | An interaction attached to a placed object |
vehicle means the interaction's placed vehicle, not whether the player is driving. The choices apply to all interactions of that type in this script, not to individual locations. Decorative entities, spawn points and location boundaries without an interaction aren't affected.
For example, use a Ped for management and a Point for selling vehicles to give those actions different methods. Two actions placed with the same type use the same method. See Setting Up Locations.
Choose providers
Keep these settings separate from Config.InteractionMethod. They choose which installed resource handles each method:
Config.Target = "auto" -- or "ox_target"
Config.DrawText = "auto" -- or "jg-textui", "qb-DrawText", "okokTextUI", "ox_lib", "ps-ui"
Config.DrawText3d = "auto" -- or "sleepless_interact"
Config.RadialMenu = "auto" -- or "ox_lib"auto detects a supported running resource. Install and start the providers for every method you select before starting jg-dealerships. Set a provider explicitly if you have more than one installed and want a particular one.
3dtextui requires sleepless_interact. Its prompt is near the entity or the point or zone centre, within 2.5 metres; it doesn't cover the whole polygon. Use textui or radial if players should interact anywhere inside a polygon.
Restart jg-dealerships after changing the config. Visit each interaction type you changed and check that the selected prompt opens the expected action.
Last updated 29 September 2026