Debugging Common Issues

This guide outlines steps to troubleshoot and resolve common issues that may arise with The A Team resources on your FiveM server.

Step 1: Check the Server Console

1. Start or restart your server.
2. Open the server console and monitor for any error messages or warnings related to the resource.
3. Note down any specific error codes or descriptions.

Step 2: Monitor Resource Performance

Client-Side Monitoring

1. Press F8 to open the FiveM console.
2. For FiveM beta version users only:
   • Type resmon to open the resource monitor (Also available from the menu in the console)
   • You can view:
     • CPU time (ms)
     • Memory usage
     • Network bandwidth
   • Sort resources by CPU time to identify performance bottlenecks
3. For all FiveM versions, you can use these console commands: (Untested - TODO Test this)

   resmon basic      # Basic monitoring
   resmon dynamic    # Dynamic resource usage
   resmon time      # Time-based metrics

Server-Side Monitoring

1. Access the server console and type:

   svgui
2. Look for resources with high response times (ms).
3. Resources consistently showing high ms values may indicate:
   • Memory leaks
   • Inefficient code execution
   • Resource conflicts

Step 3: Validate Configuration Files

1. Open the resource’s configuration file (e.g., config.lua).
2. Check for:
   • Missing or incorrect values.
   • Invalid syntax (e.g., missing commas or brackets).
3. Compare your settings with the default configuration file provided with the resource.

Step 4: Verify Resource Loading

Ensure the resource is correctly loaded in server.cfg:

1. Open server.cfg.
2. Confirm the ensure resource_name line is present and correctly spelled.

Example:

ensure resource_name

Step 5: Test in Isolation

Disable other resources to isolate the issue:

1. Comment out other unimportant resource lines in server.cfg by adding # at the start of the line:

   #ensure another_resource
2. Restart the server with only the problematic resource enabled.
3. Check if the issue persists.

Step 6: Check Client-Side Errors

If the issue affects players:

1. Ask a player experiencing the issue to open their FiveM client console (F8 key).
2. Look for error messages related to the resource.
3. Collect screenshots or logs for further analysis.

Step 7: Review Documentation

Refer to the documentation provided with the resource. Look for:

• Known issues and their resolutions.
• Specific setup instructions that may have been missed.

Step 8: Reinstall the Resource

If all else fails:

1. Delete the resource folder from the resources directory.
2. Download a fresh copy from The A Team store.
3. Reinstall and configure the resource.

Step 9: Contact Support

If the issue persists, reach out to The A Team support team with the following information:

• Error messages from the server or client console.
• A copy of the server.cfg file.
• Details of any custom modifications made to the resource.

Debugging can be a straightforward process when you follow these steps. Proper error logging and isolation will help you resolve most issues efficiently.