Shipping

Installing the resource

Drop the exported resource into your server and run it.

Once you've designed your interface in Easelt Builder and exported it, you'll have a ready-to-run MTA:SA resource waiting in a .zip file. This page walks you through every step of dropping that resource into your server, starting it, and getting your GUI to draw for players — plus a few common gotchas and how to fix them.

What's in your export

When you export from Easelt Builder, you get a .zip containing a complete, self-contained MTA:SA resource. Before you install anything, it helps to know what each piece does.

meta.xml

The resource manifest. It declares your scripts as type="client" and lists the files MTA should load and send to players.

gui.lua

The client-side dx drawing code that renders your interface — the panels, buttons, sliders and text you designed.

lib.lua

The supporting library your GUI relies on. Keep it alongside gui.lua at all times.

assets/

The folder holding any images and other assets your design references.

ℹ️

The scripts are client-side dx drawing — meta.xml declares them type="client", so the GUI draws locally for each player who receives the resource.

Install it step by step

Unzip into your resources directory
Extract the exported folder into your server's resources directory, for example server/mods/deathmatch/resources/. Keep meta.xml, gui.lua, lib.lua and the assets/ folder together inside that one resource folder.
Refresh the resource list
In the server console or your admin panel, run /refresh so MTA scans the resources directory and picks up the newly added resource.
Start the resource
Run /start <resourceName>, replacing <resourceName> with your resource's folder name. MTA will begin sending the client files to connected players.
Show the cursor for interaction
For buttons and sliders to register clicks, make sure showCursor(true) is called for the player — either from your gamemode or from a small trigger resource of your own.

Server commands reference

These are the two commands you'll run to get the resource live. Type them into the server console or your admin panel.

Command	What it does
/refresh	Rescans the resources directory so MTA sees the newly added resource.
/start <resourceName>	Starts the resource and begins sending the client GUI to players.

How the GUI reaches players

Because the scripts are client-side, the GUI draws individually for each player who receives the resource. When you /start the resource, MTA streams the client files to connected players and the dx drawing runs on their machine — there's no per-player server rendering to manage.

💡

For clickable controls to work, showCursor(true) must be active for the player. Without a visible cursor, buttons and sliders can't receive clicks.

Renaming the resource

You're free to rename the resource folder to whatever fits your server's naming convention. Just remember to start it by that new folder name with /start <resourceName>.

⚠️

When you rename, keep meta.xml, gui.lua and lib.lua together in the same folder. Splitting them apart will break the resource.

Troubleshooting

Symptom	Fix
Nothing shows up on screen	Confirm the resource is actually started (`/start <resourceName>`) and that the client has downloaded it — client-side files must reach the player before anything draws.
Clicks don't work	Make sure `showCursor(true)` is called for the player. Buttons and sliders need a visible cursor to register clicks.

💡

If a change to your design isn't appearing, run /refresh again after re-exporting and re-adding the resource, then /start it so MTA resends the updated client files.