Docs

Documentation

Installation guides, configuration references and troubleshooting for every script.

General installation

The installation steps shared by every MD SCRIPTS resource, from download to first restart.

Welcome to the MD SCRIPTS documentation. This guide covers the steps shared by every script in the catalog. Read it once, then open the page of the script you purchased for its specific options.

Prerequisites

Before installing any MD SCRIPTS resource, make sure your server meets the following requirements:

  • A FiveM or RedM server running a recent recommended artifact build
  • ox_lib version 3.0 or newer, started before any MD SCRIPTS resource
  • oxmysql connected to a MySQL or MariaDB database
  • A supported framework: QBX, Qbox or ESX (most scripts also offer a standalone mode)
  • Basic familiarity with your server.cfg and the server console

Installation steps

  1. Download the resource archive from your Tebex receipt or your keymaster panel.
  2. Extract the archive into your resources folder. Keep the folder name unchanged.
  3. If the script ships an install.sql file, import it into your database once.
  4. Add the resource to your server configuration, always after its dependencies:
ensure ox_lib
ensure oxmysql
ensure md_script
  1. Restart the server. The script prints a confirmation line in the console when it boots correctly.

Configuration

All options live in config.lua at the root of the resource. The options below exist in every MD SCRIPTS resource; script specific options are documented on each script page.

OptionTypeDefaultDescription
Config.Frameworkstring"auto"Framework detection: "auto", "qbx", "esx" or "standalone".
Config.Localestring"en"Language used for in-game text. Locale files live in the locales folder.
Config.DebugbooleanfalsePrints verbose logs to the server console. Disable in production.
Config.UseTargetbooleantrueRoutes interactions through ox_target instead of key presses.
Config.SaveIntervalnumber300Seconds between automatic database saves.
Config.AdminGroupsstring[]{ "admin" }Groups allowed to use the admin commands of the script.

Troubleshooting

The resource fails to start with a "couldn't load resource" error. The folder was renamed or nested twice during extraction. The manifest must sit at resources/md_script/fxmanifest.lua, not one level deeper.

The console shows "No such export ... in resource ox_lib". Your ox_lib copy is outdated. Update it to the latest release, then restart the server.

Nothing saves to the database. oxmysql is not connected. Check your mysql_connection_string convar and confirm the credentials work from a database client.