🔰 FFA Script
Troubleshooting
Common issues and solutions for the FFA Script, plus support channels.
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.
Database Issues: `insert.sql` not importing or errors related to FFA tables.
Database Issues: `insert.sql` not importing or errors related to FFA tables.
Script Not Starting / Errors on Server Start
Script Not Starting / Errors on Server Start
- Solution: - Verify that you have correctly added
ensure rs_ffa(or your correct resource folder name) to yourserver.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) or configuration errors withinconfig.lua. - Ensure the folder name of the script in yourresourcesdirectory matches the name you used inserver.cfg(case-sensitive on Linux).
ESX Framework Compatibility Issues
ESX Framework Compatibility Issues
- 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 yourserver.cfg. - Ensure all required ESX dependencies are installed, up-to-date, and functioning correctly.
Players Not Spawning in FFA Zone / Spawn Issues
Players Not Spawning in FFA Zone / Spawn Issues
- Solution: - Check the spawn coordinates in
Config.SpawnPointswithinconfig.luato ensure they are valid and accessible. - Verify that the spawn points are not inside walls, underground, or in unreachable locations. - If using custom spawn logic, ensure the spawning functions are working correctly and not conflicting with other scripts.
Weapons Not Working / Missing Weapons in FFA
Weapons Not Working / Missing Weapons in FFA
- Solution: - Double-check your
Config.Weaponsinconfig.luafor correct weapon hashes and configurations. - Ensure that weapon spawn settings are properly configured and that players have the necessary permissions. - Verify that weapon restrictions or allowlists are not preventing weapons from being given to players in the FFA zone.
FFA Zone Markers or Blips Not Showing
FFA Zone Markers or Blips Not Showing
- Solution: - Review the
Config.Zonessection inconfig.lua. - Ensure coordinates (Location = vector3(...)) are correct for each FFA zone. - Verify thatShowMarker = trueandShowBlip = trueare set for the zones you want visible. - Check that the marker types, blip sprites, and colors are valid according to FiveM documentation.
Cannot Enter FFA Zone / Interaction Not Working
Cannot Enter FFA Zone / Interaction Not Working
- Solution: - Check
Config.EnterKeyinconfig.luato confirm which key is set for entering the FFA zone. - Ensure you are within theInteractDistdefined for the zone marker. - Look for client-side errors in the F8 console that might indicate an issue with the key press or zone entry function. - Check for resource conflicts if another script is using the same key press in the same context.
Score/Kill Tracking Not Working
Score/Kill Tracking Not Working
- Solution: - Verify that the kill tracking functions are properly configured in the script. - Check database permissions and ensure the score/statistics tables are correctly set up. - Look for any errors in the server console related to database queries or player statistics. - Ensure that the script has proper event handlers for player deaths and kills.
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.