Documentation

Cookie Development Documentation

Select a product from the left menu to view its installation guide, setup notes, commands, and usage details.

Cookie Development

Product-Based Documentation

Every package added to your Tebex store appears here automatically under its own category.

Scripts

Cookie Development - Los Angeles Minimap Pack

Installation and setup guide for the Los Angeles Minimap Pack.

FiveM Asset Minimap Pack View Product

Installation

  1. Download the Los Angeles Minimap Pack from your Tebex order.
  2. Extract the downloaded file.
  3. Move the resource folder into your FiveM server resources folder.
  4. Open your server.cfg file.
  5. Add the resource with an ensure line.
  6. Restart your server.
ensure cookie-minimap

Important Notes

  • Do not rename stream files unless the product instructions say so.
  • Make sure the folder name matches the server.cfg ensure line.
  • If the minimap does not update immediately, clear your FiveM cache.
  • Restart the server after installation.
‹ Back to Home
Others

Cookie Development - FiveM Resource Security Scanner

A local resource scanner designed to help you review FiveM resources and identify files or patterns that may require manual security checks.

Desktop Scanner FiveM Resources HTML Report View Category

How to Use

  1. Download the scanner package from your Tebex order.
  2. Extract the downloaded files to a folder on your computer.
  3. Open the Cookie Development FiveM Resource Security Scanner application.
  4. Select the FiveM resource folder or ZIP file you want to scan.
  5. Start the scan and wait until the report is generated.
  6. Open the generated HTML report to review the results.

Understanding the Report

  • Clean / No Match: The scanner did not find a matching pattern in the checked files.
  • Suspicious: A file or code pattern needs manual review before you install or use the resource.
  • High Risk: Review the flagged file carefully and remove or replace the resource if you cannot verify its source.
Important: A scanner result is a security aid, not a guarantee. A clean result does not prove that a resource is completely safe, and a suspicious result does not automatically prove that a file is malicious. Always review unknown code, verify the resource source, and keep backups before installing new resources on a live server.

Best Practices

  • Scan every new or updated resource before adding it to your server.
  • Keep the generated HTML reports for your own review history.
  • Check flagged files manually, especially server-side Lua, JavaScript, and configuration files.
  • Never install unknown resources directly on a production server without testing.
  • Use trusted sources and keep backups of your server files and database.
‹ Back to Home