> For the complete documentation index, see [llms.txt](https://xcore.gitbook.io/xcore-docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://xcore.gitbook.io/xcore-docs/vehicleshop/config-file.md). # CONFIG FILE ```lua config = {} config.settings = { lang = "cs", -- The language you can change. The folder for languages ​​is langues, write here only the last file name after lang_ AceAllowed = "x_vehicleshop_staff", -- Set pedi and ox_target to true if you want them to be used fuel = 'ox_fuel', -- 'ox_fuel', 'legacy_fuel', 'ti_fuel', 'x-fuel', 'custom' vehiclekey = 'custom', -- 'wasabi', 'okok', 'jg (wait for release)', 'custom' notify = 'ox_lib', -- 'ox_lib', 'okok', 'qs','esx', custom company_owner_sell = true, imagecreator = { cam_pos = { -737.3778, -62.7330, 43.7521, 130.2374 }, -- The position where the camera will be, which will automatically turn to the point of the car car_pos = { -741.2506, -66.8666, 41.7512, 282.5556 }, -- The position of the car where it will spawn car_color = { 131, 141 } -- https://wiki.rage.mp/index.php?title=Vehicle_Colors Color coding when spawning a car for photography }, buy_on_company_avalible = true, -- If you leave it on true, it will be possible to buy a car for the company unemployed_job_name = "unemployed", -- This changes them for the job of the unemployed for identification so that it is not possible to buy a car for the company use_markers = false, -- If you leave it on true at the place where the marker should be, a marker will appear through which the vehicleshop can be opened use_peds = true, -- If you leave it on true, npc will appear at the places marked with an ox targer to open the vehicle shop defualt_ped = "S_M_M_HighSec_02", -- The basic ped, if there is no setting in custom peds, this one will be set target_icon = "fa-sharp-duotone fa-solid fa-handshake", -- The basic icon, if not set in the custom icon, will be set for the ox target test_time = 2640, -- Time after which you can test all the time 44 = 1s default_test_location = { -- Test drive settings x = -960.1824, -- Coordinates for test drive y = -3360.8469, -- Coordinates for test drive z = 13.9444, -- Coordinates for test drive heading = 56.4959 -- Rotation, how should the car be rotated when teleporting to the test }, blip_font = "", blip_scale = 0.8, marker_render_dist = 10, -- The distance from which the marker will be displayed use_holo_text = { -- Settings for the message hologram to press and open the shop font = 4, -- Font ID for holo text scale = 0.55, -- Holo text size textColor = { r = 190, g = 180, b = 240, a = 255 }, -- Text color RGBA } } config.marker = { -- Here is the marker setup. type = 29, -- This is the id of the marker icon. https://docs.fivem.net/game-references/markers/ rotX = 0.0, -- Marker rotation. rotY = 0.0, -- Marker rotation. rotZ = 0.0, -- Marker rotation. scaleX = 1.0, -- Marker size. The default is 1 under 1, the marker shrinks. scaleY = 1.0, -- Marker size. The default is 1 under 1, the marker shrinks. scaleZ = 1.0, -- Marker size. The default is 1 under 1, the marker shrinks. colorR = 116, -- Marker color RGB colorG = 23, -- Marker color RGB colorB = 255, -- Marker color RGB colorAlpha = 255, -- Marker transparency largest value 255 smallest is 0 bobUpandDown = true, -- Moving up and down animation. faceCamera = true } config.pdms = { markers = { pdm = { type = 225, color = 27, marker = 36, -- Custom marker id ped = "S_M_M_HighSec_02", -- A custom ped that you can set for your store target_icon = "fa-solid fa-car" -- https://fontawesome.com/icons }, luxury = { type = 523, color = 46, marker = 36, ped = "S_M_M_HighSec_04", }, motors = { type = 522, color = 27, ped = "G_M_Y_Lost_03", }, boats = { type = 427, color = 27, ped = "S_M_M_MovPrem_01", }, bikes = { type = 536, color = 27, ped = "S_M_M_StudioProd_01", }, industrial_vehicle = { type = 85, color = 27, ped = "S_M_Y_DockWork_01" } } } return config ``` --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter: ``` GET https://xcore.gitbook.io/xcore-docs/vehicleshop/config-file.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.