How to Install and Manage Resources in MTA:SA — Complete Guide

Resources are the fundamental unit of any Multi Theft Auto: San Andreas server. Everything that runs on the server — gamemodes, maps, admin systems, custom scripts, visual assets — is packaged as a resource. Understanding how to install, organize, and manage these packages is what separates a server that works from one that breaks on every deploy.

This tutorial is for anyone setting up or customizing an MTA:SA server who needs to add third-party resources (community.multitheftauto.com), build their own, or reorganize a resources/ folder that has become a mess. We will cover folder structure, meta.xml syntax, dependency management, ACL, and the operational commands you will use every day. Estimated execution time: 25 to 40 minutes, depending on how many resources you need to configure.

Assumption: you already have an MTA:SA server installed and running, with access to the console (terminal or panel) and to the server files via SSH, SFTP, or management panel.

Prerequisites

Structure of a resource

An MTA:SA resource is simply a folder inside mods/deathmatch/resources/ that contains, at minimum, a meta.xml file. The folder name becomes the resource identifier — it is the name you use in start, stop, refresh, and in any reference via getResourceFromName().

The minimal structure looks like this:

mods/deathmatch/resources/
├── my-resource/
│   ├── meta.xml
│   ├── server.lua
│   ├── client.lua
│   └── files/
│       └── image.png

The meta.xml declares three things: metadata (author, version, description), files that compose the resource (scripts, maps, client files), and dependencies (other resources that must be running before).

cd /path/to/server/mods/deathmatch/resources
mkdir my-resource
cd my-resource

<meta>
    <info author="YourName" version="1.0.0" type="script"
          description="Short description of the resource" />
    <script src="server.lua" type="server" />
    <script src="client.lua" type="client" />
</meta>

<file src="files/image.png" />
<file src="sounds/effect.wav" />

Managing dependencies between resources

Resources rarely live in isolation. An admin system may depend on a UI lib; a gamemode may depend on a scoreboard system. Declaring dependencies correctly avoids the classic scenario: resource A starts, calls an exported function from resource B, and B has not finished loading yet.

<meta>
    <info author="YourName" version="1.0.0" type="script" />
    <script src="server.lua" type="server" />
    <include resource="scoreboard" />
    <include resource="mysql-lib" />
</meta>

-- server.lua of the consuming resource
local success = exports["scoreboard"]:addScoreboardColumn("Kills")

if not success then
    outputDebugString("Failed to add scoreboard column", 1)
end

Day-to-day operational commands

All resource control runs through the server console (the terminal where mta-server64 is running, or the console tab in the game server management panel). These commands do not require a server restart — changes are applied live.

refresh

start my-resource

<resource src="my-resource" startup="1" protected="0" />

ACL — Access Control List

Resources that try to use administrative functions (kickPlayer, banPlayer, setElementData on other players, internal database access) need explicit ACL permission. Without it, the function returns false and emits a warning in the console.

ACL: aclrequest list <resource-name>
ACL: aclrequest allow <resource-name> all

aclrequest list admin-system

aclrequest allow admin-system all

Verification

Confirm that everything is working:

info my-resource

Expected output includes State: Running, list of active scripts, and export count. If the state is Loaded but not Running, the resource loaded but failed to start — check the console for Lua errors.

To validate client-side scripts, join the server with the MTA:SA client, open the in-game console (F8), and run:

debugscript 3

Level 3 shows errors, warnings, and debug messages from the client side. Errors in client files often appear only here, not in the server console.

Troubleshooting

Resource does not appear on refresh

Most common cause: malformed meta.xml. XML does not tolerate unclosed tags or attributes without quotes. Validate with any online parser or open it in VSCode with the XML extension. Secondary cause: folder name containing a space or special character (accent, cedilla) — rename to pure ASCII.

Error “Couldn’t find file ‘file.lua’ for resource”

The meta.xml references a file that does not exist or has a typo in the name. Remember that Linux is case-sensitive: Server.lua and server.lua are different files. List the folder contents with ls -la and compare exactly with the src= value in meta.xml.

Resource starts but functions do not work

Usually this is an ACL issue (admin function without permission) or a dependency issue (provider resource not running). Run info <name> on the consumer to see pending ACL requests, and resources to confirm the provider is Running.

”Unable to start resource X (dependencies not met)”

The dependency declared in <include> does not exist in the resources/ folder or failed to start. Download and install the dependency first, or remove the <include> if the dependency is not actually required.

Next steps

With resources operational, it pays to go deeper on three fronts: automated backups of the resources/ folder before each deploy, version control via Git (commit the whole folder excluding logs and cache), and exception monitoring via outputDebugString centralized in a logging resource.

If you are putting an MTA:SA server into production with many concurrent players, a Hostini VPS already comes with latency optimized for the Americas and edge DDoS protection — a noticeable difference on servers with 50+ slots where the host’s lag freezes everything. For frequent deploys, consider automating via a webhook that runs git pull on the resources/ folder and triggers refreshall in the server console.