Flint's Unofficial List of Support Guidelines

I would follow this guide before posting a support forum.

If you post a support forum, make sure to look this over with the "Search" feature at the top of this page and see if anyone else has your issue.

-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------

No matter what issue you encounter, post a log of your RagePluginHook console because this helps users, and G17 Media watch what your issue is. Your RagePluginHook console log is in your main GTA V directory as "RagePluginHook.txt".

-------------------------------------------------------------------------------------------------------------

Also, if you have any third party mods installed always list them as they can cause issues with LSPDFR. (EX: Wanted Levels Working, ETC)

-------------------------------------------------------------------------------------------------------------

Search the rest of the web if your issue has been addressed somewhere else. (EX: Someone could have the same issue, but post it at RagePluginHook.net)

-------------------------------------------------------------------------------------------------------------

Always before you post a support forum try to troubleshoot the issue yourself, this could be simply deleting a mod and seeing if that fixes it, but make sure you try to fix it yourself before bringing it to the community.

-------------------------------------------------------------------------------------------------------------

This is just a short start to these guidelines this list is planned to be VERY long as time goes by, and I watch the support forums people send in. If you have something you would like me to add to these guidelines let me know in the replies.

 

Edited July 17, 201510 yr by FlintSpellhunter

We already have this, there is no need to make your own: 

 

If you feel this topic has been closed in error, please report this post.