Multi Theft Auto: Wiki - User contributions [en]

User talk:AnubhavTheWiki

2014-02-04T14:25:10Z

Shmorf: Please move to the Tutorials sub-category on the forums.

I suggest you to move your 'tutorial' to a special sub-category called 'Tutorials' in the Scripting category on the forums before this shit gets deleted from the Wiki. ( https://forum.mtasa.com/viewforum.php?f=148 )

Element

2013-11-25T16:21:05Z

Shmorf: Another undo

An '''element''' is a generic class that can represent almost all in-game [[entity|entities]]. The built-in element types are:

{{Elements}}

Any other element type can be created as an abstract element, not referring to any game [[entity]]. For example, '''resource''' and '''map''' elements are created when resources and maps are loaded to group entities they create as their children.

Elements share common functions such as type and list retrieval, a destroy operation to remove both the element and the game entity it is linked to (except for some elements which can't be destroyed, for example client elements), [[element data]] storing and retrieval, and many more common operations.

All elements are stored internally in a [[Element tree|tree structure]], and as such every element except the '''root''' element has a parent element, that can be the '''root''' element, a '''resource''', '''map''' or another element. This is purely for declaring the scope of function calls.

==Related scripting functions==
===Client===
{{Client element functions}}
===Server===
{{Element functions}}
[[Category:Scripting Concepts]]

[[it:Elemento]]
[[ru:Element]]
[[es:Elemento]]

Element tree

2013-11-25T16:20:23Z

Shmorf: Undo´d a useless edit

[[File:Tre.png|frame|Element tree]]
MTA uses a so-called ''element tree'' to store all the elements that exist on the server and the client. This is directly related to the set of running [[resources]] and their map files' XML layout, although it can be changed at run-time by scripts.

If you are familiar with the concept of ''trees'' in computer-science, this should be easy to understand. If you are not, think of it like a family tree - except everyone only has a single parent. Every [[element]] has a ''parent'' element.

All elements that are created within scripts or from .map files are child elements of the resource they belong to. Thus, most elements (except for [[client]]s) exist only within resources and are also destroyed as soon as their resource is stopped.

==Tree elements==
* '''root''': This is at the very base of the tree - all elements are children (or descendants) of this element.
* '''resource''': These are direct children of the root element - with one for each ''running'' resource. This element is called the ''resource root''. Its ID holds the name of the resource.
* '''map''': Each resource element contains at least one map element, representing either a ".map" file in the resource or the one containing the elements created by scripts (this is called the ''dynamic'' map). Their IDs contain the maps' filenames, or ''dynamic'' for the dynamic map.
** Map files can contain a number of other [[element]]s as well as an unlimited number of custom elements.

==Example==
This in an example of a serverside tree dumped to XML from a running server.
''Please note that it is shortened on some places for the sake of overview.''
<syntaxhighlight lang="xml">
<root>
<console/>
<player dontRespawn="false"/>
<player dontRespawn="false" lastSpawnarea=""/>
<resource id="resourcebrowser"/>
<resource id="ajax"/>
<resource id="resourcemanager"/>
<resource id="spawnmanager"/>
<resource id="mapmanager"/>
<resource id="runcode"/>
<resource id="fr">
<map id="dynamic">
<vehicle/>
</map>
</resource>
<resource id="elementbrowser"/>
<resource id="assault">
<map id="dynamic">
<team/>
<team/>
<blip/>
<marker/>
<colshape/>
<blip/>
<blip/>
</map>
</resource>
<resource id="as-farm">
<map id="dynamic"/>
<map id="as-farm.map">
<spawngroup req="" type="attacker">
<spawnarea posY="-8.3976354598999" posX="20.182683944702" skins="9" ... />
</spawngroup>
<spawngroup req="" type="attacker">
<spawnarea posY="32.166355133057" posX="-46.90763092041" skins="9" ... />
</spawngroup>
<spawngroup req="" type="attacker">
<spawnarea posY="35.214984893799" posX="-33.486911773682" skins="9" ... />
</spawngroup>
<spawngroup req="" type="attacker">
<spawnarea posY="35.214984893799" posX="-33.486911773682" skins="9" ... />
</spawngroup>
<objective id="first" type="checkpoint" description="Breach into the farm" ... />
<pickup type="weapon" ... />
</map>
</resource>
</root>
</syntaxhighlight>
===Explanation===
This tree consists of a number of resource root elements, the [[Element/Console|server console]] and two [[player]] elements, that are direct children of the '''root''' element. All these resources have a ''dynamic map'' as child element (it is just not shown for most of them). These contain the elements that are created dynamically by this resource using scripts, for example a [[vehicle]]. If the resource has a map file, it is also a child element, itself containing all the elements in the .map file.

Let's have a closer look at the '''assault''' resource: This contains just one ''dynamic'' map that has 2 teams, 3 blips, 1 marker and 1 colshape as child elements. These are the elements that are created by the script, for example the marker, the colshape and one of the blips are probably used for the objective.

The '''as-farm''' resource's function on the contrary is to be a map for the '''assault''' gamemode. The dynamic map is empty (it could contain elements if there was a script in it though), while there is a map called 'as-farm.map', that contains a number of elements. These are mostly custom elements (like spawngroup, spawnarea, objective) but also a few elements that MTA creates automactically after loading the map (like pickup). In the brackets after the element type, you can see the element data it contains. These are identical with the attributes the .map file contains within these elements, while you can also set and get element data for any other elements (e.g. players) with [[setElementData]] and [[getElementData]].

==Pratical application==
Elements can have as many children as they like. This does not directly affect the map in any way, but it comes in to its own when combined with the scripting system.

===Setting data for elements===
If you call a set... function on a node of the element tree, the function will affect every element within it (that it can work on).

So, the following code would set the size of every marker (the only type of element the setMarkerSize function can work on) that is below the root element to ''2.5''.
<syntaxhighlight lang="lua">
setMarkerSize ( getRootElement(), 2.5 )
</syntaxhighlight>

The same can be done on any element, it is not restricted to the root element.

===Map manager===
The [[#Example|example above]] shows the way the [[map manager]] uses different resources. The 'assault' resource is the gamemode, that manages what happens on the server using scripts and thus by creating elements in the tree dynamically. When a map resource is started, the gamemode receives a [[resource|resource pointer]] referring to the started resource - in this case ''as-farm'' - from which you can retrieve and store the resource root element. Using this element in conjunction with functions like [[getElementsByType]], [[getElementData]] and various others, you can access any of the information that was loaded into the tree from the 'as-farm.map'-file through scripts in the gamemode resource.

Another thing that has to be considered related to the tree of elements is the fact that when you change the map, you don't have to remove any elements you created within the map resource, while you '''do''' have to remove elements that are created within the gamemode resource, '''if''' they are specific to the map (which will be probably the case for those items you create based on information read from the map resource's .map files).

==Element browser==
You can start the resource ''elementbrowser'' to see a live view of the element tree on your server. Just start the resource and browser to your server's web page and choose the ''Element browser'' option in the sidebar (firefox only currently).
[[Category:Scripting Concepts]]
[[es:Árbol de elementos]]
[[ru:Element tree]]

BlowVehicle

2013-10-21T16:10:15Z

Shmorf: Added client class example.

__NOTOC__
{{Server client function}}
This function will blow up a vehicle. This will cause an explosion and will kill the driver and any passengers inside it.

==Syntax==
<section name="Server" class="server" show="true">
<syntaxhighlight lang="lua">
bool blowVehicle ( vehicle vehicleToBlow, [ bool explode=true ] )
</syntaxhighlight>

===Required Arguments===
*'''vehicleToBlow:''' The vehicle that you wish to blow up.
===Optional Arguments===
{{OptionalArg}}
*'''explode:''' If this argument is ''true'' then the vehicle will explode, otherwise it will just be blown up silently.
</section>
<section name="Client" class="client" show="true">
<syntaxhighlight lang="lua">
bool blowVehicle ( vehicle vehicleToBlow )
</syntaxhighlight>

===Required Arguments===
*'''vehicleToBlow:''' The vehicle that you wish to blow up.
</section>
===Returns===
Returns ''true'' if the vehicle was blown up, ''false'' if invalid arguments were passed to the function.

==Example==
<section name="Example 1: Server and client" class="both" show="true">
This example will blow up every vehicle in the game.
<syntaxhighlight lang="lua">
vehicles = getElementsByType ( "vehicle" )
for vehicleKey, vehicleValue in ipairs(vehicles) do
blowVehicle ( vehicleValue )
end
</syntaxhighlight>

It is worth noting that the same could be achieved with the following:
<syntaxhighlight lang="lua">
blowVehicle ( root ) -- root (getRootElement) is a built in MTA variable and therefore we do not have to define it.
</syntaxhighlight>
</section>

<section name="Example 2: Server" class="server" show="true">
This example will blow a player's vehicle when he enters the car, like a carbomb.
<syntaxhighlight lang="lua">
riggedVehicle = createVehicle(445, 0, 0, 5)
function blowVehicleEnter ( thePlayer, seat, jacked )
--ENGINE START BOMB.
if seat == 0 then --check if the seat the player got into was id 0 - i.e. driver seat
blowVehicle ( source ) --if it was, toast him
end
end
addEventHandler ( "onVehicleEnter", riggedVehicle, blowVehicleEnter ) --trigger the function when a certain vehicle is entered
</syntaxhighlight>
</section>

==Client Class Example==
'''Heads up!''' Client classes only work on '''MTA 1.4''', therefore we highly recommend you to visit [[Client_Scripting_Classes|Client Scripting Classes]] first.
<section name="Example 1: Client" class="client" show="true">
This script will create an Infernus at the center (0, 0, 3) of San Andreas upon execution.
<syntaxhighlight lang="lua">
addEventHandler( "onClientResourceStart", resourceRoot,
function()
infernus = Vehicle.create( 411, Vector3( 0, 0, 3 ) ); -- Create an Infernus and spawn it at the middle of SA.
infernus:setColor( 0, 0, 0 ); -- Set its color to black.
end)

addCommandHandler( "blowinfernus",
function()
if not infernus.blown then -- Check if the Infernus is blown up or not.
infernus:blow();
else -- Ouch, it's blown up, let's output an error to the client.
outputChatBox( "The Infernus has already been blown up by you.", 255, 0, 0, false );
end
end)
</syntaxhighlight>
</section>

==See Also==
{{Vehicle_functions}}

Client Scripting Classes

2013-10-21T16:05:24Z

Shmorf: /* Vehicle */

<pageclass class="client"></pageclass>
{{Adding_Pages_to_Categories_and_Templates}}
This page lists all the '''client-side''' scripting classes that are being implemented in the 1.4 version of Multi Theft Auto. It mirrors the procedural [[Client_Scripting_Functions|Client Functions]].

Classes can be instantiated by either calling the '''create''' method, when available, or calling the class. For example: ''Vehicle(...)'' is the same as ''Vehicle.create(...)''.

__TOC__

==Vector3==
{{Client_vector3_class}}

==Matrix==
{{Client_matrix_class}}

==Element==
{{Client_element_class}}

===Entity===
====Ped====
<section name="Ped class" class="server" show="true">
{{Client_ped_class}}
</section>

=====Player=====
<section name="Player class" class="server" show="true">
{{Client_player_class}}
</section>

====Vehicle====
<section name="Vehicle class" class="server" show="true">
{{Client_vehicle_class}}
</section>

====Object====
<section name="Object class" class="server" show="true">
{{Client_object_class}}
</section>

====Marker====
<section name="Marker class" class="server" show="true">
{{Client_marker_class}}
</section>

====Blip====
<section name="Object class" class="server" show="true">
{{Client_object_class}}
</section>

====Pickup====
<section name="Pickup class" class="server" show="true">
{{Client_pickup_class}}
</section>

====Collision shape====
<section name="ColShape class" class="server" show="true">
{{Client_colshape_class}}
</section>

====Projectile====
<section name="Projectile class" class="server" show="true">
{{Client_projectile_class}}
</section>

====Radar area====
<section name="RadarArea class" class="server" show="true">
{{Client_radararea_class}}
</section>

====Team====
<section name="Team class" class="server" show="true">
{{Client_team_class}}
</section>

====Water====
<section name="Water class" class="server" show="true">
{{Client_water_class}}
</section>

====Sound====
<section name="Sound class" class="server" show="true">
{{Client_sound_class}}
</section>

====Sound3D====
<section name="Sound3D class" class="server" show="true">
{{Client_sound3_class}}
</section>

====Weapon====
<section name="Weapon class" class="server" show="true">
{{Client_weapon_class}}
</section>

===Miscellaneous===
====GUI Base====
<section name="GuiElement class" class="server" show="true">
{{Client_GUIElement_class}}
</section>

=====Window=====
<section name="GuiWindow class" class="server" show="true">
{{Client_GUIWindow_class}}
</section>

=====Button=====
<section name="GuiButton class" class="server" show="true">
{{Client_GUIButton_class}}
</section>

=====Edit box=====
<section name="GuiEdit class" class="server" show="true">
{{Client_GUIEdit_class}}
</section>

=====Label=====
<section name="GuiLabel class" class="server" show="true">
{{Client_GUILabel_class}}
</section>

=====Memo box=====
<section name="GuiMemo class" class="server" show="true">
{{Client_GUIMemo_class}}
</section>

=====Image=====
<section name="GuiImage class" class="server" show="true">
{{Client_GUIImage_class}}
</section>

=====Combo box=====
<section name="GuiComboBox class" class="server" show="true">
{{Client_GUIComboBox_class}}
</section>

=====Check box=====
<section name="GuiCheckBox class" class="server" show="true">
{{Client_GUICheckBox_class}}
</section>

=====Radio button=====
<section name="GuiRadioButton class" class="server" show="true">
{{Client_object_class}}
</section>

=====Scroll pane=====
<section name="GuiScrollPane class" class="server" show="true">
{{Client_GUIScrollPane_class}}
</section>

=====Scroll bar=====
<section name="GuiScrollBar class" class="server" show="true">
{{Client_GUIScrollBar_class}}
</section>

=====Progress bar=====
<section name="GuiProgressBar class" class="server" show="true">
{{Client_GUIProgressBar_class}}
</section>

=====Grid list=====
<section name="GuiGridList class" class="server" show="true">
{{Client_GUIGridList_class}}
</section>

=====Tab panel=====
<section name="GuiTabPanel class" class="server" show="true">
{{Client_GUITabPanel_class}}
</section>

=====Tab=====
<section name="GuiTab class" class="server" show="true">
{{Client_GUITab_class}}
</section>

==Resource==
{{Client_resource_class}}

==Timer==
{{Client_timer_class}}

==File==
{{Client_file_class}}

==XmlNode==
{{Client_xmlNode_class}}

Client Scripting Classes

2013-10-21T16:04:38Z

Shmorf: /* Vehicle */

<pageclass class="client"></pageclass>
{{Adding_Pages_to_Categories_and_Templates}}
This page lists all the '''client-side''' scripting classes that are being implemented in the 1.4 version of Multi Theft Auto. It mirrors the procedural [[Client_Scripting_Functions|Client Functions]].

Classes can be instantiated by either calling the '''create''' method, when available, or calling the class. For example: ''Vehicle(...)'' is the same as ''Vehicle.create(...)''.

__TOC__

==Vector3==
{{Client_vector3_class}}

==Matrix==
{{Client_matrix_class}}

==Element==
{{Client_element_class}}

===Entity===
====Ped====
<section name="Ped class" class="server" show="true">
{{Client_ped_class}}
</section>

=====Player=====
<section name="Player class" class="server" show="true">
{{Client_player_class}}
</section>

====Vehicle====
<section name="Vehicle class" class="server" show="true">
{{Client_vehicle_class#Client_Class_Example}}
</section>

====Object====
<section name="Object class" class="server" show="true">
{{Client_object_class}}
</section>

====Marker====
<section name="Marker class" class="server" show="true">
{{Client_marker_class}}
</section>

====Blip====
<section name="Object class" class="server" show="true">
{{Client_object_class}}
</section>

====Pickup====
<section name="Pickup class" class="server" show="true">
{{Client_pickup_class}}
</section>

====Collision shape====
<section name="ColShape class" class="server" show="true">
{{Client_colshape_class}}
</section>

====Projectile====
<section name="Projectile class" class="server" show="true">
{{Client_projectile_class}}
</section>

====Radar area====
<section name="RadarArea class" class="server" show="true">
{{Client_radararea_class}}
</section>

====Team====
<section name="Team class" class="server" show="true">
{{Client_team_class}}
</section>

====Water====
<section name="Water class" class="server" show="true">
{{Client_water_class}}
</section>

====Sound====
<section name="Sound class" class="server" show="true">
{{Client_sound_class}}
</section>

====Sound3D====
<section name="Sound3D class" class="server" show="true">
{{Client_sound3_class}}
</section>

====Weapon====
<section name="Weapon class" class="server" show="true">
{{Client_weapon_class}}
</section>

===Miscellaneous===
====GUI Base====
<section name="GuiElement class" class="server" show="true">
{{Client_GUIElement_class}}
</section>

=====Window=====
<section name="GuiWindow class" class="server" show="true">
{{Client_GUIWindow_class}}
</section>

=====Button=====
<section name="GuiButton class" class="server" show="true">
{{Client_GUIButton_class}}
</section>

=====Edit box=====
<section name="GuiEdit class" class="server" show="true">
{{Client_GUIEdit_class}}
</section>

=====Label=====
<section name="GuiLabel class" class="server" show="true">
{{Client_GUILabel_class}}
</section>

=====Memo box=====
<section name="GuiMemo class" class="server" show="true">
{{Client_GUIMemo_class}}
</section>

=====Image=====
<section name="GuiImage class" class="server" show="true">
{{Client_GUIImage_class}}
</section>

=====Combo box=====
<section name="GuiComboBox class" class="server" show="true">
{{Client_GUIComboBox_class}}
</section>

=====Check box=====
<section name="GuiCheckBox class" class="server" show="true">
{{Client_GUICheckBox_class}}
</section>

=====Radio button=====
<section name="GuiRadioButton class" class="server" show="true">
{{Client_object_class}}
</section>

=====Scroll pane=====
<section name="GuiScrollPane class" class="server" show="true">
{{Client_GUIScrollPane_class}}
</section>

=====Scroll bar=====
<section name="GuiScrollBar class" class="server" show="true">
{{Client_GUIScrollBar_class}}
</section>

=====Progress bar=====
<section name="GuiProgressBar class" class="server" show="true">
{{Client_GUIProgressBar_class}}
</section>

=====Grid list=====
<section name="GuiGridList class" class="server" show="true">
{{Client_GUIGridList_class}}
</section>

=====Tab panel=====
<section name="GuiTabPanel class" class="server" show="true">
{{Client_GUITabPanel_class}}
</section>

=====Tab=====
<section name="GuiTab class" class="server" show="true">
{{Client_GUITab_class}}
</section>

==Resource==
{{Client_resource_class}}

==Timer==
{{Client_timer_class}}

==File==
{{Client_file_class}}

==XmlNode==
{{Client_xmlNode_class}}

CreateVehicle

2013-10-21T15:55:37Z

Shmorf: Added client class example.

{{Needs_Checking|
* Numberplates only seem to work for some vehicles, and then only for the front or rear plate only
* Explain the direction parameter which should always be false and what is the point of having a parameter whose value need to be the same all the time. --[[User:MTA SE|MTA SE]] 20:05, 5 July 2012 (UTC)
* The numberplates have to contain at least 1 letter. For example "132" will not work and the function will fail but, "13A" or "132A" will work
}}
__NOTOC__
{{Server client function}}
{{note_box|Vehicles (and other elements) created client-side are only seen by the client that created them, aren't synced and players cannot enter them. They are essentially for display only.}}
This function creates a vehicle at the specified location.

Its worth noting that the position of the vehicle is the center point of the vehicle, not its base. As such, you need to ensure that the z value (vertical axis) is some height above the ground. You can find the exact height using the client side function [[getElementDistanceFromCentreOfMassToBaseOfModel]], or you can estimate it yourself and just spawn the vehicle so it drops to the ground.

==Syntax==
<syntaxhighlight lang="lua">
vehicle createVehicle ( int model, float x, float y, float z [, float rx, float ry, float rz, string numberplate, bool bDirection, int variant1, int variant2 ] )
</syntaxhighlight>

===Required Arguments===
* '''model''': The [[Vehicle IDs|vehicle ID]] of the vehicle being created.
* '''x''': A floating point number representing the X coordinate on the map.
* '''y''': A floating point number representing the Y coordinate on the map.
* '''z''': A floating point number representing the Z coordinate on the map.

===Optional Arguments===
{{OptionalArg}}
* '''rx''': A floating point number representing the rotation about the X axis in degrees.
* '''ry''': A floating point number representing the rotation about the Y axis in degrees.
* '''rz''': A floating point number representing the rotation about the Z axis in degrees.
* '''numberplate''': A string that will go on the number plate of the car (max 8 characters). This is only applicable to cars.
* '''direction''': A boolean which should be set to false. *SERVER ONLY*
{{New feature/item|3.0120|1.2||
* '''variant1''': An integer for the first vehicle variant see [[Vehicle variants]]
* '''variant2''': An integer for the second vehicle variant see [[Vehicle variants]]
}}

===Returns===
Returns the [[vehicle]] element that was created. Returns ''false'' if the arguments are incorrect, or if the vehicle limit of 65535 is exceeded.

==Using trains==
Trains are created using the createVehicle function. They are placed at the nearest point of the GTASA train pathing (railroad tracks) from their spawning point.

==Example==
<section name="Example 1: Server" class="server" show="true">
This script spawns a Rhino on top of one lucky individual.
<syntaxhighlight lang="lua">
function scriptCreateTank ( player, command )
local luckyBugger = getRandomPlayer() -- get a random player
local x, y, z = getElementPosition ( luckyBugger ) -- retrive the player's position
createVehicle ( 432, x, y, z + 10 ) -- create the tank 10 units above them
outputChatBox ( "You got Tank'd!", luckyBugger )
end
--Attach the 'scriptCreateTank' function to the "tank" command
addCommandHandler ( "tank", scriptCreateTank )
</syntaxhighlight>
</section>

<section name="Example 2: Client" class="client" show="true">
This script spawns a Rhino on top of the local player.
<syntaxhighlight lang="lua">
function scriptCreateTank ( commandName )
local luckyBugger = getLocalPlayer() -- get the local player
local x, y, z = getElementPosition ( luckyBugger ) -- retrive the player's position
createVehicle ( 432, x, y, z + 10 ) -- create the tank 10 units above them
outputChatBox ( "You got Tank'd!", 255, 0, 0)
end
--Attach the 'scriptCreateTank' function to the "tank" command
addCommandHandler ( "tank", scriptCreateTank )
</syntaxhighlight>
</section>

<section name="Example 3: Server" class="server" show="false">
This example creates a vehicle five units to the right of a player when they type ''createvehicle'' and its name in the console:
<syntaxhighlight lang="lua">
local distance = 5 --units

-- define our handler (we'll take a variable number of parameters where the name goes, because there are vehicle names with more than one word)
function consoleCreateVehicle ( sourcePlayer, commandName, ... )
-- if a player triggered it, not the admin,
if ( sourcePlayer ) then
-- calculate the position of the vehicle based on the player's position and rotation:
local x, y, z = getElementPosition ( sourcePlayer ) -- get the player's position
local rotZ = getPedRotation ( sourcePlayer ) -- get the player's rotation around the Z axis in degrees
x = x + ( ( math.cos ( math.rad ( rotZ ) ) ) * distance ) -- calculate the X position of the vehicle
y = y + ( ( math.sin ( math.rad ( rotZ ) ) ) * distance ) -- calculate the Y position of the vehicle

-- get the complete vehicle name by joining all passed parameters using Lua function table.concat
local vehicleName = table.concat({...}, " ")
-- get the vehicle's model ID from the name
local vehicleID = getVehicleModelFromName ( vehicleName )
-- if vehicle ID is valid,
if vehicleID then
-- create the vehicle using the information gathered above:
local newVehicle = createVehicle ( vehicleID, x, y, z, 0, 0, rotZ )
-- if vehicle creation failed, give the player a message
if not newVehicle then
outputConsole ( "Failed to create vehicle.", sourcePlayer )
end
end
end
end

-- Attach the 'consoleCreateVehicle' function to the "createvehicle" command
addCommandHandler ( "createvehicle", consoleCreateVehicle )
</syntaxhighlight>
</section>

==Client Class Example==
'''Heads up!''' Client classes only work on '''MTA 1.4''', therefore we highly recommend you to visit [[Client_Scripting_Classes|Client Scripting Classes]] first.
<section name="Example 1: Client" class="client" show="true">
This script will create an Infernus at the center (0, 0, 3) of San Andreas upon execution.
<syntaxhighlight lang="lua">
addEventHandler( "onClientResourceStart", resourceRoot,
function()
infernus = Vehicle.create( 411, Vector3( 0, 0, 3 ) ); -- Create an Infernus and spawn it at the middle of SA.
infernus:setColor( 0, 0, 0 ); -- Set its color to black.
end)

addCommandHandler( "blowinfernus",
function()
if not infernus.blown then -- Check if the Infernus is blown up or not.
infernus:blow();
else -- Ouch, it's blown up, let's output an error to the client.
outputChatBox( "The Infernus has already been blown up by you.", 255, 0, 0, false );
end
end)
</syntaxhighlight>
</section>

==See Also==

{{Vehicle functions}}

BlowVehicle

2013-10-21T01:03:16Z

Shmorf: root is a built in MTA var.

Talk:Client Scripting Classes

2013-10-21T00:57:58Z

Shmorf:

@Ixjf: Whatsup with XmlNode man, I cant stand the lowercase letters of the word Xml. u undo'd it again doee. -- Shmorf (( Somewhere around 03:00AM ))

GetVehiclePlateText

2013-10-20T20:00:08Z

Shmorf: Shortened example var. 'localPlayerOccupiedVehicle' -> 'vehicle'

__NOTOC__
{{Server client function}}
This function is used to retrieve the text on the number plate of a specified vehicle.

==Syntax==
<syntaxhighlight lang="lua">
string getVehiclePlateText ( vehicle theVehicle )
</syntaxhighlight>

===Required Arguments===
*'''theVehicle:''' The [[vehicle]] that you wish to retrieve the plate text from.

===Returns===
Returns a ''string'' that corresponds to the plate on the text, ''false'' if a bad argument was passed or if the vehicle is not a car.

==Example==
<section name="Example" class="client" show="true">
This example outputs the text on the license plate of the vehicle the player is driving to the chatbox.
<syntaxhighlight lang="lua">
function outputLicensePlate ( command )
if isPedInVehicle(localPlayer) then --let's check if they're in a vehicle
-- if they are in a vehicle
local vehicle = getPedOccupiedVehicle ( localPlayer ) --let's get the vehicle
local plateText = getVehiclePlateText ( vehicle ) --get the license plate text
if plateText then -- if there was a license plate,
outputChatBox ( "Your license plate is: " .. plateText )-- output it to the chatbox
else
outputChatBox ( "Your vehicle has no license plate." )
end
else
outputChatBox ( "You're not in a vehicle." )
end
end
-- add our function as a handler to the "plate" command
addCommandHandler( "plate", outputLicensePlate )
</syntaxhighlight>
</section>

==See Also==
{{Vehicle functions}}

Client Scripting Classes

2013-10-20T19:55:17Z

Shmorf: Ninja edit Xml -> XML don't you dare to undo again ixjf

Client Scripting Classes

2013-10-20T18:01:24Z

Shmorf:

Talk:Client Scripting Classes

2013-10-20T14:49:24Z

Shmorf: Blanked the page

Talk:Client Scripting Classes

2013-10-20T14:25:01Z

Shmorf: It's Qais, not Qaisjp.

Won't we be repeating ourselves if we have to copy things from procedural to oop? --[[User:Qais|Qais]] 04:11PM, 20 October 2013 (UTC)

Noh --[[User:Shmorf|Shmorf]] 04:23PM, 20 October 2013 (UTC)

Talk:Client Scripting Classes

2013-10-20T14:24:36Z

Shmorf: Added Qaisjp tags

Won't we be repeating ourselves if we have to copy things from procedural to oop? --[[User:Qaisjp|Qaisjp]] 04:11PM, 20 October 2013 (UTC)

Noh --[[User:Shmorf|Shmorf]] 04:23PM, 20 October 2013 (UTC)

Talk:Client Scripting Classes

2013-10-20T14:23:47Z

Shmorf:

Won't we be repeating ourselves if we have to copy things from procedural to oop?

Noh --[[User:Shmorf|Shmorf]] 04:23PM, 20 October 2013 (UTC)

User talk:FaLsE Country

2013-10-20T13:07:35Z

Shmorf: Created page with "You made a mess in your previous edit, thankgod I undo'd it. --Shmorf 03:06PM, 20 October 2013 (UTC)"

You made a mess in your previous edit, thankgod I undo'd it. --[[User:Shmorf|Shmorf]] 03:06PM, 20 October 2013 (UTC)

SetPedCameraRotation

2013-10-20T13:02:41Z

Shmorf: Undo revision 37338 by FaLsE Country (talk)

{{Client function}}
__NOTOC__
This function sets the camera rotation of a ped.

==Syntax==
<syntaxhighlight lang="lua">
bool setPedCameraRotation ( ped thePed, float cameraRotation )
</syntaxhighlight>

===Required Arguments===
*'''thePed:''' The [[ped]] whose camera rotation is to be changed
*'''cameraRotation:''' The new direction that the ped will walk if you set their forwards control state

===Returns===
Returns ''true'' if the camera rotation was changed, ''false'' otherwise.

==Example==
<syntaxhighlight lang="lua">--TODO</syntaxhighlight>

==See Also==
{{Client ped functions}}

User talk:Mickael1000

2013-10-09T15:43:03Z

Shmorf: Undo'd your last change.

=Translating pages=
I undo'd your last change because you translated the English version of it.--[[User:Shmorf|Shmorf]] 17:40, 9 October 2013 (GMT)

How you can help

2013-10-09T15:37:18Z

Shmorf: Undo revision 37295 by Mickael1000 (talk)

__NOTOC__
Multi Theft Auto has loads of areas in which you can help us. In turn, we'll be more than happy to help you get started with any ideas you have, help test them and - if they're good enough - release them to the whole community. This page outlines the key areas you could do something in, of course, there's many things we've not thought of, so think outside the box!

==Coding for MTASA==
* Submit source patches for the mod, containing requested features or bugfixes. ([[Coding guidelines]])
* Translate MTA:SA to your native language - http://translate.multitheftauto.com/

==Scripting==
* Create a gamemode
**[[Scripting Introduction]]
**[http://www.lua.org/pil/index.html "Programming in Lua" Manual]
* Create an administration page on the HTTP server.
**[[Resource Web Access]]
* Make a general purpose resource that provides useful functions to other resources.

==Mapping==
* Create a map with the map editor for an existing gamemode.
**[[Resource:Editor|Map Editor Manual]]

==Web development==
* Work with lil_Toady to add new features and improvements to community.mtasa.com.
* Create your own system for statistics - using the [[PHP SDK]] as a basis. Contact eAi or jbeta for help.

==Documentation==
Before you make changes check out: [[Help:Editing Guidelines|Editing Guidelines]]
* Finish documentation for [[:Category:Incomplete|Incomplete functions]] - ask in #mta.scripting if you're not sure of something.
* Add examples to [[:Category:Needs Example|functions & events missing examples]] - please test them, and again, as if you need help.
* Review and verify [[:Category:Needs Checking|pages that need checking]] - make sure highlighted issues are solved before removing pages from the category.
* Expand the pages that explain [[:Category:Scripting_Concepts|MTA core concepts]].
* Write tutorials to help new people.
* Translate the wiki pages so people from other countries can get started in MTA too.
* Create documentation for undocumented functions and events [[Undocumented Items]]

==Specific tasks==
* Create a fuzzer to check for crashes in our scripting functions.
* Help develop/fix existing gamemodes. Contact the original author on IRC (or ask a developer) to tell the author so you can work together.
* The web interface resources (resourcemanager, resourcebrowser and webadmin chiefly) are really only compatible with Firefox. Someone could put in some time to make these work on Internet Explorer, Opera and Safari. See [[User_talk:EAi|eAi]] for help.

[[pl:Jak możesz pomóc]]
[[ru:How you can help]]
[[es:Cómo puedes ayudar]]
[[hu:How you can help]]

Id

2013-07-18T21:05:35Z

Shmorf: Removed vehicle components from 'See Also' list.

ID stands for identification. It is a whole-number integer that refers to many mechanics of San Andreas.
----
Game elements using IDs:
''Note: does not include small ID lists related to specific functions or IDs created by MTA''
*[[Animations|Animations]]
*[[Character Skins]]
*[[CJ_Clothes|Clothing styles]]
*[[Death Reasons]]
*[[Garage|Garage IDs]]
*[[Interior IDs]]
*[[Material IDs]]
*[[Projectiles]]
*[[Radar Blips]]
*[[Sounds]]
*[[Vehicle IDs]]
*[[Vehicle Colors]]
*[[Vehicle Upgrades]]
*[[Weapons|Weapons]]
*[[Weather]] ''Note: blended weather allows for many more undocumented effects''

==See Also==
*[[Vending|List of San Andreas Vending machine locations]]
*[[IDE_List|San Andreas IDE List]]

==Credits==
{{IDs}}
;Credit for information contained in the pages:
:Ransom (initial creation, formatting, and all lists not credited to others)
:eAi (vehicle colors list)
:erorr404/Talidan/Brophy (sound list)
:Talidan (radar blip pictures/vehicle list)
:Hellfish (skin pictures [http://www.gtaforums.com/index.php?showtopic=205220 SOURCE])
:Brophy/Ratt/Panther/Twig (lots of inital ID data)
:GTAForums (Allowing Ransom to find IDs for lists)

[[de:Id]]
[[ru:Id]]
[[Category:ID Lists]]

Id

2013-07-18T20:49:19Z

Shmorf: Added vehicle components to 'see also' sub category.

ID stands for identification. It is a whole-number integer that refers to many mechanics of San Andreas.
----
Game elements using IDs:
''Note: does not include small ID lists related to specific functions or IDs created by MTA''
*[[Animations|Animations]]
*[[Character Skins]]
*[[CJ_Clothes|Clothing styles]]
*[[Death Reasons]]
*[[Garage|Garage IDs]]
*[[Interior IDs]]
*[[Material IDs]]
*[[Projectiles]]
*[[Radar Blips]]
*[[Sounds]]
*[[Vehicle IDs]]
*[[Vehicle Colors]]
*[[Vehicle Upgrades]]
*[[Weapons|Weapons]]
*[[Weather]] ''Note: blended weather allows for many more undocumented effects''

==See Also==
*[[Vending|List of San Andreas Vending machine locations]]
*[[IDE_List|San Andreas IDE List]]
*[[Vehicle_components|List of vehicle components]]

==Credits==
{{IDs}}
;Credit for information contained in the pages:
:Ransom (initial creation, formatting, and all lists not credited to others)
:eAi (vehicle colors list)
:erorr404/Talidan/Brophy (sound list)
:Talidan (radar blip pictures/vehicle list)
:Hellfish (skin pictures [http://www.gtaforums.com/index.php?showtopic=205220 SOURCE])
:Brophy/Ratt/Panther/Twig (lots of inital ID data)
:GTAForums (Allowing Ransom to find IDs for lists)

[[de:Id]]
[[ru:Id]]
[[Category:ID Lists]]

OnClientVehicleNitroStateChange

2013-05-05T22:16:12Z

Shmorf: /* Example */ Updated

{{Client event}}
__NOTOC__
This event gets triggered when nitro state is changing.

==Parameters==
<syntaxhighlight lang="lua">
bool state
</syntaxhighlight>
*'''state:''' current state of nitro

==Source==
The source of this event is the player vehicle.

==Example==
This example is showing short chat message on nitro state changing.
<section name="Client" class="client" show="true">
<syntaxhighlight lang="lua">
function nitro_updateState(state)
if state then
outputChatBox("Nitro #00FF00activated!", 255, 200, 0, true)
elseif not state then
outputChatBox("Nitro #FF0000deactivated!", 255, 200, 0, true)
end
end
addEventHandler("onClientVehicleNitroStateChange", root, nitro_updateState)
</syntaxhighlight>
</section>

==See Also==
===Client vehicle events===
{{Client_vehicle_events}}
===Client event functions===
{{Client_event_functions}}

User:Shmorf

2013-05-05T21:12:27Z

Shmorf: Created page with "Hi, I´m Shmorf. An experienced cardboard folder."

Hi, I´m Shmorf. An experienced cardboard folder.