FAQ & tips

Answers to common questions, plus practical tips.

This page answers the questions Easelt Builder users ask most, and shares tips for getting the cleanest, most predictable results out of your MTA:SA dx GUIs. If you're new here, the short version is: everything runs in your browser, your work stays private, and your designs are built to survive whatever resolution your players run.

Privacy & storage

Is my work uploaded anywhere?

No. Easelt Builder runs entirely in your browser, and your designs are saved locally on your own machine. Your work is encrypted at rest and there is no server sync — nothing you build is sent to a server, uploaded to the cloud, or shared with anyone unless you export it and hand it over yourself.

Resolutions & scaling

Does my design work on all resolutions?

Yes. Easelt Builder stores every position and size as fractions of the screen rather than fixed pixels. That means a panel you place in the center stays centered, and an element sized to a third of the width stays a third of the width, whether the player is on 1280×720 or 3840×2160. Your layout scales cleanly across every resolution.

Text, rotation & rendering

Why doesn't my rotated text tilt?

MTA:SA's dxDrawText cannot rotate text — the letters always render upright. When you rotate a text element in Easelt Builder, the box rotates but the letters stay upright, which is exactly how it will look in-game. This is deliberate WYSIWYG behavior: the builder shows you the real engine result rather than a tilt that would never appear on your players' screens.

In-game behavior

Why don't my buttons respond in-game?

Your dx elements only receive clicks when the cursor is visible. The host resource must call `showCursor(true)` to enable interaction. If your buttons look right but nothing happens when you click them in-game, this is almost always the reason.

Assets: images & fonts

Can I use my own images and fonts?

Yes. Import your own images and fonts directly from the inspector. When you export your design, they ship alongside it in the assets/ folder, so your custom artwork and typography travel with the resource and are ready to use in-game with no extra setup.

Interactivity with Blueprint

How do I add click logic?

Open Blueprint, wire up your logic there, and then export. Blueprint is where behavior lives — you connect what happens when an element is clicked, then the exported resource carries that logic into the game.

How do I test before exporting?

In Blueprint, press ▶ Test to run your design and interactions live. This lets you confirm your click logic and flow behave the way you expect before you commit to an export.

1. Design your GUI
   Lay out your elements on the canvas and style them in the inspector.
2. Open Blueprint
   Switch to Blueprint to add click logic and behavior.
3. Test with ▶
   Press ▶ Test to run your design live and verify interactions.
4. Export
   Export when everything works — your logic and assets ship together.

Languages & localization

Does it support Arabic?

Yes. Arabic text is reshaped and reordered on export so it renders correctly in-game, where MTA:SA won't do that shaping for you. You type Arabic naturally in the builder and Easelt Builder handles the right-to-left ordering and letter joining when you export.

In what languages is this documentation available?

This documentation is available in five languages:

• English
• Arabic
• French
• Portuguese
• Spanish

Multiple designs & screens

Can I have multiple designs or screens?

Yes. Use File → Designs… to create and manage multiple designs, and use `switchDesign` in Blueprint to move between screens at runtime — perfect for multi-panel interfaces, menus that swap views, or a login screen that hands off to a main dashboard.

About Easelt Builder

What are Easelt and C4?

Easelt Builder is the product — the browser-based visual designer you're using. Easelt · C4 is the maker and copyright holder behind it.

Tips for cleaner designs