Skip to main content

​
Troubleshooting Common Issues

Before seeking support, please ensure your server artifacts are up-to-date, you’ve restarted your server after installation/changes, and you’ve checked the F8 client console and server console for specific error messages.
  • Solution: - Verify that you have correctly added ensure rs_clothing (or your correct resource folder name) to your server.cfg. - Check the server console for any error messages when the script attempts to start. These messages can provide clues about missing dependencies (like ESX itself, esx_skin, skinchanger) or configuration errors within config.lua.
  • Ensure the folder name of the script in your resources directory matches the name you used in server.cfg (case-sensitive on Linux).
  • Solution: - Confirm that your ESX version is compatible (e.g., ESX v1.2, ESX Legacy). Check the script’s purchase page or main documentation for version requirements. - Make sure es_extended (or your ESX base) is running correctly and is one of the first resources started in your server.cfg. - Ensure esx_skin and skinchanger are installed, up-to-date, and functioning correctly as they are crucial dependencies for character appearance.
  • Solution: This feature requires OneSync to be enabled on your server and set to infinity (e.g., onesync_enable infinity in your server.cfg). Verify your OneSync configuration. - If Config.Dimension is set to false in config.lua, this feature will be disabled.
  • Solution: - Double-check your Config.Categories in config.lua for correct item IDs (drawable IDs), texture IDs, pricing, and any Overrides.
  • Ensure that custom labels and specific settings for items are correctly formatted. A misplaced comma or bracket can break parts of the config. - Verify that the category IDs (e.g., arms, tshirt_1) and item IDs are valid for the ped models (male/female) being used.
  • Solution: - Review the Config.Locations section in config.lua. - Ensure coordinates (Location = vector4(...)) are correct for each store. - Verify that ShowMarker = true and ShowBlip = true are set for the locations you want visible. - Check that the marker types, blip sprites, and colors are valid according to FiveM documentation.
  • Solution: - Check Config.OpenMenuKey in config.lua to confirm which key is set. - Ensure you are within the InteractDist defined for the marker in Config.Locations. - Look for client-side errors in the F8 console that might indicate an issue with the key press or menu opening function. - Check for resource conflicts if another script is using the same key press in the same context.

​
Getting Support

If you’ve gone through the troubleshooting steps and are still experiencing issues:

Resrant Scripts Discord

Join our official Discord server. This is the primary way to receive direct support, report bugs, and engage with the community.

Check Consoles for Errors

Before asking for support, please gather any relevant error messages from: - Your F8 client console (press F8 in-game). - Your server console. Providing these errors helps us diagnose the issue much faster.

Verify Dependencies

Double-check that all required dependencies (ESX, esx_skin, skinchanger, and any others mentioned by the script) are installed, up-to-date, and working correctly.

Review `config.lua` Carefully

Many issues stem from simple syntax errors (like missing commas) or misconfigured options in config.lua. Review it carefully, perhaps using a Lua validator.

​
Additional Resources

These resources can be helpful for general FiveM development and understanding how ESX and related systems work:

ESX Documentation

Official documentation for the ESX Framework.

FiveM Server Setup Guide

A comprehensive guide to setting up and maintaining a FiveM server.

FiveM Native Reference

Documentation for FiveM native functions, useful for understanding game mechanics and scripting.