Multi Theft Auto: Wiki - Recent changes [en]

User:PandaBesh

PandaBesh — Thu, 09 Jul 2026 18:28:31 GMT

User account PandaBesh was created

User:Henrique Mello Sillva

Henrique Mello — Thu, 09 Jul 2026 18:23:49 GMT

User account Henrique Mello Sillva was created by Henrique Mello

User:Henrique Mello

Henrique Mello — Thu, 09 Jul 2026 18:22:20 GMT

User account Henrique Mello was created

User:QUANBOSS

QUANBOSS — Wed, 08 Jul 2026 00:57:12 GMT

User account QUANBOSS was created

User:Rondo

Rondo — Sat, 04 Jul 2026 19:28:20 GMT

User account Rondo was created

User:Titania2233socaspanosinvejosos

Titania2233socaspanosinvejosos — Sat, 04 Jul 2026 02:24:10 GMT

User account Titania2233socaspanosinvejosos was created

MacOS

LopSided — Fri, 03 Jul 2026 11:19:26 GMT

Replace outdated link to Wineskin Winery

← Older revision		Revision as of 11:19, 3 July 2026
Line 23:		Line 23:

	=== Grabbing the Winery===		=== Grabbing the Winery===
	* Grab the [~~http~~://wineskin.~~urgesoftware~~.~~com~~/~~tiki-index.php?page=Downloads~~ Wineskin Winery]. At the time of writing, v1.7. This allows you to create your own wrapper.		* Grab the [https://sourceforge.net/projects/wineskin/files/Wineskin%20Winery.app%20Version%201.7.zip/download Wineskin Winery]. At the time of writing, v1.7. This allows you to create your own wrapper.
	* Open ''Wineskin Winery.app'', and [[Media:MacOS_wineskin_tut1.png\|click "Update" underneath "No Wrapper Installed" to download the master wrapper.]].		* Open ''Wineskin Winery.app'', and [[Media:MacOS_wineskin_tut1.png\|click "Update" underneath "No Wrapper Installed" to download the master wrapper.]].
	* Now click the + plus button. This will bring up a new window titled "Add Engine".		* Now click the + plus button. This will bring up a new window titled "Add Engine".

Dumpdelete

IManGaaX — Wed, 01 Jul 2026 05:57:24 GMT

← Older revision		Revision as of 05:57, 1 July 2026
Line 1:		Line 1:
	{{Useful Function}}		{{Useful Function}} __NOTOC__
	<lowercasetitle>dumpdelete</lowercasetitle>		<lowercasetitle>dumpdelete</lowercasetitle>
	~~__NOTOC__~~
	This function recursively deletes elements inside a table, and if the element is a valid game object (such as a timer or an element), it destroys element or kills the timer.		This function recursively deletes elements inside a table, and if the element is a valid game object (such as a timer or an element), it destroys element or kills the timer.

	==Syntax==		==Syntax==
	<syntaxhighlight lang="lua">dumpdelete( table o )</syntaxhighlight>		<syntaxhighlight lang="lua">dumpdelete( table o )</syntaxhighlight>

	===Required Arguments===		===Required Arguments===
	* '''o''': The table or object to recursively process and delete its elements.		* '''o''': The table or object to recursively process and delete its elements.

	===Returns===		===Returns===
	This function does not return any value. It processes the table and deletes elements as required.		This function does not return any value. It processes the table and deletes elements as required.

	==Code==		==Code==
	<section name="~~Server- and/or clientside Script~~" class="both" show="true">		<section name="Shared" class="both" show="true">
	<syntaxhighlight lang="lua">		<syntaxhighlight lang="lua">
	function dumpdelete(o)		local visited = {}
	if type(o) == 'table' then
	for k, v in pairs(o) do		function dumpdelete(o)
	dumpdelete(v)		if type(o) == 'table' then
	end		if visited[o] then return end
	else		visited[o] = true
	if isElement(o) then
	destroyElement(o)		for k, v in pairs(o) do
	~~end~~		if type(v) == 'table' then
	if isTimer(o) then		dumpdelete(v)
	killTimer(o)		elseif isElement(v) then
	end		destroyElement(v)
	end		elseif isTimer(v) then
	end		killTimer(v)
			end
			o[k] = nil
			end

			visited[o] = nil
			else
			if isElement(o) then
			destroyElement(o)
			elseif isTimer(o) then
			killTimer(o)
			end
			end
			end
	</syntaxhighlight>		</syntaxhighlight>
	</section>		</section>

	==Example==		'''Author:''' Xenius
	<section name="~~Server- and/or clientside Script~~" class="both" show="true">
	<syntaxhighlight lang="lua">local vehicle = createVehicle(411, 0, 0, 0)		==Example==
			<section name="Shared" class="both" show="true">
			<syntaxhighlight lang="lua">
			local vehicle = createVehicle(411, 0, 0, 0)
	local ped = createPed(200, 0, 0, 0)		local ped = createPed(200, 0, 0, 0)
	local timer = setTimer(function() end, 1000, 0)		local timer = setTimer(function() end, 1000, 0)
Line 53:		Line 68:
	</section>		</section>

	~~Author: Xenius~~		==See Also==

	~~==See Also==~~
	{{Useful_Functions}}		{{Useful_Functions}}

User:IManGaaX

IManGaaX — Tue, 30 Jun 2026 05:34:05 GMT

← Older revision		Revision as of 05:34, 30 June 2026
Line 25:		Line 25:
	*[[getClosestPoint]] <span style="color:gray; font-size:smaller;">» This function finds the closest point from a given element to a list of points in 2D space.</span>		*[[getClosestPoint]] <span style="color:gray; font-size:smaller;">» This function finds the closest point from a given element to a list of points in 2D space.</span>
	*[[setVehicleDirtEnabled]] <span style="color:gray; font-size:smaller;">» This function toggles a dirt removal shader effect on the specified vehicle.</span>		*[[setVehicleDirtEnabled]] <span style="color:gray; font-size:smaller;">» This function toggles a dirt removal shader effect on the specified vehicle.</span>
			*[[wait]] <span style="color:gray; font-size:smaller;">» This function pauses the execution of a function for a specific amount of time. It allows you to write sequential, readable code instead of using complex callback structures or multiple timers.</span>
	</div>		</div>

Wait

IManGaaX — Tue, 30 Jun 2026 05:12:00 GMT

← Older revision		Revision as of 05:12, 30 June 2026
(2 intermediate revisions by the same user not shown)
Line 6:		Line 6:

	==Syntax==		==Syntax==
	<syntaxhighlight lang="lua">void ~~Wait~~( int milliseconds )</syntaxhighlight>		<syntaxhighlight lang="lua">void wait( int milliseconds )</syntaxhighlight>

	===Required Arguments===		===Required Arguments===
Line 32:		Line 32:
	end		end

	function ~~Wait~~(ms)		function wait(ms)
	local co = coroutine.running()		local co = coroutine.running()

	if not co then		if not co then
	outputDebugString("~~Wait~~() must be called inside an async function!", 1)		outputDebugString("wait() must be called inside an async function!", 1)
	end		end

Line 58:		Line 58:
	outputChatBox("Script started!")		outputChatBox("Script started!")

	~~Wait~~(1000)		wait(1000)

	outputChatBox("1 second has passed.")		outputChatBox("1 second has passed.")

	~~Wait~~(2000)		wait(2000)

	outputChatBox("3 seconds total.")		outputChatBox("3 seconds total.")
Line 73:		Line 73:
	outputChatBox("Loading data..", 0, 255, 0)		outputChatBox("Loading data..", 0, 255, 0)

	~~Wait~~(1500)		wait(1500)

	outputChatBox("Welcome iManGaaX!", 0, 255, 0)		outputChatBox("Welcome iManGaaX!", 0, 255, 0)

	~~Wait~~(3000)		wait(3000)

	fadeCamera(true, 2.5)		fadeCamera(true, 2.5)

	~~Wait~~(2000)		wait(2000)

	outputChatBox("You are now free to move.", 0, 255, 0)		outputChatBox("You are now free to move.", 0, 255, 0)
	end		end
			async(welcomeToServer)()

			--// Example 3

			async(function()
			local seconds = 3

			outputChatBox("Starting countdown: "..seconds.." seconds..", 255, 255, 0)

	async(~~welcomeToServer~~)()		wait(1000)

			for i = seconds, 1, -1 do
			outputChatBox(i, 255, 255, 0)
			wait(1000)
			end

			outputChatBox("Go!", 0, 255, 0)
			end)()

			--// Example 4

			async(function()
			while true do
			outputChatBox("Hello "..getPlayerName(localPlayer)..", If you need help, contact one of the staff!")
			wait(60000)
			end
			end)()
	</syntaxhighlight>		</syntaxhighlight>
	</section>		</section>

Template:Useful Functions

IManGaaX — Tue, 30 Jun 2026 04:50:58 GMT

Utility

← Older revision		Revision as of 04:50, 30 June 2026
Line 318:		Line 318:
	*[[dumpdelete]] <span style="color:gray; font-size:smaller;">» This function recursively deletes elements inside a table, destroying elements like vehicles, peds, or killing timers.</span>		*[[dumpdelete]] <span style="color:gray; font-size:smaller;">» This function recursively deletes elements inside a table, destroying elements like vehicles, peds, or killing timers.</span>
	*[[isEventHandlerAdded]] <span style="color:gray; font-size:smaller;">» This function checks whether a specific event handler has already been added to an element.</span>		*[[isEventHandlerAdded]] <span style="color:gray; font-size:smaller;">» This function checks whether a specific event handler has already been added to an element.</span>
	*[[~~Wait~~]] <span style="color:gray; font-size:smaller;">» This function pauses the execution of a function for a specific amount of time. It allows you to write sequential, readable code instead of using complex callback structures or multiple timers.</span>		*[[wait]] <span style="color:gray; font-size:smaller;">» This function pauses the execution of a function for a specific amount of time. It allows you to write sequential, readable code instead of using complex callback structures or multiple timers.</span>

	===String functions===		===String functions===

Wait

IManGaaX — Tue, 30 Jun 2026 04:50:16 GMT

Created page with "{{Useful Function}} __NOTOC__ <lowercasetitle></lowercasetitle> This function pauses the execution of a function for a specific amount of time. It allows you to write sequential, readable code instead of using complex callback structures or multiple timers. '''Note:''' This function must be used inside a function wrapped by the <code>async</code> helper. ==Syntax== <syntaxhighlight lang="lua">void Wait( int milliseconds )</syntaxhighlight> ===Required Arguments=== * '..."

New page

{{Useful Function}} __NOTOC__
<lowercasetitle></lowercasetitle>
This function pauses the execution of a function for a specific amount of time. It allows you to write sequential, readable code instead of using complex callback structures or multiple timers.

'''Note:''' This function must be used inside a function wrapped by the <code>async</code> helper.

==Syntax==
<syntaxhighlight lang="lua">void Wait( int milliseconds )</syntaxhighlight>

===Required Arguments===
* '''milliseconds''': The time in milliseconds to pause the execution.

==Code==
<section name="Shared" class="both" show="true">
<syntaxhighlight lang="lua">
function async(func)
return function(...)
local args = {...}
local co = coroutine.create(func)

local function resume(...)
local status, err = coroutine.resume(co, ...)

if not status and err then
outputDebugString("Async Error: "..tostring(err), 1)
outputDebugString("Stack trace: "..debug.traceback(co, err), 1)
end
end

resume(unpack(args))
end
end

function Wait(ms)
local co = coroutine.running()

if not co then
outputDebugString("Wait() must be called inside an async function!", 1)
end

setTimer(function()
coroutine.resume(co)
end, ms, 1)

coroutine.yield()
end
</syntaxhighlight>
</section>

'''Author:''' [[User:IManGaaX|Youssef Maged (iManGaaX)]]

==Example==
<section name="Client" class="client" show="true">
<syntaxhighlight lang="lua">
--// Example 1

addEventHandler("onClientResourceStart", resourceRoot, async(function()
outputChatBox("Script started!")

Wait(1000)

outputChatBox("1 second has passed.")

Wait(2000)

outputChatBox("3 seconds total.")
end))

--// Example 2

function welcomeToServer()
fadeCamera(false, 1.0)
outputChatBox("Loading data..", 0, 255, 0)

Wait(1500)

outputChatBox("Welcome iManGaaX!", 0, 255, 0)

Wait(3000)

fadeCamera(true, 2.5)

Wait(2000)

outputChatBox("You are now free to move.", 0, 255, 0)
end

async(welcomeToServer)()
</syntaxhighlight>
</section>

==See Also==

{{Useful_Functions}}

Template:Useful Functions

IManGaaX — Tue, 30 Jun 2026 04:41:45 GMT

Utility: (Add New Useful Function)

← Older revision		Revision as of 04:41, 30 June 2026
Line 318:		Line 318:
	*[[dumpdelete]] <span style="color:gray; font-size:smaller;">» This function recursively deletes elements inside a table, destroying elements like vehicles, peds, or killing timers.</span>		*[[dumpdelete]] <span style="color:gray; font-size:smaller;">» This function recursively deletes elements inside a table, destroying elements like vehicles, peds, or killing timers.</span>
	*[[isEventHandlerAdded]] <span style="color:gray; font-size:smaller;">» This function checks whether a specific event handler has already been added to an element.</span>		*[[isEventHandlerAdded]] <span style="color:gray; font-size:smaller;">» This function checks whether a specific event handler has already been added to an element.</span>
			*[[Wait]] <span style="color:gray; font-size:smaller;">» This function pauses the execution of a function for a specific amount of time. It allows you to write sequential, readable code instead of using complex callback structures or multiple timers.</span>

	===String functions===		===String functions===

User:XD0Rio

XD0Rio — Sun, 28 Jun 2026 17:02:39 GMT

User account XD0Rio was created

Resource:Px Gui

Yxvx — Sun, 28 Jun 2026 03:57:14 GMT

← Older revision		Revision as of 03:57, 28 June 2026
(One intermediate revision by the same user not shown)
Line 1:		Line 1:
	Pixel™ https://github.com/Pixel-TM/		<pageclass class="resource" subcaption="Resource"></pageclass>
			'''Pixel™ https://github.com/Pixel-TM/'''
			----------------------------------
			'''Soon'''
			[[Category:Resource]]

File:Pixel™.png

Yxvx — Sun, 28 Jun 2026 03:47:06 GMT

Yxvx uploaded File:Pixel™.png Pixel Team Logo // yx.vx, v_mk

New page

== Summary ==
Pixel Team Logo // yx.vx, v_mk

GUI Classes/Button:Create

Yxvx — Sun, 28 Jun 2026 03:36:26 GMT

← Older revision		Revision as of 03:36, 28 June 2026
(One intermediate revision by the same user not shown)

Px Gui

Yxvx — Sun, 28 Jun 2026 03:31:42 GMT

Redirected page to Resource:Px Gui

New page

#REDIRECT [[Resource:Px_Gui]]

Px

Yxvx — Sun, 28 Jun 2026 03:31:13 GMT

Redirected page to Resource:Px Gui

New page

#REDIRECT [[Resource:Px_Gui]]

Resource:Px Gui

Yxvx — Sun, 28 Jun 2026 02:01:52 GMT

Created page with "Pixel™ https://github.com/Pixel-TM/"

New page

Pixel™ https://github.com/Pixel-TM/

User:Yxvx

Yxvx — Sun, 28 Jun 2026 01:56:25 GMT

User account Yxvx was created

User:Diano

Diano — Thu, 25 Jun 2026 17:00:55 GMT

User account Diano was created

Call

Tails — Wed, 24 Jun 2026 17:25:01 GMT

@@ Line 77: / Line 77: @@
 ==Example==
 <section name="Server" class="server" show="true">
 This extract shows adding of a "kills" column to the scoreboard resource. This then sets the ''gameShowKills'' variable to true(or false), telling the rest of the script to start outputting kills.
@@ Line 124: / Line 94: @@
 end
 </syntaxhighlight>
-'''scoreboard Resource:'''
+'''Scoreboard resource:'''
 <syntaxhighlight lang="lua">
 function removeScoreboardColumn(columnName)
@@ Line 133: / Line 103: @@
      -- What ever scripted ...
 end
 </syntaxhighlight>
 </section>

Scripting Introduction temp

Tails — Tue, 23 Jun 2026 20:31:34 GMT

Created page with "==MTA Scripting: From Zero to Your First Script== Many beginners think scripting requires pages of complex code before anything happens. In Multi Theft Auto (MTA), a fully working script can be as short as a single line. This tutorial will show you the bare basics of how scripts work, how to navigate the MTA Wiki to find functions, and how to expand your script progressively into interactive commands and events. ===What is a "Resource"?=== In MTA, everything you run..."

New page

==MTA Scripting: From Zero to Your First Script==

Many beginners think scripting requires pages of complex code before anything happens. In Multi Theft Auto (MTA), a fully working script can be as short as a single line.

This tutorial will show you the bare basics of how scripts work, how to navigate the MTA Wiki to find functions, and how to expand your script progressively into interactive commands and events.

===What is a "Resource"?===
In MTA, everything you run on a server (gamemodes, maps, custom scripts) is called a '''resource'''.
A resource is simply a folder inside your server directory that contains:
# One configuration file named '''meta.xml''' (which tells the server what files to load).
# One or more script files written in the '''Lua''' programming language.

====Server-side vs. Client-side====
MTA splits scripts into two distinct environments:
* '''Server-side (Server):''' Scripts that run on the host server. They manage things that affect everyone, like the game world, weather, global variables, and player accounts.
* '''Client-side (Client):''' Scripts that run on the individual player's computer. They handle things the player sees directly on their screen, like custom user interfaces (GUIs) and visual effects.

In this tutorial, we will start with '''Server-side''' scripting, and then show you how to transition to the client.

---

==Step 1: The One-Line Script==
Let us create the absolute simplest working script possible: a script that sets the game world's weather.

Navigate to your server's resources directory:
server/mods/deathmatch/resources/

Create a new folder here and name it: `my_first_script`

====1. Create your meta.xml====
Inside your `my_first_script` folder, create a plain text file, name it `meta.xml`, and type or paste the following code:

<syntaxhighlight lang="xml">
<meta>
<info author="YourName" type="script" name="My First Script" description="Simple weather script" />
<script src="script.lua" type="server" />
</meta>
</syntaxhighlight>

''Reminder: The `<script />` tag tells the server engine to locate a file named `script.lua` and run it in the server environment (`type="server"`).''

====2. Write your script.lua====
In the same folder, create a text file named `script.lua`. Open it in your code editor and '''type''' this exact line of code yourself:

<syntaxhighlight lang="lua">
setWeather(8)
</syntaxhighlight>

Let us look at what you just wrote. You called a function named [[setWeather]] and passed it an argument of `8`. The number `8` is an identifier that tells the MTA engine to change the sky to a raining thunderstorm.

====3. Run the script====
# Start your server executable (`MTA Server.exe`).
# In the server console window, type: `start my_first_script` and press Enter.
# Connect to your server in-game. When you spawn, the weather will instantly become rainy.

---

==Understanding the MTA Wiki==
Now, you might be wondering: how did we know that [[setWeather]] exists, or that putting an `8` inside the parentheses makes it rain?

There is an easy solution for that: The MTA Wiki. You do not need to memorize code; you just need to know how to read the documentation.

If you search for [[setWeather]] on the wiki, you will see a syntax block that looks like this:

<syntaxhighlight lang="lua">
bool setWeather ( int weatherID )
</syntaxhighlight>

To be able to understand how functions work in MTA, we need to learn how to read this syntax on the wiki.

====How to read this syntax:====
* '''bool''' (Boolean): The first word tells you what the function ''returns'' after it finishes. A boolean means it gives back either `true` (success) or `false` (failure).
* '''setWeather''': The exact name of the function you must type.
* '''int weatherID''' (Integer): The information you must provide inside the parentheses. An `int` expects a whole number (like `0`, `1`, or `8`). The documentation page lists what each number means (e.g., `8` is a rainstorm).

Now let us look at another essential function, [[outputChatBox]]:

<syntaxhighlight lang="lua">
bool outputChatBox ( string text [, element visibleTo=root, int r=255, int g=255, int b=255, bool colorCoded=false ] )
</syntaxhighlight>

====How to read optional parameters:====
* '''string text''': The first argument must be a string (regular text wrapped in quotation marks, like `"Hello world"`).
* '''Square Brackets `[ , ... ]`''': Anything inside square brackets is '''optional'''. You do not have to type it.
* '''Default Values (`=`)''': If you skip an optional argument, the engine uses the default value shown. For example, `visibleTo=root` means if you don't specify a target player, the message defaults to `root` (meaning it sends to everyone). `r=255, g=255, b=255` defaults the text color to white.

---

==Step 2: Making Things Interactive (Events)==
Our one-line script runs immediately when the resource starts, but games are interactive. You usually want code to trigger only when a specific action happens in the world—like a player entering a vehicle or taking damage. We handle this using [[Event|Events]].

Let us replace our script with something more interesting: greeting players personally the moment they join the server.

Open your `script.lua`, delete the old code, and write this complete updated code:

<syntaxhighlight lang="lua">
-- Define a function containing the actions we want to happen
function welcomeNewPlayer()
-- 'source' is a built-in variable representing the player who just joined
outputChatBox("Welcome to the server!", source)
end

-- Connect our function to the built-in player join event
addEventHandler("onPlayerJoin", root, welcomeNewPlayer)
</syntaxhighlight>

====How this flows:====
# '''function welcomeNewPlayer()''': We group our code inside a named block called a function. This code sits silently and does nothing until it is called.
# '''[[addEventHandler]]''': We tell the server to listen for a specific trigger.
# '''[[onPlayerJoin]]''': The built-in MTA event that triggers whenever any player connects.
# '''root''': This tells the event listener where to listen. Using the predefined global variable `root` means "listen for anyone connecting to the entire server."
# '''welcomeNewPlayer''': The name of the function we want to fire when the event happens.
# '''[[source]]''': Inside an event function, `source` is a hidden variable created by MTA. You can refer to the wiki page for [[source]] to learn more. For `onPlayerJoin`, `source` always refers to the specific player element who just connected.

---

==Step 3: Giving Control to Players (Commands)==
Next, let us allow players to trigger code whenever they type a command in the chat box, such as `/rain`.

To make a command, we follow a flow very similar to events: we write a function, and then we link that function to a command word using [[addCommandHandler]].

Replace the code in your `script.lua` with this basic command setup:

<syntaxhighlight lang="lua">
-- 1. Write the function we want the command to trigger
function makeSkyRain()
setWeather(8)
outputChatBox("The sky is now dark and raining!")
end

-- 2. Hook the command word "/rain" to our function
addCommandHandler("rain", makeSkyRain)
</syntaxhighlight>

If you restart your resource and type `/rain` in the game chat, the weather will instantly start storming.

===Adding Arguments to Commands===
What if we want the player to choose the weather ID themselves? Like typing `/setweather 8`.

When a player uses a server-side command handler, MTA automatically passes three variables into your function:
# The '''player''' who typed the command.
# The '''name''' of the command itself.
# Whatever '''text''' the player typed after the space.

Let us update `script.lua` to accept a weather ID argument.

<syntaxhighlight lang="lua">
-- The function receives: the player element, the command name, and the extra text
function customWeatherCommand(thePlayer, commandName, weatherIDText)

-- Convert the typed text into a real number
local weatherNumber = tonumber(weatherIDText)

-- Validation check: If the player didn't type a number, stop right here
if not weatherNumber then
outputChatBox("Syntax: /setweather [ID number]", thePlayer)
return -- 'return' instantly stops the function from continuing
end

-- If the check passed, change the weather to the typed number
setWeather(weatherNumber)
end

addCommandHandler("setweather", customWeatherCommand)
</syntaxhighlight>

===Server-Side vs. Client-Side Commands===
Note that we have configured `script.lua` to be on the server side in our `meta.xml`. This means the command will run on the server side and change the weather for '''everyone''' on the server!

Depending on your server, you might not want players changing the weather for everybody. We could fix this in two ways:
# Make it so only administrators are able to use the command.
# OR, write the command on the '''client side''' instead.

Let us look at how to implement the second option. A client-side script will only change the weather for the player who typed the command, leaving everyone else's weather untouched.

====Modifying the Meta====
To add a client-side script, create a new text file inside your `my_first_script` folder and name it `client.lua`. Then, update your `meta.xml` to tell the server about this new client file:

<syntaxhighlight lang="xml">
<meta>
<info author="YourName" type="script" name="My First Script" description="Simple weather script" />
<script src="script.lua" type="server" />
<script src="client.lua" type="client" />
</meta>
</syntaxhighlight>

====Writing the Client-Side Command====
Open `client.lua` and add the following code:

<syntaxhighlight lang="lua">
function localWeatherCommand(commandName, weatherIDText)
local weatherNumber = tonumber(weatherIDText)

if not weatherNumber then
outputChatBox("Syntax: /myweather [ID number]")
return
end

setWeather(weatherNumber)
outputChatBox("You changed your local weather!")
end

addCommandHandler("myweather", localWeatherCommand)
</syntaxhighlight>

Notice a big difference? In client-side commands, we don't need `thePlayer` as the first function argument. This is because on the client side, the script is only running for one person, so the player element is always automatically the [[localPlayer]].

Now, typing `/setweather 8` (Server) changes the sky for everyone, but typing `/myweather 8` (Client) changes it only for you!

---

==Step 4: Your Best Friend (Debugging)==
As you write your own scripts, you will inevitably make mistakes. If you misspell a function name or forget a closing parenthesis, your script simply will not work.

However, debugging is not just for typos or syntax errors—it can show other errors too, like logic errors, passing the wrong type of data (e.g., passing text instead of a number), or trying to modify a vehicle or player element that has already disconnected or been destroyed.

Instead of guessing what went wrong, you should use MTA's built-in script monitor.

===Enabling Debugscript===
In the game client, open your console (usually by pressing the `F8` key or the `~` key) and type:
debugscript 3

A small transparent box will appear at the bottom of your screen. The `3` tells MTA to show all Errors, Warnings, and Information messages in real-time.

====Seeing it in action====
Let us intentionally make a typo to see how `/debugscript 3` helps us. Open your `script.lua` and change [[setWeather]] to a misspelled word:

<syntaxhighlight lang="lua">
function brokenCommand()
setWeatherrrr(8) -- Intentionally misspelled function
end
addCommandHandler("brokeweather", brokenCommand)
</syntaxhighlight>

Save the file, restart your resource, and type `/brokeweather` in-game.

Look at the bottom of your screen. You will see a red error message pop up:
ERROR: my_first_script/script.lua:2: attempt to call global 'setWeatherrrr' (a nil value)

This debug line tells you exactly where the problem is: inside the `my_first_script` folder, in `script.lua`, on '''line 2'''. It even tells you that `setWeatherrrr` is a "nil value" (meaning the engine doesn't recognize the word).

Keeping `/debugscript 3` open while you code is the single most important habit you can build as an MTA developer.

User:Fe4tww

Fe4tww — Tue, 23 Jun 2026 19:29:24 GMT

User account Fe4tww was created

User:Peerless

Peerless — Thu, 18 Jun 2026 13:28:52 GMT

User account Peerless was created

User:Sameeroo

Sameeroo — Wed, 17 Jun 2026 10:40:11 GMT

User account Sameeroo was created

User:Jjjd

Jjjd — Sun, 14 Jun 2026 15:04:52 GMT

User account Jjjd was created

User:Cldo

Cldo — Sat, 13 Jun 2026 20:37:46 GMT

User account Cldo was created

User:Andrade777

Andrade777 — Fri, 12 Jun 2026 01:05:54 GMT

User account Andrade777 was created

User:Kzx80

Kzx80 — Thu, 11 Jun 2026 21:51:01 GMT

User account Kzx80 was created

GuiCreateButton

Tails — Wed, 10 Jun 2026 16:03:38 GMT

Example

← Older revision		Revision as of 16:03, 10 June 2026
Line 42:		Line 42:

	addEventHandler("onClientGUIClick", myButton, function()		addEventHandler("onClientGUIClick", myButton, function()
	local myText = guiGetText(myInput~~, ""~~) -- Grab the input value		local myText = guiGetText(myInput) -- Grab the input value
	if myText ~= "" then -- Make sure the input not empty		if myText ~= "" then -- Make sure the input not empty
	outputChatBox(myText)		outputChatBox(myText)

GuiCreateGridList

Tails — Wed, 10 Jun 2026 15:55:51 GMT

fix oop closing tag

← Older revision		Revision as of 15:55, 10 June 2026
Line 35:		Line 35:
	</syntaxhighlight>		</syntaxhighlight>

	'''Example 2:''' Using [[OOP]] we can write shorter and cleaner code (Requires <oop>true<oop> in the meta file). This creates a player list with 2 columns.		'''Example 2:''' Using [[OOP]] we can write shorter and cleaner code (Requires <oop>true</oop> in the meta file). This creates a player list with 2 columns.
	<syntaxhighlight lang="lua">		<syntaxhighlight lang="lua">
	local list = GuiGridList(0.80, 0.40, 0.15, 0.35, true)		local list = GuiGridList(0.80, 0.40, 0.15, 0.35, true)

FromJSON

Tails — Wed, 10 Jun 2026 15:50:47 GMT

minor fixes

← Older revision		Revision as of 15:50, 10 June 2026
Line 21:		Line 21:

	===Returns===		===Returns===
	Returns the ~~parse~~ JSON data as multiple values or a single table depending on the input JSON structure:		Returns the parsed JSON data as multiple values or a single table depending on the input JSON structure:
	* Returns '''multiple separate values''' (unpacked) if the root element of the JSON is an array		* Returns '''multiple separate values''' (unpacked) if the root element of the JSON is an '''array'''
	* Returns a ~~single~~ table if the root element of the JSON is an object		* Returns a '''table''' if the root element of the JSON is an '''object'''
	* Returns [[nil]] if the JSON string is invalid or malformed.		* Returns [[nil]] if the JSON string is invalid or malformed.

Line 41:		Line 41:
	This example shows how to capture all values of a JSON array in a single Lua table.		This example shows how to capture all values of a JSON array in a single Lua table.
	<syntaxhighlight lang="lua">		<syntaxhighlight lang="lua">
	local jsonArray = '["Apple", "Orange"]'		local jsonArray = '["Apple", "Orange", "Banana"]'

	-- Put the fromJSON call inside of a table directly to capture all the values of the JSON array		-- Put the fromJSON call inside of a table directly to capture all the values of the JSON array
	local fruits = {fromJSON(jsonArray)}		local fruits = {fromJSON(jsonArray)}

	~~print(~~fruits[1], fruits[2]) --> Output: Apple Orange		if fruits[1] then -- Make sure the JSON was parsed correctly
			for i=1, #fruits do
			print(fruits[i])
			end
			--[[ Output:
			Apple
			Orange
			Banana
			]]
			end

	</syntaxhighlight>		</syntaxhighlight>