r_scripts Docs.
  • Introduction
  • Paid Resources
    • r_notify
      • Installation
      • Configuration
      • API
    • r_trapphone
      • Dependencies
      • Installation
      • Configuration
      • Common Errors
    • r_killfeed
      • Dependencies
      • Installation
      • Configuration
    • r_prison
      • Dependencies
      • Installation
      • Configuration
      • API
        • Client
        • Server
    • r_lottery
      • Dependencies
      • Installation
      • Configuration
    • r_blackmarket
      • Dependencies
      • Installation
      • Configuration
    • r_storageunits
      • Dependencies
      • Installation
      • Configuration
    • r_buddies
      • Dependencies
      • Installation
      • Configuration
  • Free Resources
    • r_bridge
      • Dependencies
      • Compatibilities
      • Installation
      • Configuration
    • r_communityservice
      • Dependencies
      • Installation
      • Configuration
    • r_drugsales
      • Dependencies
      • Installation
      • Configuration
    • r_energydrinks
      • Dependencies
      • Installation
      • Configuration
    • r_moneywash
      • Dependencies
      • Installation
      • Configuration
    • r_whippets
      • Dependencies
      • Installation
      • Configuration
Powered by GitBook
On this page
  • Misconfiguration Code 1801
  • Misconfiguration Code 1802
  1. Paid Resources
  2. r_trapphone

Common Errors

Last updated 3 months ago

This section will cover some of the common configuration errors and how to solve them.

Misconfiguration Code 1801

This error is thrown when you have a drug in the cfg_regions.luafile that is not present in the main config. Go over your configuration files and be sure the drug names are all correct and matching those in your inventory system.


Misconfiguration Code 1802

This error is thrown when you have duplicate contact names within the cfg_regions.luafile. This will cause major issues within the resource, be sure that every potential contact has a unique name within the resource.


For any other issues, open a support ticket in our

Discord