Multi Theft Auto: Wiki - User contributions [en]

PL/getAccountsBySerial

2016-03-06T09:01:23Z

Wielebny: passing empty string as an argument / przekazywanie pustego stringu jako argument

__NOTOC__
{{Server function}}
{{New items|3.014|1.4|
Funkcja ta zwraca tabelę [[table]] zawierającą wszystkie konta [[account]] które zalogowały się na dany [[serial]]. Jeżeli serial jest pustym stringiem, zwrócone zostaną wszystkie konta na które nie logowano się nigdy.
}}

==Składnia==
<syntaxhighlight lang="lua">
table getAccountsBySerial ( string serial )
</syntaxhighlight>
{{OOP|This function is a static function underneath the Account class.|Account.getAllBySerial||}}
===Wymagane argumenty===
*'''serial:''' [[serial]] z którego chcemy pobrać konta

===Zwracana wartość===
Funkcja ta zwraca tabelę ''[[table]]'' zawierającą konta powiązane z tym serialem. ''Fałsz'' jeżeli podaliśmy zły [[serial]] w argumencie.

==Przykład==
Przykład ten dodaje komendę ''getAccounts'' która wyświetla ilość kont powiązaną z naszym serialem.
<syntaxhighlight lang="lua">
addCommandHandler("getAccounts",
function (player, cmd)
local serial = getPlayerSerial(player)
local accounts = getAccountsBySerial(serial)
outputChatBox("You have " .. #accounts .. " accounts.", player)
end)
</syntaxhighlight>

==Zobacz również==
{{Account_functions}}

[[en:getAccountsBySerial]]

Client on Linux Manual

2015-11-13T19:18:02Z

Wielebny: notes about basswma crashes

{{Needs Checking|MTA: SA 1.5 and greater versions seem to have problems when launching under Wine. Please consider rewriting this manual to point people to use an alternative (like VMWare) instead.}}
{{Warning|This page is for Linux players '''ONLY''', for Windows go [[Client Manual|here]].|true}}
==Before you start==

First of all, please ensure your computer fits the requirements needed.
Read the [[Client_Manual|Client Manual]] page for further informations, or join us on IRC @ irc://irc.multitheftauto.com/mta

===Requirements===
The hardware requirements for Multi Theft Auto: San Andreas are the same than on Windows.
For software requirements, you need:
* Wine (get it on your package manager (synaptic, apt, pacman, yum etc.); follow instructions [https://www.winehq.org/download/ubuntu here] if you're using Ubuntu
(as of MTA 1.4.1 Ubuntu's default Wine package seems to be incompatible with Visual C++, which is required to install MTA)
* Windows fonts installed:
** tahoma.ttf
** tahomabd.ttf
** verdana.ttf
Get them on the Internet, e.g. [http://fontonic.com/ fontonic.com]

Or get the zip archive with the 3 fonts here: [http://www.4shared.com/zip/IsErUbQAba/wine_mta_fonts.html wine_mta_fonts.zip]

Install them in: <syntaxhighlight lang="lua">~/.wine/dosdevices/c:/windows/Fonts/</syntaxhighlight>
(~/ points to your user home folder on Linux, .wine is the default wineprefix)

==Installing the game==
Download the MTA installer from [http://www.mtasa.com mtasa.com], ensure you can launch it (chmod +x) then install it when you want.

==Running the game==
Once installed, double-clicking on the Multi Theft Auto.exe should work. If not, try in a terminal the following command: "wine Multi Theft Auto.exe" in the directory you installed Multi Theft Auto to.
If it doesn't work, check the contents of the file c:/Program_Files/Multi Theft Auto/MTA/CEGUI.log, which may contain useful information.

==Known issues==
===Specific issues===
* Impossible connection through the server browser [Fixed in the [http://bugs.mtasa.com/view.php?id=5084 5084 bug] ]

* MTA won't start on Ubuntu 12.04 LTS [Temporary fix is available [http://forum.mtasa.com/viewtopic.php?p=434011#p434011 here] ]

===Other issues===
* MTA isn't starting (even with fonts installed)
#Try to start MTA:SA in a virtual desktop
#:Go to WineConfig, choose the tab "Graphics" and select "Emulate a virtual desktop".<br>
#Try to delete your gta_sa.set file
#:which is located in the "GTA San Andreas User Files" folder, which can be found in your home directory.<br>'''(Remember to create a copy, if you're playing San Andreas in singleplayer)'''
#Try to delete your MTA config file
#:which is: "MTA San Andreas 1.3/MTA/coreconfig.xml"<br>'''(Also remember to create a copy, if you don't want to lose your edited MTA configuration)'''

* Crash when connecting
*:Sometimes the audio-server makes problems (could be related to pulseaudio), in this case you've to go to WineConfig and choose the tab Audio, then deselect "ALSA" and select "EsoundD". Save the settings and restart MTA.
* Crash in basswma.dll module while streaming audio
*:Install Windows Media Player 10
*:
<syntaxhighlight lang="lua">
winetricks wmp10
</syntaxhighlight>
* Special Detections (SD)
*:If you are using a 64 wine version you may have problems with [http://wiki.multitheftauto.com/wiki/Anti-cheat_guide#.3Cenablesd.3E.3C.2Fenablesd.3E Special Detections]. If the server you are trying to connect keeps showing something like [http://i.imgur.com/33T8a82.jpg this], then you should make a [http://wiki.archlinux.org/index.php/Wine#Using_WINEARCH 32 bit wine prefix] (or bottle).
*:
<syntaxhighlight lang="lua">export WINEARCH=win32 WINEPREFIX=~/.winegta
winecfg</syntaxhighlight>
Change Windows version on bottom to Windows 7 and press OK. Now you have a 32 bit wine prefix on ~/.winegta.
Install GTA:SA and them MTA.
After this, MTA and GTA have been installed within ~/.winegta prefix which is a 32 bit wine environment.

== See Also ==
* [http://nightly.mtasa.com/ nightly.mtasa.com] - For nightly builds.

[[Category:Support]]
[[ru:Client on Linux Manual]]
[[hu:Client on Linux Manual]]

Upgrade list

2015-11-06T10:35:20Z

Wielebny: typo

This is a list of upgrades that correspond to [[getVehicleUpgradeOnSlot]].

----

{| class="wikitable sortable" style="width:10%;"
|-
! ID || Upgrade Type
|-
| '''0''' || Hood
|-
| '''1''' || Vent
|-
| '''2''' || Spoiler
|-
| '''3''' || Sideskirt
|-
| '''4''' || Front Bullbar
|-
| '''5''' || Rear Bullbar
|-
| '''6''' || Headlights
|-
| '''7''' || Roof
|-
| '''8''' || Nitrous
|-
| '''9''' || Hydraulics
|-
| '''10''' || Stereo
|-
| '''11''' || Unknown
|-
| '''12''' || Wheels
|-
| '''13''' || Exhaust
|-
| '''14''' || Front Bumper
|-
| '''15''' || Rear Bumper
|-
| '''16''' || Misc.
|-

|}

[[it:Cris G. / Morelli]]

Talk:Predefined variables list

2015-06-17T11:19:54Z

Wielebny: Two variables that probably don't have to be hidden anymore

== sourceResource && sourceResourceRoot ==

Are sourceResource and sourceResourceRoot really still broken? --[[User:Wielebny|Wielebny]] ([[User talk:Wielebny|talk]]) 11:19, 17 June 2015 (UTC)

Template:Garages

2015-06-09T15:08:27Z

Wielebny: garage location

{| class="wikitable" style="width: auto; text-align: center; table-layout: fixed;"
|-
!ID
!Name/Description
!Approximate location (x,y,z)
|-
|'''0'''
|Commerce Region, Loading Bay Garage (Life's a Beach)
|-
|'''1'''
|LSPD Police Impound Garage
|-
|'''2'''
|Mission Garage near El Corona (Los Desperados)
|1873,-2101,14
|-
|'''3'''
|Eight Ball Autos near El Corona
|1836,-1860,14
|-
|'''4'''
|Mission Garage near El Corona (Cesar Vialpando)
|1793,-2141,14
|-
|'''5'''
|Player Garage: El Corona
|-
|'''6'''
|LS Burglary Garage near Playe del Seville
|2743,-2000,14
|-
|'''7'''
|LowRider Tuning Garage in Willowfield
|2645,-2033,14
|-
|'''8'''
|Pay 'n' Spray in Idlewood
|-
|'''9'''
|Player Garage: Johnson House
|2502,-1685,14
|-
|'''10'''
|Transfender in Temple
|1047,-1032,32
|-
|'''11'''
|Pay 'n' Spray in Temple
|1028,-1034,32
|-
|'''12'''
|Pay 'n' Spray in Santa Maria Beach
|484,-1726,11
|-
|'''13'''
|Player Garage: Santa Maria Beach
|318,-1772,5
|-
|'''14'''
|Player Garage: Mulholland
|1351,-619,109
|-
|'''15'''
|Wheel Archangels in Ocean Flats
| -2708,211,4
|-
|'''16'''
|Mission Garage in Ocean Flats (T-Bone Mendez)
|-
|'''17'''
|Player Garage: Hashbury
|-
|'''18'''
|Transfender near Wang Cars in Doherty
|-1924,221,35
|-
|'''19'''
|Pay 'n' Spray near Wang Cars in Doherty
| -1913,263,40
|-
|'''20'''
|SF Burglary Garage, Loading Bay near Doherty
|-
|'''21'''
|Player Garage: Doherty
| -2029,140,29
|-
|'''22'''
|Mission Garage in Doherty Garage
|-
|'''23'''
|Woozie's Mission Garage in Chinatown (Ran Fa Li)
|-
|'''24'''
|Michelle's Pay 'n' Spray in Downtown
| -1786,1202,26
|-
|'''25'''
|Player Garage: Calton Heights
|-
|'''26'''
|SFPD Police Impound Garage
|-
|'''27'''
|Pay 'n' Spray in Juniper Hollow
| -2424,1037,50
|-
|'''28'''
|Player Garage: Paradiso
|-
|'''29'''
|LVPD Police Impound Garage
|-
|'''30'''
|Airport Plane Garage in Las Venturas
|1578,1242,11
|-
|'''31'''
|LV Burglary Garage near Camel's Toe
|-
|'''32'''
|Pay 'n' Spray near Royal Casino
|-
|'''33'''
|Transfender in come-a-lot
|-
|'''34'''
|Player Garage: Rockshore West
|-
|'''35'''
|Welding Wedding Bomb-workshop in Emerald Isle
|-
|'''36'''
|Pay 'n' Spray in Redsands East
|-
|'''37'''
|Player Garage: Redsands West
|-
|'''38'''
|Player Garage: Prickle Pine
|-
|'''39'''
|Player Garage: Whitewood Estates
|-
|'''40'''
|Pay 'n' Spray in El Quebrados
| -1411,2599,56
|-
|'''41'''
|Pay 'n' Spray in Fort Carson
|-
|'''42'''
|Player Garage: Fort Carson
|-
|'''43'''
|Player Garage: Verdant Meadows
|-
|'''44'''
|Mission Garage in El Castillo del Diablo (Interdiction)
| -385,2230,42
|-
|'''45'''
|Airport Garage in Verdant Meadows
|-
|'''46'''
|Mission Garage in Angel Pine (Puncture Wounds)
|-
|'''47'''
|Pay 'n' Spray in Dillimore
|-
|'''48'''
|Player Garage: Palomino Creek
|-
|'''49'''
|Player Garage: Dillimore
|}

GuiSetAlpha

2015-06-07T05:27:48Z

Wielebny: note about default value

{{Client function}}
__NOTOC__
This changes the alpha level (the visibleness/transparency) of a GUI element

==Syntax==

<syntaxhighlight lang="lua">
bool guiSetAlpha ( element guielement, float alpha )
</syntaxhighlight>

===Required Arguments===
*'''guiElement:''' the GUI element whose visibility is to be changed
*'''alpha:''' The visibility/transparency of the GUI element. Ranges from 0 (fully transparent) to 1 (fully opaque). Default value is 0.80.

===Returns===
Returns ''true'' if the gui element's alpha was successfully changed, ''false'' otherwise.

==Example==
This creates a GUI window and allows a player to change it's alpha (the visibleness/transparency) value with a command.
<syntaxhighlight lang="lua">--Create a gridlist
myWindow = guiCreateWindow ( 0.30, 0.10, 0.5, 0.60, "GUI window title", true )

--Add a command handler to change the alpha of the GUI window.
--Usage example: '/alpha 0.8', where 0.8 is stored as alphaAmount
function changeAlpha ( commandName, alphaAmount )
alphaAmount = tonumber(alphaAmount)
guiSetAlpha ( myWindow, alphaAmount )
end
addCommandHandler ( "alpha", changeAlpha )
</syntaxhighlight>

==See Also==
{{GUI functions}}

OutputChatBox

2015-05-23T00:23:43Z

Wielebny: Informational change: default RGB value in hex

{{Server client function}}
{{Note_box|Avoid outputting text to the chatbox that isn't actually chat, as this can be annoying for players. Output information and status messages to the HUD.}}
__NOTOC__
This outputs the specified text string to the chatbox. It can be specified as a message to certain player(s) or all players.

It can optionally allow you to embed color changes into the string by setting the colorCoded boolean to true. This allows:
<syntaxhighlight lang="lua">
outputChatBox ( "#FF0000Hello #00FF00World", getRootElement(), 255, 255, 255, true )
</syntaxhighlight>
This will display as: '''<span style='color:red;'>Hello</span> <span style='color:green'>World</span> '''

==Syntax==
<section name="Server" class="server" show="true">
<syntaxhighlight lang="lua">bool outputChatBox ( string text [, element visibleTo=getRootElement(), int r=231, int g=217, int b=176, bool colorCoded=false ] )</syntaxhighlight>
{{OOP||[[player]]:outputChat}}
==Required Arguments==
*'''text:''' The text string that you wish to send to the chat window. If more than 128 characters it will not be showed in chat.

==Optional Arguments==
{{OptionalArg}}
*'''visibleTo:''' This specifies who the chat is visible to. Any players in this element will see the chat message. See [[visibility]].
*'''r:''' The amount of red in the color of the text. Default value is 231.
*'''g:''' The amount of green in the color of the text. Default value is 217.
*'''b:''' The amount of blue in the color of the text. Default value is 176.
*'''colorCoded:''' A boolean value determining whether or not '#RRGGBB' tags should be used.
Note: The #RRGGBB format must contain capital letters a-f is not acceptable but A-F is. Default RGB values in this format are: '#E7D9B0'.
</section>
<section name="Client" class="client" show="true">
<syntaxhighlight lang="lua">bool outputChatBox ( string text [, int r=231, int g=217, int b=176, bool colorCoded=false ] )</syntaxhighlight>

==Required Arguments==
*'''text:''' The text string that you wish to send to the chat window. If more than 128 characters it will not be showed in chat.

==Optional Arguments==
{{OptionalArg}}
*'''r:''' The amount of red in the color of the text. Default value is 231.
*'''g:''' The amount of green in the color of the text. Default value is 217.
*'''b:''' The amount of blue in the color of the text. Default value is 176.
*'''colorCoded:''' A boolean value determining whether or not '#RRGGBB' tags should be used.
Note: The #RRGGBB format must contain capital letters a-f is not acceptable but A-F is. Default RGB values in this format are: '#E7D9B0'.

</section>

==Returns==
Returns ''true'' if the message was displayed successfully. Returns ''false'' if invalid arguments are specified.

==Example==
<section name="Server" class="server" show="true">
'''Example 1:''' This example displays a chat message to all users.
<syntaxhighlight lang="lua">
x = 5
y = 10
-- Displays the message
outputChatBox ( "I have " .. x .. " apples and " .. y .. " oranges." )
</syntaxhighlight>

'''Example 2:''' This example outputs a simple colour coded message, "Red White", where the 'White' is in white colour, and 'Red' is in a red colour.
<syntaxhighlight lang="lua">
outputChatBox ( "Red #FFFFFFWhite", getRootElement(), 255, 0, 0, true )
</syntaxhighlight>

'''Example 3:''' This example allows for coloured chat, according to a player's nametag. This makes use of colour coded outputs.
<syntaxhighlight lang="lua">
function colouredChat ( message, theType )
if theType == 0 then --if its normal chat (not /me or teamchat) then
cancelEvent() --prevent MTA from outputting chat
message = string.gsub(message, "#%x%x%x%x%x%x", "") --remove any hex tags in a player's chat to prevent custom colours by using lua's string.gsub
local r,g,b = getPlayerNametagColor ( source ) --get the player's nametag colour
local chatterName = getPlayerName ( source ) --get his name
--output a message with the name as his nametag colour, and the rest in white.
outputChatBox ( chatterName..":#FFFFFF "..message, getRootElement(), r, g, b, true )
end
end
addEventHandler("onPlayerChat", getRootElement(), colouredChat)
</syntaxhighlight>

'''Example 4:''' This example displays a chat message to a single user called ''someguy''.
<syntaxhighlight lang="lua">
-- Find the player element for the player called 'someguy'
myPlayer = getPlayerFromName ( "someguy" )
-- If a player was found called 'someguy' then...
if ( myPlayer ~= false ) then
x = 5
y = 10
-- Display the message
outputChatBox ( "I have " .. x .. " apples and " .. y .. " oranges.", myPlayer )
end
</syntaxhighlight>

'''Example 5:''' These two functions can speed up typing, and display a message when a player Joins.
<syntaxhighlight lang="lua">
local msg_red,msg_green,msg_blue = 255,255,0

function servertalkprivate(message, sendto)
--Talk to one client only
outputChatBox(tostring(message), sendto, msg_red, msg_green, msg_blue, true)
end

function servertalk(message)
--Talk to everyone
servertalkprivate(message, getRootElement())
end

function onJoin()
servertalkprivate("Welcome to My Server", source)
end

addEventHandler("onPlayerJoin",getRootElement(),onJoin)
</syntaxhighlight>

'''Example 6:''' This can be used to display a message when the player joins and sets its armor to 100. '''(By Bilal135)'''
<syntaxhighlight lang="lua">
function onJoin()
setPedArmor(source, 100)
outputChatBox("Welcome To The Server", source, 255, 0, 0)
end
addEventHandler("onPlayerJoin", root, onJoin)
</syntaxhighlight>
</section>

==See Also==
{{Server functions}}
[[cs:outputChatBox]]
[[ru:outputChatBox]]

Vehicle variants

2015-02-03T01:41:43Z

Wielebny: additional variant for sadler

== Custom Variants ==
With the introduction of vehicle variants we now have the ability to add custom variants using custom models. Variants can be anything from different adverts to additional parts of the model..
[[Image:Infernus.png|200px|thumb|left|Custom Infernus Variant]]

==How to Add Variants==
Adding variants requires modifying your DFF by adding a part of the model you wish to be a variant and naming it extra1, extra2, extra3, extra4 or extra5 then setting it's parent to the chassis_dummy this tells GTA it has variant information and after this your variant will work in MTA.

==Spawning Custom Variants==
Spawning custom variants is more complicated as we do not know the variants are there so the random variant spawner (TM) will not spawn the added variant.

A way around this is to implicitly specify which variant you require in createVehicle this will bypass our random variant spawner (TM) and allow you to spawn it.

Any invalid variant will show up as the default model with no variation.

==GTA Variants==
{| class="wikitable sortable" style="width: auto; table-layout: fixed;"
|-
! scope="col" | Vehicle Name
! scope="col" | Vehicle ID
! scope="col" class="unsortable" | Variants
|-
| Ambulance
| 416
| Numbers: 0 = 37, 1 = 71
|-
| Trailer 1
| 435
| Side Ads: 0 = Cok-o-Pops, 1 = Munky Juice, 2 = Hinterland, 3 = Zip, 4 = RS Haul, 5 = Ranch
|-
| Trailer 2
| 450
| Contents: 0 = Filled with gravel/coal/stone
|-
| Bagboxb
| 607
| Contents: 0,1,2 = Various distributions of loose baggage
|-
| Baggage
| 485
| Rear Cargo Items: 0 = Earmuffs, 1 = Small Case, 2 = Large Case
|-
| Barracks
| 433
| Bed Covering: 0 = Opaque Fabric, 1 = Camo Netting
|-
| Benson
| 499
| Side Ads: 0 = Shady Industries, 1 = LSD, 2 = The Uphill Gardener, 3 = Discount Furniture
|-
| BF-400
| 581
| Exhausts: 0 = Single Type1, 1 = Single Type2, 2 = Dual Type3 - Fairings (with Windshields): 3 = Half-size, 4 = Full-size
|-
| BF Injection
| 424
| Body: 0 = Side Panels
|-
| Bloodring Banger
| 504
| Numbers/Roof Color: 0 = 328/White, 1 = 464/Check, 2 = 172/Check, 3 = 100/White, 4 = 284/White, 5 = 505/Check
|-
| Bobcat
| 422
| Bed Items: 0 = Spare Tire, 1 = Sprunk Cans
|-
| Burrito
| 482
| Roof Items: 0 = Roof Lights + Spoiler
|-
| Caddy
| 457
| Rear Cargo (Driver Side): 0 = Golfbag1, 1 = Satchel1, 2 = Golfbag2, Rear Cargo (Pass Side): 3 = Satchel2, 4 = Golfbag3, 5 = Golfbag4
|-
| Camper
| 483
| 0 = Open Curtains & Second Bench Seat, 1 = Open Roof Vent, Closed Curtains, Bed in Back, Peace Sign
|-
| Cheetah
| 415
| Side Mirrors: 0 = Single, Placed High, 1 = Dual, Placed Normally
|-
| Coach
| 437
| Name on Side: 0 = Big O Tours, 1 = Bikini Line
|-
| Coastguard
| 472
| Various Items 0 = Items all Over, 1 = Items Grouped in Back, 2 = Items all Over + 2 Oars in Front
|-
| FCR-900
| 521
| Exhausts: 0 = Single Type1, 1 = Dual Type1, 2 = Dual Type2, Fairings (with Windshields): 3 = Half-size, 4 = Full-size
|-
| Fire Truck
| 407
| Numbers: 0 = 64, 1 = 16, 2 = 47
|-
| Flatbed
| 455
| Numbers: 0 = 64, 1 = 16, 2 = 47
|-
| Hotknife
| 434
| 0 = Partial Engine Cover
|-
| Hotring Racer 2
| 502
| Numbers: 0 = 96, 1 = 67, 2 = 73, 3 = 52, 4 = 45, 5 = 14
|-
| Hotring Racer 3
| 503
| Numbers: 0 = 82, 1 = 26, 2 = 65, 3 = 07, 4 = 36, 5 = 60
|-
| Kart
| 571
| Body Panels: 0 = Both Sides, 1 = Steering Column
|-
| Launch
| 595
| Roofs: 0 = Over passenger section, 1 = Over driver section
|-
| Marquis
| 484
| 0 = Windshield over Cabin Entrance
|-
| Mesa
| 500
| 0 = Roof Over Back, 1 = Roll Bar in Back
|-
| Monster 2
| 556
| 0 = Roof Spoiler, 1 = Roof Lights, 2 = Roll Bar with Lights
|-
| Monster 3
| 557
| 0 = Couldn't Determine 1 = Roof Lights
|-
| Mr. Whoopee
| 423
| Rear Sign: 0 = Cherry Popping Good, 1 = Slow Children Ahead
|-
| Mule
| 414
| Side Ads: 0 = Toy Corner, 1 = Binco, 2 = Semi, 3 = Shafted Appliances
|-
| NRG-500
| 522
| Exhausts: 0 = Single Pair1, 1 = Single Pair2, 2 = Dual Pair2 - Fairings (with Windshields): 3 = Smooth, 4 = With Side Cutouts
|-
| Patriot
| 470
| Cargo Area 0 = Low Cover, 1 = Roof/High Cover, 2 = Roll Bar
|-
| Perennial
| 404
| Cargo Area 0 = Low Cover, 1 = Roof/High Cover, 2 = Roll Bar
|-
| Picador
| 600
| Items in Bed: 0 = Planks, 1 = Sprunk Cans
|-
| Pony
| 413
| 0 = Sound System in Back
|-
| Reefer
| 453
| Items in Back: 0 = Boxes of Fish, 1 = Bench
|-
| Romero
| 442
| Coffins: 0 = Brown Style1, 1 = Black Style2, 2 = Brown Style3
|-
| Rumpo
| 440
| Side Ads: 0 = Cok-o-Pops, 1 = Harry Plums, 2 = Dick Goblin's, 3 = Final Build, 4 = Transfender, 5 = Wheel Arch Angels
|-
| Sadler
| 543
| Items in Bed: 0 = Two Propane Tanks & Crate, 1 = Two Barrels, 2 = Sprunk Cans, 3 = Open Crates, 4+ = Empty bed
|-
| Damaged Sadler
| 605
| Items in Bed: 0 = Two Propane Tanks & Crate, 1 = Two Barrels, 2 = Sprunk Cans, 3 = Open Crates, 4+ = Empty bed
|-
| Securicar
| 428
| Side Logo: 0 = Chuff, 1 = Lock&Load
|-
| Slamvan
| 535
| Steering Wheel: 0 = Normal, 1 = Chain (Default has none!)
|-
| Stallion
| 439
| Roof: 0 = Hardtop, 1 = Softtop (up), 2 = Softtop (folded)
|-
| Super GT
| 506
| 0 = Full Roof
|-
| S.W.A.T.
| 601
| Number: 0 = 1, 1 = 9, 2 = 6, 3 = 7
|-
| Berkley's RC Van
| 459
| 0 = Boxes of Toys in Back
|-
| Tram
| 449
| 0,1,2,3 = (4 defined extras, but I don't know what they are)
|-
| Trashmaster
| 408
| 0 = Some bits of trash sticking out of the back
|-
| Tug
| 583
| Case in Back: 0 = Red Case, 1 = Green Case
|-
| Utility Van
| 552
| 0 = Cones, Barrel in back + Cone lying on passenger side rail, 1 = Cones, Barrel in back + Cone lying on driver side rail
|-
| Walton
| 478
| Items in Bed: 0 = Two Propane Tanks, 1 = Open Crates, 2 = Propane Tank and Barrel
|-
| Windsor
| 555
| 0 = Roof, 1 = No Roof
|-
| Yankee
| 456
| Side Ads: 0 = Big Gas, 1 = RS Haul, 2 = Star Balls, 3 = Flower Power
|-
| ZR-350
| 477
| 0 = Rear Spoiler
|- class="sortbottom"
! Vehicle Name
! Vehicle ID
! Variants
|-
|}

Above table serialized in Lua:

<syntaxhighlight lang="lua">
local vehicleModelVariants={
[404]={0,1,2},
[407]={0,1,2},
[408]={0},
[413]={0},
[414]={0,1,2,3},
[415]={0,1},
[416]={0,1},
[422]={0,1},
[423]={0,1},
[424]={0},
[428]={0,1},
[433]={0,1},
[434]={0},
[435]={0,1,2,3,4,5},
[437]={0,1},
[439]={0,1,2},
[440]={0,1,2,3,4,5},
[442]={0,1,2},
[449]={0,1,2,3,4},
[450]={0},
[453]={0,1},
[455]={0,1,2},
[456]={0,1,2,3},
[457]={0,1,2,3,4,5},
[459]={0},
[470]={0,1,2},
[472]={0,1,2},
[477]={0},
[478]={0,1,2},
[482]={0},
[483]={0,1},
[484]={0},
[485]={0,1,2},
[499]={0,1,2,3},
[500]={0,1},
[502]={0,1,2,3,4,5},
[503]={0,1,2,3,4,5},
[504]={0,1,2,3,4,5},
[506]={0},
[521]={0,1,2,3,4},
[522]={0,1,2,3,4},
[535]={0,1},
[543]={0,1,2,3,4},
[552]={0,1},
[555]={0,1},
[556]={0,1,2},
[557]={0,1},
[571]={0,1},
[581]={0,1,2,3,4},
[583]={0,1},
[595]={0,1},
[600]={0,1},
[601]={0,1,2,3},
[605]={0,1,2,3,4},
[607]={0,1,2},
}
</syntaxhighlight>

[[Category:ID Lists]]
[[ru:Vehicle variants]]
[[de:Fahrzeug Varianten]]

Id

2014-04-15T17:20:17Z

Wielebny: Link to paintjob 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]]
*[[Paintjob|Paintjobs]]
*[[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]]
[[zh-cn:ID 列表]]

[[Category:ID Lists]]

Paintjob

2014-04-15T17:19:40Z

Wielebny: +see also

Paintjobs can be applied on a vehicle using [[setVehiclePaintjob]].

To remove a paintjob from a vehicle, apply paintjob number 3 to it.

==Supported vehicles==
* Blade: 0,1,2
* Broadway: 0,1
* Camper: 0
* Elegy: 0,1,2
* Flash: 0,1,2
* Jester: 0,1,2
* Remington: 0,1,2
* Savanna: 0,1,2
* Slamvan: 0,1,2
* Sultan: 0,1,2
* Tornado: 0,1,2
* Uranus: 0,1,2

==Serialized table of supported vehicles==
<syntaxhighlight lang="lua">
local supported_vehicles={
[483]={0}, -- camper
[534]={0,1,2}, -- remington
[535]={0,1,2}, -- slamvan
[536]={0,1,2}, -- blade
[558]={0,1,2}, -- uranus
[559]={0,1,2}, -- jester
[560]={0,1,2}, -- sultan
[561]={0,1,2}, -- stratum
[562]={0,1,2}, -- elegy
[565]={0,1,2}, -- flash
[567]={0,1,2}, -- savanna
[575]={0,1}, -- broadway
[576]={0,1,2}, -- tornado
}
</syntaxhighlight>

==See Also==
[[id|ID Lists]]

Paintjob

2014-04-15T17:18:06Z

Wielebny: Paintjob list

SetVehiclePaintjob

2014-04-15T17:13:47Z

Wielebny: Link to paintjob list

__NOTOC__
{{Server client function}}
This function changes the paintjob on the specified vehicle. <br/>
See [[Paintjob|paintjob]] for list of supported vehicles.

==Syntax==
<syntaxhighlight lang="lua">bool setVehiclePaintjob ( vehicle theVehicle, int value )</syntaxhighlight>

===Required Arguments===
*'''theVehicle''': The [[vehicle]] you wish to change the paintjob of.
*'''value''': A whole number representing the new paintjob id. Ranges from 0 up to 3.

==Returns==
Returns ''true'' if the vehicle's paintjob was changed. Otherwise ''false''.

==Example==
This example will set the paintjob of a new sultan to '2'.
<syntaxhighlight lang="lua">
newvehicle = createVehicle ( 560, 100, 100, 40 ) -- create the sultan
setVehiclePaintjob ( newvehicle, 2 ) -- change the paintjob
</syntaxhighlight>

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

Vehicle variants

2014-02-18T05:35:05Z

Wielebny: some scripting help - serialized table of vehicle model variants

== Custom Variants ==
With the introduction of vehicle variants we now have the ability to add custom variants using custom models. Variants can be anything from different adverts to additional parts of the model..
[[Image:Infernus.png|200px|thumb|left|Custom Infernus Variant]]

==How to Add Variants==
Adding variants requires modifying your DFF by adding a part of the model you wish to be a variant and naming it extra1, extra2, extra3, extra4 or extra5 then setting it's parent to the chassis_dummy this tells GTA it has variant information and after this your variant will work in MTA.

==Spawning Custom Variants==
Spawning custom variants is more complicated as we do not know the variants are there so the random variant spawner (TM) will not spawn the added variant.

A way around this is to implicitly specify which variant you require in createVehicle this will bypass our random variant spawner (TM) and allow you to spawn it.

Any invalid variant will show up as the default model with no variation.

==GTA Variants==
{| class="wikitable sortable" style="width: auto; table-layout: fixed;"
|-
! scope="col" | Vehicle Name
! scope="col" | Vehicle ID
! scope="col" class="unsortable" | Variants
|-
| Ambulance
| 416
| Numbers: 0 = 37, 1 = 71
|-
| Trailer 1
| 435
| Side Ads: 0 = Cok-o-Pops, 1 = Munky Juice, 2 = Hinterland, 3 = Zip, 4 = RS Haul, 5 = Ranch
|-
| Trailer 2
| 450
| Contents: 0 = Filled with gravel/coal/stone
|-
| Bagboxb
| 607
| Contents: 0,1,2 = Various distributions of loose baggage
|-
| Baggage
| 485
| Rear Cargo Items: 0 = Earmuffs, 1 = Small Case, 2 = Large Case
|-
| Barracks
| 433
| Bed Covering: 0 = Opaque Fabric, 1 = Camo Netting
|-
| Benson
| 499
| Side Ads: 0 = Shady Industries, 1 = LSD, 2 = The Uphill Gardener, 3 = Discount Furniture
|-
| BF-400
| 581
| Exhausts: 0 = Single Type1, 1 = Single Type2, 2 = Dual Type3 - Fairings (with Windshields): 3 = Half-size, 4 = Full-size
|-
| BF Injection
| 424
| Body: 0 = Side Panels
|-
| Bloodring Banger
| 504
| Numbers/Roof Color: 0 = 328/White, 1 = 464/Check, 2 = 172/Check, 3 = 100/White, 4 = 284/White, 5 = 505/Check
|-
| Bobcat
| 422
| Bed Items: 0 = Spare Tire, 1 = Sprunk Cans
|-
| Burrito
| 482
| Roof Items: 0 = Roof Lights + Spoiler
|-
| Caddy
| 457
| Rear Cargo (Driver Side): 0 = Golfbag1, 1 = Satchel1, 2 = Golfbag2, Rear Cargo (Pass Side): 3 = Satchel2, 4 = Golfbag3, 5 = Golfbag4
|-
| Camper
| 483
| 0 = Open Curtains & Second Bench Seat, 1 = Open Roof Vent, Closed Curtains, Bed in Back, Peace Sign
|-
| Cheetah
| 415
| Side Mirrors: 0 = Single, Placed High, 1 = Dual, Placed Normally
|-
| Coach
| 437
| Name on Side: 0 = Big O Tours, 1 = Bikini Line
|-
| Coastguard
| 472
| Various Items 0 = Items all Over, 1 = Items Grouped in Back, 2 = Items all Over + 2 Oars in Front
|-
| FCR-900
| 521
| Exhausts: 0 = Single Type1, 1 = Dual Type1, 2 = Dual Type2, Fairings (with Windshields): 3 = Half-size, 4 = Full-size
|-
| Fire Truck
| 407
| Numbers: 0 = 64, 1 = 16, 2 = 47
|-
| Flatbed
| 455
| Numbers: 0 = 64, 1 = 16, 2 = 47
|-
| Hotknife
| 434
| 0 = Partial Engine Cover
|-
| Hotring Racer 2
| 502
| Numbers: 0 = 96, 1 = 67, 2 = 73, 3 = 52, 4 = 45, 5 = 14
|-
| Hotring Racer 3
| 503
| Numbers: 0 = 82, 1 = 26, 2 = 65, 3 = 07, 4 = 36, 5 = 60
|-
| Kart
| 571
| Body Panels: 0 = Both Sides, 1 = Steering Column
|-
| Launch
| 595
| Roofs: 0 = Over passenger section, 1 = Over driver section
|-
| Marquis
| 484
| 0 = Windshield over Cabin Entrance
|-
| Mesa
| 500
| 0 = Roof Over Back, 1 = Roll Bar in Back
|-
| Monster 2
| 556
| 0 = Roof Spoiler, 1 = Roof Lights, 2 = Roll Bar with Lights
|-
| Monster 3
| 557
| 0 = Couldn't Determine 1 = Roof Lights
|-
| Mr. Whoopee
| 423
| Rear Sign: 0 = Cherry Popping Good, 1 = Slow Children Ahead
|-
| Mule
| 414
| Side Ads: 0 = Toy Corner, 1 = Binco, 2 = Semi, 3 = Shafted Appliances
|-
| NRG-500
| 522
| Exhausts: 0 = Single Pair1, 1 = Single Pair2, 2 = Dual Pair2 - Fairings (with Windshields): 3 = Smooth, 4 = With Side Cutouts
|-
| Patriot
| 470
| Cargo Area 0 = Low Cover, 1 = Roof/High Cover, 2 = Roll Bar
|-
| Peren
| 404
| Cargo Area 0 = Low Cover, 1 = Roof/High Cover, 2 = Roll Bar
|-
| Picador
| 600
| Items in Bed: 0 = Planks, 1 = Sprunk Cans
|-
| Pony
| 413
| 0 = Sound System in Back
|-
| Reefer
| 453
| Items in Back: 0 = Boxes of Fish, 1 = Bench
|-
| Romero
| 442
| Coffins: 0 = Brown Style1, 1 = Black Style2, 2 = Brown Style3
|-
| Rumpo
| 440
| Side Ads: 0 = Cok-o-Pops, 1 = Harry Plums, 2 = Dick Goblin's, 3 = Final Build, 4 = Transfender, 5 = Wheel Arch Angels
|-
| Sadler
| 543
| Items in Bed: 0 = Two Propane Tanks & Crate, 1 = Two Barrels, 2 = Sprunk Cans, 3 = Open Crates
|-
| Damaged Sadler
| 605
| Items in Bed: 0 = Two Propane Tanks & Crate, 1 = Two Barrels, 2 = Sprunk Cans, 3 = Open Crates
|-
| Securicar
| 428
| Side Logo: 0 = Chuff, 1 = Lock&Load
|-
| Slamvan
| 535
| Steering Wheel: 0 = Normal, 1 = Chain (Default has none!)
|-
| Stallion
| 439
| Roof: 0 = Hardtop, 1 = Softtop (up), 2 = Softtop (folded)
|-
| Super GT
| 506
| 0 = Full Roof
|-
| S.W.A.T.
| 601
| Number: 0 = 1, 1 = 9, 2 = 6, 3 = 7
|-
| Berkley's RC Van
| 459
| 0 = Boxes of Toys in Back
|-
| Tram
| 449
| 0,1,2,3 = (4 defined extras, but I don't know what they are)
|-
| Trashmaster
| 408
| 0 = Some bits of trash sticking out of the back
|-
| Tug
| 583
| Case in Back: 0 = Red Case, 1 = Green Case
|-
| Utility Van
| 552
| 0 = Cones, Barrel in back + Cone lying on passenger side rail, 1 = Cones, Barrel in back + Cone lying on driver side rail
|-
| Walton
| 478
| Items in Bed: 0 = Two Propane Tanks, 1 = Open Crates, 2 = Propane Tank and Barrel
|-
| Windsor
| 555
| 0 = Roof, 1 = No Roof
|-
| Yankee
| 456
| Side Ads: 0 = Big Gas, 1 = RS Haul, 2 = Star Balls, 3 = Flower Power
|-
| ZR-350
| 477
| 0 = Rear Spoiler
|- class="sortbottom"
! Vehicle Name
! Vehicle ID
! Variants
|-
|}

Above table serialized in Lua:

<syntaxhighlight lang="lua">
local vehicleModelVariants={
[404]={0,1,2},
[407]={0,1,2},
[408]={0},
[413]={0},
[414]={0,1,2,3},
[415]={0,1},
[416]={0,1},
[422]={0,1},
[423]={0,1},
[424]={0},
[428]={0,1},
[433]={0,1},
[434]={0},
[435]={0,1,2,3,4,5},
[437]={0,1},
[439]={0,1,2},
[440]={0,1,2,3,4,5},
[442]={0,1,2},
[449]={0,1,2,3,4},
[450]={0},
[453]={0,1},
[455]={0,1,2},
[456]={0,1,2,3},
[457]={0,1,2,3,4,5},
[459]={0},
[470]={0,1,2},
[472]={0,1,2},
[477]={0},
[478]={0,1,2},
[482]={0},
[483]={0,1},
[484]={0},
[485]={0,1,2},
[499]={0,1,2,3},
[500]={0,1},
[502]={0,1,2,3,4,5},
[503]={0,1,2,3,4,5},
[504]={0,1,2,3,4,5},
[506]={0},
[521]={0,1,2,3,4},
[522]={0,1,2,3,4},
[535]={0,1},
[552]={0,1},
[555]={0,1},
[556]={0,1,2},
[557]={0,1},
[571]={0,1},
[581]={0,1,2,3,4},
[583]={0,1},
[595]={0,1},
[600]={0,1},
[601]={0,1,2,3},
[605]={0,1,2,3},
[607]={0,1,2},
}
</syntaxhighlight>

[[Category:ID Lists]]
[[ru:Vehicle variants]]
[[de:Fahrzeug Varianten]]

Template:Garages

2013-10-14T19:03:19Z

Wielebny: juniper hollow garage location

{| class="wikitable" style="width: auto; text-align: center; table-layout: fixed;"
|-
!ID
!Name/Description
!Approximate location (x,y,z)
|-
|'''0'''
|Commerce Region, Loading Bay Garage (Life's a Beach)
|-
|'''1'''
|LSPD Police Impound Garage
|-
|'''2'''
|Mission Garage near El Corona (Los Desperados)
|1873,-2101,14
|-
|'''3'''
|Eight Ball Autos near El Corona
|1836,-1860,14
|-
|'''4'''
|Mission Garage near El Corona (Cesar Vialpando)
|1793,-2141,14
|-
|'''5'''
|Player Garage: El Corona
|-
|'''6'''
|LS Burglary Garage near Playe del Seville
|2743,-2000,14
|-
|'''7'''
|LowRider Tuning Garage in Willowfield
|2645,-2033,14
|-
|'''8'''
|Pay 'n' Spray in Idlewood
|-
|'''9'''
|Player Garage: Johnson House
|2502,-1685,14
|-
|'''10'''
|Transfender in Temple
|1047,-1032,32
|-
|'''11'''
|Pay 'n' Spray in Temple
|1028,-1034,32
|-
|'''12'''
|Pay 'n' Spray in Santa Maria Beach
|484,-1726,11
|-
|'''13'''
|Player Garage: Santa Maria Beach
|318,-1772,5
|-
|'''14'''
|Player Garage: Mulholland
|1351,-619,109
|-
|'''15'''
|Wheel Archangels in Ocean Flats
| -2708,211,4
|-
|'''16'''
|Mission Garage in Ocean Flats (T-Bone Mendez)
|-
|'''17'''
|Player Garage: Hashbury
|-
|'''18'''
|Transfender near Wang Cars in Doherty
|-1924,221,35
|-
|'''19'''
|Pay 'n' Spray near Wang Cars in Doherty
| -1913,263,40
|-
|'''20'''
|SF Burglary Garage, Loading Bay near Doherty
|-
|'''21'''
|Player Garage: Doherty
| -2029,140,29
|-
|'''22'''
|Mission Garage in Doherty Garage
|-
|'''23'''
|Woozie's Mission Garage in Chinatown (Ran Fa Li)
|-
|'''24'''
|Michelle's Pay 'n' Spray in Downtown
|-
|'''25'''
|Player Garage: Calton Heights
|-
|'''26'''
|SFPD Police Impound Garage
|-
|'''27'''
|Pay 'n' Spray in Juniper Hollow
| -2424,1037,50
|-
|'''28'''
|Player Garage: Paradiso
|-
|'''29'''
|LVPD Police Impound Garage
|-
|'''30'''
|Airport Plane Garage in Las Venturas
|1578,1242,11
|-
|'''31'''
|LV Burglary Garage near Camel's Toe
|-
|'''32'''
|Pay 'n' Spray near Royal Casino
|-
|'''33'''
|Transfender in come-a-lot
|-
|'''34'''
|Player Garage: Rockshore West
|-
|'''35'''
|Welding Wedding Bomb-workshop in Emerald Isle
|-
|'''36'''
|Pay 'n' Spray in Redsands East
|-
|'''37'''
|Player Garage: Redsands West
|-
|'''38'''
|Player Garage: Prickle Pine
|-
|'''39'''
|Player Garage: Whitewood Estates
|-
|'''40'''
|Pay 'n' Spray in El Quebrados
| -1411,2599,56
|-
|'''41'''
|Pay 'n' Spray in Fort Carson
|-
|'''42'''
|Player Garage: Fort Carson
|-
|'''43'''
|Player Garage: Verdant Meadows
|-
|'''44'''
|Mission Garage in El Castillo del Diablo (Interdiction)
| -385,2230,42
|-
|'''45'''
|Airport Garage in Verdant Meadows
|-
|'''46'''
|Mission Garage in Angel Pine (Puncture Wounds)
|-
|'''47'''
|Pay 'n' Spray in Dillimore
|-
|'''48'''
|Player Garage: Palomino Creek
|-
|'''49'''
|Player Garage: Dillimore
|}

PlaySound

2013-09-05T11:52:17Z

Wielebny:

__NOTOC__
{{Client function}}
Creates a [[sound]] element and plays it immediately after creation for the local player.<br />
<br />
'''Note:''' The only supported audio formats are MP3, WAV, OGG, RIFF, MOD, XM, IT, S3M and PLS(e.g. Webstream).

==Syntax==
<syntaxhighlight lang="lua">element playSound ( string soundPath, [ bool looped = false ] )</syntaxhighlight>

===Required Arguments===
*'''soundPath:''' The [[filepath]] or URL of the sound file you want to play. (Sound specified by filepath has to be predefined in the [[meta.xml]] file with <file /> tag.)

===Optional Arguments===
{{OptionalArg}}
*'''looped:''' A [[boolean]] representing whether the sound will be looped. To loop the sound, use ''true''. Loop is not available for streaming sounds, only for sound files.

===Returns===
Returns a [[sound]] element if the sound was successfully created, ''false'' otherwise.

==Example==
<syntaxhighlight lang="lua">
function wasted (killer, weapon, bodypart)
local sound = playSound("sounds/wasted.mp3") --Play wasted.mp3 from the sounds folder
setSoundVolume(sound, 0.5) -- set the sound volume to 50%
end

addEventHandler("onClientPlayerWasted", getLocalPlayer(), wasted) --add the event handler
</syntaxhighlight>

==See Also==
{{Client_audio_functions}}
[[AR:playSound]]
[[DE:playSound]]

RemovePedFromVehicle

2013-08-26T19:02:54Z

Wielebny: server -> server&client function

{{Server client function}}
__NOTOC__
This function removes a ped from a vehicle immediately. This works for drivers and passengers. Note that this removes the ped from the vehicle and puts him in the exact position where the command was initiated.

'''Available client side from 1.3.1''' (It will only work with client side vehicles and peds)

==Syntax==
<syntaxhighlight lang="lua">
bool removePedFromVehicle ( ped thePed )
</syntaxhighlight>

===Required Arguments===
*'''thePed:''' The ped you wish to remove from a vehicle

===Returns===
Returns ''true'' if the operation was successful, ''false'' otherwise.

==Example==
Small example to show how to remove a ped from any vehicle it's in.
<syntaxhighlight lang="lua">
function setupForRace ( )
RacerPed = createPed ( 252, 0, 0, 3 ) -- create a ped called "RacerPed".
local RaceVehicle = createVehicle ( 411, 4, 0, 3 ) -- create a vehicle.
warpPedIntoVehicle ( RacerPed, RaceVehicle ) -- warp the ped straight into the vehicle
setTimer(removeThePed, 5000, 1) -- Setup a timer which will remove the ped from the vehicle after 5 seconds.
end
addCommandHandler ( "startrace", setupForRace ) -- add a command to start race

function removeThePed ( )
removePedFromVehicle ( RacerPed ) -- Removes the ped from any vehicle.
end
</syntaxhighlight>

==See Also==
{{Ped functions}}

User:Wielebny

2013-08-21T09:28:18Z

Wielebny: formatting

Also known as W.

== My community scripts ==
* mta-billiard [http://community.mtasa.com/index.php?p=resources&s=details&id=5307 community] [https://github.com/lpiob/mta-billiard github repo]

== My gamemodes ==
* [http://github.com/lpiob/MTA-XyzzyRP MTA-XyzzyRP] - complete, open-sourced, polish RP gamemode, developed originally for lss-rp.pl

User:Wielebny

2013-08-21T09:28:02Z

Wielebny: contributions

Also known as W.

== My community scripts ==
* mta-billiard [http://community.mtasa.com/index.php?p=resources&s=details&id=5307 community] [https://github.com/lpiob/mta-billiard github repo]

== My gamemodes ==
* [github.com/lpiob/MTA-XyzzyRP MTA-XyzzyRP] - complete, open-sourced, polish RP gamemode, developed originally for lss-rp.pl

DxDrawLinedRectangle

2013-08-04T07:14:15Z

Wielebny: fixed few typos

{{Useful Function}}
__NOTOC__
This is a function that will create a rectangle outline with dx lines.

==Syntax==
<syntaxhighlight lang="lua">bool dxDrawLinedRectangle( float x, float y, float width, float height, int color [int width=1, bool postGUI=false ] )</syntaxhighlight>

===Required Arguments===
* '''x:''' An integer representing the absolute start X position of the line, represented by pixels on the screen.
* '''y:''' An integer representing the absolute start Y position of the line, represented by pixels on the screen.
* '''width:''' An float representing the width of the area, drawn in a right direction from the origin.
* '''height:''' An float representing the height of the rectangle, drawn in a downwards direction from the origin.
* '''color:''' the hex color of the rectangle, produced using tocolor or 0xAARRGGBB (AA = alpha, RR = red, GG = green, BB = blue).

==Optional Arguments==
{{OptionalArg}}
* '''width:''' An integer representing how thick the lines will be.
* '''postGUI:''' A bool representing whether the line should be drawn on top of or behind any ingame GUI.

===Returns===
Returns a ''true'' if the operation was successful, ''false'' otherwise.

==Code==
<section name="Clientside script" class="client" show="true">
<syntaxhighlight lang="lua">
function dxDrawLinedRectangle( x, y, width, height, color, _width, postGUI )
local _width = _width or 1
dxDrawLine ( x, y, x+width, y, color, _width, postGUI ) -- Top
dxDrawLine ( x, y, x, y+height, color, _width, postGUI ) -- Left
dxDrawLine ( x, y+height, x+width, y+height, color, _width, postGUI ) -- Bottom
return dxDrawLine ( x+width, y, x+width, y+height, color, _width, postGUI ) -- Right
end</syntaxhighlight>
</section>

==Example==
This draws a green rectangle:
<syntaxhighlight lang="lua">
local sx, sy = guiGetScreenSize ( )
addEventHandler("onClientRender", root,
function()
dxDrawLinedRectangle( 5, 5, sx/2, sy/2, tocolor ( 0, 255, 0, 255 ), 3, true )
end
)
</syntaxhighlight>

Author: xXMADEXx

==See Also==
{{Useful_Functions}}

IsElementWithinColShape

2013-06-24T18:46:35Z

Wielebny:

{{Server client function}}
__NOTOC__
This function is used to determine if an element is within a collision shape. Please note that for legacy reasons, a colshape created on the client does not collide with elements already existing at that location until they first move. Please also note that before 1.0.3, this did not function correctly when moving a colshape.

Please note that this function doesn't verify whether element is in the same dimension and interior, additional checks could be implemented manually if they are needed.

==Syntax==
<syntaxhighlight lang="lua">bool isElementWithinColShape ( element theElement, colshape theShape )</syntaxhighlight>

===Required Arguments===
*'''theElement:''' The [[element]] you're checking.
*'''theShape:''' The [[colshape]] you're checking

===Returns===
Returns ''true'' if the element is within the colshape, ''false'' otherwise

==Example==
This small script is an example of detecting if a player is within a certain defined colshape. This could serve as a base to perform many functions, rather than just an output.
<syntaxhighlight lang="lua">
local circlearea = createColCircle ( 0, 0, 10 )

function ColShapeHit ( thePlayer, matchingDimension )
local detection = isElementWithinColShape ( thePlayer, circlearea )
--A variable called 'detection' stores the result of asking if the player
--who entered a colshape is within the specific colshape called 'circlearea'.
--The result is either true or false.
detection = detection and getElementDimension( thePlayer ) == getElementDimension( circlearea )
--Let's additionally check element dimensions.
if detection then
outputChatBox ( getPlayerName(thePlayer).." is in the 'circle area' col shape" )
end
--if detection was true then the player is in the col shape. Output a
--message to confirm this
end
addEventHandler ( "onColShapeHit", getRootElement(), ColShapeHit )
</syntaxhighlight>

==See Also==
{{element functions}}

Talk:IsElementWithinAColShape

2013-06-24T18:44:32Z

Wielebny: Y U NO USE builtin functions?

I don't consider this example very well written. In case that player element enters the colshape, and then disconnects, the inColShape[player_element] will never be freed, resulting in memory leak.

Besides, this code isn't restart-proof and can't handle more than one colshape.

Also, why not [[IsElementWithinColShape]]? --[[User:Wielebny|Wielebny]] 18:44, 24 June 2013 (UTC)

User talk:MrSecond

2013-02-19T20:16:19Z

Wielebny: note about last edits

http://wiki.multitheftauto.com/index.php?title=Scripting_Introduction&action=history
Your edits have been reverted more than once. Don't replace english pages with your translation - instead create a new page, according to this wiki structure. --[[User:Wielebny|Wielebny]] 20:16, 19 February 2013 (UTC)

Scripting Introduction

2013-02-19T20:14:18Z

Wielebny: undone changes by MrSecond

Resources are a key part of MTA. A resource is essentially a folder or zip file that contains a collection of files, plus a meta file that describes to the server how the resource should be loaded and what files it does contain. A resource can be seen as being partly equivalent to a program running in an operating system - it can be started and stopped, and multiple resources can run at once.

Everything that has to do with scripting happens in resources, what a resource does defines if it is a gamemode, a map or anything else. MTA comes with resources that you can optionally use in your gamemodes, such as maplimits to keep playings within a playing area or deathpickups to create weapon pickups.
{{tip|Your first step to begin Lua scripting should be using an Lua editor. This makes scripting much easier. We recommend [http://notepad-plus.sourceforge.net/uk/site.htm Notepad++] or [http://luaedit.sourceforge.net/ LuaEdit]. There is also an unofficial [[MTASE|MTA Script Editor]] (in work-in-progress state) that you can test out.}}

==Creating a working script==
We will first learn how to make a basic script that lets the player walk around in the city, step by step.
===Where are all the scripts?===
Let's take a look at the script's file structure. Go to your MTA Server folder, and follow the path below:

server/mods/deathmatch/resources/

You will see a lot of .zip files, which are the packaged sample scripts shipped with MTA. Each file is a "resource", and they will all be unzipped and loaded by the server when it starts. To create your own resource, simply make a folder with your preferred name. We'll use "myserver" for this tutorial.

Now you should be under this directory:

server/mods/deathmatch/resources/myserver/

===Identifying your resource===
In order to let the server know what's in the resource, a ''meta.xml'' file must be created to list the resource's content. It must be located in the resource's root directory, which is the "myserver" folder in our case. So create a text file and name it "meta.xml", and open it with notepad.

Enter the following codes in the ''meta.xml'' file:
<syntaxhighlight lang="xml">
<meta>
<info author="YourName" type="gamemode" name="My Server" description="My first MTA server" />
<script src="script.lua" />
</meta>
</syntaxhighlight>
In the ''<info />'' tag, there's a "type" field which indicates that the resource is a ''gamemode'' instead of a regular include or a ''map'', which will be explained later. A gamemode is what you need to make a stand-alone server.

The ''<script />'' tag indicates the script files contained in the resource, which we will create next.
===Creating a simple script===
Note that in the ''<script />'' tag above, the .lua file is not under another directory. Therefore we'll create the file in the same folder as meta.xml. Now you can copy and paste the following code into script.lua:
<syntaxhighlight lang="lua">
local spawnX, spawnY, spawnZ = 1959.55, -1714.46, 10
function joinHandler()
spawnPlayer(source, spawnX, spawnY, spawnZ)
fadeCamera(source, true)
setCameraTarget(source, source)
outputChatBox("Welcome to My Server", source)
end
addEventHandler("onPlayerJoin", getRootElement(), joinHandler)
</syntaxhighlight>
The script will spawn you at the coordinate (x, y, z) specified above, when you join the game. Note that the ''fadeCamera'' function must be used or the screen will be black. Also, in releases after DP2, you need to set the camera target (otherwise all the player will see is blue sky).

The '''source''' variable indicates who triggered the event. Since a player has joined when the code is triggered, you use this variable to look which has joined. So it'll spawn that player instead of everyone or a random person.

If we have a closer look on [[addEventHandler]], you can see 3 things: 'onPlayerJoin', which indicates when it's triggered. getRootElement(), which shows by what/who it can be triggered. (getRootElement() is everything/everyone) And joinHandler, which indicates the function that has to be triggered after the event is triggered. Other details will be explained later in another example, now let's just run the server and try it out!

===Running the script===
To get the server started, simply run the executable under the server/ directory. A list of server stats will be shown first; note the port number, which you'll need when joining the game. Then the server loads all the resources under the mods/deathmatch/resources/ directory, and then "ready to accept connections!"

Before you connect to the server, you must run the gamemode. Type "start myserver" and press Enter. The server will start the gamemode you just created, and will also show any errors and warnings from this point on. Now you can start the MTA client, and "Quick Connect" using the IP address of your server and the port number you saw earlier. If all goes well, after a few seconds your character will be walking on the streets of Los Santos.

Next we'll add a command to your script that players can use to spawn a vehicle beside their position. You may skip it and check out more advanced scripting with the [[Map manager|Map Manager]], which continues this tutorial. Another branch from this tutorial is [[Introduction to Scripting GUI]], you may follow it to see how Graphical User Interface in MTA is drawn and scripted.

==Creating a simple command==
Let's go back to the content of the ''script.lua'' file. As mentioned above, we want to provide a command to create a vehicle beside your current position in the game. Firstly we need to create a function we want to call and a command handler that creates the command the player will be able to enter in the console.

<syntaxhighlight lang="lua">
-- create the function the command handler calls, with the arguments: thePlayer, command, vehicleModel
function createVehicleForPlayer(thePlayer, command, vehicleModel)
-- create a vehicle and stuff
end

-- create a command handler
addCommandHandler("createvehicle", createVehicleForPlayer)
</syntaxhighlight>
''Note: Function names are clickable in code examples on the wiki and linked to the functions' documentation.''

====About command handlers====
The first argument of [[addCommandHandler]] is the name of the command the player will be able to enter, the second argument is the function this will call, in this case ''createVehicleForPlayer''.

If you have already experience in scripting, you will know that you call a function like this:
<syntaxhighlight lang="lua">
functionName(argument1, argument2, argument3, ..)
</syntaxhighlight>
<syntaxhighlight lang="lua">
functionName(thePlayer, commandName, argument3, ..)
</syntaxhighlight>
If we have a closer look on the lower example above, we can see argument1 is thePlayer and argument2 the commandName. thePlayer is simply the one who typed the command, so whatever you call it, the variable will contain the player who activated the command. commandName is simply the command they typed. So if they typed "/greet", this argument will contain "greet". Argument 3 is something extra the player typed, you'll learn it a little bit further in the tutorial. Never forget that the first 2 arguments are standard arguments, but you can name them to anything you want.

We called the [[addCommandHandler]] function this way already and since ''createVehicleForPlayer'' is a function too, it can be called that way as well. But we are using a command handler for that, which calls it in a similiar manner, internally.

For example: Someone types "createvehicle 468" ingame in the console to spawn a Sanchez, the command handler calls the createVehicleForPlayer function, as '''if''' we would have this line of code in the script:
<syntaxhighlight lang="lua">
createVehicleForPlayer(thePlayer,"createvehicle","468") -- thePlayer is the player element of the player who entered the command
</syntaxhighlight>
As we can see, it provides several parameters: the player who called the command, the command he entered and whatever text he had after that, in this case "468" as vehicle id for the Sanchez. The first two parameters are the same with all command handlers, which you can read on the [[addEventHandler]] page. For this fact, you always have to define at least those two parameters to use any after that (for example to process text that was entered after the command, like in our example the vehicle model id).

''Note: You have to add the command handler AFTER you defined the handler function, else it can't find it. The order of execution matters.''

====Writing the function====
In order to fill the function we created, we need to think about what we have to do:
* Get the players position, so we know where to spawn the vehicle (we want it to appear right beside the player)
* Calculate the position we want to spawn the vehicle at (we don't want it to appear in the player)
* Spawn the vehicle
* Check if it has been spawned successfully, or output a message

In order to achieve our goals, we have to use several functions. To find function we need to use, we should visit the [[Scripting Functions|Server Functions List]]. First we need a function to get the players position. Since players are Elements, we first jump to the '''Element functions''' where we find the [[getElementPosition]] function. By clicking on the function name in the list, you get to the function description. There we can see the syntax, what it returns and usually an example. The syntax shows us what arguments we can or have to submit.

For [[getElementPosition]], the syntax is:
<syntaxhighlight lang="lua">
float, float, float getElementPosition ( element theElement )
</syntaxhighlight>

The three ''float'' in front of the function name are the return type. In this case it means the function returns three floating point numbers. (x, y and z) Within the parentheses, you can see what arguments you have to submit. In this case only the element whose position you want to get, which is the player in our example.

<syntaxhighlight lang="lua">
function createVehicleForPlayer(thePlayer, command, vehicleModel)
-- get the position and put it in the x,y,z variables
-- (local means, the variables only exist in the current scope, in this case, the function)
local x,y,z = getElementPosition(thePlayer)
end
</syntaxhighlight>

Next we want to ensure that the vehicle won't spawn directly in the player, so we add a few units to the ''x'' variable, which will make it spawn east from the player.

<syntaxhighlight lang="lua">
function createVehicleForPlayer(thePlayer, command, vehicleModel)
local x,y,z = getElementPosition(thePlayer) -- get the position of the player
x = x + 5 -- add 5 units to the x position
end
</syntaxhighlight>

Now we need another function, one to spawn a vehicle. We once again search for it on the [[Scripting Functions|Server Functions List]], this time - since we are talking about vehicles - in the '''Vehicle functions''' section, where we will choose [[createVehicle]]. In this function's syntax, we only have one return type (which is more common), a vehicle element that points to the vehicle we just created. Also, we see that some arguments are enclosed within [ ] which means that those are optional.

We already have all arguments we need for [[createVehicle]] in our function: The position we just calculated in the ''x,y,z'' variables and the model id that we provided through the command ("createvehicle 468") and can access in the function as ''vehicleModel'' variable.

<syntaxhighlight lang="lua">
function createVehicleForPlayer(thePlayer, command, vehicleModel)
local x,y,z = getElementPosition(thePlayer) -- get the position of the player
x = x + 5 -- add 5 units to the x position
-- create the vehicle and store the returned vehicle element in the ''createdVehicle'' variable
local createdVehicle = createVehicle(tonumber(vehicleModel),x,y,z)
end
</syntaxhighlight>

Of course this code can be improved in many ways, but at least we want to add a check whether the vehicle was created successfully or not. As we can read on the [[createVehicle]] page under '''Returns''', the function returns ''false'' when it was unable to create the vehicle. Thus, we check the value of the ''createVehicle'' variable.

Now we have our complete script:
<syntaxhighlight lang="lua">
function createVehicleForPlayer(thePlayer, command, vehicleModel)
local x,y,z = getElementPosition(thePlayer) -- get the position of the player
x = x + 5 -- add 5 units to the x position
local createdVehicle = createVehicle(tonumber(vehicleModel),x,y,z)
-- check if the return value was ''false''
if (createdVehicle == false) then
-- if so, output a message to the chatbox, but only to this player.
outputChatBox("Failed to create vehicle.",thePlayer)
end
end
addCommandHandler("createvehicle", createVehicleForPlayer)
</syntaxhighlight>

As you can see, we introduced another function with [[outputChatBox]]. By now, you should be able to explore the function's documentation page yourself. For more advanced scripting, please check out the [[Map manager|Map Manager]].

==What you need to know==
You already read some things about resources, command handlers and finding functions in the documentation in the first paragraph, but there is much more to learn. This section will give you a rather short overview over some of these things, while linking to related pages if possible.
===Clientside and Serverside scripts===
You may have already noticed these or similiar terms (Server/Client) somewhere on this wiki, mostly in conjunction with functions. MTA not only supports scripts that run on the server and provide commands (like the one we wrote above) or other features, but also scripts that run on the MTA client the players use to connect to the server. The reason for this is, that some features MTA provides have to be clientside (like a GUI - Graphical User Interface), others should be because they work better and still others are better off to be serverside or just don't work clientside.

Most scripts you will make (gamemodes, maps) will probably be serverside, like the one we wrote in the first section. If you run into something that can't be solved serverside, you will probably have to make it clientside. For a clientside script for example, you would create a ordinary script file (for example called ''client.lua'') and specify it in the meta.xml, like this:
<syntaxhighlight lang="xml">
<script src="client.lua" type="client" />
</syntaxhighlight>
The ''type'' attribute defaults to 'server', so you only need to specify it for clientside scripts. When you do this, the clientside script will be downloaded to the player's computer once he connects to the server. Read more about [[Client side scripts]].

===More complex resources===
The previous section showed briefly how to add clientside scripts to the resource, but there is also much more possible. As mentioned at the very top of this page, resources can be pretty much everything. Their purpose is defined by what they do. Let's have some theoretical resources, by looking at the files it contains, the ''meta.xml'' and what they might do:

====First example - A utility script====
<syntaxhighlight lang="xml">
/admin_commands
/meta.xml
/commands.lua
/client.lua
</syntaxhighlight>
<syntaxhighlight lang="xml">
<meta>
<info author="Someguy" description="admin commands" />
<script src="commands.lua" />
<script src="client.lua" type="client" />
</meta>
</syntaxhighlight>

* The ''commands.lua'' provides some admin commands, like banning a player, muting or something else that can be used to admin the server
* The ''client.lua'' provides a GUI to be able to perform the mentioned actions easily

This example might be running all the time (maybe even auto-started when the server starts) as it's useful during the whole gaming experience and also wont interfere with the gameplay, unless an admin decides to take some action of course.

====Second example - A gamemode====
<syntaxhighlight lang="xml">
/counterstrike
/meta.xml
/counterstrike.lua
/buymenu.lua
</syntaxhighlight>
<syntaxhighlight lang="xml">
<meta>
<info author="Someguy" description="Counterstrike remake" type="gamemode" />
<script src="counterstrike.lua" />
<script src="buymenu.lua" type="client" />
</meta>
</syntaxhighlight>

* The ''counterstrike.lua'' contains similiar to the following features:
** Let players choose their team and spawn them
** Provide them with weapons, targets and instructions (maybe read from a Map, see below)
** Define the game's rules, e.g. when does the round end, what happens when a player dies
** .. and maybe some more
* The ''buymenu.lua'' is a clientside script and creates a menu to buy weapons

This example can be called a gamemode, since it not only intereferes with the gameplay, but actually defines the rules of it. The ''type'' attribute indicates that this example works with the [[Map manager]], yet another resource that was written by the QA Team to manage gamemodes and map loading. It is highly recommended that you base your gamemodes on the techniques it provides.

This also means that the gamemode probably won't run without a map. Gamemodes should always be as generic as possible. An example for a map is stated in the next example.

====Third example - A Map====
<syntaxhighlight lang="xml">
/cs-airport
/meta.xml
/airport.map
/airport.lua
</syntaxhighlight>
<syntaxhighlight lang="xml">
<meta>
<info author="Someguy" description="Counterstrike airport map" type="map" gamemodes="counterstrike" />
<map src="airport.map" />
<script src="airport.lua" />
</meta>
</syntaxhighlight>

* The ''airport.map'' in a XML file that provides information about the map to the gamemode, these may include:
** Where the players should spawn, with what weapons, what teams there are
** What the targets are
** Weather, World Time, Timelimit
** Provide vehicles
* The ''airport.lua'' might contain map-specific features, that may include:
** Opening some door/make something explode when something specific happens
** Create or move some custom objects, or manipulate objects that are created through the .map file
** .. anything else map-specific you can think of

As you can see, the ''type'' attribute changed to 'map', telling the [[Map manager]] that this resource is a map, while the ''gamemodes'' attribute tells it for which gamemodes this map is valid, in this case the gamemode from the above example.
What may come as a surprise is that there is also a script in the Map resource. Of course this is not necessarily needed in a map, but opens a wide range of possibilities for map makers to create their own world within the rules of the gamemode they create it for.

The ''airport.map'' file might look similiar to this:
<syntaxhighlight lang="xml">
<map mode="deathmatch" version="1.0">
<terrorists>
<spawnpoint posX="2332.23" posY="-12232.33" posZ="4.42223" skins="23-40" />
</terrorists>
<counterterrorists>
<spawnpoint posX="2334.23443" posY="-12300.233" posZ="10.2344" skins="40-50" />
</counterterrorists>

<bomb posX="23342.23" posY="" posZ="" />

<vehicle posX="" posY="" posZ="" model="602" />
<vehicle posX="" posY="" posZ="" model="603" />
</map>
</syntaxhighlight>

When a gamemode is started with a map, the map resources is automatically started by the mapmanager and the information it contains can be read by the gamemode resource. When the map changes, the current map resource is stopped and the next map resource is started. For a more in-depth explanation and examples of how map resources are utilized in the main script, please visit the [[Writing Gamemodes]] page.

===Events===
Events are the way MTA tells scripts about things that happen. For example when a player dies, the [[onPlayerWasted]] event is triggered. In order to perform any actions when a player dies, you have to prepare yourself similiar to adding a command handler, as shown in [[#Writing_the_script|the first chapter]].

This example will output a message with the name of the player who died:
<syntaxhighlight lang="lua">
function playerDied(totalAmmo, killer, killerWeapon, bodypart)
outputChatBox(getPlayerName(source).." died!")
end
addEventHandler("onPlayerWasted",getRootElement(),playerDied)
</syntaxhighlight>

Instead of showing what arguments are needed, the documentation page for Events shows what parameters are passed to the handler function, similiar to the way a [[#About_command_handlers|command handler]] does, just that it is different from event to event. Another important point is the ''source'' variable, that exists in handler functions. It doesn't have to be added to the parameter list of the function, but it still exists. It has a different value from event to event, for player events (as in the example above) it is the player element. As another example, you can take a look at the basic spawning player script in the first section to get an idea how ''source'' is used.

==Where to go from here==
You should now be familiar with the most basic aspects of MTA scripting and also a bit with the documentation. The [[Main Page]] provides you with links to more information, Tutorials and References that allow a deeper look into the topics you desire to learn about.
{{note|From here we recommend reading the [[debugging]] tutorial. Good debugging skills are an absolute necessity when you are making scripts. We also recommend you to use the [[predefined variables list]] to help you with certain tasks and make scripting easier and faster.}}
'''See also:'''
* [[Advanced Topics]]
[[ru:Scripting Introduction]]
[[it:Introduzione allo scripting]]
[[es:Introducción a la Programación]]
[[nl:Scripting_introductie]]

User talk:Guix

2013-01-27T15:58:04Z

Wielebny:

I think that your recent contributions are pretty useless. Why do you post functions that do nothing else than return some other functions? Functions like [[getColorBlue]], [[getColorRed]], ... provide no usefulness and should not be used by anyone. They are really bad examples. Please refrain from adding such things. --[[User:Wielebny|Wielebny]] 13:47, 26 January 2013 (UTC)

Just because you have no use for these functions doesn't mean it is useless. Actually I needed them so I made them, it was useful for me so it will be for someone else.
--[[User:Guix|Guix]] 20:41, 26 January 2013 (UTC)

<pre>function a(x) return b(x) end</pre> do you still stand that this is a useful function? It's a programming antipattern and should never be used! --[[User:Wielebny|Wielebny]] 15:56, 27 January 2013 (UTC)

User talk:Guix

2013-01-27T15:56:40Z

Wielebny:

I think that your recent contributions are pretty useless. Why do you post functions that do nothing else than return some other functions? Functions like [[getColorBlue]], [[getColorRed]], ... provide no usefulness and should not be used by anyone. They are really bad examples. Please refrain from adding such things. --[[User:Wielebny|Wielebny]] 13:47, 26 January 2013 (UTC)

Just because you have no use for these functions doesn't mean it is useless. Actually I needed them so I made them, it was useful for me so it will be for someone else.
--[[User:Guix|Guix]] 20:41, 26 January 2013 (UTC)

<pre>function a(x) return b(x) end</pre> do you still stand that this is a useful function? It's a programming pattern that should never be used! --[[User:Wielebny|Wielebny]] 15:56, 27 January 2013 (UTC)

Talk:GetResultingColor

2013-01-26T14:01:33Z

Wielebny: Created page with "This function is wrong. Mixing (0,0,0,255) with (255,255,255,128) would obviously result in (64,64,64,255), not the values that your function returns. --~~~~"

This function is wrong. Mixing (0,0,0,255) with (255,255,255,128) would obviously result in (64,64,64,255), not the values that your function returns. --[[User:Wielebny|Wielebny]] 14:01, 26 January 2013 (UTC)

User talk:Guix

2013-01-26T13:47:58Z

Wielebny: notes about users last contributions

GetAccountName

2012-12-17T21:32:07Z

Wielebny: Revert: I don't think that this was a good example of getAccountName

{{Server function}}
__NOTOC__
This function retrieves the name of an account.

==Syntax==
<syntaxhighlight lang="lua">
string getAccountName ( account theAccount )
</syntaxhighlight>

===Required Arguments===
*'''theAccount:''' The account you wish to get the name of

===Returns===
Returns a string containing the account's name, ''false'' if the account does not exist or an invalid argument was passed to the function.

==Example==
This example announces into the console when a player logs into his account.
<syntaxhighlight lang="lua">
function outputOnLogin ( previous_account, current_account, auto_login ) --when a player logs in
outputConsole(getAccountName(previous_account).." Logged into "..getAccountName(current_account)) -- announce it into the console
end
addEventHandler("onPlayerLogin",getRootElement(),outputOnLogin ) --add an event handler
</syntaxhighlight>

==See Also==
{{Account_functions}}

[[es:getAccountName]]
[[ar:getAccountName]]

OnPlayerLogin

2012-12-15T09:21:05Z

Wielebny: Changed spelling and example code

{{Server event}}
__NOTOC__
This event is triggered when a player logs into their account in-game.

==Parameters==
<syntaxhighlight lang="lua">
account thePreviousAccount, account theCurrentAccount, bool autoLogin
</syntaxhighlight>

*'''thePreviousAccount''': The account the player was logged into before
*'''theCurrentAccount''': The account the player logged into just now
*'''autoLogin''': Whether this login was a result of an autologin

==Source==
The [[event system#Event source|source]] of this event is the player [[element]] that just logged in.

==Cancel effect==
If this event is canceled the player will not be logged in.

==Example==
This example just outputs to the player console that a player in one account logged into an another account:
<syntaxhighlight lang="lua">
-- root = getElementRoot()
addEventHandler("onPlayerLogin", root,
function()
outputChatBox(getPlayerName(source).." has logged in!", root)
end
)
</syntaxhighlight>
This example allows only hardcoded serials to access given accounts.
<syntaxhighlight lang="lua">
Firewall =
{
-- [ 'accountName' ] = 'playerSerial',
[ '3ash8' ] = '9C9F3B55D9D7BB7135FF274D3BF444E4',
[ 'test5' ] = '1D6F76CF8D7193792D13789849498452',
}

addEventHandler ( 'onPlayerLogin', getRootElement ( ),
function ( _, theCurrentAccount )
local Serial = Firewall[getAccountName(theCurrentAccount)]
if ( Serial ) then
if Serial ~= getPlayerSerial ( source ) then
outputChatBox( "Sorry, you're not allowed to access this account.", source)
cancelEvent( true )
end
end
end
)
</syntaxhighlight>
{{See also/Server event|Player events}}

Talk:SetModelHandling

2012-12-03T17:23:53Z

Wielebny:

It works for sure, I use it, here's an working example: http://lss-rp.pl/_/handling82379.lua --[[User:Wielebny|Wielebny]] 17:23, 3 December 2012 (UTC)

Talk:RemoveWorldModel

2012-11-19T17:20:02Z

Wielebny: /* Server-side */

== Server-side ==

I don't see any sense using it rather server-side, because it will never delete the model from new players, in other words, there's no "rather" to it. Both are functioning the same way. [[User:Socialz|Socialz]] 08:24, 19 November 2012 (UTC)

This note was added by function author, Cazomino05. I believe, that he knows what he's doing. --[[User:Wielebny|Wielebny]] 17:20, 19 November 2012 (UTC)

MTASE

2012-11-12T18:03:50Z

Wielebny: Fixed not working links to forum

{| style="float: right; border-collapse: collapse; width: 270px"
|[[Image:MTASElogo_wiki.png]]
|}
{{TOClimit|1}}

==Introduction==
MTA Script Editor is a tool for Lua scripters, or an Integrated Development Environment (IDE). What we are aiming for is to speed up process of developing resources. We thought that process of creating new resources and testing them is, let's be honest... a pain in the ass. Even the management of resources can be a bit annoying sometimes. For instance, if you want to add a new script file to your resource first you have to create the file, then add the path to the file into meta.xml. Worst of all, if you ever forget about adding the file to meta.xml you end up hitting your head against the wall wondering why your script doesn't work.

We wanted to do something that would speed this process up so you could do so much in so little time. Previewing resources such as images and sounds have never been so easy. We are aiming for something along the lines of Visual Studio IDE.

==What we offer==
We have been working on this tool for quite some time but we had a long break due to lack of time and now I'm the only one working on this because education is more important than "having a nice time". Even though I'm working alone we are progressing smoothly in the development.

We have implemented the following features:
*Loading resources
*Easy resource management
*Preview resources such as sound and image files
*Lua and XML syntax highlighting
*On-the-fly (live) Lua syntax checker
*'New resource' wizard - allows you to create new resource with a few clicks
*Switching between resources
*Tabs for script files
*C#'s #region-like grouping code - useful when working in teams and to keep the code clean
*Start/stop server and client
*Join your local server with 1 click
*Switch between game and Script Editor with only one key on the keyboard
*ResourceZipper

==Screenshots==
*'''Main window''' - overall look of the application. On the right you can see a list of MTA functions. You can choose what functions you want to be displayed by changing item in the combo box above it. Are you going to ask what this "silly table" at the bottom of the window is doing? I knew it... It's the syntax checker. As you script the syntax is checked by Lua engine and outputs any errors you've made in the script. It speed up progress because you don't have to go into game and restart the resource to check if you fixed the syntax error. I made a little error on line 1 to show you how it looks:
[[Image:MTASEmainwnd.png]]

*'''New resource wizard''' - create a resource with 5 simple steps (3 steps are optional):
[[Image:MTASEnewreswizard.png]]

*'''Sound player''' - preview sounds by double-clicking sound file in the resource explorer:
[[Image:MTASEsoundplayer.png]]

*'''Image viewer''' - preview images by hovering you cursor over nodes in resource explorer:
[[Image:MTASEimageviewer.png]]

*'''Suggested functions''' - a "window" similar to the one in Visual Studio showing a list of functions. It also shows a tooltip telling you what the function does and its parameters. It also contains all exported functions from every resource. You can add a 3 new attributes to your exported function tag in meta.xml to let Script Editor display descriptive tooltip, like on the screenshot:
**'''retval:''' return type (eg. bool, marker, int, etc.)
**'''params:''' list of parameters
**'''description:''' short description of the function[/list]
[[Image:MTSEsuggestedfuncs.png]]
:(screenshot show an example of exported function that in meta.xml looks like the following:)
<syntaxhighlight lang="lua" lang="xml"><export function="getBankMarkers" retval="table" params="void" description="Returns a table containing all bank markers." /></syntaxhighlight>

*'''Function tooltip''' (available from 0.3) - tooltip showing function description. Moving mouse over function names in the function list (not the suggested functions list)
[[Image:MTASE_func_desc.png‎]]

*'''MTA Server Configuration''' - a window where you can change server's settings. You won't have to open mtaserver.conf and change the server settings, startup resources, adding modules, etc.
[[Image:MTASEserverconfig.png]]

*'''Customize syntax highlighter''' - you can customize many syntax highlighter properties
[[Image:MTASEcustomizesyntax.png]]

*'''Exported functions''' - you can view all exported functions from every resource
[[Image:MTASEfuncs.png]]

==Overview==
As you can see we want to simplify resource development and it seems to look pretty nice but we are still in development. There are some good key features that would attract you as a scripter. While we are still in development we wanted to ask you what you think about this tool and what would you like to see included in the release (do not ask when! we do not know when). Any suggestions? You're welcome to suggest some features and if possible we will do our best to implement it. Just visit [http://forum.multitheftauto.com/viewtopic.php?f=91&t=24834 our MTA forum topic] and post your suggestions.

==Download==

To download the tool, go to [http://forum.multitheftauto.com/viewtopic.php?f=91&t=24834 our thread on the MTA forum]. That thread is updated frequently.

==Requirements==
* To run this application you need to have .NET 2.0 Framework installed.
* You should be able to run it on Windows XP and Vista. Works on Windows 7 too!
* You must have both MTA Client and Server installed.

==FAQ==

===Error/Warning messages at startup===

===Loading irrKlang.NET2.0 library failed to load! This means you will not be able to preview sound files.===
This message appears most likely for Windows XP/Vista '''64bit''' users. It may occur on 32bit OS if that machine doesn't have .NET 2.0 SP1 installed.

There is only 1 known way to solve the problem...: Make sure you have .NET 2.0 SP1 installed, if you don't have it you can download it from [http://www.microsoft.com/Downloads/details.aspx?familyid=79BC3B77-E02C-4AD3-AACF-A7633F706BA5&displaylang=en Microsoft Download Center].

===Error parsing meta.xml===
The reason why this window comes up should be explained in the message. It's most likely that your meta.xml has the following XML declarations:
<syntaxhighlight lang="lua" lang="xml"><?xml version="1.0" encoding="UTF-8" ?>
<?xml version="1.0" encoding="UTF-16" ?></syntaxhighlight>
To solve the problem, simply open the file in WordPad or Notepad (Notepad++ may not solve the problem so use the Windows one), remove that line and save the changes.

.NET 2.0 XML parser doesn't like not "well-formed" XML files, so you may get different messages with different meta.xml files.

'''(THIS HAS BEEN FIXED IN 0.3)'''

===Not able to save file===
If you can't seem to be able to save a file that's probably because you created a new file and the file wasn't added to any resource. This is a bug and will be fixed.

===Problem with horizontal scrollbar===
If you have too long line and you paste some code on it, you may get a problem of not being able to scroll to the left (beginning of the line). This is problem with 3rd party library MTA:SE is using. It is not going to be fixed by its author (he's inactive for over 2 years now) and it's hard for us to find what is causing it. In fact, I was also given a link to another nice syntax highlighter library which I may use in the future. I hope this one doesn't have that problem.
If you encounter this problem there are a few ways to get to the beginning of the line.
* start highlighting this line so that caret moves to the left
* press Home key on your keyboard to move caret to the first character on a line

===Problems with loading some resources (meta.xml)===
If you have problems with some resources not being loaded and you get message your resource will not be shown in Resource Explorer, there are few things you can do to fix it:
- Make sure your files in not encoded in Unicode (you can open it in Windows' Notepad and save the meta.xml with ANSI encoding, don't use Notepad++ for this task since it may not change file encoding at all).
- Make sure you don't have "&" (ampersand) sign anywhere in the file since it may cause meta.xml not being parsed correctly. You should replace ampersands with '''&amp;''' as this is the correct way to represent an ampersand in XML.

Probably both of these can be fixed by changing/adding little piece of code but unfortunately I wasn't able to figure out what. If you know what can cause this parser error in C# .NET XML parser than don't hesitate and share this knowledge with me so I can fix this problem.

'''(THIS HAS BEEN FIXED IN 0.3)'''

==Contact==
You can find us on [http://forum.multitheftauto.com/viewtopic.php?f=91&t=24834 MTA forum]

==Credits==
* [http://forum.mtasa.com/memberlist.php?mode=viewprofile&u=19953 50p] - Programmer & GUI designer.
* [http://forum.mtasa.com/memberlist.php?mode=viewprofile&u=30686 Fenix1042] - Programmer.
* [http://forum.mtasa.com/memberlist.php?mode=viewprofile&u=22437 Cazomino05] - XML files with MTA functions and events.
* MTA Developers - Delivering the amazing GTA:SA Multiplayer MOD that has almost unlimited possibilities...

[[es:MTASE]]

User talk:Tomc0

2012-11-04T08:32:47Z

Wielebny: Created page with "Could you please stop making 'TODO' pages? Create one, when you have a content for it. --~~~~"

Could you please stop making 'TODO' pages? Create one, when you have a content for it. --[[User:Wielebny|Wielebny]] 08:32, 4 November 2012 (UTC)

User talk:John

2012-11-04T08:28:23Z

Wielebny: /* Tutorial for ubuntu server 12.04.1 LTS */

Stealth is a team elimination based gamemode that contains elements from counterstrike, splinter-cell, urban terror, and many original ideas thrown in. Players are encouraged to be stealthy in order to not reveal their location, and work with teammates using strategy and teamwork to win.

=Gameplay=

When a player joins a server, they are prompted to choose a team (either Mercenaries, Spies, or Spectators). You can return the team selection GUI by pressing F3.
When the round begins, players are given a menu to select their weapons and gear. If a player takes too long to select their gear, they will be moved to the spectators team. Once the player hits spawn on the menu, they spawn as either a spy or a mercenary along with their teammates.
The round is over when a team is eliminated or the timer runs out.
The team with the most living players at the end of the round wins.

==Noise==
The noise indication bar appears at the bottom right of the screen (labeled as "dB" for decibels). Whenever a player does something that creates noise, the noise bar will begin to increase. If a player is being noisy, their nametag will become visible to enemies, possibly giving away their location. If a player is being very noisy, a blip will be placed on the radar, giving away their position. In order to move about undetected players should operate as stealthily and methodically as possible.

==Headshots and Limping==
By default, if a player is shot in the head, they will be killed instantly. If they are shot in the leg, they will become crippled, slowing down movement. This can be changed via the [[#Resource_Settings|resource settings]].

==Gadgets==
Players are given several options to choose as their gadget. the default button to activate it is "R". Most gadgets have limited uses. The icon to the left to the noise bar shows which is the current gadget and how many uses it has left (if there is a limit). Available gadgets include:
*'''CLOAK''' Makes the player nearly invisible for a short period of time, allowing them to bypass proximity mines and sneak by players.
*'''RADAR BURST''' Reveals all the living players exact locations at the time of the gadgets activation.
*'''PROX MINE''' A player can crouch to place a mine that explodes when a member of the opposite team gets too close.
*'''GOGGLES''' A player can use the gadget button to toggle between infrared and night vision while holding the goggles in your hand. The goggles counteract any cloaking from other players and reveal locations of proximity mines and cameras while in night vision mode, and player positions while in infrared mode.
*'''CAMERA''' Pressing the gadget button while facing a wall places a camera. Pressing it again while standing away from it will activate the camera view. Use the arrow keys to moves the cameras angle around. Press fire while in Camera view to drop a smoke grenade from the camera. You can also pick up your own camera by approaching it and pressing the gadget button again so you can place the camera elsewhere.
*'''ARMOR''' Gives extra protection, as well as prevents headshots or legshot limping for as long as there is armor left.
*'''SHIELD''' A bulletproof riot shield.

=Resource Settings=
Stealth provides a plethora of options that can be modified via the [[Resource:admin|admin panel]]:
*General Settings:
**Friendly fire: whether or not to enable friendly fire (0 for off, 1 for on, 0 by default)
**Round delay: the delay between rounds, in seconds (10-60 accepted, 15 by default)
**Round length: round length, in minutes (1-1440 accepted, 5 by default)
**Map round limit: maximum number of rounds allowed per map (in a row) (-1-9999 accepted, -1 for infinite rounds, 3 by default)
**Weapon selection timeout: amount of time players have to choose their weapons before being moved to the spectator team, in seconds (1-439 accepted, 30 by default)
**Minimum player count: the minimum number of players needed for a round to start (2-4096 accepted, 2 by default)
**Enable damage effects: <b>TODO</b>
*Ped Stat Settings:
**Use stealth ped stats: whether or not to use stealth's ped stats (0 to ignore ped stats, 1 to apply, 1 by default)
**The rest of the ped stat settings are the skill levels players will spawn with. (0-999 accepted)
*Weapon Ammo Settings:
**All weapons have their own weapon ammo setting - this is the amount of ammo players will spawn with for the given weapon. (0-10000 accepted)

== Tutorial for ubuntu server 12.04.1 LTS ==

Hi John, why did you decide to link to a tutorial hosted somewhere else, not on that wiki? That tutorial should be an article here. Besides, I don't agree with few things in it, especially the paths are wrong, and it describes how to run mta server as root - a thing that should never be done. Please replace that link with in-wiki page. --[[User:Wielebny|Wielebny]] 16:06, 28 October 2012 (UTC)

I'm reverting this change, due to lack of rection from your side. --[[User:Wielebny|Wielebny]] 08:28, 4 November 2012 (UTC)

Server Manual

2012-11-04T08:26:45Z

Wielebny: Undo revision 33846 by John (talk)

__TOC__

==Getting started==
It is much easier than it looks to get a server up and running for your internet or LAN buddies; follow this wiki article and you will hopefully be on your way to hosting your own MTA:SA server in no time!

==Installing the server==
The dedicated server application is available in different flavours depending on the platform of the server.

===Linux installation===
There are different ways of getting a Linux server up and running:
* [http://linux.mtasa.com Getting a precompiled package]
* [[Building MTASA Server on GNU Linux]]

===FreeBSD installation===

You can run MTA:SA under FreeBSD using Linux emulation.
* Enable [http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/linuxemu-lbc-install.html Linux binary compatibility]
* Install following packages or compile them from ports: hs-terminfo, linux_base-f10, linux-f10-sqlite3
* Install [http://linux.mtasa.com/ Linux precompiled package]

===Windows installation===
Installation of the MTA:SA server on Windows is easy as pie.
*Go to the [http://mtasa.com/ download page] and download the installer.
*Once the installer is downloaded, open it.
*Select a folder where you want to install the server.
*Click Install.
*Done!

''For a full explanation of acl.xml (access control list) read: [[Access_Control_List|Access Control List]]''<br/><br/>

==Configuring your server==
The Multi Theft Auto dedicated server is initially configurable through it's console window, from within the game, and from a webbrowser. In order to make use of the two last options, it is necessary to add at least one administrator user to your configuration file.

===General configuration===
All general configuration options can be found in the 'mods/deathmatch/[[Server_mtaserver.conf|'''mtaserver.conf''']]' file and can be opened by any regular text editor.

This file is fairly straightforward; every variable has a [[Server_mtaserver.conf|description of what to do with it and how to change it]].

===Port forwarding===
If you run your server on your own private computer, and you have an router between the internet and your computer. You need to forward 3 ports.

First of all open the file 'mods/deathmatch/[[Server_mtaserver.conf|'''mtaserver.conf''']]' and search for the next lines:
<syntaxhighlight lang="xml">
<serverport>22003</serverport>
<httpport>22005</httpport>
</syntaxhighlight>

The ports are needed to setup the server correctly. We explain later how to set them, but first if you want your server to appear in the server browser there is another port we need, and that is the ASE port.
(quick example for how to turn ASE on or off):
<syntaxhighlight lang="xml">
<ase>1</ase> 
</syntaxhighlight>

Now we going to forward the ports in your router, which is not needed if you already have all ports open, or if you don't have a router with a firewall. If so, skip this part.

If you don't know how port forwarding works in your router, go to the [http://portforward.com/ Port Forward website], find your router model there, and follow the instructions there.

In almost every router you can set the port type: UDP or TCP. The following list will explain which port type is needed for what:

Main server port: UDP

HTTP Port: TCP

ASE Port: UDP (this is needed if you want your server to appear in the server list)

The ASE port is also simple to get:

ASE port = Main server port + 123

So, if you have the main server port set to 22003, then the ASE port will be 22126.

Good luck!

''In the latest version of the server, you can check the port status by using the server command [[Server_Commands#openports|openports]].''

===Client Checks===

The MTA server can be configured to disable the anti-cheat. It can also allow specific or all files to be modified (e.g. carmods.dat), and make sure clients are of a minimum version.

All of these settings are within the file 'mods/deathmatch/[[Server_mtaserver.conf|'''mtaserver.conf''']]'. See the [[Anti-cheat_guide|Anti-cheat guide]] for more details.<br/>

If you want to force a minimum client version, search for the following line:
<syntaxhighlight lang="xml">
<minclientversion></minclientversion>
</syntaxhighlight>
Accepted values look like: 1.1.1-9.02320

===Adding administrators===
It is strongly recommended to add at least one administrator to your server in order to make use of the built-in webserver to easily maintain and configure your server. This administrator will then also be able to log-in from within the game and control the server.

To add an administrator to your server, follow these steps:<br>
<ol>
<li>While the server is running, add a new account by typing '''[[Server_Commands#addaccount|addaccount name password]]''' into the server window. For example, to add user BennyLava you could type:
<div style="margin: 10px 10px 10px 10px;">
<syntaxhighlight lang="xml">
addaccount BennyLava 123password
</syntaxhighlight>
</div>
<div style="margin: 10px 10px 10px 20px;">
''Note: If you do not have access to the server window, and the 'admin' resource is running, you can add the example account by issuing the chatbox command '''/register BennyLava 123password'''''
</div>
<li>The server should display a message confirming the account has been added.
<li>Next, shutdown the server by typing '''shutdown''' into the server window.
<li>Make sure your server is stopped; if your server is still running, the following changes you make will be overwritten</li>
<li>Open the file 'mods/deathmatch/'acl.xml'''' with any text editor</li>
<li>Add the account to the ''Admin'' group by using the XML-syntax below
<div style="padding: 10px">
<syntaxhighlight lang="xml">
<acl>
...
<group name="Admin">
<acl name="Admin"/>
...
<object name="user.BennyLava" />
</group>
...
</acl>
</syntaxhighlight>
</div>

You're done! You can add as many administrators or users as you want this way, take a look at some of the other groups and ACLs for example. The ACL is also accessible through the [[Access_Control_List|Lua scripting engine]].<br>

It is recommended to take a look at the web interface, we will explain how to do this below.
</li>
</ol>
'''Note''': There are also ways to add accounts and edit rights for the server while it's running. "[[Server_Commands#addaccount|addaccount <user> <password>]]" is an internal command to add accounts, but you will have to use the web interface to add these accounts to specific groups/ACLs!<br />

===Using the web interface===
The dedicated server comes with a few Lua [[resources]] that provide a nice little web interface to your server. This can be used to easily maintain your server, as it allows you to add users, start/stop resources, and more.

The web interface resources are enabled by default and are served through the built-in HTTP web server. To make sure the built-in HTTP web server runs on a port you like (22005 by default), follow these steps:
<ol>
<li>Make sure your server is stopped
<li>Open the file 'mods/deathmatch/[[Server_mtaserver.conf|'''mtaserver.conf''']]' with any text editor</li>
<li>Verify that the HTTP server is enabled:
<div style="padding: 10px">
<syntaxhighlight lang="xml">
<httpserver>1</httpserver>
</syntaxhighlight>
</div>
</li>
<li>Change the HTTP server port to your liking:
<div style="padding: 10px">
<syntaxhighlight lang="xml">
<httpport>22005</httpport>
</syntaxhighlight>
</div>
</li>
<li>Save and close the configuration file</li>
<li>Start your server</li>
<li>If you happened to have changed the start-up resources in your configuration file, make sure the following resources are started:

# resourcebrowser
# resourcemanager
# webadmin
# webmap

These are automatically started in the default configuration file, in case you just installed your server.
</li>
<li>Open a web browser (Internet Explorer 6 or 7 are NOT supported; use [http://www.mozilla.com/firefox Mozilla Firefox], [http://www.google.com/chrome Google Chrome], [http://www.apple.com/safari/download Apple Safari], [http://www.opera.com Opera] or others) and navigate to the HTTP server URL: '''http://server:port/'''. For example, If you are running a local server on HTTP port 22005, use '''http://127.0.0.1:22005/'''.</li>
<li>Enter the username and password of the administrator you added in the previous section.</li>
</ol>

<br />
You should now be able to maintain your server from the web interface.

=== Configuring an external web server ===
The built-in web server is also used to serve files that are required by resources running on your server to any player that is connected to your server. For example, if you are running a game script with a scripted graphical user interface, or custom models, these need to be transferred to every connected player in order to function properly. This is done by either the built-in web server, or an external web server (that is usually a bit faster) but needs to be set up separately.

For performance or consistency reasons during the game, you could choose to make use of such an external web server if you have one set up. The external web server needs to be accessible for the public, so any client will be able to download the necessary client-side files in order to join and play on your server.

To enable downloading off an external web server, you should configure the [[Server_mtaserver.conf#httpdownloadurl|httpdownloadurl]] tag in your server configuration:

<div style="padding: 10px">
<syntaxhighlight lang="xml">
<httpdownloadurl>http://www.myserver.tld/directory/here</httpdownloadurl>
</syntaxhighlight></div>

Since all the default resources provided with the dedicated server are zipped, and are normally automatically extracted by the built-in web server, you now have to provide a way for the clients to download the compressed files to their computers. To configure MTA to maintain a copy of only your unzipped client resources, set [[Server_mtaserver.conf#httpautoclientfiles|httpautoclientfiles]] in your server configuration:

<div style="padding: 10px">
<syntaxhighlight lang="xml"><httpautoclientfiles>1</httpautoclientfiles>
</syntaxhighlight></div>

Now when you launch the server, the directory '''<SERVER>/mods/deathmatch/resource-cache/http-client-files''' will contain the correct client files for hosting on an external web server. If the web server is on the same machine, you can simply link the appropriate web server directory to '''http-client-files'''. If the web server is on a separate machine, ensure it has access to '''http-client-files''' via a network path, or maintain a remote copy using synchronization software.

'''Note 1''': Please try to avoid any special characters (e.g. ~, !) in your download URLs.<br />
'''Note 2''': Please do not use a trailing slash in your download URL (e.g. ''hxxp://www.myserver.tld/directory'' rather than ''hxxp://www.myserver.tld/directory/'')

==Starting your server==
Begin by making sure that you have finished all configuration of your server, starting your server is the last stage so everything must be ready!

To start your server double click on MTA Server.exe, make sure you allow it through any firewalls and forward ports where necessary.

==Installing/Updating resources on your server==
Resources can come in two formats, either a ZIP format or just a normal folder with the script files inside it. The MTA:SA server supports both these methods.

# Move or copy the new resource to your <SERVER>\mods\deathmatch\resources folder.
# In the server window type in the command [[Server_Commands#refresh|refresh]], this will re-scan the resources folder and update the live resources where necessary.

==Uninstalling resources==
Resources can easily be removed from your server if you no longer want them.

# Delete the ZIP file or the folder of the resource you wish to uninstall
# In the server window type in the command "refresh" (without the quotes), this will re-scan the resources folder and update the live resources where necessary.

==Administrating your server==
You can start resources by typing the command "start resourcename" in the server console, or stop ones with "stop resourcename".

It's also possible to execute these and other admin commands from the in-game console (which you can bring up with the ` key or F8); for this to work, you first need to log in with the command "[[Server_Commands#login|login username password]]". Additionally, you can press the p key to bring up the admin panel: this is a graphical interface which allows you to easily kick or ban misbehaving players, among others.

For further commands, type [[Server_Commands#help|help]] in a console.

==Starting a map/gamemode==
See the commands section of the documentation for [[Resource:Map manager|mapmanager]] for more information.

==Useful Notes==

# You may also update the resources while in-game as long as you have the correct access levels by typing "refresh" in the clients console or "/refresh" in the chat window. This may cause a second of lag if you have many resources.
# In the above instructions, <SERVER> is the path to your server's main directory. In most cases this is C:\Program Files\MTA San Andreas\server
# You can choose a different config file for the server to use by passing it in the command line after a --config argument, e.g. mtaserver.exe --config anotherconfig.cfg.
# Do not be alarmed by the warning regarding the parsing of the settings.xml file. This happens because your server installation is still clean and unused.

====Need further help?====
Why not pop over to our [http://forum.mtasa.com/ Forums] or join us on [irc://irc.multitheftauto.com/mta IRC] (irc.multitheftauto.com #mta - [http://www.mirc.com mIRC])

[[es:Manual del Servidor]]
[[de:Server Anleitung]]
[[it:Manuale del Server]]
[[nl:Server Manual]]
[[ru:Server Manual]]
[[pl:Server Manual]]

[[Category:Support]]

User talk:John

2012-10-28T16:06:39Z

Wielebny: /* Tutorial for ubuntu server 12.04.1 LTS */ new section

GetVehicleUpgradeSlotName

2012-09-21T08:49:22Z

Wielebny: fixed not working example

__NOTOC__
{{Server client function}}
This function returns the name of an upgrade slot name (e.g. roof, spoiler).

==Syntax==
There are two ways of using this function, the parameter can either be the slot ID (0 to 16) or an upgrade ID (1000 to 1193)
<syntaxhighlight lang="lua">
string getVehicleUpgradeSlotName ( int slot/upgrade )
</syntaxhighlight>

===Required Arguments===
*'''slot/upgrade:''' the slot ID or corresponding upgrade ID of which you want the name.
{{Vehicle Upgrades}}

===Returns===
Returns a ''string'' with the slot name if a valid slot or upgrade ID was given, ''false'' otherwise.

==Example==
<section name="Server" class="server" show="true">
This example prints the name and upgrades on each slot of an entered vehicle to the chat.
<syntaxhighlight lang="lua">
function scriptOnPlayerEnterVehicle ( theVehicle, seat, jacked )
local upgrades = getVehicleUpgrades ( theVehicle )
for _, upgrade in ipairs ( upgrades ) do
outputChatBox ( getVehicleUpgradeSlotName ( upgrade ) .. ": " .. upgrade )
end
end
addEventHandler ( "onPlayerVehicleEnter", getRootElement(), scriptOnPlayerEnterVehicle )
</syntaxhighlight>
</section>

==See Also==
{{Vehicle_functions}}

RestoreWorldModel

2012-09-13T12:38:21Z

Wielebny: I believe that's a better example

__NOTOC__
{{Server client function|New items}}

This function allows restoring of world object,which was removed with [[RemoveWorldModel]].

==Syntax==
<syntaxhighlight lang="lua">
bool restoreWorldModel ( int modelID, float radius, float x, float y, float z [, int iInterior = -1 ] )
</syntaxhighlight>

===Required Arguments===
*'''modelID:''' A whole integer specifying the GTASA object model ID.
*'''radius:''' A floating point number representing the radius that will be eliminated.
*'''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.
{{New items|3.0132|1.3.2|
*'''iInterior:'''
}}

===Returns===
Returns ''true'' if the world object was restored, ''false'' otherwise.

==Requirements==
{{Requirements|1.2.0-9.03618|1.2.0-9.03618|}}

==Example==
Remove every lamp post (object 1226) besides Grove Street.
<syntaxhighlight lang="lua">
removeWorldModel(1226, 4000, 0, 0, 0, -1)
restoreWorldModel(1226, 50, 2489, -1665, 13, -1)

</syntaxhighlight>

==Changelog==
{{ChangelogHeader}}
{{ChangelogItem|1.3.1-9.04636|Added iInterior argument}}

==See Also==
{{Client_world_functions}}

Strona główna

2012-09-13T06:25:03Z

Wielebny: Undo revision 33107 by Sebastian (removal talk)

__NOTOC__
Witaj w polskiej wersji Multi Theft Auto wiki. Znajdziesz tutaj bogactwo informacji na temat użytkowania Multi Theft Auto.

Jest wiele [[How you can help|rzeczy które możesz zrobić]], by pomoc nam w rozwijaniu MTA - stworzyć mapę, gamemod, pomóc w dokumentowaniu funkcji, napisać przykładowy kod, napisać samouczek lub po prostu grać w MTA i raportować błędy, które znajdziesz.

Jeśli masz jakieś pytania bądź problemy związane z pisaniem skryptów, zapytaj nas na [[PL/IRC_Channel|kanale IRC]].
<div style="clear:both;"></div>
{| width="100%" cellspacing="0" cellpadding="0"
| colspan="2" |

|-
| width="50%" style="vertical-align:top;" |
<div style="border: 1px dotted #AAAAAA;padding:4px 8px 8px 8px;margin:10px; background:#fff0ac;">
====Graj====
* Aby zacząć grać w Multi Theft Auto San Andreas, kliknij na ten [http://multitheftauto.googlecode.com/files/mtasa-1.3.exe link]
* [[PL/Client_Manual|Instrukcja ogsługi clienta]] [[Image:Plflag.png|Artykuł w języku polskim]]/[[Image:usen.gif|Artykuł w języku angielskim]]
* [[PL/Server_Manual|Instrukcja obsługi serwera]] [[Image:Plflag.png|Artykuł w języku polskim]]
</div>

<div style="border: 1px dotted #AAAAAA;padding:4px 8px 8px 8px;margin:10px;">
====Dla początkujących====
* [[Known_Issues_-_FAQ|Znane problemy - FAQ]] [[Image:usen.gif|Artykuł w języku angielskim]]
* [[PL/Migracja_z_MTA:Race_do_MTA:SA_1.0.x|Migracja z MTA:Race do MTA:SA 1.0.x]] [[Image:Plflag.png|Artykuł w języku polskim]]
* [[Map_manager|Menadżer map]] [[Image:usen.gif|Artykuł w języku angielskim]]

</div>

<div style="border: 1px dotted #AAAAAA;padding:4px 8px 8px 8px;margin:10px;">

====Pisanie skryptów====

* [[Wstęp do pisania skryptów|Wstęp do pisania skryptów]] [[Image:Plflag.png|Artykuł w języku polskim]]/[[Image:usen.gif|Artykuł w języku angielskim]]
* [[Introduction to Scripting the GUI|Wstęp do pisania skryptów GUI]] [[Image:usen.gif|Artykuł w języku angielskim]]
* [http://robhol.net/guide/basics "The basics of scripting"] [[Image:usen.gif|Artykuł w języku angielskim]]
* [[Debugging|Samouczek debugowania]] [[Image:usen.gif|Artykuł w języku angielskim]] - Jak znaleźć błędy w swoich skryptach
* [[Resources|Wstęp do zasobów (resources)]] [[Image:usen.gif|Artykuł w języku angielskim]]
** [[Resource Web Access|Dostęp WWW do zasobów]] [[Image:usen.gif|Artykuł w języku angielskim]] - Jak pisać strony WWW z wykorzystaniem zasobów
** [[:Category:Resource|Katalog zasobów]] [[Image:usen.gif|Artykuł w języku angielskim]]
** [[PL/Meta.xml|Meta.xml]] [[Image:Plflag.png|Artykuł w języku polskim]]
* [[Writing_Gamemodes|Pisanie gamemodów]] [[Image:usen.gif|Artykuł w języku angielskim]]
* [[Useful_Functions|Przydatne funkcje]] [[Image:usen.gif|Artykuł w języku angielskim]]

</div>

<div style="border: 1px dotted #AAAAAA;padding:4px 8px 8px 8px;margin:10px;">

====Bazy danych====
Ta sekcja opisuje wszystkie możliwości Lua umożliwiane przez MTA bądź zasoby.
* [[PL/Category:Resource|Katalog zasobów]] [[Image:Plflag.png‎|Artykuł w języku polskim]] - Musisz je poznać, aby tworzyć właściwe skrypty
* [[PL/Client side scripts|Skrypty po stronie klienta]] [[Image:Plflag.png‎|Artykuł w języku polskim]]
</div>
<div style="border: 1px dotted #AAAAAA;padding:4px 8px 8px 8px;margin:10px;">

====General Lua Help====
Strony zaprojektowane, by pomóc Ci zrozumieć Lua
*[http://www.lua.org/pil/index.html "Programming in Lua" Manual]
*[http://lua-users.org/wiki/TutorialDirectory Lua Wiki]
*[http://nixstaller.berlios.de/manual/0.2/nixstaller_9.html A general guide to Lua from Nixstaller]
</div>

| width="50%" style="vertical-align:top;" |
<div style="border: 1px dotted #AAAAAA;padding:4px 8px 8px 8px;margin:10px;">

====Map Editor====
*[[PL/Resource:Editor|Instrukcja obsługi]] [[Image:Plflag.png‎|Artykuł w języku polskim]]
*[[Resource:Editor/EDF|Editor Definition Format]] [[Image:usen.gif|Artykuł w języku angielskim]]
*[[Resource:Editor/Plugins|Pluginy]] [[Image:usen.gif|Artykuł w języku angielskim]]
*[[Resource:Editor#FAQ|Najczęściej Zadawane Pytania]] [[Image:usen.gif|Artykuł w języku angielskim]]
</div>

<div style="border: 1px dotted #AAAAAA;padding:4px 8px 8px 8px;margin:10px;">

====Rozwijanie Multi Theft Auto====
* [[Roadmap]] [[Image:usen.gif|Artykuł w języku angielskim]]
* [[Git Coding Guidelines]] [[Image:usen.gif|Artykuł w języku angielskim]]
</div>

<div style="border: 1px dotted #AAAAAA;padding:4px 8px 8px 8px;margin:10px; background:#CCCCFF;">

====Odwołania====
* [[PL/Funkcje po stronie klienta|Funkcje po stronie klienta]] [[Image:Plflag.png‎|Artykuł w języku polskim]]
* [[Client Scripting Events|Zdarzenia po stronie klienta]] [[Image:usen.gif|Artykuł w języku angielskim]]
* [[Server Scripting Functions|Funkcje po stronie serwera]] [[Image:usen.gif|Artykuł w języku angielskim]]
* [[Server Scripting Events|Zdarzenia po stronie serwera]] [[Image:usen.gif|Artykuł w języku angielskim]]

* [[MTA Classes|Klasy MTA]] [[Image:usen.gif|Artykuł w języku angielskim]] - Szczegółowe opisy wszystkich niestandardowych typów MTA
** [[Element|Elementy MTA]] [[Image:usen.gif|Artykuł w języku angielskim]] / [[Element tree|Drzewo elementów]] [[Image:usen.gif|Artykuł w języku angielskim]]
</div>

<div style="border: 1px dotted #AAAAAA;padding:4px 8px 8px 8px;margin:10px;">

====[[Id|Listy ID]]====
*[[Animations|Animacje]]
*[[Character Skins|Skiny Postaci]] [[Image:usen.gif|Artykuł w języku angielskim]]
*[[CJ_Clothes|Ubrania]] [[Image:usen.gif|Artykuł w języku angielskim]]
*[[Garage|Garaże]] [[Image:usen.gif|Artykuł w języku angielskim]]
*[[Interior IDs|Interiory]]
*[[PL/Pociski|Pociski]][[Image:Plflag.png|Artykuł w języku polskim]]
*[[Radar Blips|Punkty na radarze]]
*[[Sounds|Dźwięki]] [[Image:usen.gif|Artykuł w języku angielskim]]
*[[PL/Pojazdy|Pojazdy]][[Image:Plflag.png|Artykuł w języku polskim]]
*[[PL/Kolory Pojazdów|Kolory pojazdów]][[Image:Plflag.png|Artykuł w języku polskim]]
*[[Vehicle Upgrades|Modyfikacje pojazdów]]
*[[PL/Weapons|Bronie]] [[Image:Plflag.png|Artykuł w języku polskim]]/[[Image:usen.gif|Artykuł w języku angielskim]]
*[[PL/Pogoda|Pogoda]][[Image:Plflag.png|Artykuł w języku polskim]]
</div>

|-
| colspan="2" |
|}
{{Languages list|pl}}

Talk:PL/Serwery/

2012-09-13T06:22:12Z

Wielebny: Nobody's against so I'm erasing this page and removing links to it.

Czy ta lista jest nam potrzebna? Przecież to samo jest w server browser, na dodatek to trzeba będzie ręcznie aktualizować. Proponuje usunać ten artykuł. --[[User:Wielebny|Wielebny]] 12:54, 5 September 2012 (UTC)

This list is incomplete and should be considered as server spam, I propose to delete this page. --[[User:Wielebny|Wielebny]] 06:03, 11 September 2012 (UTC)

Nobody's against so I'm erasing this page and removing links to it. --[[User:Wielebny|Wielebny]] 06:22, 13 September 2012 (UTC)

OnClientSoundBeat

2012-09-13T06:19:44Z

Wielebny: fixed 'event will does not work'

{{Client event}}
__NOTOC__
{{New feature|4.0131|1.3.1|
This event is triggered when a '''sound''' beats.
}}
{{Note|This event does not work correctly pre 1.3.1-9-04627}}
==Parameters==
<syntaxhighlight lang="lua">
int theTime
</syntaxhighlight>

*'''theTime''': the time of the beat

==Source==
The [[event system#Event source|source]] of this event is the [[Element/Sound|sound's element]].

==Example==
<syntaxhighlight lang="lua">
-- Not done yet
</syntaxhighlight>

==Requirements==
{{Requirements|n/a|1.3.0-9.04162}}

==See Also==
===Client sound events===
{{Sound_events}}
===Client event functions===
{{Client_event_functions}}

User talk:Sebastian

2012-09-11T06:04:56Z

Wielebny: pasted a reminder to visit talk page of one of user's last edit

Zapoznaj się proszę z dyskusją na stronie http://wiki.multitheftauto.com/wiki/Talk:PL/Serwery/ - dotyczy ona Twoich ostatnich zmian na polskiej częsci tej wiki --[[User:Wielebny|Wielebny]] 06:04, 11 September 2012 (UTC)

Talk:PL/Serwery/

2012-09-11T06:03:39Z

Wielebny: Added english explanation for deletion of this page.

Talk:PL/Serwery/

2012-09-05T12:54:50Z

Wielebny: Created page with "Czy ta lista jest nam potrzebna? Przecież to samo jest w server browser, na dodatek to trzeba będzie ręcznie aktualizować. Proponuje usunać ten artykuł. --~~~~"

Template:Garages

2012-08-29T17:05:53Z

Wielebny: Added locations of some garages

{| class="wikitable" style="width: auto; text-align: center; table-layout: fixed;"
|-
!ID
!Name/Description
!Approximate location (x,y,z)
|-
|'''0'''
|Commerce Region, Loading Bay Garage (Life's a Beach)
|-
|'''1'''
|LSPD Police Impound Garage
|-
|'''2'''
|Mission Garage near El Corona (Los Desperados)
|1873,-2101,14
|-
|'''3'''
|Eight Ball Autos near El Corona
|1836,-1860,14
|-
|'''4'''
|Mission Garage near El Corona (Cesar Vialpando)
|1793,-2141,14
|-
|'''5'''
|Player Garage: El Corona
|-
|'''6'''
|LS Burglary Garage near Playe del Seville
|2743,-2000,14
|-
|'''7'''
|LowRider Tuning Garage in Willowfield
|2645,-2033,14
|-
|'''8'''
|Pay 'n' Spray in Idlewood
|-
|'''9'''
|Player Garage: Johnson House
|2502,-1685,14
|-
|'''10'''
|Transfender in Temple
|1047,-1032,32
|-
|'''11'''
|Pay 'n' Spray in Temple
|1028,-1034,32
|-
|'''12'''
|Pay 'n' Spray in Santa Maria Beach
|484,-1726,11
|-
|'''13'''
|Player Garage: Santa Maria Beach
|318,-1772,5
|-
|'''14'''
|Player Garage: Mulholland
|1351,-619,109
|-
|'''15'''
|Wheel Archangels in Ocean Flats
| -2708,211,4
|-
|'''16'''
|Mission Garage in Ocean Flats (T-Bone Mendez)
|-
|'''17'''
|Player Garage: Hashbury
|-
|'''18'''
|Transfender near Wang Cars in Doherty
|-1924,221,35
|-
|'''19'''
|Pay 'n' Spray near Wang Cars in Doherty
| -1913,263,40
|-
|'''20'''
|SF Burglary Garage, Loading Bay near Doherty
|-
|'''21'''
|Player Garage: Doherty
| -2029,140,29
|-
|'''22'''
|Mission Garage in Doherty Garage
|-
|'''23'''
|Woozie's Mission Garage in Chinatown (Ran Fa Li)
|-
|'''24'''
|Michelle's Pay 'n' Spray in Downtown
|-
|'''25'''
|Player Garage: Calton Heights
|-
|'''26'''
|SFPD Police Impound Garage
|-
|'''27'''
|Pay 'n' Spray in Juniper Hollow
|-
|'''28'''
|Player Garage: Paradiso
|-
|'''29'''
|LVPD Police Impound Garage
|-
|'''30'''
|Airport Plane Garage in Las Venturas
|1578,1242,11
|-
|'''31'''
|LV Burglary Garage near Camel's Toe
|-
|'''32'''
|Pay 'n' Spray near Royal Casino
|-
|'''33'''
|Transfender in come-a-lot
|-
|'''34'''
|Player Garage: Rockshore West
|-
|'''35'''
|Welding Wedding Bomb-workshop in Emerald Isle
|-
|'''36'''
|Pay 'n' Spray in Redsands East
|-
|'''37'''
|Player Garage: Redsands West
|-
|'''38'''
|Player Garage: Prickle Pine
|-
|'''39'''
|Player Garage: Whitewood Estates
|-
|'''40'''
|Pay 'n' Spray in El Quebrados
| -1411,2599,56
|-
|'''41'''
|Pay 'n' Spray in Fort Carson
|-
|'''42'''
|Player Garage: Fort Carson
|-
|'''43'''
|Player Garage: Verdant Meadows
|-
|'''44'''
|Mission Garage in El Castillo del Diablo (Interdiction)
| -385,2230,42
|-
|'''45'''
|Airport Garage in Verdant Meadows
|-
|'''46'''
|Mission Garage in Angel Pine (Puncture Wounds)
|-
|'''47'''
|Pay 'n' Spray in Dillimore
|-
|'''48'''
|Player Garage: Palomino Creek
|-
|'''49'''
|Player Garage: Dillimore
|}

User talk:Arthur Richard

2012-08-21T10:49:25Z

Wielebny: added notice about reverting user edit

I'm reverting your change at http://wiki.multitheftauto.com/index.php?title=Building_MTASA_Server_on_GNU_Linux&curid=5232&diff=32438&oldid=32314 - I don't think that there should be links to binaries not hosted on official mta repositories, besides your package isn't compliant Linux hierarchy standards, as it places data files in /usr/bin. --[[User:Wielebny|Wielebny]] 10:47, 21 August 2012 (UTC)

Building MTASA Server on GNU Linux

2012-08-21T10:48:32Z

Wielebny: Undo revision 32438 by Arthur Richard (talk)

== Preparing your system ==

In order to build the Multi Theft Auto dedicated server, you will have to set up your system with the correct libraries and tools. How these are installed depends on your distribution.

Our network module (net.dll or net.so) is distributed as a precompiled binary library. The file for GNU/Linux can be found inside the lastest Linux nightly from [http://nightly.mtasa.com/ here]. Use the net.so from 1.4 if you are compiling from the trunk, or the net.so from 1.3.x if you are compiling the 1.3.x branch. Be sure the read the top of ''MTA10_Server/version.h'' as it contains directions on how to compile the different build types.

{{Note|This article is only for developers who changed the server code, if you are looking for the precompiled server (for normal server owners). Go to: [http://linux.mtasa.com/ linux.mtasa.com]}}

'''Debian Linux'''

Includes derivative distributions such as Ubuntu.

You will need the necessary build tools, headers and libraries, which are distributed through the following Debian packages (e.g. Debian Lenny):

* '''build-essential:''' contains the necessary tools, headers and libraries to build applications
* '''automake:''' contains the automake tools
* '''libtool:''' contains the libtool software required to build libraries
* '''libcurl3-dev:''' contains the cURL library (version 3 without SSL support)
* '''libpcre3-dev:''' contains the PCRE library (version 3)
* '''libsqlite3-dev:''' contains the SQLite library (version 3)
* '''libreadline5-dev:''' contains the readline library (version 5)
* '''subversion:''' contains the SVN client used to check out our code repository
* '''libncurses5-dev:''' contains software for controlling writing to the console screen
* '''libncursesw5-dev:''' contains support for wide characters
* '''libsparsehash-dev:''' contains support for Google's hash-map '''(So you don't have to compile sparehash!)'''
* '''libmysqlclient-dev:''' contains the MySQL library
To install these packages through apt, use the apt-get install <package list> command as in the following example (execute as root):

<syntaxhighlight lang="lua">apt-get install build-essential automake libtool libcurl4-openssl-dev libpcre3-dev libsqlite3-dev libreadline5-dev subversion libncurses5-dev libncursesw5-dev libsparsehash-dev libmysqlclient-dev</syntaxhighlight>

'''Gentoo Linux'''

You will need the necessary build tools, headers and libraries. Because Gentoo’s portage system is designed to compile any packages on your own system, the necessary build tools will have already been installed. This only leaves you to install the necessary libraries:

* '''sqlite:''' contains the SQLite library
* '''subversion:''' contains the SVN client used to check out our code repository
* '''curl:''' contains the cURL library; to compile with SSL support, apply the net-misc/curl ssl USE flag
To compile and install these packages through emerge, use the emerge -v <package list> command. The -v option shows additional * * information and can be omitted. (If you want to use any USE flags, prepend emerge with USE="use flags here". You can also use the -pv option to verify that you’re using the correct flags.) Refer to the [http://www.gentoo.org/doc/en/handbook/handbook-x86.xml?part=2&chap=1 Gentoo Handbook] or manual for more information on emerge.

Example:

<syntaxhighlight lang="lua">emerge -v subversion sqlite
USE=“net-misc/curl ssl” emerge -v curl
</syntaxhighlight>

'''Fedora'''

You will need these packages to be able to successfully compile a MTA server on Fedora:
* '''glibc-devel:'''
* '''curl-devel:''' contains the cURL library
* '''pcre-devel:''' contains the PCRE library
* '''sqlite3-devel:''' contains the SQLite library
* '''readline-devel:''' contains the readline library
* '''lua-devel:''' contains the Lua libraries
* '''subversion:''' contains the SVN client to check out the source code
To install these packages through yum, use the yum install <package list> command as in the following example (execute as root):

<syntaxhighlight lang="lua">yum install glibc-devel curl-devel pcre-devel sqlite3-devel readline-devel lua-devel subversion</syntaxhighlight>

'''A warning for x64'''

The MTA:SA server currently cannot be properly compiled in 64-bit mode. Instead, you should compile it in 32-bit mode and run it using 32-bit compatibility mode (use the -m32 flag).

== General instructions for {{Current Version|full}} ==

'''Downloading the source.'''

First you need to download the source.

svn checkout <nowiki>http</nowiki>://mtasa-blue.googlecode.com/svn/branches/{{Current Version|full}}/ mtasa-blue
cd mtasa-blue

Then compile it thus:
autoreconf -fiv
export PKG_CONFIG_PATH=/usr/lib32/pkgconfig
./configure LDFLAGS="-m32" CPPFLAGS="-m32" CFLAGS="-m32" CXXFLAGS="-m32" $@
make
make -C MTA10_Server install
make -C Shared/XML install

Get the net.so like this:
wget <nowiki>http</nowiki>://nightly.mtasa.com/?multitheftauto_linux-{{Current Version|full}}-rc-latest -O multitheftauto_linux-{{Current Version|full}}-latest.tar.gz
tar -xzf multitheftauto_linux-{{Current Version|full}}-latest.tar.gz --transform 's:[^/]*:latest_nightly:'
mv latest_nightly/net.so MTA10_Server/output/
rm -rf latest_nightly multitheftauto_linux-{{Current Version|full}}-latest.tar.gz

Copy config files:
cp MTA10_Server/mods/deathmatch/acl.xml MTA10_Server/output/mods/deathmatch/acl.xml
cp MTA10_Server/mods/deathmatch/mtaserver.conf MTA10_Server/output/mods/deathmatch/mtaserver.conf

Get resources:
svn export <nowiki>http</nowiki>://mtasa-resources.googlecode.com/svn/trunk/ MTA10_Server/output/mods/deathmatch/resources

And the server should be ready in MTA10_Server/output

=== '''Troubleshooting''' ===

Any errors during the compilation of json-c can be solved by calling autoreconf -fi from the json-c directory.

If you’re getting any unexpected errors while compiling, please check our [http://bugs.mtasa.com/ Bug tracker] or our [irc://irc.multitheftauto.com/ IRC channel]

== '''Server crashes''' ==

If your Linux server crashes, please obtain a backtrace and post a report on our [http://bugs.mtasa.com/ Bug tracker]

====To obtain a backtrace:====
===Do you have a core dump file in the the MTA server directory?===
It's usually called 'core', and usually over 100MB, and looks something like this:
[[Image:Core.png]]
====If you have a core dump file in the the MTA server directory:====
*Install gdb. To install gdb on Debian, use this command:
apt-get install gdb
*And from the MTA install directory do this command
gdb mta-server -c core
*When gdb launches, do this command to get a backtrace:
bt full
*Save the output
*(To exit gdb, use the quit command)

====If you do not have a core dump file in the the MTA server directory:====
*Install gdb. To install gdb on Debian, use this command:
apt-get install gdb
*And from the MTA server directory start the mta-server like this:
gdb mta-server --eval-command run
*Now wait for a crash. (Ignore weird screen output in the meantime)
*When a crash occurs, do this command to get a backtrace:
bt full
*Save the output
*(To exit gdb, use the quit command)

== '''Server freezes''' ==

If your Linux server freezes, please obtain a backtrace with thread information and post a report on our [http://bugs.mtasa.com/ Bug tracker]

====To obtain a backtrace with thread information:====
*Install gdb. To install gdb on Debian, use this command:
apt-get install gdb
*And from the MTA server directory start the mta-server like this:
gdb mta-server --eval-command run
*Now wait for a freeze. (Ignore weird screen output in the meantime)
*When a freeze occurs, press ctrl-c to start gdb
*Then do this command to get a backtrace:
bt full
*Save the output
*Then do this command to get a thread information:
info threads
*Save the output
*(To exit gdb, use the quit command)

== '''Running on a 64 bit Linux''' ==
* Install 32 bit libs for your distro
If you get a problem with such as "libreadline.so.5: cannot open shared object file: No such file or directory.", it can be solved on Debian by doing this:
<syntaxhighlight lang="lua">
wget http://ftp.uk.debian.org/debian/pool/main/r/readline5/libreadline5_5.2-7_i386.deb
dpkg -X libreadline5_5.2-7_i386.deb temp
cp -d temp/lib/libreadline.so.5* /usr/lib32/
</syntaxhighlight>

[[ru:Building MTASA Server on GNU Linux]]

RU/outputChatBox

2012-08-21T10:39:27Z

Wielebny: Default outputChatBox colors are not 255,255,255 but 231,217,176

{{RU/Server client function}}
{{Note_box|Не рекомендуется выводить в чат информацию, которая самими чатом (разговором) не является. Для целей отображения вспомогательной информации следует использовать возможности GUI}}
__NOTOC__
Эта функция выводит текстовую строку в окно чата. Можно осуществлять вывод как в чат отдельных игроков, так и всех сразу.

Дополнительно можно использовать строки с цветовыми кодами, передавая параметр ''colorCoded'' равным 'true'. Пример:
<syntaxhighlight lang="lua">
outputChatBox ( "#FF0000Hello #00FF00World", getRootElement(), 255, 255, 255, true )
</syntaxhighlight>
Это будет отображено в чате, как: '''<span style='color:red;'>Hello</span> <span style='color:green'>World</span> '''

==Синтаксис==
<section name="Server" class="server" show="true">
<syntaxhighlight lang="lua">bool outputChatBox ( string text [, element visibleTo=getRootElement(), int r=231, int g=217, int b=176, bool colorCoded=false ] )</syntaxhighlight>

==Обязательные аргументы==
*'''text:''' Текстовая строка, которая будет отправлена в окно чата.

==Дополнительные аргументы==
{{RU/OptionalArg}}
*'''visibleTo:''' Задает, кому будет виден чат. Все игроки-потомки этого элемента увидят сообщение. См. [[visibility]].
*'''r:''' Целое число - количество красного компонента в цвете текста (0 - 255, по умолчанию 231).
*'''g:''' Целое число - количество зеленого компонента в цвете текста (0 - 255, по умолчанию 217).
*'''b:''' Целое число - количество синего компонента в цвете текста (0 - 255, по умолчанию 176).
*'''colorCoded:''' Логическая переменная, которая определяет, будут ли использоваться строковые теги вида '#RRGGBB'.
'Примечания':
Если указан один из цветовых компонентов, то обязательно указывать и остальные.
'''visibleTo''' может быть объектом типа Team, тогда текст будет показан всем игрокам этой команды.
Формат #RRGGBB допускает в записи шестнадцатеричных чисел ''только'' заглавные буквы A-F.

</section>
<section name="Client" class="client" show="true">
<syntaxhighlight lang="lua">bool outputChatBox ( string text [, int r=231, int g=217, int b=176, bool colorCoded=false ] )</syntaxhighlight>

==Обязательные аргументы==
*'''text:''' Текстовая строка, которая будет отправлена в окно чата.

==Дополнительные аргументы==
{{RU/OptionalArg}}
*'''r:''' Целое число - количество красного компонента в цвете текста (0 - 255, по умолчанию 231).
*'''g:''' Целое число - количество зеленого компонента в цвете текста (0 - 255, по умолчанию 217).
*'''b:''' Целое число - количество синего компонента в цвете текста (0 - 255, по умолчанию 176).
*'''colorCoded:''' Логическая переменная, которая определяет, будут ли использоваться строковые теги вида '#RRGGBB'.
</section>

==Вывод==
Возвращает ''true'', если сообщение было успешно отправлено. Возвращает ''false'', если были переданы некорректные аргументы.

==Пример==
<section name="Server" class="server" show="true">
'''Пример 1:''' Вывод сообщения всем пользователям.
<syntaxhighlight lang="lua">
x = 5
y = 10
-- Отображает сообщение
outputChatBox ( "I have " .. x .. " apples and " .. y .. " oranges." )
</syntaxhighlight>

'''Пример 2:''' В этом пример происходит вывод простого цветного текста "Красный Белый", где слово "Красный" красного цвета, а "Белый" - белого.
<syntaxhighlight lang="lua">
outputChatBox ( "Красный #FFFFFFБелый", getRootElement(), 255, 0, 0, true )
</syntaxhighlight>

'''Пример 3:''' Этот пример позволяет игрокам писать в чат текстом того же цвета, что и их ник.
<syntaxhighlight lang="lua">
function colouredChat ( message, theType )
if theType == 0 then --если это обычный чат, а не /me или командный
cancelEvent() --останавливаем встроенный в МТА вывод сообщения
message = string.gsub(message, "#%x%x%x%x%x%x", "") --убираем любые шестнадцатеричные метки с помощью функции string.gsub из lua
local r,g,b = getPlayerNametagColor ( source ) --выясняем, какого цвета ник игрока
local chatterName = getPlayerName ( source ) --выясняем имя
--выводим сообщение в чат, при этом ник игрока будет написан его цветом, а остальной текст белым
outputChatBox ( chatterName..":#FFFFFF "..message, getRootElement(), r, g, b, true )
end
end
</syntaxhighlight>

'''Пример 4:''' Пишем сообщение в чат игроку под ником ''someguy''.
<syntaxhighlight lang="lua">
-- Ищем игрока с именем 'someguy'
myPlayer = getPlayerFromNick ( "someguy" )
-- Если игрок с таким именем найден, то ...
if ( myPlayer ~= false ) then
x = 5
y = 10
-- отправляем ему в чат сообщение
outputChatBox ( "I have " .. x .. " apples and " .. y .. " oranges.", myPlayer )
end
</syntaxhighlight>

'''Пример 5:''' Отправляем приветствие игроку, зашедшему на сервер.
<syntaxhighlight lang="lua">
function onJoin()
outputChatBox ("Добро пожаловать на сервер!", source)
end

addEventHandler("onPlayerJoin",getRootElement(),onJoin)
</syntaxhighlight>
</section>

==Смотрите также==
{{Server functions}}
[[cs:outputChatBox]]
[[en:outputChatBox]]

CS/outputChatBox

2012-08-21T10:38:14Z

Wielebny: Default outputChatBox colors are not 255,255,255 but 231,217,176

{{CS/Server client function}}
__NOTOC__
Tato funkce odesle urcity retezec (string) do chatu. Muze byt poslana jednomu hracovi, vsem nebo skupine hracu.

Volitelne tato funkce muze podporovat vice barev v jedne zprave kdyz nastavite argument ''colorCoded'' na ''true'' Toto znamena ze:
<syntaxhighlight lang="lua">
outputChatBox ( "#FF0000Hello #00FF00World", getRootElement(), 255, 255, 255, true )
</syntaxhighlight>
Bude zobrazeno jako: '''<span style='color:red;'>Hello</span> <span style='color:green'>World</span> '''

==Syntax==
<section name="Server" class="server" show="true">
<syntaxhighlight lang="lua">bool outputChatBox ( string text [, element visibleTo=getRootElement(), int r=231, int g=217, int b=176, bool colorCoded=false ] )</syntaxhighlight>

==Povinne argumenty==
*'''text:''' Retezec textu ktery si prejete aby byl odeslan. Ovsem, pokud ma vice jak 128 charakteru, nebude zobrazen v chatu.

==Volitelne argumenty==
*'''visibleTo:''' Toto urcuje komu se dana zprava zobrazi. Zprava bude osdeslana vsem hracum v urcenem prvku. (Napriklad celemu tymu hracu). Defaultne se posila vsem. (getRootElement())
*'''r:''' Mnozstvi cervene barvy v textu. Defaultne 231.
*'''g:''' Mnozstvi zelene barvy v textu. Defaultne 217.
*'''b:''' Mnozstvi modre barvy v textu. Defaultne 176.
*'''colorCoded:''' Hodnota typu boolean ktrea urcuje zda-li '#RRGGBB' tagy budou pouzity pro zmenu barvy textu.
</section>
<section name="Client" class="client" show="true">
<syntaxhighlight lang="lua">bool outputChatBox ( string text [, int r=231, int g=217, int b=176, bool colorCoded=false ] )</syntaxhighlight>

==Povinne argumenty==
*'''text:''' Retezec textu ktery si prejete aby byl odeslan. Ovsem, pokud ma vice jak 128 charakteru, nebude zobrazen v chatu.

==Volitelne argumenty==
*'''r:''' Mnozstvi cervene barvy v textu. Defaultne 231.
*'''g:''' Mnozstvi zelene barvy v textu. Defaultne 217.
*'''b:''' Mnozstvi modre barvy v textu. Defaultne 176.
*'''colorCoded:''' Hodnota typu boolean ktrea urcuje zda-li '#RRGGBB' tagy budou pouzity pro zmenu barvy textu.
</section>

==Vracena hodnota==
Vrati ''true'' pokud byla zprava uspesne odeslana. Vrati ''false'' pokud jste pouzili neplatne argumenty.

==Priklad==
<section name="Server" class="server" show="true">
'''Priklad 1:''' tento priklad zobrazi zpravu vsem hracum a zobrazi hodnoty promennych.
<syntaxhighlight lang="lua">
x = 5
y = 10
outputChatBox ( "Ja mam " .. x .. " jablek a " .. y .. " pomerancu." ) --Zobrazi zpravu jako "Ja mam 5 jablek a 10 pomerancu."
</syntaxhighlight>

'''Priklad 2:''' Tento priklad zobrazi jednoduchou barevnou zpravu, "Cervena Bila", kde 'White' je v bile barve, a 'Cervena' je v cervene barve.
<syntaxhighlight lang="lua">
outputChatBox ( "Cervena #FFFFFFBila", getRootElement(), 255, 0, 0, true )
</syntaxhighlight>

'''Priklad 3:''' Tento priklad odesle zpravu pouze hracovi s nickem ''nekdo''.
<syntaxhighlight lang="lua">
myPlayer = getPlayerFromName ( "nekdo" ) --Najdeme hrace s timto nickem

if ( myPlayer ~= false ) then --Pokud byl hrac nalezen tak..
x = 5
y = 10
-- Zobrazime zpravu
outputChatBox ( "Mam " .. x .. " jablek a " .. y .. " pomerancu.", myPlayer )
end
</syntaxhighlight>

</section>

//'''Poznamka:''' omlouvam se za preklad bez diakritiky. --[[User:Miki785|Miki785]] 16:59, 16 June 2012 (UTC)

==Zhlednete take==
{{Server functions}}
[[category:Cesky]]
[[en:outputChatBox]]
[[ru:outputChatBox]]

OutputChatBox

2012-08-21T06:38:34Z

Wielebny: Default outputChatBoxColors are not 255,255,255 but 231,217,176

{{Server client function}}
{{Note_box|Avoid outputting text to the chatbox that isn't actually chat, as this can be annoying for players. Output information and status messages to the HUD.}}
__NOTOC__
This outputs the specified text string to the chatbox. It can be specified as a message to certain player(s) or all players.

It can optionally allow you to embed color changes into the string by setting the colorCoded boolean to true. This allows:
<syntaxhighlight lang="lua">
outputChatBox ( "#FF0000Hello #00FF00World", getRootElement(), 255, 255, 255, true )
</syntaxhighlight>
This will display as: '''<span style='color:red;'>Hello</span> <span style='color:green'>World</span> '''

==Syntax==
<section name="Server" class="server" show="true">
<syntaxhighlight lang="lua">bool outputChatBox ( string text [, element visibleTo=getRootElement(), int r=231, int g=217, int b=176, bool colorCoded=false ] )</syntaxhighlight>

==Required Arguments==
*'''text:''' The text string that you wish to send to the chat window. If more than 128 characters it will not be showed in chat.

==Optional Arguments==
{{OptionalArg}}
*'''visibleTo:''' This specifies who the chat is visible to. Any players in this element will see the chat message. See [[visibility]].
*'''r:''' The amount of red in the color of the text. Default value is 231.
*'''g:''' The amount of green in the color of the text. Default value is 217.
*'''b:''' The amount of blue in the color of the text. Default value is 176.
*'''colorCoded:''' A boolean value determining whether or not '#RRGGBB' tags should be used.
Note: '''visibleTo''' can also be a Team object, in this case, the text will be visible to all the players of that team. Also the #RRGGBB format must contain capital letters a-f is not acceptable but A-F is.
</section>
<section name="Client" class="client" show="true">
<syntaxhighlight lang="lua">bool outputChatBox ( string text [, int r=231, int g=217, int b=176, bool colorCoded=false ] )</syntaxhighlight>

==Required Arguments==
*'''text:''' The text string that you wish to send to the chat window. If more than 128 characters it will not be showed in chat.

==Optional Arguments==
{{OptionalArg}}
*'''r:''' The amount of red in the color of the text. Default value is 231.
*'''g:''' The amount of green in the color of the text. Default value is 217.
*'''b:''' The amount of blue in the color of the text. Default value is 176.
*'''colorCoded:''' A boolean value determining whether or not '#RRGGBB' tags should be used.
</section>

==Returns==
Returns ''true'' if the message was displayed successfully. Returns ''false'' if invalid arguments are specified.

==Example==
<section name="Server" class="server" show="true">
'''Example 1:''' This example displays a chat message to all users.
<syntaxhighlight lang="lua">
x = 5
y = 10
-- Displays the message
outputChatBox ( "I have " .. x .. " apples and " .. y .. " oranges." )
</syntaxhighlight>

'''Example 2:''' This example outputs a simple colour coded message, "Red White", where the 'White' is in white colour, and 'Red' is in a red colour.
<syntaxhighlight lang="lua">
outputChatBox ( "Red #FFFFFFWhite", getRootElement(), 255, 0, 0, true )
</syntaxhighlight>

'''Example 3:''' This example allows for coloured chat, according to a player's nametag. This makes use of colour coded outputs.
<syntaxhighlight lang="lua">
function colouredChat ( message, theType )
if theType == 0 then --if its normal chat (not /me or teamchat) then
cancelEvent() --prevent MTA from outputting chat
message = string.gsub(message, "#%x%x%x%x%x%x", "") --remove any hex tags in a player's chat to prevent custom colours by using lua's string.gsub
local r,g,b = getPlayerNametagColor ( source ) --get the player's nametag colour
local chatterName = getPlayerName ( source ) --get his name
--output a message with the name as his nametag colour, and the rest in white.
outputChatBox ( chatterName..":#FFFFFF "..message, getRootElement(), r, g, b, true )
end
end
addEventHandler("onPlayerChat", getRootElement(), colouredChat)
</syntaxhighlight>

'''Example 4:''' This example displays a chat message to a single user called ''someguy''.
<syntaxhighlight lang="lua">
-- Find the player element for the player called 'someguy'
myPlayer = getPlayerFromName ( "someguy" )
-- If a player was found called 'someguy' then...
if ( myPlayer ~= false ) then
x = 5
y = 10
-- Display the message
outputChatBox ( "I have " .. x .. " apples and " .. y .. " oranges.", myPlayer )
end
</syntaxhighlight>

'''Example 5:''' These two functions can speed up typing, and display a message when a player Joins.
<syntaxhighlight lang="lua">
local msg_red,msg_green,msg_blue = 255,255,0

function servertalkprivate(message, sendto)
--Talk to one client only
outputChatBox(tostring(message), sendto, msg_red, msg_green, msg_blue, true)
end

function servertalk(message)
--Talk to everyone
servertalkprivate(message, getRootElement())
end

function onJoin()
servertalkprivate("Welcome to My Server", source)
end

addEventHandler("onPlayerJoin",getRootElement(),onJoin)
</syntaxhighlight>
</section>

==See Also==
{{Server functions}}
[[cs:outputChatBox]]
[[ru:outputChatBox]]