SCOOBY

Installation guides

Browse resources ↗

GTA 5

ASI mods and trainers

  1. Select Download on the Scooby resource. Check its Edition and Requirements, then read the package’s included instructions.
  2. Install the ASI loader and Script Hook V version specified in those instructions. Legacy and Enhanced releases can have different requirements.
  3. Extract the complete mod package. Place its ASI plugin, configuration and supporting folders where the included readme instructs; many plugins use the folder containing the game executable.
  4. Start the game and use the activation key listed in the mod’s instructions. Keep the original package so you can identify its installed files later.

Menyoo, Rampage and Simple Trainer use their own documented exports and supporting folders. Preserve their original files when installing a downloaded package.

Download ASI mods on Scooby →

GTA 5

.NET mods

  1. Select Download on Scooby. Check the resource’s required GTA edition, Script Hook V, .NET script host and runtime versions.
  2. Install the host and its documented dependencies before adding the mod. Follow the package’s edition-specific instructions.
  3. Extract the mod with all of its supporting files. Use the scripts folder or other destination specified in the included readme.
  4. Keep DLLs, configuration, images and data folders together as supplied. Follow the mod’s activation and troubleshooting instructions.

A .NET game mod runs through its documented script host. Keep its host and runtime requirements with the downloaded package.

Download .NET mods on Scooby →

GTA 5

Menyoo / XML vehicles and map mods

  1. Check whether the download is a saved vehicle, an object-placement map or a model package. Keep XML, INI and JSON exports in their original format.
  2. For a supported vehicle XML, use Scooby’s Vehicle → Saved Vehicles library and its folder control, then refresh and select the file.
  3. For a placement map, use a compatible map loader or the Menyoo / Simple Trainer workflow named by its author. Use that loader’s folder control or the package’s documented map directory.
  4. Install any required custom vehicle, ped or map assets first. A placement preset can only reference models available to its loader.

A trainer-specific map and a streamed map asset are different formats. Changing a filename extension does not convert between them.

Saved vehicle imports →Model and addon requirements →

GTA 5

Outfits

  1. Download a compatible outfit and preserve its extension. Native saves use JSON; supported XML outfits also load.
  2. Open Self → Outfit Editor → Saved Outfits → Open Folder, or open C:\scooby\GTA5\outfits.
  3. Copy the outfit there, select Refresh, and select the file to apply it.
  4. Use the character model and game edition the outfit was made for.

Current builds also browse supported Stand, Cherax, INI and Menyoo exports through the ordinary outfit library. Use the same outfits folder, preserve the original structure and choose the supported importer. Older other-menu folders are migrated by current builds. An extension alone does not guarantee compatibility.

Full outfit guide →

GTA 5

Vehicles and modded builds

  1. Download the original preset. Supported structures include JSON, XML and INI; the file’s contents must match a supported importer.
  2. Open Vehicle → Saved Vehicles → Open Folder, or open C:\scooby\GTA5\vehicles.
  3. Copy the preset there, open Browse, select Refresh, and select the vehicle.
  4. Current builds also browse compatible other-menu exports in this same library. Preserve their original format and folder structure.

A saved build references existing vehicle models and attachments. Install any required addon models separately. Renaming an extension does not convert the preset.

Full vehicle guide →

GTA 5

Addon vehicles, peds and textures

  1. Download the resource on Scooby and check its Edition, Requirements and included readme. RPF, YFT, YDD and YTD files are game assets.
  2. For the split Scooby addon collection, download all seven archive parts into the same folder. Keep their names unchanged and extract the .zip.001 with an archive tool that supports split ZIPs.
  3. Choose a vehicle pack under addons/vehicles/Legacy or Enhanced. In a compatible Scooby build, import your chosen content through Addons/Replacements. For a loose ped, import its complete ped folder.
  4. Follow the package readme and keep dependencies together. Supported Legacy packs can use Settings → Converter for Enhanced; moving a folder between editions does not convert it.
  5. After the assets are installed, use the supplied spawn name or load the compatible vehicle/outfit preset.

For texture packages, check the exact target model and required loader. Keep original downloads and avoid replacing files while a pack is mounted.

Addon and edition guide →

GTA 5

Addon objects, animations, maps and clothing

  1. Download the package on Scooby and check its game edition and Requirements.
  2. Extract the complete package, preserving model, texture, animation and supporting folder paths.
  3. Install the dependencies and use the loader or import workflow named in the included readme.
  4. Use the package’s supplied names or compatible presets after its assets are installed.

Keep the package’s original instructions and files together. Menyoo XML and INI placement presets use the separate Maps category.

GTA 5

Addon weapons

  1. Open the original release and check which GTA V edition and DLC loader it supports.
  2. Install the complete game asset package using its readme. Keep model, texture and metadata files together.
  3. Use the in-game model name supplied with the release in a trainer that supports add-on weapons.

RED DEAD REDEMPTION 2

Addon peds

  1. Download the complete ped ZIP on Scooby and read its Requirements and included COMMUNITY-INSTALL.txt.
  2. Copy the ZIP into C:\scooby\RDR2\Addon Archives.
  3. Open Addons/Replacements → Archives → Refresh Archives. Select the pack root and choose Import to Library.
  4. Use Refresh Library, then Validate Direct Pack before choosing a compatible load or staging action.
  5. Keep install.xml, ped metadata and all streaming dependencies together. Use the package’s model names after registration and loading.

Direct Pack loading is experimental in the native menu. LML staging requires Lenny’s Mod Loader and applies on the next game launch. Archive validation and in-game model registration are separate steps.

RED DEAD REDEMPTION 2

Addon objects, animations and maps

  1. Download the RDR2 resource on Scooby and read its Requirements and included installation instructions.
  2. Keep the complete asset package and all supporting folders together.
  3. Install any required loader or dependencies and follow the included readme for the package’s destination.
  4. Use the supplied model names or compatible presets after installation.

Choose a package made for RDR2 and the loader specified in its instructions.

GTA 5

LSC paintjobs

  1. Download the paintjob’s native Scooby JSON and keep any category folders supplied with it.
  2. Get inside the vehicle you want to paint. Open Vehicle Editor → Save/Load Paint Jobs → Open Folder.
  3. Copy the JSON into C:\scooby\GTA5\LSC\PaintJobs, preserving its category folder when present.
  4. In Save/Load Paint Jobs, choose the matching Folder and Saved Paint Job.
  5. Select Load Paint Job to apply it to your current vehicle.

The paintjob library accepts native JSON files in the scooby.paintjob format. The resource collection includes 2,299 native paintjobs. Vehicle livery texture packages have their own installation category.

GTA 5

Vehicle liveries and texture packages

  1. Download the resource on Scooby and check its target vehicle, game edition and Requirements.
  2. Install any required addon vehicle first. Keep the livery package’s original files and folder structure.
  3. Follow the included readme for the texture package’s destination and installation tools.
  4. Keep the original download and avoid replacing files while the vehicle pack is mounted.

These packages install vehicle texture assets. Native Scooby LSC PaintJobs are JSON presets and use the separate Paintjobs category.

Addon and edition guide →

GTA 5

ClickUI and ListUI themes

  1. Choose a Scooby appearance JSON or theme bundle. Extract it and copy the JSON, or the complete bundle with its images, into C:\scooby\GTA5\themes.
  2. Open Settings → Appearance → Themes and select Refresh Library.
  3. Select the theme, choose Both, ClickUI or ListUI under Save / Load Scope, then select Load Selected Theme.

Keep the JSON at the top of its bundle folder. Standalone ClickUI appearance presets can use themes\ClickUI; use the package readme and the menu’s folder control for that format. A theme only supplies interfaces included in its export. For a style-specific Stand profile or X-Force UI preset, use the matching native ListUI style controls and its package instructions.

Scooby themes can borrow another menu’s appearance while using Scooby’s own format. Original Cherax ClickGUI themes belong in Cherax’s theme library. For Scooby ClickUI, choose a version made for Scooby.

Full GTA theme guide →

GTA 5

Config profiles

  1. Open the menu’s config library and use its folder control to find the active profile directory.
  2. Back up your current settings, then copy a compatible Scooby exported profile into that directory.
  3. Refresh the config list, select the profile and load it. Review the loaded settings.

Edition-specific profiles use C:\scooby\GTA5\configs\Enhanced or Legacy. With shared configs enabled, the directory is C:\scooby\GTA5\configs\Shared. Use the active menu folder rather than guessing the edition.

GTA 5 / RED DEAD REDEMPTION 2

ListUI style image packs

  1. Choose a pack made for your menu and its active ListUI style.
  2. For builds using native style profiles, use C:\scooby\GTA5\Themes\ListUI or C:\scooby\RDR2\Themes\ListUI.
  3. Keep the pack in the exact style folder supplied by the author, such as 2TAKE1, IMPULSE, Stand, Silkroad v3-v4, Silkroad Simple, Ozark v34 or X-Force v6.
  4. Use the ListUI appearance controls to choose the style and reload its images. Keep all backgrounds, headers and selection images together.

Older RDR2 builds use the separate images\ListUI workflow below. Use your menu’s Open Folder control and the package readme to select the correct format. Navigation layout samples are separate from image themes.

RED DEAD REDEMPTION 2

Player and horse outfits

  1. Copy a Scooby RDR2 outfit JSON directly into C:\scooby\RDR2\outfits. Horse outfits belong in its Horse subfolder.
  2. For a player outfit, open Self → Outfits → Outfits → Saved Outfits.
  3. Select Refresh, select the file, and choose Load Selected Outfit.

Check the intended character, model and Online gender. RDR2 outfit files are separate from GTA 5 and RedM exports. The outfit editor requires a license that includes the feature.

Player outfits → Horse outfits →

RED DEAD REDEMPTION 2

Appearance and ListUI images

  1. Copy saved appearance JSON directly into C:\scooby\RDR2\theme. This folder is singular.
  2. Open Settings → Appearance → Themes → Saved Themes, refresh, select the theme and choose Load.
  3. For a ListUI image theme, copy the whole image folder into C:\scooby\RDR2\images\ListUI.
  4. Open the ListUI Images controls, select Reload Images, choose the theme with Next Theme, and enable the desired slots.

Preserve slot filenames such as header, background and selector. Appearance JSON and image themes are separate; install both when supplied.

Full RDR2 theme guide →

RED DEAD REDEMPTION 2

Config profiles

  1. Back up your current profile. Copy the compatible .config file directly into C:\scooby\RDR2\configs.
  2. Open Settings → GUI → Configs and select Refresh.
  3. Choose the file in Config Library and select Load Selected.

A config does not install its author’s scripts, themes or outfits. Install those separately.

Config and backup guide →

COUNTER-STRIKE 2

Players, weapons, knives and equipment

  1. For a package in the in-game repo, open Custom → Repo, search or filter by category, preview it and choose Download and install.
  2. For a downloaded archive, extract the complete resource trees. In Custom → Library, open the category’s gear menu and choose Import folder or Import weapon folder.
  3. Keep compiled models, materials, textures, animations, sounds and icons at their original relative paths. Use Sync to rescan.
  4. Select the model in Library, check the target, team and scope, then select Equip model.

Some library features depend on your Scooby build. For manual installation, close CS2 and copy the resource trees into the game’s game\csgo folder. Use Steam → Manage → Browse local files to find your installation.

Full model installation guide →

COUNTER-STRIKE 2

Custom pet model packs

Open the pack’s details for its model paths, license and supported builds. Keep the models, materials and textures at their original relative paths. Follow the pack’s instructions to install it or generate it from your local CS2 files.

Add or update a pet pack

Put a redistributable pack or a reference to a locally generated pack in project/resource-inbox/cs2/scooby/pets/. Include the creator, source, license and model paths in resource.json. To update a listing, edit the files or metadata in its existing folder.

Resource inbox instructions ↗

COUNTER-STRIKE 2

Textures

  1. For image textures, open Custom → Textures → Open folder and copy the PNG, JPG or GIF into C:\scooby\CS2\textures.
  2. Select the image, target and team/weapon scope, preview it, and apply the change.
  3. For a map project, preserve the complete folder and choose Open project on its map-project.json. Check the map, then select Apply opened project.
Textures and map projects →

COUNTER-STRIKE 2

Build a Hammer material from PBR textures

  1. Download the diffuse, OpenGL normal and roughness maps at the same resolution. Place the images in your map addon’s content/csgo_addons/<addon>/materials/ folder.
  2. Launch CS2 Workshop Tools for that addon. Create a .vmat in Material Editor with the Csgo Complex shader. Assign the diffuse map to Color, the OpenGL normal map to Normal, and the roughness map to Roughness. Use separate maps for the individual slots and add ambient occlusion or metalness if the asset supplies them.
  3. Save the material inside the addon. Select it in Hammer’s Asset Browser, apply it to a map surface, then build and test the map.
Browse CS2 textures → · Valve’s Workshop resources ↗ · Poly Haven textures ↗

COUNTER-STRIKE 2

How to use a skybox in Scooby

You’ll need a Scooby CS2 build with VFX sky image import.

  1. Download a 2:1 PNG panorama from the skybox library, such as Ion Nebula, Rose Dawn or Storm Bank.
  2. In Scooby, open VFX, go to the Sky controls and use the image import to select the downloaded .png file.
  3. Look up on a map with a visible sky to see your new skybox.
Browse CS2 skyboxes →

REDM

RSG object streaming files

  1. Download the complete file set supplied with the RSG prop listing, including its model, texture and archetype files.
  2. Place the original YDR, YTD and YTYP files together in a compatible RedM server resource’s stream folder.
  3. Preserve the source resource’s manifest and register stream/prop_weed_ytyp.ytyp using its DLC_ITYP_REQUEST data-file declaration.
  4. Have the server owner start the resource and use the supplied model names after it loads.

These are RedM server assets. Native single-player Scooby RDR2 import compatibility has not been established.

FIVEM / REDM

Server resources and custom assets

  1. Download the resource on Scooby and check the intended runtime, requirements and dependencies. FiveM and RedM use separate resource packages.
  2. If the download is a server resource, give it to the server owner or install it using the included server instructions.
  3. Keep its resource manifest, stream folders and supporting files together. Follow the readme for server configuration and startup order.
  4. For a menu preset, use the menu’s import or Open Folder control instead.

Client preset folders do not install server resources. Access to a server does not grant permission to change its resources.

FiveM setup → RedM setup →

FIVEM

Install FiveM character and animal models

  1. Choose a FiveM add-on and check the author’s supported game build, dependencies and model name. If you want pet interactions, also check which companion script supports the animal.
  2. Unpack the resource on a server you administer. Place the folder that contains fxmanifest.lua under the server’s resources directory. Keep the supplied stream folder, textures and metadata in their original locations.
  3. Add ensure <resource-folder> to server.cfg, after any required resources. To test a new resource on a running test server, enter refresh and then ensure <resource-folder> in the server console.
  4. Use the model name from the author’s instructions or the ModelName entry in peds.meta with your server’s authorized ped selector or spawning tool. The resource folder and model name can differ.
  5. Test movement, textures and any advertised outfit variants. If the model fails to load, check the server console, the exact model name, and whether the manifest mounts the supplied metadata with PED_METADATA_FILE. Restore your normal character appearance after testing a player model.
Browse FiveM character and animal models → Cfx metadata reference → Cfx server commands →

FIVEM

Install and test FiveM animations and emotes

  1. Check what the release contains. A menu such as RPEmotes Reborn is a complete resource. A pose pack can contain only .ycd clips and setup instructions for the menu you already use.
  2. For a clip pack, keep the .ycd files in the resource’s stream folder and start it as the author describes. Use the dictionary and clip names from the release when registering the emote.
  3. Follow your menu’s instructions for adding entries. RPEmotes Reborn provides AnimationListCustom.lua for custom entries. Use the matching instructions if the release gives an example for a different menu.
  4. Test the emote on the intended character and check that it starts and cancels. For a shared emote, have a second player confirm the timing and any props. Check synchronization and the game build against your menu’s setup guide if the two players see different results.
Browse FiveM animations and emotes → RPEmotes Reborn setup →

FIVEM

Install and test FiveM props

  1. Open the creator’s release and find the resource folder with fxmanifest.lua. Keep the streamed models, textures and any supplied .ytyp file together. If the author uses DLC_ITYP_REQUEST for a YTYP, keep the declaration and its path intact.
  2. Add the resource under resources on your test server and start it from server.cfg. For an example map, visit the location the author lists. For individual props, place one using the supplied model name in a compatible placement tool.
  3. Have a second player connect and check that the prop has the right texture, scale and collision. If it is missing, check the exact model name and the console for missing stream files. If it appears twice, check for an example map and a separate placement at the same spot.
  4. Configure inventory items separately if the pack provides them. Test the prop on its own first, then verify that the intended item or placement resource uses that model.
Browse FiveM props and objects → Cfx.re resource manifest reference →

FIVEM

Install and test FiveM clothing

  1. Check which freemode model the release supports. An add-on introduces a drawable or prop in a clothing collection. A texture replacement updates the appearance of an existing item, so look in the original slot when testing it.
  2. On a test server, place the creator’s resource folder under resources. Keep the manifest and streamed assets together. Add ensure followed by the resource’s folder name to server.cfg and follow any load order the creator specifies.
  3. Open the server’s appearance menu on the supported model and try the item and its textures. If an existing outfit changed or a garment shows the wrong texture, test with other packs that touch the same clothing slot disabled.
  4. When an appearance resource supports collection-based outfits, save the collection name and its local drawable index. Cfx.re documents that a GTA title update can shift the global indexes for custom collections.
Browse FiveM clothing and textures → Cfx.re clothing collection reference →

FIVEM

Install and test a FiveM vehicle add-on

  1. Choose the creator’s FiveM package and confirm its game build, edition and dependencies. Locate the folder with fxmanifest.lua. Keep the stream folder and the vehicle, handling and tuning metadata together.
  2. Copy that resource folder into resources on a test server. Add ensure followed by its folder name to server.cfg. Start any dependencies first and check the console for missing files.
  3. Use the model name from the release notes or the modelName entry in vehicles.meta in your vehicle spawner. For example, the Sunrise R resource is hycsunrise and its model is hycsun.
  4. Spawn the vehicle before adding it to a shop or job. Check the doors, lights, sound and any advertised tuning options. If it only breaks when another pack is enabled, compare their model and metadata names before changing either package.
Browse FiveM vehicle add-ons → Browse FiveM sound packs → Cfx.re vehicle metadata reference →

FIVEM

Install and test a FiveM map add-on

  1. Check the maintainer’s required server edition, game build and dependencies. A YMAP places map objects. A custom interior can also include models, textures, collision and YTYP definitions. Keep the author’s files together.
  2. On a test server, copy the folder with fxmanifest.lua into resources and add ensure followed by its folder name to server.cfg. If the archive wraps several resources, start the map folder named in the instructions.
  3. Connect and visit the area with other maps for that location disabled. Check entrances, floors and doors from both sides. Reconnect and check again so you can catch missing assets that only show up when a player first joins.
  4. Enable the other maps one at a time. If walls flicker, objects appear twice or collisions no longer match, stop the last resource you enabled and compare again. Keep a copy of the previous server.cfg so you can restore the working setup.
Browse FiveM map add-ons → Cfx.re resource manifest reference →

FIVEM

Install FiveM graphics packs and textures

  1. Open the listing’s author page and choose the FiveM release. Check whether it is a client graphics pack, a ReShade preset, or a server-streamed resource.
  2. For a client graphics pack, close FiveM, extract the archive, and follow the author’s installation path. For example, Hiromasa documents %LOCALAPPDATA%/FiveM/FiveM.app/plugins for its packs. Keep a backup of any files you replace.
  3. For a ReShade preset, install the required shaders and any named base mod, such as QuantV. Put the preset .ini in your ReShade presets folder and select it in the overlay.
  4. For a server-streamed package such as Oulsen’s satellite map, have the server operator keep the manifest and stream files together, add the resource to the server’s resources directory, and enable it in server.cfg.

Cfx.re documents that client graphics mods are unavailable in FiveM for GTA V Enhanced during early access. Check the game edition and the server’s client-mod policy before installing.

Cfx.re compatibility notes → Browse FiveM graphics packs and textures →

FIVEM

Compare graphics packs and check performance

  1. Start with stock graphics and take a baseline in a private test session. Keep the same location, camera angle, resolution and game settings for both passes.
  2. Check the same street in clear daylight, at dusk and at night. In daylight, look for detail in white walls, clouds and signs. At dusk, check for lost detail in shaded doorways. At night, check whether streetlights bloom over road markings or make the HUD hard to read.
  3. Walk the same route and pan past fences, foliage and signs. These fine details make shimmer, ghosting and oversharpening easier to spot. At a waterfront, check that the sunset reflection keeps detail around the brightest part.
  4. Repeat the route with one pack or preset changed. Compare frame times and visible stutter along with average FPS. A clip recorded on a different server or at a different time of day is useful for judging the look, but cannot establish a performance gain.

If the result looks wrong or FiveM crashes, close the game, roll back the last change and retest the stock setup before adding anything else.

FIVEM

Measure what an FPS pack changes

  1. Press F8 to open the FiveM console and run cl_drawperf true. The overlay shows FPS and GPU usage. Keep your resolution, frame cap and graphics settings fixed during the comparison.
  2. Choose a route on a test server you control. First compare the stock client and the pack at the same time of day and in the same weather. Then repeat in a second condition, such as at night, to check whether the result holds when lighting changes.
  3. Let the scene load before recording your readings. Run the same route twice for each setup and note FPS during movement and any recurring stutter. Check whether any improvement comes with changes to shadow detail, reflections or road textures that matter to you.
  4. Run cl_drawperf false when you finish. Keep your measurements with your settings so you can repeat the comparison after changing the pack.
Cfx.re performance overlay commands →

FIVEM

Check whether your FiveM client supports the old custom crosshair

In September 2026, Cfx removed its crosshair guide and the drawing code from the FiveM source repository. The old commands may be unavailable on your installed build.

  1. On a test server you administer, or in FiveM single-player, press F8 and enter cl_customCrosshair by itself. If the console returns a setting, record its value and try cl_customCrosshair true. If the setting is unknown or the reticle never appears, use the game’s available HUD options.
  2. If the reticle appears, try cl_crosshairsize 3 for line length and cl_crosshair_drawoutline true for an outline. Record the original values before changing them. Compare the result on a bright wall and against a dark background at the resolution you play at.
  3. Restore the values you recorded. To disable the old custom reticle, use cl_customCrosshair false on builds that support it. If a server disables the setting, follow the server’s HUD rules.

PNG and GIF crosshair packs are image files. The old F8 commands draw a reticle from settings such as line length and color. For a server HUD that supports images, use the file format and dimensions its maintainer specifies.

Archived Cfx crosshair reference → Cfx source change →

FIVEM

Test sky colors, timecycles and vehicle lights

  1. Decide who should see the change. A client timecycle pack changes the view on your installation. For vehicle lighting that players should share, have the server operator test a compatible server resource.
  2. Choose the FiveM package on the maintainer’s page. For VisualVanilla, that is 2.0 for FiveM (FINAL) in All Versions. For U1D GFX Core, choose FiveM 1.0.0. Follow the selected package’s written instructions.
  3. Hold the camera still on a test server and compare the same weather and time with the pack on and off. Then advance from daylight to dusk to see how the colors blend. Check cloud edges, street markings and building shadows. A striking sky at one hour can look very different during the transition.
  4. For server lighting, have a second player join the test server and look at the same vehicle at night. If the lights are too bright or differ between clients, check which server resources and client presets affect lighting. Test one change at a time.
Browse FiveM sky and lighting packs →

FIVEM

Load and tune a ReShade preset

  1. On a compatible FiveM Legacy setup where the server allows ReShade, save the preset .ini in the presets folder named by its author. Keep your current preset as a separate file.
  2. Open the ReShade overlay and select the new file from the preset selector on the Home tab. If an effect fails to load, check the author’s shader list and the overlay log. In a preset, the Techniques line can help you identify missing .fx files.
  3. Compare effects on and off from the same camera angle. If shadows look flat or signs lose detail, try adjusting the color or contrast effect first. If pavement and brick edges look grainy while moving, turn down sharpening and check whether more than one sharpening effect is active.
  4. Save your changes to a copy. If the overlay never appears, check your game edition and the server’s policy before changing anything else.
ReShade preset instructions →

FIVEM

Tell a preset from a full client pack

  • A ReShade preset is typically an .ini with a list of shader dependencies. Load it through your compatible ReShade installation and keep your previous preset so you can switch back.
  • A pack with a citizen folder can replace client files. Check the archive against the maintainer’s file list and game edition before changing anything. If the archive includes runtime DLLs or has no original release, skip it and choose a documented pack.
  • An archive labelled DLSS may bundle ReShade and third-party DLLs. Upscaling, frame generation and neural rendering have different hardware requirements. Check the original project’s compatibility notes for your exact GPU and edition before installing; a filename naming a GPU series is insufficient. Cfx.re says graphics mods are unavailable on FiveM Enhanced during early access.

Check the server’s client plugin policy first. To troubleshoot a compatible pack, start with the stock client, add one documented component at a time and back up the exact files you replace.

Cfx.re client plugin guidance →

FIVEM

Set up a mixed FiveM pack one component at a time

  1. Open the archive outside FiveM and check its folder tree. A bundle can put a ReShade preset, audio replacements and a citizen folder under a single wrapper directory. Open any nested archive separately and match each component to its original maintainer’s instructions and supported edition.
  2. Close FiveM. Confirm the path to your active installation before changing files. Cfx.re’s installer normally uses %LOCALAPPDATA%\FiveM and can also install into a folder you choose. Write down the files each component adds or replaces and keep copies of the originals outside the game folders.
  3. Try the component you want first. Launch FiveM and test it before adding the next one. If two components name the same destination file, choose one unless the maintainer provides a combined version. To compare a dramatic color grade or night sky, check whether the HUD and light surfaces stay readable during ordinary play. Montage cuts and slow motion make it hard to judge how a preset behaves live.
  4. If a change causes a crash, missing audio or a modified-file error, close FiveM, remove the files that change added and restore the copies you made. Launch again with the restored setup. If you no longer have the original files, use the official support instructions for the affected installation.
Cfx.re installation paths → Cfx.re client troubleshooting →

FIVEM

Check and compare FiveM sound packs

  1. Check what the archive contains before installing. Files such as RESIDENT.rpf and WEAPONS_PLAYER.rpf are replacement archives. A server audio resource instead comes with a manifest and can declare its own AUDIO_WAVEPACK. Use the maintainer’s instructions for the correct package type and game edition.
  2. Check the server’s rules for client replacements. Where allowed, back up the exact files the maintainer says to replace and try one pack at a time on a private test server. Two packs that replace the same archive can overwrite one another.
  3. Compare the same sound at the same distance and in the same location with your game and system volume unchanged. Listen to both a single sound and a short burst, then check whether voice and ambient sounds stay clear. Recording volume and compression vary between clips, so use the live comparison to judge loudness and distortion.
  4. If sounds go missing, crackle, or the client reports modified files, restore the originals and retest. For a server resource, have the operator check the manifest, dependencies and console.
Browse FiveM sound packs → Cfx.re audio resource reference →

FIVEM

Deploy a public server recipe with txAdmin

  1. Pick the correct Legacy or Enhanced FXServer build. Start FXServer to open txAdmin, link your Cfx.re account and have your own server registration key ready. On Windows, Enhanced requires the Visual C++ redistributable listed in the Cfx.re setup guide.
  2. Choose a fresh server-data directory. For a basic Cfx.re server, skip database setup. For Qbox, ESX Legacy or QBCore, start MariaDB and have a database connection ready. Qbox requires MariaDB 10.9 or newer and does not support MySQL or XAMPP.
  3. Choose the listed template in Popular Recipes for the Basic Server, Qbox Framework or ESX Legacy. For Qbox Lean or QBCore, open the recipe page, copy the YAML file’s Raw URL and paste it into Remote URL Template. The older QBCore guide shows a Popular Recipes entry that txAdmin has since deprecated.
  4. Review and run the recipe. After the server starts, check the console for resource or database errors and connect to the test server before opening it to players. Keep your own configuration and database backup before replacing an existing installation.
Browse FiveM server recipes → Cfx.re txAdmin setup →

FIVEM

Add a Lua menu to a FiveM resource

  1. Check the menu dependency your script expects. MenuV runs as a standalone resource, the context menu is part of Ox Lib, and qb-menu is common in QBCore setups.
  2. Install the dependency in the server’s resources directory according to its maintainer. Start it before your script and check the server console for missing dependencies.
  3. Connect to your test server and open the menu through the resource that uses it. Check that each option works for the roles that should see it. Enforce permissions for server actions on the server even when the client menu hides the option.
Browse FiveM Lua Menus → Cfx.re resource setup →

REDM

Install RedM weapon models and skins

  1. Close RedM and extract the selected skin archive. The weapon packs in this collection provide weapons.rpf.
  2. Open the folder containing your RedM launcher, then open RedM Application Data. Find or create citizen/platform/packs/base/models.
  3. Back up any existing weapons.rpf in that folder, then copy the extracted file there. Restart RedM and check the affected weapon.

The scope packs in this collection also replace weapons.rpf. Use one replacement at a time. Restore your backup to switch back.

Browse RedM weapon models and skins →

REDM

Install RedM sound packs

  1. Close RedM and extract WEAPONS_PLAYER.rpf from the sound pack you chose.
  2. Find the base Red Dead Redemption 2 installation folder containing RDR2.exe. Open x64/audio/sfx inside it.
  3. Save a copy of the original WEAPONS_PLAYER.rpf outside the game folder. Copy in the replacement, then relaunch RedM.

These sound packs all replace the same RDR2 file. Restore the original archive to undo the change.

Browse RedM sound packs →

GTA 5

Graphics packs

Open the creator’s release page or install guide from the graphics pack card. Choose the single-player package for your GTA 5 edition. On GTA5-Mods, check All Versions when a creator offers separate Legacy and Enhanced downloads.

Browse GTA 5 graphics packs →

REDM

Install RedM graphics packs and textures

  1. Close RedM. Open the folder containing your RedM launcher, then open RedM Application Data.
  2. Back up the existing citizen folder. Extract the selected graphics ZIP to a separate folder.
  3. Merge the pack’s citizen folder into RedM Application Data, preserving its paths. Copy the supplied files over their matching paths and leave the rest of the installed citizen folder in place.
  4. Check the pack’s Requirements for Vulkan, DirectX 12 or optional ReShade settings. If the pack includes a DX12 version and you use DX12, follow its instructions for citizen/common/data/visualsettings.dat.
  5. Restart RedM and check the preset. Use one variant at a time when a pack offers different colors or replaces the same files.

To undo the changes, restore the files from your backup and remove any files added by that pack. Check the download’s Requirements for pack-specific folders and dependencies.

For creator-hosted releases such as Hiromasa’s packs, use the version and RedM installation steps on the creator’s release page.

Browse RedM graphics packs and textures →

REDM

Install RedM UI presets

  1. Close RedM. In RedM Application Data, open citizen/common/data/ui. Create the ui folder if it is missing.
  2. For a weapon-wheel or color preset, back up any existing colors.xml. Save the chosen preset in this folder as colors.xml.
  3. For UI Boost, back up any existing durations.xml and place the downloaded durations.xml in the same folder.
  4. Restart RedM. If your color preset calls for it, turn off colorblindness mode under Settings → Display.

Choose one colors.xml at a time. UI Boost uses a separate filename and can be installed alongside a color preset.

Browse RedM UI presets →

REDM

Install RedM visual effects

  1. Close RedM and extract the effect. Open RedM Application Data and use the destination listed for the download.
  2. For More Blood, place vfxbloodinfo.ymt in citizen/common/data/effects.
  3. For tracer and muzzle effects that supply fxlists.rpf and textures.rpf, put both files from the same preset in citizen/platform/data/effects/ptfx.
  4. Create missing destination folders as needed. Back up matching files before replacing them, then restart RedM.

Effect packs that replace the same files are alternatives. Keep the paired files from each preset together.

Browse RedM visual effects →

REDM

Install RedM scope and reticle visuals

  1. Close RedM and extract weapons.rpf from the scope pack.
  2. In RedM Application Data, find or create citizen/platform/packs/base/models.
  3. Back up any existing weapons.rpf, copy in the replacement, then restart RedM and check the scope.

Scope packs and weapon skins that replace weapons.rpf use the same destination. Choose one unless the author supplies a combined pack.

Browse RedM scope visuals →

REDM

Apply RedM client settings

  1. Open the listing’s Requirements to identify the file or in-game setting. Close RedM before editing or replacing a file.
  2. For Low Graphics, No Grass, Potato Graphics or resolution changes, back up %APPDATA%/CitizenFX/rdr3_settings/system.xml. Apply the named settings in your existing XML. For Low Graphics, replace only the portion specified in its guide, through the closing </advancedGraphics> tag.
  3. For file-based environment effects, follow the item’s path under RedM Application Data. For example, No Vignette and No Wind use citizen/common/data/timecycle. Back up matching files before merging.
  4. For Weapon Keybinds, use Settings → Controls → Mouse & Keyboard → Key Mapping in the pause menu. Restart after file changes and review the result.

Some downloads are text instructions. Apply the values they list to the named file or menu setting.

Browse RedM client settings →

LEFT 4 DEAD 1 & 2

Install game add-ons

  1. Check the listing’s game and required items. Follow its author’s instructions for any special installation steps.
  2. For an L4D2 Workshop item, select Subscribe on Steam. Start L4D2 and let it finish downloading the add-ons.
  3. For a manual .vpk, close the game and extract the VPK if it arrived in an archive. In Steam, use Manage → Browse local files on the matching game. Copy the VPK into left4dead\addons for L4D1 or left4dead2\addons for L4D2.
  4. Launch the game and check its Add-ons menu. If two replacements change the same model, texture, or sound, enable one at a time.
Browse Left 4 Dead add-ons → Valve’s L4D1 VPK instructions ↗ Valve’s L4D2 VPK instructions ↗

LEFT 4 DEAD 1 & 2

Start a custom campaign

Install every part of the campaign and enable it in Add-ons. When starting a game, choose Add-on Campaign in the campaign picker. For co-op, each player needs the same release of the campaign and its dependencies.

Browse maps and campaigns →

LEFT 4 DEAD 1 & 2

Textures, skyboxes and materials

For a VPK or Workshop item, use the game add-on steps above. For a Hammer kit, extract its materials folder into left4dead or left4dead2 inside the matching Steam game folder. Preserve the supplied paths so each .vmt can find its .vtf textures.

Open Hammer from the matching game’s Authoring Tools. For a skybox, set Map → Map Properties → SkyBox Texture Name to the value in the kit’s INSTALL.txt. For a brush material, select the supplied material in the Texture Browser. Include the kit’s required files when distributing your map.

Browse skyboxes → Browse textures →

LEFT 4 DEAD 1 & 2

Sound replacements

Check which sound the pack replaces and install it using its Workshop or VPK instructions. Test it with any other packs for that sound disabled. Keep the original folder layout for packs distributed as loose audio files and use the author’s instructions for their destination.

Browse sound packs →

LEFT 4 DEAD 1 & 2

Source console presets

  1. Download the .cfg file and check its game label. In Steam, use Manage → Browse local files on the matching game.
  2. Place the file in left4dead\cfg for L4D1 or left4dead2\cfg for L4D2.
  3. Start the game, enable the developer console in Options → Keyboard/Mouse, and open it. Run exec followed by the filename, for example exec my-preset.cfg.
Browse Left 4 Dead configs → Scooby profiles and folders →

GTA 5 · SCOOBY

Addon packs

  1. Check the package’s GTA edition, required loader and included readme. Download every part of a split archive before extracting it.
  2. For a pack supported by your Scooby build, open Addons/Replacements and use its import or folder control.
  3. Import the complete pack with its metadata and streaming dependencies. Use the package’s validation and load controls before spawning its models.
  4. For a pack that requires another loader, follow its original installation instructions instead of placing it in a vehicle preset folder.

Supported Legacy packs can use Settings → Converter for Enhanced. Check the converted result and the package’s requirements.

DLC and edition guide →

GTA 5 · SCOOBY

Menu wallpapers and background images

  1. Download the original image and check whether it is intended for ClickUI, a ListUI style or another appearance slot.
  2. For ClickUI, open the appearance image controls and use Open ClickUI Image Folder or Browse For Background.
  3. For ListUI, select the target style and image slot, then use that slot’s Open Folder or Browse control.
  4. Keep any supplied header, selector and background files together. Select the image and enable the matching appearance slot.

A wallpaper changes menu artwork. It does not install a game texture or a complete theme preset.

GTA 5 · NENYOO

Nenyoo saved vehicles

  1. Download a preset supported by Nenyoo’s vehicle importer. Keep its original JSON, XML, INI or TXT structure.
  2. Open Saved Vehicles → Open Folder, or open %LOCALAPPDATA%\Nenyoo\Plus\Vehicles.
  3. Copy the preset into the folder, return to Saved Vehicles and select it to spawn the build.
  4. Install any required addon models first. Check the intended GTA edition and attachments.

Supported Stand and Cherax vehicle data can use this importer. Their scripts, themes and translation files have separate host requirements.

GTA 5 · NENYOO

Nenyoo saved outfits

  1. Choose an outfit supported by Nenyoo’s outfit importer and check its required character model.
  2. Copy the original preset into %LOCALAPPDATA%\Nenyoo\Plus\Outfits.
  3. Open Outfits → Saved Outfits and select the file to apply it.
  4. Keep any required model assets and attachments with their original installation instructions.

The current library scans XML, JSON, INI, CFG and TXT files; the contents must match a supported outfit format. Supported other-menu data stays in its original format.

GTA 5 · NENYOO

Nenyoo placement maps

  1. Check that the download is a supported placement preset and install any required models first.
  2. Use the Spooner file controls to open the active map folder. Nenyoo’s Spooner files are under %LOCALAPPDATA%\Nenyoo\Plus\Spooner.
  3. Keep the preset and its supporting files together, then select it using the compatible Spooner loader.

Streamed map assets use the Addons / Maps category and their required loader. Preserve the original format and author instructions.

GTA 5 · NENYOO

Nenyoo DLC and addon library

  1. Download the complete package and check its edition and dependencies.
  2. Open Misc → Custom DLCs → Open install folder. The install inbox is %LOCALAPPDATA%\Nenyoo\Plus\DLC\_inbox.
  3. Place the supported archive or complete unpacked pack in the inbox. Keep its metadata and asset dependencies together.
  4. Allow the library to process the package, review the reported result, then open its pack entry and use its supported actions.

Models become available through the matching vehicle, model or object browser after loading. Follow the original readme for packages that require another loader.

GTA 5 · NENYOO

Nenyoo Lua themes

  1. Choose a theme packaged for Nenyoo. Extract its complete folder, including its theme Lua, fonts, images and bundled scripts.
  2. Place the folder in %LOCALAPPDATA%\Nenyoo\Plus\Themes. Keep the supplied relative paths intact.
  3. Open Settings → Choose Theme and select the installed theme. Use Reload Lua Theme after editing its files.

Nenyoo themes execute through its theme API. A style named Stand or X-Force still requires the Nenyoo version of that theme; original host presets and Scooby appearance JSON use their own loaders.

GTA 5 · NENYOO

Nenyoo config profiles

  1. Back up your current profile and choose an export made for your Nenyoo build.
  2. Use Settings → Config Profiles and its folder control when available. The native profile directory is %LOCALAPPDATA%\Nenyoo\Plus\Configs.
  3. Copy the complete profile there, return to Config Profiles and select its load action.

A profile supplies settings and hotkeys. Install its required themes, scripts and model assets separately.

GTA 5 · NENYOO

Nenyoo user scripts

  1. Check the listing’s download state and required Nenyoo API or explicitly supported dialect. Download pending means an installable package is not available yet.
  2. For an available compatible package, open Scripts → Open Scripts Folder. This opens %LOCALAPPDATA%\Nenyoo\Plus\Scripts\User.
  3. Preserve the package’s entry script, modules and relative folders. Select Refresh Script List, choose the script and use its load action.

Nenyoo builds can provide API compatibility layers, including the shipped Stand layer. Match the script’s required dialect and supported calls to your installed build; a source listing alone does not establish full runtime compatibility. Themes belong in Themes, and built-in API files belong to the menu installation.

GTA 5 · NENYOO

Nenyoo languages

  1. Open Settings → Language to choose a language supplied by your Nenyoo build.
  2. For an additional language package, check that it targets the same Nenyoo runtime and follow its included installation instructions.
  3. Keep the translation manifest and any required fonts with the package.

Nenyoo loads its translation assets through its runtime package. lang.cfg stores the selected language; it is not a translation catalog. Scooby Languages files use a different host format.

NENYOO

Bundled assets and loader translations

Match the resource to your Nenyoo build and keep its source filename and folder structure. Loader translations are shared between games. Fonts, textures and emote audio are listed under the game that supplies them.

Browse the Nenyoo source folders ↗

RED DEAD REDEMPTION 2 · NENYOO

RDR2 translations

Choose the language supplied with your Nenyoo RDR2 build. Match any replacement JSON to the RDR2 translation folder and keep the original filename. Use the Loader translations category for the launcher.

RED DEAD REDEMPTION 2 · NENYOO

Built-in RDR2 Lua modules

Use the Nenyoo RDR2 build that supplies these HUD and camera features. The catalog links to their original Lua source. The runtime loads the modules from its own feature folders.

GTA 5 · STAND

Stand vehicle presets

  1. For Stand’s built-in garage, choose an original Stand .txt vehicle preset.
  2. Open Vehicle → Garage → Open Folder and copy the preset there.
  3. Return to Garage, find the saved entry and select it. Install required addon models separately.

For Menyoo .xml and other supported construct formats, use the corresponding Lua importer, such as Stand Constructor. Check the resource for the required loader.

Stand’s documented controls →

GTA 5 · STAND

Stand outfit presets

  1. Choose an outfit for the required character model.
  2. Open Self → Appearance → Outfit → Wardrobe → Open Folder and copy the original Stand .txt preset there. Use a matching Lua importer for other outfit formats.
  3. Select it in Wardrobe to apply the outfit.
Stand’s documented controls →

GTA 5 · STAND

Stand themes and headers

  1. Download the original Stand theme package and preserve its profile, theme and header folders.
  2. Use Stand → Open Stand Folder to locate the active installation, then follow the package’s readme for its original destinations.
  3. If a theme includes a profile, open Stand → Profiles → Open Folder, install that profile and load it through Profiles.

The author’s optional ThemeRepo manager uses ThemeRepo.pluto in %APPDATA%\Stand\Lua Scripts. Back up existing artwork before using it: its documented downloads replace the Theme and Custom Headers folders.

A Scooby ListUI style called Stand is installed through Scooby’s appearance controls. It is a separate package format.

ThemeRepo author instructions →

GTA 5 · STAND

Stand profiles

Back up your current settings. Use Stand → Profiles → Open Folder, copy the matching profile and load it through Profiles. Profiles store command settings; install referenced scripts and artwork separately.

Stand’s documented controls →

GTA 5 · STAND

Stand Lua and Pluto scripts

  1. Check the required Stand version and API. A Download pending listing is a source reference until its package is available.
  2. Use Stand → Lua Scripts → Open Folder, or open %APPDATA%\Stand\Lua Scripts.
  3. Copy the available package’s original Lua or Pluto entry file and dependencies. Keep its resources and store directories where the author specifies.
  4. Select the installed script in Stand’s Lua Scripts library.

Stand’s Lua / Pluto API is separate from Scooby, Nenyoo, Cherax and X-Force scripting APIs.

Stand Lua API documentation →

GTA 5 · STAND

Stand language selection

Select a supplied language under Stand → Settings → Language. For a script translation, follow that script’s language instructions and preserve its language files. Use a manual menu-translation package only when its author documents the matching Stand build and installation method.

Stand’s language controls →

GTA 5 · CHERAX

Cherax vehicle and outfit presets

  1. For the built-in libraries, choose a Cherax .json preset for your version and the correct vehicle or character model.
  2. Open the matching saved-vehicle or outfit library. Use its Open Folder or Import control when provided; otherwise follow the resource’s original readme.
  3. Keep the file’s original format and dependencies. Refresh or reopen the library and select the imported preset.

Menyoo .xml, .ini and other menus’ JSON schemas need a compatible Lua loader. Check the listing for the matching importer.

Supported Cherax vehicle and outfit data can also use Scooby’s or Nenyoo’s importers. Select the destination menu above for its verified folders. This data support does not extend to Cherax Lua APIs, themes or languages.

GTA 5 · CHERAX

Cherax Lua scripts

  1. Check the required Cherax build and API. Its public API documentation specifies Lua 5.4; individual scripts can require a particular API generation.
  2. For an available matching package, open Cherax’s script folder control or use %APPDATA%\Cherax\Lua, the directory documented by Cherax.
  3. Copy the script with its complete dependency folders, then load it using Cherax’s script library.

If a script offers multiple versions, choose the release that matches your Cherax build and download that version.

Cherax Lua API and directory →

GTA 5 · CHERAX

Cherax themes, configs and languages

  1. Choose a file explicitly packaged for the installed Cherax build and the selected resource type.
  2. Open the corresponding appearance, config or language library. Use its import or folder control when available; otherwise use the destination in the author’s readme.
  3. Back up your current files, preserve the package structure and load it through the matching Cherax control.

For themes, select ClickGUI or ListUI in Cherax and import the files made for that interface. Dual-interface packs include separate settings for each interface.

GTA 5 · X-FORCE

X-Force saved vehicles and outfits

  1. Check that the resource is an original X-Force preset for your installed version.
  2. Use the corresponding saved-vehicle or outfit library’s import or folder control when provided. Follow the package’s documented destination if the menu does not expose one.
  3. Preserve its format and supporting files, then load it through that same library.

Check required models and the GTA edition before applying the preset.

GTA 5 · X-FORCE

X-Force UI presets

  1. Choose an original X-Force UI preset for your installed version.
  2. Use the menu’s UI preset folder control. The original reference installation stores UI presets under C:\X-Folder\files\ui.
  3. Keep its .ui file and required images together as instructed by the package, then select it through X-Force’s UI controls.

Scooby’s X-Force ListUI style has its own appearance loader and resource folders. Select Scooby above for those packages.

GTA 5 · X-FORCE

X-Force scripts

  1. Check the original author’s supported X-Force build, script API and dependencies.
  2. For an available package, use X-Force’s script-library folder or import control when provided. Follow the package readme for its entry script and supporting files.
  3. Load the script through that host’s script library.

A Download pending listing is not an installable script yet. Other menus’ vehicle or outfit import support does not establish X-Force Lua API compatibility.

GTA 5 · X-FORCE

X-Force config and language files

  1. Use a package documented for the installed X-Force version.
  2. Back up the existing file and use the matching config or language import / folder control when provided.
  3. Keep the original names and dependencies and follow the author’s readme for loading it.

Use an explicit destination from the installed host or the package documentation; these formats do not share Scooby’s config and Languages folders.

GTA 5 · STAND

Stand profiles and resource bundles

  1. Open the pack’s source page for its download and setup instructions.
  2. Back up your Stand folder before copying profiles, scripts or artwork. Keep the pack’s folder structure and follow the author’s instructions for each component.

GTA 5 · STAND

Addon vehicles

  1. Choose the package for your game edition from the author’s download page.
  2. Install the vehicle DLC using the Story Mode loader specified by the author.
  3. Load the installed vehicle by its model name. Keep saved Stand vehicle presets in their own garage folder.

GTA 5 · CHERAX

Vehicle DLC packs

  1. For a compatible ModVerse RPF7 pack, follow the ModVerse DLC setup for Cherax.
  2. For an author-hosted vehicle, choose the archive for your game edition and follow the author’s Story Mode installation instructions.
  3. Keep the model, textures and metadata together. Use the vehicle’s supplied model name after loading the DLC.

GTA 5 · ADDON ASSETS

DLC and addon requirements

  1. Read the addon’s original installation instructions and check the GTA edition and required loader.
  2. Install the full asset package through that documented loader. A downloaded model pack can require additional tools even when a preset is listed for .
  3. Preserve metadata, textures, model and animation dependencies. Use the package’s supplied model names after loading.

A saved vehicle or outfit preset does not install its referenced DLC assets. Only use a native addon importer when the installed menu explicitly supports that package format.

GTA 5 · APPEARANCE FILES

Menu wallpapers

  1. Choose artwork for the selected menu and its background or header slot.
  2. Open ’s matching appearance controls. Use the slot’s image browser or folder control when provided.
  3. Keep theme-bundled artwork at the relative paths specified by its author, then select or reload the corresponding image.

Wallpaper folders vary by menu, theme and version. Use the active appearance control or the package readme for its destination.

GTA 5 · PLACEMENT MAPS

Map presets that require Lua

Open the map through a Lua loader that supports its exact format. Use Constructor for supported Stand map files, or the matching Cherax importer listed on the resource, such as BiggerScript. Install any model dependencies separately.

GTA 5 · RESOURCE PACKAGES

Other files and required loaders

  1. Check the resource’s target game edition, required host and original installation instructions.
  2. Use the author’s documented loader for game assets, ASI plugins or .NET scripts. For a menu import, use the corresponding library’s folder control when provided.
  3. Keep the complete package and dependencies together and follow its activation instructions.

The selected menu identifies the destination collection. Each package still requires its stated loader and supported file format.

GTA 5 Legacy · Yim v1

Install Lua scripts in Yim v1 (Legacy)

  1. Download a package from Yim v1 Lua scripts, extract the ZIP, and check the included instructions for any dependencies.
  2. Open Settings → Lua Scripts → Open Lua Scripts Folder in YimMenu. You can also press Win + R and enter %AppData%\YimMenu\scripts.
  3. Copy the entry .lua file and its supporting files into that folder. Keep their relative paths. If the package tells you to copy a whole folder, such as SSV2, copy it intact.
  4. In Lua Scripts, select Reload All and look for the script. Check the package instructions for the tab or hotkey that opens it.

If a script fails to load, check that you extracted the ZIP, kept its dependencies together and downloaded the version for your YimMenu and game build. Libraries and Lua Language Server files have their own setup instructions.

GTA 5 Legacy · Yim v1

Import JSON and XML vehicles in Yim v1

  1. Download a vehicle pack and extract it. Pick the presets you want to add.
  2. Copy .json files to %AppData%\YimMenu\saved_json_vehicles or .xml files to %AppData%\YimMenu\xml_vehicles.
  3. Open the matching saved or XML vehicle list in YimMenu. Refresh the list and select a preset.

Some presets reference additional models or attachments. If a vehicle loads with parts missing, check that those assets are available in your game build.

GTA 5 Legacy · Yim v1

Import XML maps in Yim v1

  1. Extract the XML map pack and choose a map.
  2. Copy its .xml file to %AppData%\YimMenu\xml_maps.
  3. Open YimMenu’s XML map list, refresh it, and select the map. Load any models it requires before importing it.

GTA 5 Legacy · Yim v1

Import JSON outfits in Yim v1

  1. Extract the outfit pack and copy the chosen .json files to %AppData%\YimMenu\saved_outfits.
  2. Open YimMenu’s saved outfits, refresh the list, and select the preset for your character model.

GTA 5 Enhanced · Yim v2

Install Lua scripts in Yim v2 (Enhanced)

  1. Download a package from Yim v2 Lua scripts and extract the ZIP.
  2. In YimMenu v2, open Settings → Lua Scripts → Open Lua Scripts Folder. You can also open %AppData%\YimMenuV2\scripts directly.
  3. Copy the files as directed by the package. For Samurai’s Scripts Enhanced, copy samurais_v2.lua and the includes folder from SSV2-enhanced into scripts. Keep the folder contents together.
  4. Open Lua Scripts. If the new script appears under Disabled, select it to load it. If it is already enabled and you replaced its files, select it and choose Reload.

YimMenu v2 uses its own Lua API. Match the script’s stated YimMenu v2 and GTA 5 Enhanced build requirements when troubleshooting a load error.