Multi Theft Auto: Wiki - User contributions [en]

Changes in 1.6.1

2025-08-26T17:50:27Z

JHXP: Added a redirect to the changelog page for 1.7.

#REDIRECT [[Changes in 1.7]]

MediaWiki:Grouppage-helper

2024-04-05T18:23:41Z

JHXP: Protected "MediaWiki:Grouppage-helper" ([Edit=Allow only administrators] (indefinite) [Move=Allow only administrators] (indefinite))

Multi Theft Auto: Wiki:Helpers

MediaWiki:Grouppage-helper

2024-04-05T18:23:32Z

JHXP: Created page with "Multi Theft Auto: Wiki:Helpers"

Multi Theft Auto: Wiki:Helpers

MediaWiki:Group-helper-member

2024-04-05T18:22:19Z

JHXP: Protected "MediaWiki:Group-helper-member" ([Edit=Allow only administrators] (indefinite) [Move=Allow only administrators] (indefinite))

helper

MediaWiki:Group-helper-member

2024-04-05T18:22:10Z

JHXP: Created page with "helper"

helper

MediaWiki:Group-helper

2024-04-05T18:20:32Z

JHXP: Protected "MediaWiki:Group-helper" ([Edit=Allow only administrators] (indefinite) [Move=Allow only administrators] (indefinite))

Helpers

MediaWiki:Group-helper

2024-04-05T18:20:01Z

JHXP: Created page with "Helpers"

Helpers

ES/Funciones del cliente

2019-09-14T16:10:53Z

JHXP: Original author: Lukio

<pageclass class="client"></pageclass>
{{Adding_Pages_to_Categories_and_Templates}}
Esta página enumera todas las '''client-side''' funciones de secuencias de comandos que se han implementado y están disponibles como funciones nativas del Deathmatch mod. Para solicitar una función o evento, utilice [[Requested Functions and Events]] "Funciones y eventos solicitados"

Para más funciones, comprobar el [[UsefulFunctions|useful functions page]]. "Funciones útiles | página de funciones útiles"
TOC

==Funciones de Audio==
{{Client_audio_functions}}

==Funciones Blip==
{{Client_blip_functions}}

==Funciones del Navegador==
{{CEF_functions}}

==Funciones de la Camara==
{{Client_camera_functions}}

==Ropa y Funciones Corporales==
{{Client_Clothes_and_body_functions}}

==Funciones de Colisión==
{{Client_collision_shape_functions}}

==Funciones del Cursor==
{{Client_cursor_functions}}

==Funciones de Dibujo==
{{Drawing_functions}}

Template:Current Version

2017-10-07T18:51:47Z

JHXP: Updated current version.

{{#ifeq:{{{1|}}}|master|1.5|
{{#ifeq:{{{1|}}}|short|1.5|
{{#ifeq:{{{1|}}}|fullnodots|155|
{{#ifeq:{{{1|}}}|full|1.5.5| 3.0155 }}
}}
}}
}}

PL/Known Issues - FAQ

2017-07-03T16:13:39Z

JHXP: /* Mam GTA San Andreas w wersji Steam. Czy mogę grać w MTA:SA? */

{{Note_box|Przed sprawdzeniem problemu upewnij się, czy wszystko jest [http://wiki.multitheftauto.com/wiki/Up-to-date na bieżąco].}}
Napisz tutaj swoją propozycję Q&A, dotyczącą znanych problemów z MTA:SA i ich rozwiązanie, zwłaszcza prosimy zgłaszać problemy, które są napotykane aktualnie oraz które mogą być spotykane przez użytkowników w ostatecznej wersji.
Zapraszamy również do edytowania gramatyki i poprawiania zdań na mądre.

* [[PL/Resource:Editor#FAQ|Edytor Map FAQ/Znane problemy można znaleźć tutaj.]]<br>
* [[MTA 0.5r2 Known Issues|Znane problemy dotyczące MTA 0.5r2 można znaleźć tutaj .]]

==Klient==

===Ogólne===

====Mam GTA San Andreas w wersji Steam. Czy mogę grać w MTA:SA?====

:Tak, możesz grać w MTA:SA 1.5 i wyższe jeśli posiadasz GTA San Andreas zakupioną (lub zarejestrowaną) na platformie Steam. Wystarczy, że zainstalujesz grę GTASA poprzez Steam, a następnie ściągniesz i zainstalujesz klienta MTA:SA, a niezbędne zmiany wykonają się automatycznie.:

:Poniższy opis dotyczy WYŁĄCZNIE MTA:SA w wersji 1.4 i niższych:
:''GTA:SA w wersji Steam jest obecnie niekompatybilne z MTA:SA. Jednakże, wykonując kilka prostych kroków, wersja Steam może działać bez problemu:''

:''*'''Opcja 1:''' Znajdź '''GTA SA 1.00 No CD'''(Google znajdzie potrzebny plik). Należy uzyskać 1.00 Cracked / NOCD EXE, nie obraz płyty.''

::''*Otwórz plik Winrar'em lub innym narzędziem do archiwizacji, a w nim powinien być gta_sa.exe. Umieść ten plik w twoim katalogu instalacyjnym. Jest to zwykle '''C:\Program Files\Steam\steamapps\common\grand theft auto san andreas'''. Żadne pliki nie muszą być wymieniane w czasie tego procesu.''

:''Procedura ta nie ma wpływu na wersję steam GTA:SA, ale pozwoli to na działanie MTA:SA.''

:''*'''Opcja 2:''' Użyj nieoficjalną [http://forums.steampowered.com/forums/showthread.php?t=1952458 łatkę] obniżającą wersję steam GTA:SA, należy obniżyć wersję do 1.0, a nie do 1.01.''

====Czy MTA:SA jest kompatybilne z GTA San Andreas w wersji 1.01 lub 2.00?====

:Nie. Jednak jest możliwość zmiany wersji na 1.00 - zobacz [https://forum.mtasa.com/viewtopic.php?t=15151 ten temat forum], aby uzyskać instrukcje jak to zrobić.

====Czarny ekran/zawieszony ekran powitalny GTA:SA====

:*'''MTA:SA pokazuje stale czarny ekran lub zawieszony ekran powitalny GTA:SA.'''

:Może to być konieczne, aby podczas / po ekranie powitalnym w GTA:SA trzeba było dać swój wkład w celu pominięcia filmu poprawnie. Spróbuj kliknąć lewy przycisk myszy kilka razy lub naciskając kilka klawiszy.

:*'''MTA:SA pokazuje stale czarny ekran po ekranie powitalnym GTA:SA (ewentualnie z tekstem w prawym dolnym rogu).'''

:Może być to spowodowane brakiem wsparcia dla DirectX lub funkcji karty graficznej w systemie, które są potrzebne do uruchomienia dynamicznie renderowanego menu. To dynamiczne menu jest domyślnie włączone. Można go wyłączyć, otwierając [http://wiki.multitheftauto.com/wiki/Coreconfig.xml coreconfig.xml](głowny folder MTA:SA\katalog MTA) i zmieniając wartość menu_options do 248.

====Zatrzymanie się MTA po ekranie powitalnym====

:*'''Nic się nie dzieje po ekranie powitalnym 'Stop playing with yourself' '''

:Jeśli używasz NVIDIA GeForce, spróbuj wyłączyć nView Desktop Manager przed włączeniem MTA.

:Również spróbować usunąć plik ustawień GTA San Andreas ("gta_sa.set") w folderze "Dokumenty\GTA San Andreas User Files".

:Jeśli to wszystko zawiedzie sprawdź czy twoje oprogramowanie antywirusowe nie blokuje MTA.

====Błąd MTA po ekranie powitalnym====

:*'''MTA wywala po logu 'Stop playing with yourself'. Zarówno tryb pojedynczego gracza jak i MTA:Race działało przedtem dobrze.

:Spróbuj pobrać najnowsze pliki DirectX Runtime ze strony [http://www.microsoft.com/en-us/download/details.aspx?id=35 Microsoft] . Sprawdź również w Menedżerze zadań, czy proces gta_sa.exe nie jest już uruchomiony.

:Jeżeli masz ustawioną niestandardową rozdzielczość (np. 960x720), spróbuj zmienić rozdzielczość na powszechnie obsługiwaną (np. 640 × 480, 800 × 600, 1024 × 768, 1152 × 864, 1280 × 1024) poprzez uruchomienie Grand Theft Auto: San Andreas w trybie pojedynczego gracza, wyznaczając nową rozdzielczość.

:Jeśli jesteś użytkownikiem systemu Windows Vista lub Windows 7, wykonaj następujące czynności:

:*Włącz tryb kompatybilności dla systemu Windows XP SP3 zarówno dla Multi Theft auto.exe jak i gta_sa.exe, ustaw ich poziom uprawnień do "Uruchom ten program jako administrator".

:*Skonfiguruj zapobieganie wykonywaniu danych: Użyj ustawień Włącz funkcję DEP dla wszystkich programów i usług oprócz tych wybranych
. Kliknij dodaj i znajdź "Multi Theft auto.exe" oraz "gta_sa.exe" i dodaj je.

:*Uruchom MTA jako administrator.

===="Pliki danych zostały zmienione"====

:*Komunikat informujący o błędzie "pliki danych San Andreas zostały zmienione"

:Można to naprawić poprzez zainstalowanie tej [http://updatesa.mtasa.com/sa/files/GTASA-data-1.0.4.exe poprawki](aktualnie brak).

Jeśli to nie zadziała, spróbuj ponownie zainstalować GTA San Andreas.

====Błąd po dołączeniu do dowolnego serwera====

:*'''MTA:SA wywala po dołączeniu do dowolnego serwera. Tryb pojedynczego gracza działa dobrze.'''

:Modyfikacje mogą źle wpływać na działanie MTA:SA. Zawsze należy używać czystego GTA:SA do grania w MTA:SA.

====Sterowanie nie działa====

:*'''Moje ustawienia nie wydają się działać tak, jak powinny.'''

:Spróbuj użyć polecenie 'copygtacontrols' w konsoli.

==== Incorrect models ====
:* '''Woman model's breasts look awkward ingame / I'm seeing odd, spider-like shaped player models.'''

:This is caused by the way GTA handles player stats. To fix this, be sure to set both fat and muscles player stats to 0, when you're changing player skin.

==== Niepoprawne działanie drive-by ====
:* '''Drive-by nie działa tak jak powinno'''

:Drive-by jest obsługiwane przez skrypt i może być zależne od załadowanego trybu gry.

==== Unsaved settings ====
:* '''My MTA setting(s) didn't get saved (...) I crashed.'''

:First, configure the MTA the way you want to, then exit the game and launch it again. Settings should get saved. Alternatively, try removing the coreconfig.xml file, then configure it and quit the game.

==== Wsparcie dla pada ====
:* '''MTA nie rozpoznaje mojego pada'''

:Ensure that your controller is the first controller recognised by Windows (MTA will only use the first controller). You can configure your gamepad in options in MTASA's main menu.

:Upewnij się, że twój kontroler jest pierwszym rozpoznanym kontrolerem przez system Windows (MTA używa jedynie pierwszego kontrolera). Możesz skonfigurować swojego pada w opcjach MTA:SA w głównym menu.

==== Free mouselook not working properly ====
:* '''MTA doesnt recognise my mouse'''

:Some people got problems with their mouse in MTA. They can use it in the menu, connect to a server, but they can't use the mouse for free look.
:This problem can be solved by entering a server, click your Win/Windows key at your keyboard once, and then click your mouse.
:If that doesn't work try starting GTA in Singleplayer, go to options > controler setup and set "Configuration" to "Mouse + Keys" instead of "Joypad".

==== Server browser not working ====
:* '''The in-game server browser shows "Loading" but does not come up with any servers'''

:Depending on the type and status of the internet connection you are using, it can take up to a few seconds for the server browser to retrieve all the servers. Please wait a little longer for the results to appear.

:If all else fails, you can logon to [http://www.game-monitor.com/search.php?game=mta GameMonitor], and click the green play icon to play on that server.

==== Invalid serial number ====
:* '''I am getting an 'Invalid serial number' error when trying to launch or play the game'''

:You are running an outdated version of Multi Theft Auto. Head over to the [http://mtasa.com/ main page] and download the latest version of Multi Theft Auto.

==== 'Network module not compatible!' on MTA:SA launch ====
:* '''I am getting 'Network module not compatible!' error message upon launching MTA:SA

:This could mean that your MTA:SA install is incomplete or broken. Reinstall it.

==== 'No such mod installed (deathmatch)' ====
:* '''I am getting a 'No such mod installed (deathmatch)' error message when trying to connect to any server

:'''Option 1:''' Simply re-install MTA. <br>
:'''Option 2:''' Run both gta_sa.exe and Multi Theft Auto.exe with administrator privileges.

==== Nie znaleziono plików D3dx9_**.dll ====
:* '''Kiedy uruchamiam MTA:SA, pojawia się błąd - Nie znaleziono plików D3dx9_**.dll (** = cyfry).

:Oznacza to, że DirectX 9 nie jest zainstalowany, bądź nieaktualny.
:Zainstalować/zaktualizować DirectX możesz ze strony firmy Microsoft - [http://www.microsoft.com/downloads/details.aspx?displaylang=en&FamilyID=2da43d38-db71-4c1b-bc6a-9b6652cd92a3 DirectX End-User Runtime Web Installer].

==== CRC mismatch ====
:* '''When joining a server, the chatbox shows 'CRC mismatch'
:This is a server problem. Tell the owner to look at the server section of this page.

==== 'Error loading netc.dll module! (Error 14001)' on MTA:SA launch ====
:* Full error message:
:''Error loading netc.dll module! (Error 14001: The application has failed to start because its side-by-side configuration is incorrect. Please see the application event log for more detail.)''

:Make sure you have installed Microsoft Visual C++ 2008 regular and SP1 redistributable packages (x86):

:[http://www.microsoft.com/downloads/details.aspx?FamilyID=9b2da534-3e03-4391-8a4d-074b9f2bc1bf&displaylang=en Microsoft Visual C++ 2008 Redistributable package (x86)]

:[http://www.microsoft.com/download/en/details.aspx?id=5582 Microsoft Visual C++ 2008 SP1 Redistributable package (x86)]

==== 'Error 1935. An error occurred during the installation of assembly 'Microsoft.VC90.ATL...' ====
: Download the 'Fix it' helper from here: [http://support.microsoft.com/default.aspx?scid=kb;en-us;946414]

==== Twój antywirus ostrzega Cię o użytkowaniu MTA:SA ====
:* '''Twój antywirus informuje Cię, że MTA:SA bądź jego instalator jest złośliwym oprogramowaniem bądź wirusem.'''
:MTA '''NIE''' zawiera żadnych wirusów, złośliwych oprogramowań, programów szpiegujących, ani żadnej licencji oprogramowania typu "adware". Powinieneś przeinstalować MTA:SA [http://mtasa.com stąd] jeśli wątpisz we właściwość Twojej kopii MTA:SA.

==== Kiedy pobierane są duże mapy, postęp pobierania zatrzymuje się ====
:* '''Kiedy pobierane są duże mapy, postęp pobierania zatrzymuje się, lecz transmisja trwa nadal.'''
:Problem został naprawiony w [http://forum.mtasa.com/viewtopic.php?f=31&t=39555#p402093 MTA:SA 1.3].

=== Windows Vista® / Windows 7-specific ===

==== Crash on connect ====
:* '''I seem to crash whenever I connect to a server just before I go in-game on Vista'''

:This seems to be an issue with the Microsoft DirectX April 2006 SDK Redistributable DLL file (d3dx9_30.dll) when running in compatibility mode. Please make sure that compatibility mode is competely turned off for '''both''' your GTA_SA.exe and Multi Theft Auto.exe executables.

==== Clock manipulation error ====
:* '''I am getting 'Clock manipulation detected!' error message upon launching MTA:SA

:This is caused by incorrect system date/time being set (which could be a result of wrong settings or a faulty battery on the pc's motherboard). Setting time and date again should fix the problem.

:It might also happen if you are using an AMD Athlon 64 X2 processor with some old drivers. Update them at [http://support.amd.com/us/Pages/drivers.aspx AMD's site].

==== Halt on launch ====
:* '''When I launch MTA:SA, nothing happens (GTA_SA.exe is running but not loading up)

:Run MTA:SA with Administrator privileges. To do this, right click on the installer executable, choose 'Properties', go into 'Compatibility' tab and tick the check box on the last field and try again.

==== General GTA problems ====
:* '''I have unexplainable GTA problems or crashes'''

:Make sure your computer as well as your GTA install meet the [[Deathmatch_Client_Manual#System_requirements|minimum requirements]] and that you are not running in any 98/2000/XP/2003 compatibility modes.

:Also try the solutions from these pages:
:* http://www.gtaforums.com/index.php?showtopic=273549&view=findpost&p=4537502
:* http://pullmonkey.com/2007/4/30/how-i-got-gta-san-andreas-to-work-with-a-crappy-os-vista

==== Performance Issues Sandy Bridge / Second Generation Intel Core ====
:* '''Slow MTA performance on Sandy Bridge Processors while other games and San Andreas Singleplayer run fine.'''
:There seems to be a issue in combination with the Windows power profile running in power saving mode, you can solve this issue by changing the power profile to high performance when playing MTA:SA.
:* Topic about this issue: [http://forum.mtasa.com/viewtopic.php?f=104&t=31745 Sandy Bridge performance issues?]

==Serwer==
===Ogólne===
====Fatal error 3====
:*'''Dostaję Fatal error 3 ilekroć połączę się z serwerem.'''
:Ten błąd zdarza się, gdy serwer próbuje się połączyć i nie jest w stanie dostarczyć wymaganych plików do pobrania bo nie ma włączonego pobierania http. Należy ustawić '''httpdownload''' w konfiguracji na '''1'''.
====Download error 9: Error downloading requested files====
:*'''Dostaję Download error 9: Error downloading requested files, kiedy łączę się ze swoim serwerem.
: Ten błąd zdarza się, gdy serwer próbuje się połączyć, aby pobrać pliki. Powoduje to błąd HTTP 404(Nie znaleziono) i błąd u ciebie.
:*Jeśli korzystasz z wbudowanego serwera ('''httpserver''' jest ustawiony na '''1''' i '''httpdownloadurl''' jest pusty), upewnij się, że serwer HTTP jest dostępny (można sprawdzić dostęp za pomocą przeglądarki) dla każdego.
:*Po skonfigurowaniu zewnętrznego serwera WWW('''httpdownloadurl''' jest ustawiony na niestandardowy adres URL), upewnij się, że HTTP jest dostępny i upewnij się, że przeczytałeś [http://wiki.multitheftauto.com/wiki/Deathmatch_Server_Manual#Configuring_an_external_web_server konfigurowanie zewnętrznego serwera WWW].
====CRC mismatch====
:*'''Kiedy klient dołączy do mojego serwera, jego ChatBox pokazuje "CRC mismatch"'''
:CRC mismatch występuje, gdy:
:*Pliki serwerowe zostały zmienione, ale zasób nie został ponownie uruchomiony/odświeżony.
:*Zewnętrzny serwer HTTP jest używany, a pliki nie są zsynchronizowane.
====Brakujące konta====
:Plik ''accounts.xml'' nie jest używany od 1.0.4, został zastąpiony plikiem o nazwie ''internal.db''. Aby zapewnić, że informacje starego konta będą migrowane:
:*Zatrzymaj serwer
:*Upewnij się, że twój stary ''accounts.xml'' jest poprawny.
:*Usuń ''internal.db''
:*Uruchom serwer
====Brakujące zasoby====
:Od 1.0.4, nazwy zasobów nie mogą zawierać kropek.
====Download error 28====
:Spróbuj wyłączyć aplikacje antywirusowe lub zapory. Jeśli tak to działa, spróbuj dodać wyjątek do zapory, aby umożliwić połączenie się twojego portu http.
====Znikające konto====
:Informacje o koncie (lub czegokolwiek innego) nie są poprawnie zapisywane, może być to spowodowane uszkodzeniem bazy danych. Od wersji 2836, serwer sprawdza integralność plików baz danych SQLite na starcie. Jeśli zgłasza błąd bazy danych, przeczytaj [http://wiki.multitheftauto.com/wiki/How_to_repair_the_database_files jak naprawić pliki bazy danych].
:Jeśli używasz starszej wersji i masz kłopoty, takie jak znikanie konta, należy uaktualnić serwer do [http://nightly.multitheftauto.com/ ostatniej wersji].
====Problemy związane z Windows'em====
: Nie zgłaszano problemów w 1.3.5.
====Problemy związane z Linux'em====
====Domyślnie nohup tworzy nieskończenie wielki nohup.out====
:Tymczasowe rozwiązanie to wyłączyć plik nohup: 'nohup ./mta_server > /dev/null &'

Template:Current Version

2017-04-22T03:45:45Z

JHXP: Updated current version.

{{#ifeq:{{{1|}}}|master|1.5|
{{#ifeq:{{{1|}}}|short|1.5|
{{#ifeq:{{{1|}}}|fullnodots|154|
{{#ifeq:{{{1|}}}|full|1.5.4| 3.0154 }}
}}
}}
}}

Category:Pages with broken file links

2017-01-01T18:58:53Z

JHXP: Removed Vandalism

Strona główna

2017-01-01T18:56:05Z

JHXP: Removed Vandalism

{| width="100%" cellspacing="0" cellpadding="0"
| colspan="2" |
<div style="/*border: 1px solid #D8D8D8;*/ padding-left: 15px; padding-right: 15px; height: 100%;">
[[File:Mtalogo.png|left|100px|link=http://wiki.multitheftauto.com/]]'''Witaj na polskiej wiki [[PL/Multi Theft Auto|Multi Theft Auto]].''' Znajdziesz tutaj wiele informacji na temat korzystania z Multi Theft Auto.

Jest wiele [[PL/How you can help|rzeczy które możesz zrobić]], aby pomóc nam w rozwijaniu MTA - stworzyć mapę, tryb gry, pomóc w dokumentowaniu funkcji, napisać przykładowy kod, napisać poradnik lub po prostu grać w MTA i zgłaszać 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]].
<br/><br/>[ Stop playing with yourself ]
</div>
|}
{| width="100%" cellspacing="0" cellpadding="0"
| colspan="2" |
|-
|width="50%" style="vertical-align:top;" |<div style="border: 1px solid #D8D8D8; padding:4px 8px 8px 8px; margin:10px; background: #FFFCF2;">
<div style="float:right; width: 32px;">[[File:Input-gaming.png‎|link=]]</div>
<h3>Graj</h3>
<div style="background: #FFEEAA; border: 1px solid #FFCD19;">
[[File:Go-down.png|link=http://mtasa.com/]] ''' [http://mtasa.com/ Pobierz Multi Theft Auto: San Andreas {{Current Version|full}}]'''</div>
* [[PL/Where to buy GTASA|Gdzie kupić GTASA]] [[Image:Plflag.png|Artykuł w języku polskim]]
* [[PL/Polish_MTA_version|Polska wersja MTA:SA]] [[Image:Plflag.png|Artykuł w języku polskim]]
* [[PL/Client Manual|Obsługa klienta]] [[Image:Plflag.png|Artykuł w języku polskim]]

* [[PL/Changes_in_{{padleft:|5|{{Current Version|full}}}}| Zmiany w {{padleft:|5|{{Current Version|full}}}}]] [[Image:Plflag.png|Artykuł w języku polskim]]
* [[PL/Known_Issues_-_FAQ|Znane problemy]] [[Image:Plflag.png|Artykuł w języku polskim]]/[[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 {{padleft:|3|{{Current Version|full}}}}]] [[Image:Plflag.png|Artykuł w języku polskim]]
* [[PL/Server Manual|Obsługa serwera]] [[Image:Plflag.png|Artykuł w języku polskim]]
* [[Map manager|Menadżer map]] [[Image:usen.gif|Artykuł w języku angielskim]]

<h3>Edytor map</h3>
*[[PL/Resource:Editor|Instrukcja]] [[Image:Plflag.png|Artykuł w języku polskim]]
*[[PL/Resource:Editor/EDF|Edytor Właściwości Mapy]] [[Image:Plflag.png|Artykuł w języku polskim]]/[[Image:usen.gif|Artykuł w języku angielskim]]
*[[Resource:Editor/Plugins|Pluginy]] [[Image:usen.gif|Artykuł w języku angielskim]]
*[[PL/Resource:Editor#FAQ|Najczęściej zadawane pytania]] [[Image:Plflag.png|Artykuł w języku polskim]]
</div>
<div style="border: 1px solid #D8D8D8; padding:4px 8px 8px 8px; margin:10px;">
<div style="float:right; width: 32px;">[[File:Package-x-generic.png‎|link=]]</div>
<h3>Bazy danych</h3>
Ta sekcja opisuje wszystkie możliwości Lua umożliwiane przez MTA lub zasoby.
* [[PL/Category:Resource|Katalog zasobów]] - 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]]
* [[Modules|Moduły]] [[Image:usen.gif|Artykuł w języku angielskim]]
</div>

<div style="border: 1px solid #D8D8D8; padding:4px 8px 8px 8px; margin:10px;">
<div style="float:right; width: 32px;">[[File:Applications-development.png‎‎‎|link=]]</div>
<h3>Rozwijanie Multi Theft Auto</h3>
[[File:Go-down.png|link=http://nightly.mtasa.com/]] [http://nightly.mtasa.com/ Nightly builds]
* [[Compiling_MTASA|Kompilacja MTASA na Windows]] [[Image:usen.gif|Artykuł w języku angielskim]]
* [[Building_MTASA_Server_on_GNU_Linux|Kompilacja MTASA na GNU/Linux]] [[Image:usen.gif|Artykuł w języku angielskim]]
* [[Coding guidelines|Wytyczne dot. pisania kodu]] [[Image:usen.gif|Artykuł w języku angielskim]]
* [https://github.com/multitheftauto/mtasa-blue Repozytorium Github]
* [[Roadmap]] [[Image:usen.gif|Artykuł w języku angielskim]]
* [http://bugs.mtasa.com/ Bugtracker]
* [[Branches|Branże]] [[Image:usen.gif|Artykuł w języku angielskim]]
</div>
<div style="border: 1px solid #D8D8D8; padding:4px 8px 8px 8px; margin:10px;">
<div style="float:right; width: 32px;">[[File:Applications-office.png|link=]]</div>
<h3>Polskie Wiki - jak możesz pomóc?</h3>
* Pomóż tłumaczyć hasła, przy których jest angielska flaga
* Twórz hasła, które istnieją w angielskiej wiki, a których u nas brakuje
** Staraj się, aby nowe artykuły miały takie same nazwy (angielskie), a jedynie poprzedzane były przedrostkiem PL/ - przykład: [[PL/Character_Skins]]
* Zwołaj znajomych, informuj na forach, niech inni dowiedzą się o takiej możliwości!
* Jeśli nie masz pomysłu na edycję, wykonaj coś z [[PL/Todo|tej listy]]. Możesz ją także rozbudować.
</div>

<div style="border: 1px solid #D8D8D8; padding:4px 8px 8px 8px; margin:10px;">
<div style="float:right; width: 32px;">[[File:Internet-group-chat.png‎|link=]]</div>
<h3>Społeczność</h3>
* [http://forum.multitheftauto.com/ Forum]
* IRC: [irc://irc.multitheftauto.com/mta irc.multitheftauto.com #mta]
* [http://community.mtasa.com/ MTA Community] - dodaj lub pobierz skrypty
* [http://twitter.com/#!/MTAQA/ Twitter] - [http://www.youtube.com/user/MTAQA Youtube] - [http://plus.google.com/102014133442331779727/ Google+] - [http://www.moddb.com/mods/multi-theft-auto-san-andreas ModDB]
</div>

| width="50%" style="vertical-align:top;" |

<div style="border: 1px solid #D8D8D8; padding:4px 8px 8px 8px; margin:10px;">
<div style="float:right; width: 32px;">[[File:Accessories-text-editor.png|link=]]</div>
<h3>Skryptowanie</h3>
* [[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]]
* [[Debugging|Poradnik debugowania]] [[Image:usen.gif|Artykuł w języku angielskim]] - Jak znaleźć błędy w swoich skryptach
* [[Resources|Wstęp do zasobów]] [[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]] - każdy zasób jest definiowany przez plik meta
** [[ACL]] [[Image:usen.gif|Artykuł w języku angielskim]] - Access Control List, który jest niezbędny, aby skrypty działały
* [[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]]
Linki na fora
* [https://forum.mtasa.com/forum/71-scripting/ Forum na temat skryptowania]
* [https://forum.mtasa.com/forum/123-tutorials/ Forum z poradnikami do skryptowania]
* [https://forum.mtasa.com/topic/24702-mtasa-wiki-offline-copies-online-mirrors/ Kopie Wiki]
<div style="float:right; width: 32px;">[[File:start-here.png|link=]]</div>
<h3>Pomoc dotycząca LUA</h3>
Strony zaprojektowane, by pomóc Ci zrozumieć język LUA.
*[http://www.lua.org/pil/index.html "Programming in Lua" Manual]
**[http://www.lua.org/manual/5.1/#index Internal Lua functions reference]
*[http://lua-users.org/wiki/TutorialDirectory Lua Wiki]
*[http://nixstaller.sourceforge.net/manual/0.5.1/nixstaller_10.html A general guide to Lua from Nixstaller]
</div>

<div style="border: 1px solid #D8D8D8; padding:4px 8px 8px 8px; margin:10px; background:#F2F2FF;">
<div style="float:right; width: 32px;">[[File:Preferences-system.png|link=]]</div>
<h3>Odwołania</h3>
* [[PL/Funkcje po stronie klienta|Funkcje po stronie klienta]] [[Image:Plflag.png|Artykuł w języku polskim]]
* [[PL/Client Scripting Events|Zdarzenia po stronie klienta]] [[Image:Plflag.png|Artykuł w języku polskim]]
* [[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]]

* [[PL/MTA Classes|Klasy MTA]] [[Image:Plflag.png|Artykuł w języku polskim]]/[[Image:usen.gif|Artykuł w języku angielskim]] -- Szczegółowe opisy wszystkich 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 solid #D8D8D8; padding:4px 8px 8px 8px; margin:10px;">
<div style="float:right; width: 32px;">[[File:System-file-manager.png|link=]]</div>
<h3>[[PL/Id|Listy ID]]</h3>
*[[PL/Animations|Animacje]] [[Image:Plflag.png|Artykuł w języku polskim]]
*[[PL/Character Skins|Skiny postaci]] [[Image:Plflag.png|Artykuł w języku polskim]]
*[[PL/CJ_Clothes|Ubrania]] [[Image:Plflag.png|Artykuł w języku polskim]]
*[[PL/Garage|Garaże]] [[Image:Plflag.png|Artykuł w języku polskim]]
*[[PL/Interior IDs|Interiory]] [[Image:Plflag.png|Artykuł w języku polskim]]
*[[PL/Material IDs|Materiały]] [[Image:Plflag.png|Artykuł w języku polskim]]
*[[PL/Projectiles|Pociski]] [[Image:Plflag.png|Artykuł w języku polskim]]
*[[PL/Radar Blips|Znaczniki]] [[Image:Plflag.png|Artykuł w języku polskim]]
*[[PL/Sounds|Dźwięki]] [[Image:Plflag.png|Artykuł w języku polskim]]
*[[PL/Vehicle IDs|Pojazdy]] [[Image:Plflag.png|Artykuł w języku polskim]]
*[[PL/Vehicle Colors|Kolory pojazdów]] [[Image:Plflag.png|Artykuł w języku polskim]]
*[[PL/Vehicle Upgrades|Modyfikacje pojazdów]] [[Image:Plflag.png|Artykuł w języku polskim]]
*[[Vehicle variants|Warianty pojazdów]] [[Image:usen.gif|Artykuł w języku angielskim]]
*[[PL/Vehicle component manipulation|Manipulowanie komponentami pojazdów]] [[Image:Plflag.png|Artykuł w języku polskim]]
*[[PL/Weapons|Bronie]] [[Image:Plflag.png|Artykuł w języku polskim]]
*[[PL/Weather|Pogoda]] [[Image:Plflag.png|Artykuł w języku polskim]]/[[Image:usen.gif|Artykuł w języku angielskim]]
</div>
<div style="padding:4px 8px 8px 8px; margin:10px;">
[[File:Osi symbol.png|75px|link=http://opensource.org/|left]]
'''Multi Theft Auto''' jest '''Otwartym Oprogramowaniem'''.
<br/>To znaczy, że każdy może pomóc w byciu Multi Theft Auto lepszym!
</div>
|-
| colspan="2" |
|}
{| width="100%" cellspacing="0" cellpadding="0"
| colspan="2" |
<div style="padding-left: 15px; padding-right: 15px;" class="plainlinks">
[[File:MTALogo_8ball.png|left|85px|link=Archive]]
<ul style="list-style: none; width: 200px; float: left;">
<li>'''O [[PL/Multi Theft Auto|Multi Theft Auto]]'''</li>
<li>[[PL/Archive|Archiwum]]</li>
<li>[[Press Coverage|MTA w mediach]]</li>
<li>[http://code.google.com/p/mtasa-blue/people/list Developerzy]</li>
</ul>
<ul style="list-style: none; width: 200px; float: left;">
<li>'''Multi Theft Auto 0.5'''</li>
<li>[[PL/Archive#Multi_Theft_Auto_0.5|Pobierz]]</li>
<li>[[MTA 0.5r2 Known Issues|Zauważone problemy]]</li>
</ul>
<ul style="list-style: none; width: 200px; float: left;">
<li>'''Statystyki Wiki'''</li>
<li>{{NUMBEROFARTICLES}} artykuły</li>
<li>{{NUMBEROFPAGES}} strony</li>
<li>{{NUMBEROFFILES}} pliki</li>
</ul>
<ul style="list-style: none; width: 240px; float: left;">
<li>{{NUMBEROFEDITS}} edycji</li>
<li>{{NUMBEROFADMINS}} administratorów</li>
<li>{{NUMBEROFUSERS}} zarejestrowanych użytkowników</li>
<li>{{NUMBEROFACTIVEUSERS}} aktywnych użytkowników</li>
</ul>
</div>
|}

__NOTOC__
__NOEDITSECTION__
{{Languages list|pl}}

Press Coverage

2017-01-01T18:44:45Z

JHXP: Reverted edits by Marcin778 (talk) to last revision by JHXP

{{Needs Checking|Please fix the dead links and/or re-upload the files.}}

The following is a list of press coverage during MTA's history, it may not be full and only contains the sources we are aware of.

=Written press=

* Power Unlimited | March 2003 - [http://files.mtasa.com/media/Power_Unlimited-2003_Mar.jpg Page 1], [http://files.mtasa.com/media/Power_Unlimited-2003_Mar-Translation.txt Translation]
* PC Gamer | May 2003 - [http://files.mtasa.com/media/PC_Gamer-2003_May.jpg Page 1]
* Hyper | September 2003 - [http://files.mtasa.com/media/Hyper-2003_Sep-AU.jpg Page 1], [http://files.mtasa.com/media/Hyper-2003_Sep-AU-Translation.txt Translation]
* Igromania | September 2003 [http://files.mtasa.com/media/Igromania-2003_Sep_1-RU.jpg Page 1], [http://files.mtasa.com/media/Igromania-2003_Sep_2-RU.jpg Page 2], [http://files.mtasa.com/media/Igromania-2003_Sep-RU-Translation.txt Translation], [http://www.igromania.ru/articles/46216/Multi_Theft_Auto_Setevoi_bespredel_Osnovy_igry_v_GTA_3_po_ceti_i_cherez_internet.htm On-line copy]
* Computer Games | October 2003 - [http://files.mtasa.com/media/Computer_Games-2003_Oct.jpg Page 1]
* PC Gameplay | December 2003 - [http://files.mtasa.com/media/PC_Gameplay-2003_Dec.jpg Page 1], [http://files.mtasa.com/media/PC_Gameplay-2003_Dec-Translation.txt Translation]
* PC Gamer | April 2004 - [http://files.mtasa.com/media/1.0/Images/pcgamer.jpg Page 1]
* GamePro | June 2005 - [http://files.mtasa.com/media/GamePro_June_2005_4.jpg Page 1]
* PC Zone | March 2006 - [http://files.mtasa.com/media/PCZone_March_2006.jpg Page 1]
* Igromania | April 2006
* GameStar | January 2008 - [http://files.mtasa.com/media/1.0/Images/mtaongamestarscan.jpg Page 1]
* Total PC Gaming | Issue 26, October 2009 - [http://files.mtasa.com/media/TPCG_Issue_26.pdf Page 1] (preprint) (included on DVD)

=TV=

* G4TV.com | [http://www.youtube.com/watch?v=B6FqSiJBMgM Multi Theft Auto @ G4TV.com @ YouTube] | October 10 2003

=Internet=

While MTA has been mentioned and reviewed in a lot of articles, and here is a list of those which were recorded. It is worth noting that this list is very incomplete.

* 1UP.com | [http://www.1up.com/features/fan-theft-auto Fan Theft Auto] | [https://archive.is/ojGXK Snapshot] | Unknown? (2003-2005)
{{Quote|
What would an online version of Grand Theft Auto: Vice City be like? What if there had been a Grand Theft Auto game for the Nintendo Entertainment System back in the days when this system reigned? For fans of Grand Theft Auto, they don't just dream these what-ifs -- they bring them to life.
}}

* MegaGames | [http://www.megagames.com/news/multiplayer-killing-spree-vc?tab=description Multiplayer Killing Spree in VC] | [https://archive.is/Izs2U Snapshot] | April 04 2003
{{Quote|
A mention in Eurogamer brought the efforts of the Multi Theft Auto team to our attenion and following a short multiplayer session we are sold on the MTA:VC mod.
Not satisfied with applying their genius to creating a multiplayer mod for GTA 3, the team focused on Vice City and their efforts have been finally rewarded with a very enjoyable multiplayer experience.

Although extremely addictive and interesting the GTA Vice City multiplayer client is buggy and not for those gamers that have been hand-reared by the big studios. If you enjoy a decent rampage through the murky depths of Vice City however, you will definitely love this.

Although installation is fairly simple and straightforward, make sure you read and understand the extensive FAQ on the developer's web site, a link to which can be found by following the download tab.
Weighing in at 500 kb the MTA:VC client is a lot of pleasure from a very small package, enjoy.}}
* IGN | [http://pc.ign.com/articles/519/519510p2.html True Crime - Streets of L.A. review] | [https://archive.is/YXj9E Snapshot] | May 27 2004

{{Quote|The on-foot combat modes, Dojo Master and Battle Master, feel more like minigames than full-fledged modes. Dojo Master, the melee mode, has exactly one round. You knock the guy out and boom, the round ends and you're kicked to a summary screen. And the camera was just plain not right, seemingly unable to properly pull back and frame the scene. I had to move myself out of the way of the camera many times so I could see what was going on. Battle Master, also known as "last man standing," is also exactly one round, with very small maps and only one life per player. '''All in all, multiplayer doesn't rise to the level of something I'd recommend over, say, Multi-Theft Auto'''.''}}

* IGN | [http://pc.ign.com/articles/605/605982p1.html GTA San Andreas PC Hands-On] | [https://archive.is/aqBhh Snapshot] | April 19 2005

{{Quote|Other than that, there won't be any new content--no new vehicles, weapons, missions, et cetera. '''Nor will Rockstar add any multiplayer, but I think it's safe to expect another Multi-Theft Auto from the MTA Team not too long after release'''.}}

* Gamespy [http://xbox360.gamespy.com/xbox-360/saints-row/718937p1.html Saints Row preview] | August 29 2006

{{Quote|In spite of its popularity among console owners, it is PC gamers who've reaped the most benefits from the Grand Theft Auto series. '''Besides the numerous skins and tweaks available, one of the most infamous mods for GTA is the one known as Multi Theft Auto'''. The modification allows players to get online and battle against other players for dominance. '''The idea has extended to other sandbox-style games, but like their single-player counterparts, the MTA cloning worked about as well as the GTA cloning.''' That is, no one's really come close to emulating it. Anyone involved in Saints Row who says that GTA had no influence on their title probably also has some beachfront property in Omaha to sell you.

With that out of the way, THQ sponsored an event in San Francisco to preview the multiplayer portion of Volition's next-gen title. We didn't go near the single-player portion of the game, instead opting to stay on the designated path of system link gameplay to see how Saints Row performs. '''What we saw was the concept of what would be known as another GTA clone extended to its next logical point on the 360: cloning Multi Theft Auto.'''}}

* OSDir.com | [http://osdir.com/Article4775.phtml Multi Theft Auto: Hacking Multi-Player Into Grand Theft Auto With Open Source] | March 29 2005

:OSDir.com did an interview with four of MTA's developers about the open source software they use in the process of creating MTA.

* Fileplanet | [http://files.mtasa.com/media/FilePlanet-Mar_2006.jpg Frontpage] | March 16 2006

:MTA was covered for several days on the Fileplanet frontpage after the initial MTA:SA release.

* Global Gaming | [http://www.ggl.com/?controller=News&id=2982&method=article Homebrews: Multi-Theft Auto] | May 5 2006

* Mega Games | [http://www.megagames.com/news/multi-theft-auto-san-andreas Multi Theft Auto - San Andreas] | February 6 2006
{{Quote|
Fans of the Grand Theft Auto series of games will, no doubt, be familiar with the efforts of the Multi Theft Auto team and their wonderful MTA:VC which allowed multi-player mayhem to spill onto the streets of Vice City.

Following 8 months of hard work, the multiplayer modification is now available for GTA:SA. Most gamers were very disappointed to find out that RockStar did not plan to introduce a multiplayer mode for GTA:SA, even though MTA:VC had clearly demonstrated how desired such a feature would be. PC gamers can now enjoy multiplayer fun in the streets of San Andreas with a new, feature-rich version of MTA utilising the brand new Blue core.

From the creator's blog: The process of developing this release has been a lot of hard work and quite a few long nights, especially when most of our team members are busy with their real lives, but now weŒre glad to announce that weŒre finally ready to show you our work. WeŒve been looking forward to this for a very long time and weŒre certainly very happy with how it looks. We hope you like it too! Smile

This release also features a very easy to use map editor allowing anyone to create a map containing spawnpoints, checkpoints, objects and "pickups". The maps created can be added to an MTA server and played online with your friends at any time.

This version of MTA features a new game mode called Race while expect frequent improvements and updates from the developers.
}}

* Neowin | [http://www.neowin.net/index.php?act=view&id=32142 Multi Theft Auto: San Andreas Released] | January 24 2006
{{Quote|
Popular action game Grand Theft Auto: San Andreas was always a single player game from the beginning (except the parts where a second player can shoot from the car, but that's hardly multiplayer). But as of yesterday, the talented team of programmers that brought us Multi Theft Auto: Vice City have released their new multiplayer mod for San Andreas.
}}

* Games Galore | [http://games.techwhack.com/54/multi-theft-auto/ Multi Theft Auto] | September 4 2006
{{Quote|
The nice people at Multi Theft Auto have this article up, discussing their new core technology that will be deployed in future versions of MultiTheftAuto.

The new core technology, codenamed ‘blue’, offers many of the features that have been requested by the software’s users over the last year and a half, these include: Support for boats, support for firing from vehicles, support for drive-bys, and support for planes.

As well as supporting all these features, the new core will introduce a revolutionary new way of writing modifications for Vice City, combining the existing methods with a fully integrated C++ add-on system, giving anyone who wishes to the ability to create complex and exciting mods, far beyond the possibilities of ‘traditional’ methods.”
}}

* GameSpot | [http://www.gamespot.com/pages/unions/read_article.php?topic_id=24250612&union_id=338 MTA: San Andreas Is Here!!!] | January 24 2006

* Slashdot | [http://games.slashdot.org/article.pl?sid=08%2F11%2F24%2F0237259& Multi Theft Auto - San Andreas Goes Open Source] | November 24 2008

* Linux Magazine | [http://www.linux-magazine.com/Online/News/Open-Source-Mod-for-Grand-Theft-Auto Open-Source Mod for Grand Theft Auto] | November 24 2008
{{Quote|
"Today we are marking a new milestone in the history of Multi Theft Auto [...] we have made the decision to re-launch Multi Theft Auto as an open-source project." The developer announcement on the Grand Theft Auto website comes just before the official release of the multiplayer mod of GTA version 1.0.

Since 2003, up to 16 developers have worked on the multiplayer-modus. Work which included not only Reverse Engineering and LUA scripting, but also manufacturer Rockstar concepted extensions for the single-player modus GTA-3, as in GTA III, GTA: Vice City and GTA: San Andreas. Server and clients offering the original game can be found on the project website.

The announcement on the GTA page continues, "Of course, the migration to open-source is more than just slamming your undocumented source code in a zip up for anyone that is interested." The repository code has been cleaned up, accurate documentation and headers have been added and proper credits to authors noted.

The release of the source code is supposed to encourage the contribution of external developers. To this end, the bugtracker has been opened and access to the build system made available. A clean and stable multiplayer extension requires more than a memory address and offsets, say the developers.
The code can be viewed at the Google Code Repository and a detailed developer Wiki provides insights to programming and scripting.
}}

* GamingBolt | [http://gamingbolt.com/15-modders-who-changed-pc-gaming 15 Modders who changed PC gaming] | March 20 2010
:The MTA Team were labelled as one of 15 modders who changed PC gaming, turning Grand Theft Auto San Andreas into ''"into the one truly decent, fully functioning multiplayer segment to a great game"''.
{{Quote|
Grand Theft Auto San Andreas takes the award for having the largest living GTA universe. Some argue that it was the best game in the franchise- and the massive amounts of free roaming and the (slight) emphasis on realism really helped push the game above and beyond people’s expectations. One thing the game didn’t have though, was multiplayer. This was sorely missed in a game with so much racing and free roaming potential, but luckily the good folks behind MTA found a solution. What started out as an experiment with crude forms of online racing has turned into the one truly decent, fully functioning multiplayer segment to a great game.
}}

* PCGames.de | [http://www.pcgames.de/Bestenlisten-Thema-203022/Bilder/Die-Top-10-der-einflussreichsten-Modder-Diese-Mods-haben-die-Branche-aufgemischt-744688/galerie/1274990/ Die Top 10 der einflussreichsten Modder (Top 10 Most Influential Modders) ] | April 9 2010

:The MTA Team were classed as one of the Top 10 most influential modders of all time.

* usercreated | [http://usercreated.org/2010/04/12/unmissable-mods-month-multi-theft-auto/ Unmissable Mods Month: Multi Theft Auto ] | April 12 2010

:Multi Theft Auto was characterized as an "''Unmissable mod''" that was "''an incredibly elegant way of forcing multiplayer onto an engine that was never designed for it in the first place''".

* 1UP.com | [http://www.1up.com/do/reviewPage?pager.offset=1&cId=3180268&p=2 APB Review] | July 6 2010
:Multi Theft Auto distinguished as a ''"cheaper, better multiplayer PC [game]"'' to All Points Bulletin, a commercial RPG.

* FilePlanet Blog | [http://blog.fileplanet.com/2011/08/29/monday-mod-multi-theft-auto-san-andreas/ Monday Mod: Multi Theft Auto: San Andreas] | August 29 2011
:Multi Theft Auto was praised for the ''"[the charm] from the user generated content all thanks to the Multi Theft Auto toolkit"''

* ModDB [http://www.moddb.com/events/2011-mod-of-the-year-awards/features/moty-players-choice-mod-of-the-year 2011 Mod of the Year - Players Choice #1] | 2011

* Gamers Association | [http://www.gamers-association.com/2013/01/mtasainterview/ Interviewing the Minds Behind Multi Theft Auto: San Andreas] | January 6 2013
{{Quote|
A few days back I was lucky enough to have the privilege of getting to ask the developers behind Multi Theft Auto: San Andreas some questions. For those of you who are unaware of exactly what MTA:SA is, it’s Multiplayer Grand Theft Auto: San Andreas on the surface, but it’s also so much more. If you’re interested in getting your hands on some sweet borderline-MMO free-roaming goodness, then you can download the mod at Multi Theft Auto’s website. You are going to need to pick up the PC version of GTA: San Andreas, though (it’s totally worth it).
}}

* Rock, Paper, Shotgun | [https://www.rockpapershotgun.com/2016/09/15/why-a-million-people-still-play-multiplayer-grand-theft-auto-san-andreas-every-month/ Why A Million People Still Play Multiplayer Grand Theft Auto: San Andreas Every Month] | September 15 2016
{{Quote|
I asked one of the MTA developers, a chemical engineer named Dan, to help me understand what makes this San Andreas multiplayer community tic. Dan started out as a Multi Theft Auto player back before San Andreas even came out — when the mod was available for GTA 3 and Vice City. He was drawn in by its accessibility. “At the time the big game was Counter-Strike,” he recalls. He downloaded it and gave it a shot, but it seemed impenetrable. “I’d jump in and get shot immediately and have to wait like three minutes to jump into the next round.” But with Multi Theft Auto he didn’t have to worry about being killed constantly by skilled players. He could just drive around and have fun.
}}

<gallery>
File:ModDB.png|ModDB Frontpage. October, 2009
File:Mtafileplanet.jpg|Fileplanet Frontpage. March, 2006
</gallery>

= Other Media =
* MTA Forum | [http://forum.mtasa.com/viewtopic.php?f=5&t=128#p810 2003 official R* reaction] | 2003
{{Quote|
Hi Blokker,
<br/><br/>
I had a look at the first version of Multi Theft Auto and was very impressed with what you guys did.
It looks like there is a lot of work to be done yet but a lot of progress has been made already.
I'm looking forward to playing GTAIII as a multiplayer game.
Being from Holland myself it's good to see the old 'hacking culture' is still going strong in the Lowlands.
<br/><br/>
I also have to say the web site itself looks very professional. It's a shame the project will no doubt get delayed somewhat when Vice City comes out for the PC.
<br/>
Keep up the good work.
<br/><br/>
Technical manager
<br/>
Rockstar North.
}}

[[Category:Historical]]

AR/الصفحه الرئيسيه

2017-01-01T18:44:42Z

JHXP: Reverted edits by Marcin778 (talk) to last revision by Ahmed Ly

{| width="100%" cellspacing="0" cellpadding="0"
| colspan="2" |
<div style="border: 1px solid #D8D8D8; padding: 5px; height: 130px;">
[[File:Mtalogo.png|left|100px]].Multi Theft Auto ستجد هنا معلومات غنية عن استخدام .'''Multi Theft Auto أهلا بك فى الويكي الخاص ب'''


.[[IRC Channel]] أو [irc://irc.gtanet.com/Arab_scripting Arab_scripting] إذا كان لديك أي أسئلة أو مشاكل تتعلق بالبرمجة ، يمكنك السؤال على

</div>
|}
{| width="100%" cellspacing="0" cellpadding="0"
| colspan="2" |
|-
|width="50%" style="vertical-align:top;" |<div style="border: 1px solid #D8D8D8; padding:4px 8px 8px 8px; margin:10px;">

<div style="border: 1px dotted #AAAAAA;padding:4px 8px 8px 8px;margin:10px;">
====مكتبات====

* [[AR/Math| math مكتبة ]] [[Image:Sa.png|اللغة العربية|20px]]
* [[AR/String| string مكتبة ]] [[Image:Sa.png|اللغة العربية|20px]]
* [[AR/Table| table مكتبة ]] [[Image:Sa.png|اللغة العربية|20px]]
* [[AR/Other| مكتبات اخرى ]] [[Image:Sa.png|اللغة العربية|20px]]

</div>

<div style="float:right; width: 32px;">[[File:Input-gaming.png‎]]</div>
=== لعب ===
<div style="background: #FFEEAA;">
[[File:Go-down.png|link=http://mtasa.com/]] ''' [http://mtasa.com/ تحميل لعبة ام تي اي اخر اصدار {{Current Version|full}}]'''</div>

* [[AR/دليل اللاعب|(Client) دليل اللاعب]] [[Image:Sa.png|اللغة العربية|20px]] [[Image:flag_us.png|اللغة الأنجليزية|20px]]
* [[Changes_in_{{padleft:|3|{{Current Version|full}}}}| {{padleft:|3|{{Current Version|full}}}} التغيرات فى ]] [[Image:flag_us.png|اللغة الأنجليزية|20px]]
* [[Known_Issues_-_FAQ|مشاكل معروفه]] [[Image:flag_us.png|اللغة الأنجليزية|20px]]
* [[Upgrading_from_MTA:Race|MTA:SA {{padleft:|3|{{Current Version|full}}}} الى MTA:RACE المهاجرة من]] [[Image:flag_us.png|اللغة الأنجليزية|20px]]
* [[Server_Manual|(Server) دليل السيرفر]] [[Image:flag_us.png|اللغة الأنجليزية|20px]]
* [[Map_manager|ادارة الخرائط]] [[Image:flag_us.png|اللغة الأنجليزية|20px]]

=== صنع الخرائط ===
*[[Resource:Editor|دليل]] [[Image:flag_us.png|اللغة الأنجليزية|20px]]
*[[Resource:Editor/EDF|EDF صيغة]] [[Image:flag_us.png|اللغة الأنجليزية|20px]]
*[[Resource:Editor/Plugins|الاضافات]] [[Image:flag_us.png|اللغة الأنجليزية|20px]]
*[[Resource:Editor#FAQ|أسئلة وأجوبة]] [[Image:flag_us.png|اللغة الأنجليزية|20px]]
</div>

<div style="border: 1px solid #D8D8D8; padding:4px 8px 8px 8px; margin:10px;">
<div style="float:right; width: 32px;">[[File:Package-x-generic.png‎]]</div>
=== قواعد البيانات ===
MTA لـ (Resources) فى صنع المودات Lua يوضح هذا القسم امكانيات
* [[:Category:Resource|(Resources)]] كتالوج المودات
* [[Client side scripts]]
* [[Modules]]
</div>

<div style="border: 1px solid #D8D8D8; padding:4px 8px 8px 8px; margin:10px;">
<div style="float:right; width: 32px;">[[File:Applications-development.png‎‎‎]]</div>
=== Multi Theft Auto تطوير ===
[[File:Go-down.png|link=http://nightly.mtasa.com/]] [http://nightly.mtasa.com/ Nightly builds]
* [[Compiling_MTASA|Compiling MTASA on Windows]]
* [[Building_MTASA_Server_on_Mac_OS_X|Compiling MTASA on Mac OS X]]
* [[Building_MTASA_Server_on_GNU_Linux|Compiling MTASA on GNU/Linux]]
* [[Coding guidelines]]
* [https://github.com/multitheftauto/mtasa-blue Main Github repository]
* [[Roadmap]]
* [http://bugs.mtasa.com/ Bugtracker]
</div>
<div style="border: 1px solid #D8D8D8; padding:4px 8px 8px 8px; margin:10px;">
<div style="float:right; width: 32px;">[[File:Applications-office.png‎]]</div>
=== Wiki - كيف يمكنك المساعدة ===
* [[:Category:Incomplete|تكملة الوثائق الغير مكتملة]]
* [[:Category:Needs_Example |eventsو لل functionsاضف مثال لل]].
* [[:Category:Needs Checking|مراجعة والتحقق من الصفحات التي تحتاج التحقق]]
* كتابة دروس لمساعدة الناس
* ترجمة صفحات الويكي
</div>

<div style="border: 1px solid #D8D8D8; padding:4px 8px 8px 8px; margin:10px;">
<div style="float:right; width: 32px;">[[File:Internet-group-chat.png‎]]</div>
=== المجتمع ===
* [http://forum.multitheftauto.com/ المنتدى]
* IRC: [irc://irc.multitheftauto.com/mta irc.multitheftauto.com #mta]
* [http://community.mtasa.com/ MTA Community] - تنزيل ومشاركة المودات
* [http://twitter.com/#!/MTAQA/ Twitter] - [http://www.youtube.com/user/MTAQA Youtube] - [http://plus.google.com/102014133442331779727/ Google+] - [http://www.moddb.com/mods/multi-theft-auto-san-andreas ModDB]
</div>

| width="50%" style="vertical-align:top;" |

<div style="border: 1px solid #D8D8D8; padding:4px 8px 8px 8px; margin:10px;">
<div style="float:right; width: 32px;">[[File:Accessories-text-editor.png]]</div>
=== (Scripting) البرمجة ===
* [[AR/مقدمه في البرمجه|مقدمه في البرمجه]] [[Image:Sa.png|اللغة العربية|20px]] [[Image:flag_us.png|اللغة الأنجليزية|20px]]
* [[Introduction to Scripting the GUI| مقدمة فى برمجة الواجهة الرسومية]] [[Image:flag_us.png|اللغة الأنجليزية|20px]]
* [[Debugging|كيفية البحث عن الأخطاء فى السكربت]] [[Image:flag_us.png|اللغة الأنجليزية|20px]]
* [[Resources|(Resources) مقدمة فى المودات]] [[Image:flag_us.png|اللغة الأنجليزية|20px]]
** [[الوصول الى المودات عن طريق الويب]] [[Image:flag_us.png|اللغة الأنجليزية|20px]]
** [[:Category:Resource|(Resources) كتالوج المودات]] [[Image:flag_us.png|اللغة الأنجليزية|20px]]
** [[Meta.xml]] - الذى يحدد ذلك (meta.xml) ملف التعريف (Resources) وراء كل المودات
** [[ACL]] - و هذا أمر حيوى لسكربتات معقدة للعمل Access Control List
* [[Writing_Gamemodes|Gamemodes كتابة]]
* [[Useful_Functions|وظائف مفيدة]]
<div style="float:right; width: 32px;">[[File:start-here.png]]</div>
====LUA تعلميات عامه حول====
صفحات مصممه للمساعدة في فهم اللغه
*[http://www.lua.org/pil/index.html "LUA دليل البرمجة في]
**[http://www.lua.org/manual/5.1/#index Lua دليل وظائف]
*[http://lua-users.org/wiki/TutorialDirectory Lua ويكي]
*[http://nixstaller.berlios.de/manual/0.2/nixstaller_9.html Nixstaller من Lua أرشادات عامة في]
</div>

<div style="border: 1px solid #D8D8D8; padding:4px 8px 8px 8px; margin:10px; background:#E5E5FF;">
====Reference====
* [[AR/Client Scripting Functions|Client-side Functions]] [[Image:Sa.png|اللغة العربية|20px]] جاري الترجمة
* [[Client Scripting Events|Client-side Events]]
* [[AR/Server Scripting Functions|Server-side Functions]] [[Image:Sa.png|اللغة العربية|20px]] تم الترجمة جزئياً
* [[Server Scripting Events|Server-side Events]]

* [[MTA Classes]] - Detailed descriptions of all MTA custom types
** [[Element|MTA Elements]] / [[Element tree]]
</div>
<div style="border: 1px solid #D8D8D8; padding:4px 8px 8px 8px; margin:10px;">
<div style="float:right; width: 32px;">[[File:System-file-manager.png]]</div>
====[[Id|قائمة الأي دي]]====
*[[Animations|الحركات]]
*[[Character Skins|الشخصيات]]
*[[CJ_Clothes|CJ ملابس]]
*[[Garage|الكراجات]]
*[[Interior IDs|المحلات]]
*[[Material IDs|الادوات]]
*[[Projectiles|الصواريخ والمقذوفات]]
*[[Radar Blips|ايقونات الرادار]]
*[[Sounds|الإصوات]]
*[[Vehicle IDs|السيارات]]
*[[Vehicle Colors|الوان السيارات]]
*[[Vehicle Upgrades|اضافات السيارات]]
*[[Vehicle variants|متغيرات السيارات]]
*[[Weapons|الاسلحه]]
*[[Weather|الجو]]

</div>
<div style="padding:4px 8px 8px 8px; margin:10px;">

[[File:Osi symbol.png|75px|link=http://opensource.org/]]

</div>
أفضل(Multi Theft Auto)هي مصدر مفتوح هذا يعني ان اي شخص يمكن ان يساهم لجعل '''MTA'''
|-
| colspan="2" |
|}
{| width="100%" cellspacing="0" cellpadding="0"
| colspan="2" |
<div style="padding: 5px;" class="plainlinks">
<ul style="list-style: none; width: 200px; float: left;">
<li>'''About Multi Theft Auto'''</li>
<li>[[Archive]]</li>
<li>[[Press Coverage]]</li>
<li>[http://code.google.com/p/mtasa-blue/people/list Developers]</li>
</ul>
<ul style="list-style: none; width: 200px; float: left;">
<li>'''Multi Theft Auto 0.5'''</li>
<li>[[Archive#Multi_Theft_Auto_0.5|Download]]</li>
<li>[[MTA 0.5r2 Known Issues|Known Issues]]</li>
</ul>
<ul style="list-style: none; width: 200px; float: left;">
<li>'''Wiki Stats'''</li>
<li>{{NUMBEROFARTICLES}} Articles</li>
<li>{{NUMBEROFPAGES}} Pages</li>
<li>{{NUMBEROFUSERS}} Registered Users</li>
</ul>
</div>
|}
__NOTOC__
__NOEDITSECTION__
{{Languages list|ar}}

CS/hlavni

2017-01-01T18:44:40Z

JHXP: Reverted edits by Marcin778 (talk) to last revision by Miki785

__NOTOC__
__NOEDITSECTION__
{| width="100%" cellspacing="0" cellpadding="0"
| colspan="2" |
<div style="border: 1px solid #D8D8D8; padding: 5px; height: 130px;">

[[File:Mtalogo.png|left|100px]]'''Vítejte na Multi Theft Auto Wiki!''' Na této wiki najdete bohaté informace jak používat Multi Theft Auto.

'''Do ceskeho jazyka je prelozeno velice malo stranek, uplny seznam prelozenych stranek naleznete zde: [http://wiki.multitheftauto.com/wiki/Category:Cesky]'''

Je tu spousta [[How you can help|věcí kterými nám můžete pomoci]] zlepšit MTA - vytvorit mapu, herní mód, pomoci zdokumentovat informace o funkcích, napsat ukázkové kódy, Psát tutoriály, nebo jen hrát MTA a hlásit bugy na které narazíte.

Pokuď máte něaké problémy se scriptovánním, neváhejte nám napsat na náš [[IRC Channel]].
<br><br>''Přestaň hrát sám se sebou'' (''Stop playing with yourself!'')
</div>
|}
{| width="100%" cellspacing="0" cellpadding="0"
| colspan="2" |
|-
|width="50%" style="vertical-align:top;" |<div style="border: 1px solid #D8D8D8; padding:4px 8px 8px 8px; margin:10px;">
<div style="float:right; width: 32px;">[[File:Input-gaming.png‎]]</div>
=== Hraní ===
<div style="background: #FFEEAA;">
[[File:Go-down.png|link=http://mtasa.com/]] ''' [http://mtasa.com/ Stáhněte Multi Theft Auto: San Andreas {{Current Version|full}}]'''</div>
* [[CS/Client Manual|Klient Manuál]]
* [[Changes_in_1.1| Změny v 1.1]][[Image:usen.gif|Pouze v Angličtině]]
* [[Known_Issues_-_FAQ|Známé problémy]][[Image:usen.gif|Pouze v Angličtině]]
* [[Upgrading_from_MTA:Race|Migrace z MTA:Race na MTA:SA 1.0.x]][[Image:usen.gif|Pouze v Angličtině]]
* [[Server Manual]][[Image:usen.gif|Pouze v Angličtině]]
* [[Map manager|Map Manager]][[Image:usen.gif|Pouze v Angličtině]]

=== Map Editor ===
*[[Resource:Editor|Manual]][[Image:usen.gif|Pouze v Angličtině]]
*[[Resource:Editor/EDF|Editor Definition Format]][[Image:usen.gif|Pouze v Angličtině]]
*[[Resource:Editor/Plugins|Plugins]][[Image:usen.gif|Pouze v Angličtině]]
*[[Resource:Editor#FAQ|Nejčastější dotazy]][[Image:usen.gif|Pouze v Angličtině]]
</div>
<div style="border: 1px solid #D8D8D8; padding:4px 8px 8px 8px; margin:10px;">
<div style="float:right; width: 32px;">[[File:Package-x-generic.png‎]]</div>
====Databáze====
Tato sekce diskutuje o všech možnostech v LUA nebo informace o resources.
* [[:Category:Resource|Resource katalog]][[Image:usen.gif|Pouze v Angličtině]] - Musíte se naučit jak správně psát scripty.
* [[Client side scripts|Client side scripty]][[Image:usen.gif|Pouze v Angličtině]]
* [[Modules]][[Image:usen.gif|Pouze v Angličtině]]
</div>

<div style="border: 1px solid #D8D8D8; padding:4px 8px 8px 8px; margin:10px;">
<div style="float:right; width: 32px;">[[File:Applications-development.png‎‎‎]]</div>
====Rozširujeme Multi Theft Auto====
[[File:Go-down.png|link=http://nightly.mtasa.com/]] [http://nightly.mtasa.com/ Noční buildy]
* [[Compiling_MTASA|Kompilace MTASA na Windows]][[Image:usen.gif|Pouze v Angličtině]]
* [[Building_MTASA_Server_on_Mac_OS_X|Kompilace MTASA NA Mac OS X]][[Image:usen.gif|Pouze v Angličtině]]
* [[Building_MTASA_Server_on_GNU_Linux|Kompilace MTASA na GNU/Linux]]
* [[Coding guidelines|Scriptovací pokyny|]]
* [http://code.google.com/p/mtasa-blue Google Code SVN][[Image:usen.gif|Pouze v Angličtině]]
* [[Roadmap]][[Image:usen.gif|Pouze v Angličtině]]
* [http://bugs.mtasa.com/ Bugtracker][[Image:usen.gif|Pouze v Angličtině]]
</div>
<div style="border: 1px solid #D8D8D8; padding:4px 8px 8px 8px; margin:10px;">
<div style="float:right; width: 32px;">[[File:Applications-office.png‎]]</div>
=== Wiki - Jak můžete pomoci ===
* Dokončete dokumentaci pro [[:Category:Incomplete|Nedokončené funkce]].[[Image:usen.gif|Pouze v Angličtině]]
* [[:Category:Needs_Example |Pridejte ukázky k funkcím]].[[Image:usen.gif|Pouze v Angličtině]]
* Prohlídněte a potvrďte [[:Category:Needs Checking|stránky které potrebují kontrolu]].[[Image:usen.gif|Pouze v Angličtině]]
* Pište tutoriály abyste pomohli nováčkům.
* Prekládejte wiki stránky.
</div>

<div style="border: 1px solid #D8D8D8; padding:4px 8px 8px 8px; margin:10px;">
<div style="float:right; width: 32px;">[[File:Internet-group-chat.png‎]]</div>
=== Komunita ===
* [http://forum.multitheftauto.com/ Forum][[Image:usen.gif|Pouze v Angličtině]]
* IRC: [irc://irc.multitheftauto.com/mta irc.multitheftauto.com #mta][[Image:usen.gif|Pouze v Angličtině]]
* [http://community.mtasa.com/ MTA Community][[Image:usen.gif|Pouze v Angličtině]] - Sdílejte a stahujte resources.
* [http://www.youtube.com/user/MTAQA Youtube Channel][[Image:usen.gif|Pouze v Angličtině]]
</div>

| width="50%" style="vertical-align:top;" |

<div style="border: 1px solid #D8D8D8; padding:4px 8px 8px 8px; margin:10px;">
<div style="float:right; width: 32px;">[[File:Accessories-text-editor.png]]</div>
=== Skriptování ===
* [[Scripting Introduction|Úvod do skriptování]][[Image:usen.gif|Pouze v Angličtině]]
* [[Introduction to Scripting the GUI|Úvod do skriptování GUI]][[Image:usen.gif|Pouze v Angličtině]]
* [[Debugging|Debugging Tutorial]][[Image:usen.gif|Pouze v Angličtině]] - Jak nalézt chyby ve vašich scriptech.
* [[Resources|Úvod do resources]][[Image:usen.gif|Pouze v Angličtině]]
** [[Resource Web Access]][[Image:usen.gif|Pouze v Angličtině]] - Jak můžete psát webové stránky s resources.
** [[:Category:Resource|Resource Katalog]][[Image:usen.gif|Pouze v Angličtině]]
** [[CZ/Meta.xml|Meta.xml]] - Za každým resource je Meta která jej definuje.
** [[ACL]][[Image:usen.gif|Pouze v Angličtině]] - Access Control List, toto je důležite pro komplexní skripty aby fungovali.
* [[Writing_Gamemodes|Psaní herních módů]][[Image:usen.gif|Pouze v Angličtině]]
* [[Useful_Functions|Užitečné funkce]][[Image:usen.gif|Pouze v Angličtině]]
<div style="float:right; width: 32px;">[[File:start-here.png]]</div>
====Obecná pomoc s LUA====
Stránky které tu jsou od toho aby vám pomohli chápat jazyk LUA
*[http://www.lua.org/pil/index.html "Programováni v LUA" Manual][[Image:usen.gif|Pouze v Angličtině]]
**[http://www.lua.org/manual/5.1/#index reference vnitrních LUA funkcí][[Image:usen.gif|Pouze v Angličtině]]
*[http://lua-users.org/wiki/TutorialDirectory Lua Wiki][[Image:usen.gif|Pouze v Angličtině]]
*[http://nixstaller.berlios.de/manual/0.2/nixstaller_9.html Obecný průvodce pro Lua od Nixstaller][[Image:usen.gif|Pouze v Angličtině]]
</div>

<div style="border: 1px solid #D8D8D8; padding:4px 8px 8px 8px; margin:10px; background:#CCCCFF;">
====Reference====
* [[Client Scripting Functions|Client-side Funkce]][[Image:usen.gif|Pouze v Angličtině]]
* [[Client Scripting Events|Client-side Eventy]][[Image:usen.gif|Pouze v Angličtině]]
* [[Server Scripting Functions|Server-side Funkce]][[Image:usen.gif|Pouze v Angličtině]]
* [[Server Scripting Events|Server-side Eventy]][[Image:usen.gif|Pouze v Angličtině]]

* [[MTA Classes]][[Image:usen.gif|Pouze v Angličtině]] - Detailní vysvětlení všech MTA prvků
** [[Element|MTA Elements]] / [[Element tree]][[Image:usen.gif|Pouze v Angličtině]]
</div>
<div style="border: 1px solid #D8D8D8; padding:4px 8px 8px 8px; margin:10px;">
<div style="float:right; width: 32px;">[[File:System-file-manager.png]]</div>
====[[Id|Seznamy ID]][[Image:usen.gif|Pouze v Angličtině]]====
*[[Animations|Animace]][[Image:usen.gif|Pouze v Angličtině]]
*[[Character Skins|Skiny]][[Image:usen.gif|Pouze v Angličtině]]
*[[CJ_Clothes|Oblečení]][[Image:usen.gif|Pouze v Angličtině]]
*[[Garage|ID garáží]][[Image:usen.gif|Pouze v Angličtině]]
*[[Interior IDs|ID iteriérů]][[Image:usen.gif|Pouze v Angličtině]]
*[[Material IDs|ID materiálů]][[Image:usen.gif|Pouze v Angličtině]]
*[[Projectiles|Projektily]][[Image:usen.gif|Pouze v Angličtině]]
*[[Radar Blips|Radarové ikonky]][[Image:usen.gif|Pouze v Angličtině]]
*[[Sounds|Zvuky]][[Image:usen.gif|Pouze v Angličtině]]
*[[Vehicle IDs|ID Vozidel]][[Image:usen.gif|Pouze v Angličtině]]
*[[Vehicle Colors|Barvy vozidel]][[Image:usen.gif|Pouze v Angličtině]]
*[[Vehicle Upgrades|Upgrady(tuning) vozidel]][[Image:usen.gif|Pouze v Angličtině]]
*[[Vehicle variants|Variace vozidel]][[Image:usen.gif|Pouze v Angličtině]]
*[[Weapons|Zpraně]][[Image:usen.gif|Pouze v Angličtině]]
*[[Weather|Počasí]][[Image:usen.gif|Pouze v Angličtině]]
</div>
<div style="padding:4px 8px 8px 8px; margin:10px;">
[[File:Osi symbol.png|75px|link=http://opensource.org/]]
'''Multi Theft Auto''' je '''Open Source'''.
To znamená že se může kažý zapojit aby udělal MTA eště lepším!
</div>

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

[[Category:Cesky]]

MTA 0.5r2 Known Issues

2017-01-01T18:44:31Z

JHXP: Reverted edits by Marcin778 (talk) to last revision by Dvorapa

{{MTA0.5 page}}
__NOTOC__This applies to MTA 0.5r2 (both GTA3:MTA and MTA:VC). The known issues for MTA:SA 1.x can be found [[Known_Issues_-_FAQ | here]].

== Client issues: ==
*'''Australian and German EXEs (and possibly others) may produce an "invalid executable" error when you try to start a game.'''
As Australian and German EXEs don't work reliably with MTA, this shouldn't be a huge problem. Try to obtain a standard EXE. You can try [http://forum.mtasa.com/viewtopic.php?f=50&t=12180 '''Talidan''''s invalid executable patcher].
*'''Crash when MTA:VC DM is loading.'''
Make sure you run GTA3 or Vice City at least once in single player without MTA before actually running it with MTA. If that doesn't work, try [http://updates.rockstargames.com/patches/vicecity/vicepatch_11.zip the Vice 1.1 patch]. If that still doesn't work, post in [http://forum.mtasa.com/viewforum.php?f=50 the support forum].
*'''Freeze when the client tries to display dialog asking for game path.'''
There have been a couple of occurrence of this, and we'd be interested to see why this is. You can avoid it by manually setting the path in the mta.ini in the Multi Theft Auto directory.

For Vice City, your mta.ini should contain (replace the path if necessary):

<pre>[Game-VC]
Version=0
Location=C:\Program Files\Rockstar Games\Grand Theft Auto Vice City\gta-vc.exe</pre>

For GTA3:MTA, your mta.ini should contain (replace the path if necessary):

<pre>[Game-GTA3]
Version=1
Location=C:\Program Files\Rockstar Games\GTAIII\gta3.exe</pre>
*'''XFire crashes game during loading.'''
Both XFire and MTA use similar methods for integrating themselves into the game. We've contacted XFire to offer our support for them in implementing support for MTA, but they haven't responded. If you wish to use XFire in MTA, contact XFire. In the meantime, disable XFire before you play.
*'''MTA claims "Suspected Trainer Usage."'''
Try closing every other open window first, then if that doesn't work restart MTA. If that doesn't work, try reinstalling MTA 0.5r2.
*'''You join a server and are told you are banned, even though you aren't in the ban list.'''
The cause of this is unknown. You may be banned by a over-general ban in the server's ban list.
*'''Client crashes when you join a server.'''
This crash may be caused by the client trying to download the rich text MOTD specified by the server and failing (e.g. the site its trying to get it from is down, or the URL is invalid). If this happens, the client will crash.
*'''You have quite a few files on your computer called mtachat.txt.'''
mtachat.txt, as you probably guessed, stores a chat log. This feature was added at the last moment and not properly tested. Consequently, this problem has occurred. This is probably due to how the client has been launched (the start path determines where it saves the chat, not the install path). Feel free to delete any files you don't want.
*'''Upon clicking "Start Game" the client informs you your client is modified.'''
Click '''Start Game''' again.
*'''When playing GTA3 you receive an "Invalid Executable" error.'''
This is probably because you are using GTA3 version 1.0 instead of 1.1. You can get the GTA3 1.1 patch [http://updates.rockstargames.com/patches/grandtheftauto3/GTA3patch1.1.zip here]. If this doesn't work, or you already have GTA3 1.1, make sure you have the USA/UK EXE; you can try '''Talidan''''s [http://forum.mtasa.com/viewtopic.php?f=50&t=12180 invalid executable patcher]. Failing that, try to obtain one elsewhere.
*'''Your virus scanner informs you that the Multi Theft Auto 0.5r2 executable is a virus or malware.'''
MTA does <u>not</u> contain any viruses, malware, adware or spyware. It is flagged as a false positive because of the way the executable is packed. Ensure you only download the client from our site. [http://dl.dropbox.com/u/12783812/mta05r2_full_installer.exe This link] is uploaded by our account. Use this if you doubt the validity of your copy of MTA.
*'''You get a crash at the address 652F30 when starting the game.'''
Ensure your game language is set to English.

== Gameplay issues: ==
*'''MTA:VC (either map) crashes when you try to get on a motorcycle as passenger when it has no driver, as well as a couple other crashes in certain circumstances with motorcycles'''
Sorry, I was unable to fix this for 0.5r2. This may be fixed in a future release.
*'''MTA:VC DM: You are unable to jump or sprint when a Molotov is your active weapon, but you are able to jump and sprint with Grenades'''
This will be fixed in a future release if there is one.
*'''MTA:VC (either map): after exiting spectator mode, you may see a brief glimpse of Tommy falling and potentially receiving fall damage; once you spawn with a skin, you have less than 100 health'''
This will be fixed in a future release if there is one.
*'''GTA3:MTA, Turismo/Shoreside Scramble gamemode: During a race, if another racer dies, every living racer crashes.'''
I was also unable to fix this issue for 0.5r2. This may be fixed in a future release.
*'''GTA3:SSV, Van Heist gamemode: The home base marker flickers, and if the Securicar explodes, then the damage meter shows negative'''
Live with it, neither were worth my time to fix for 0.5r2. This may be fixed in a future release.

== Server issues: ==
*'''You receive the error "ERROR: The ServerName, ServerPort, GameMap, GameHour, GameMins, Weather and BannedFile MUST be specified in the configuration file" when you run your server, and all fields are filled in. ''Only affects Server Patch 1 Hotfix'''''
Ensure that your server name is 49 characters or less. This is a misleading error.
*'''Your client times out as soon as you connect to a server. Players all time out when they connect to your server.'''
This has been an unknown problem for quite some time now, but it seems it is caused not by MTA or the MTAServer but by MTA:mA, or more specifically scripts running on it. If the scripts send multiple messages to the player when they join it is highly likely to time them out. This results in nobody being able to play.

For now a fix is available for MTA:mA [http://forum.mtasa.com/viewtopic.php?p=181919#181919 here] (hopefully GRS will also be updated soon).

Please follow '''Aeron''''s instructions regarding its use.

A big thank-you to '''Mike''' for discovering the cause of this problem and '''Aeron''' for getting a fix out so quickly.

[[ru:MTA_0.5r2_Known_Issues]]

[[Category:Vice_City]]
[[Category:GTA3]]
[[Category:MTA_0.5]]

Vehicle Colors

2017-01-01T18:44:29Z

JHXP: Reverted edits by Marcin778 (talk) to last revision by GabWas

These are the vehicle colors you can use with [[setVehicleColor]] and [[getVehicleColor]].
{{Vehicle colors}}

==Vehicle Functions==
{{Vehicle functions}}

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

[[Category:ID Lists]]
[[ru:Vehicle colors]]
[[de:Fahrzeugfarben]]
[[pl:Vehicle Colors]]

Vehicle variants

2017-01-01T18:44:24Z

JHXP: Reverted edits by Marcin778 (talk) to last revision by Wielebny

== 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]]

Weapons

2017-01-01T18:44:22Z

JHXP: Reverted edits by Marcin778 (talk) to last revision by AlexTMjugador

Scripting functions that ask for a weapon ID need an integer that refers to the GTASA weapon ID list. They are listed below.
{{Note|
*Clip size () denotes clip size when the weapon is dual wielded. Weapons without this specification are not dual wield weapons.
*GTASA [[Weapon_skill_levels|weapon stats]] will affect movement, accuracy, damage, and dual wield capability. See [[setPedStat]] to change these stats. The default MTA server package comes with a resource called "defaultStats" that sets GTASA weapon stats to 999. See the weapon stats link for more info.
*For death reasons, especially in event handlers for onPlayerWasted or similar, also have a look at the [[Death Reasons]].
*'''Name''' is compatible with functions [[getWeaponNameFromID]], [[getWeaponIDFromName]].
}}
{|class="wikitable sortable" style="text-align:center; margin: 1em auto 1em auto; border:1px solid black"
|-
! Slot || class="unsortable" | Type || class="unsortable" | Image || Name || ID || class="unsortable" | Model ID || class="unsortable" | Clip || class="unsortable" | Sharing slot ammo
|-
! rowspan="2" | 0
! rowspan="2" | Hand
| [[Image:Fist.png]] || align="left" | Fist || 0 || - || -
| rowspan="2" | -
|-
| [[Image:Knuckle.png]] || align="left" | Brassknuckle || 1 || 331 || -
|-
! rowspan="8" | 1
! rowspan="8" | Melee
| [[Image:Golfclub.png]] || align="left" | Golfclub || 2 || 333 || -
| rowspan="8" | -
|-
| [[Image:Nitestik.png]] || align="left" | Nightstick || 3 || 334 || -
|-
| [[Image:Knife.png]] || align="left" | Knife || 4 || 335 || -
|-
| [[Image:Bat.png]] || align="left" | Bat || 5 || 336 || -
|-
| [[Image:Shovel.png]] || align="left" | Shovel || 6 || 337 || -
|-
| [[Image:Poolcue.png]] || align="left" | Poolstick || 7 || 338 || -
|-
| [[Image:Katana.png]] || align="left" | Katana || 8 || 339 || -
|-
| [[Image:Saw.png]] || align="left" | Chainsaw || 9 || 341 || -
|-
! rowspan="3" | 2
! rowspan="3" | Handguns
| [[Image:Colt45.png]] || align="left" | Colt 45 || 22 || 346 || 17 (34)
| rowspan="3" | '''No'''<br/>''Replacing handgun resets slot 2 ammo''
|-
| [[Image:Silenced.png]] || align="left" | Silenced || 23 || 347 || 17
|-
| [[Image:Deagle.png]] || align="left" | Deagle || 24 || 348 || 7
|-
! rowspan="3" | 3
! rowspan="3" | Shotguns
| [[Image:Shotgun.png]] || align="left" | Shotgun || 25 || 349 || 1
| rowspan="3" | Yes
|-
| [[Image:Sawnoff.png]] || align="left" | Sawed-off || 26 || 350 || 2 (4)
|-
| [[Image:Spas12.png]] || align="left" | Combat Shotgun || 27 || 351 || 7
|-
! rowspan="3" | 4
! rowspan="3" | Sub-Machine Guns
| [[Image:Mac10.png]] || align="left" | Uzi || 28 || 352 || 50 (100)
| rowspan="3" | Yes
|-
| [[Image:Mp5.png]] || align="left" | MP5 || 29 || 353 || 30
|-
| [[Image:Tec9.png]] || align="left" | Tec-9 || 32 || 372 || 50 (100)
|-
! rowspan="2" | 5
! rowspan="2" | Assault Rifles
| [[Image:Ak47.png]] || align="left" | AK-47 || 30 || 355 || 30
| rowspan="2" | Yes
|-
| [[Image:M4.png]] || align="left" | M4 || 31 || 356 || 50
|-
! rowspan="2" | 6
! rowspan="2" | Rifles
| [[Image:Rifle.png]] || align="left" | Rifle || 33 || 357 || 1
| rowspan="2" | '''No'''<br/>''Replacing rifle resets slot 6 ammo''
|-
| [[Image:Sniper.png]] || align="left" | Sniper || 34 || 358 || 1
|-
! rowspan="4" | 7
! rowspan="4" | Heavy Weapons
| [[Image:Rocketla.png]] || align="left" | Rocket Launcher || 35 || 359 || 1
| rowspan="4" | '''No'''<br/>''Replacing heavy weapon resets slot 7 ammo''
|-
| [[Image:Heatseek.png]] || align="left" | Rocket Launcher HS || 36 || 360 || 1
|-
| [[Image:Flame.png]] || align="left" | Flamethrower || 37 || 361 || 50
|-
| [[Image:Minigun.png]] || align="left" | Minigun || 38 || 362 || 500
|-
! rowspan="4" | 8
! rowspan="4" | Projectiles
| [[Image:Grenade.png]] || align="left" | Grenade || 16 || 342 || 1
| rowspan="4" | '''No'''<br/>''Replacing projectile resets slot 8 ammo''
|-
| [[Image:Teargas.png]] || align="left" | Teargas || 17 || 343 || 1
|-
| [[Image:Molotov.png]] || align="left" | Molotov || 18 || 344 || 1
|-
| [[Image:Satchel.png]] || align="left" | Satchel || 39 || 363 || 1
|-
! rowspan="3" | 9
! rowspan="3" | Special 1
| [[Image:Spraycan.png]] || align="left" | Spraycan || 41 || 365 || 500
| rowspan="3" | '''No'''<br/>''Replacing slot 9 weapon resets slot 9 ammo''
|-
| [[Image:Fire_ex.png]] || align="left" | Fire Extinguisher || 42 || 366 || 500
|-
| [[Image:Camera.png]] || align="left" | Camera || 43 || 367 || 36
|-
! rowspan="5" | 10
! rowspan="5" | Gifts
| [[Image:Dildo1.png]] || align="left" | Dildo || 10 || 321 || -
| rowspan="5" | -
|-
| [[Image:Dildo2.png]] || align="left" | Dildo || 11 || 322 || -
|-
| [[Image:Vibe1.png]] || align="left" | Vibrator || 12 || 323 || -
|-
| [[Image:Flowers.png]] || align="left" | Flower || 14 || 325 || -
|-
| [[Image:Cane.png]] || align="left" | Cane || 15 || 326 || -
|-
! rowspan="3" | 11
! rowspan="3" | Special 2
| [[Image:Irgoggle.png]] || align="left" | Nightvision || 44 || 368 || -
| rowspan="3" | -
|-
| [[Image:Irgoggle.png]] || align="left" | Infrared || 45 || 369 || -
|-
| [[Image:Paracute.png]] || align="left" | Parachute || 46 || 371 || -
|-
! rowspan="1" | 12
! rowspan="1" | Satchel Detonator
| [[Image:Bomb.png]] || align="left" | Bomb || 40 || 364 || -
| rowspan="1" | -
|}

==Client Functions==
{{Client_weapon_functions}}
==Server Function==
{{Weapon functions}}

[[Category:ID Lists]]
[[it:Armi]]
[[ru:Weapons]]
[[de:Waffen]]
[[pl:Weapons]]

Vehicle component manipulation

2017-01-01T18:44:19Z

JHXP: Reverted edits by Marcin778 (talk) to last revision by Roma ™

== Vehicle component manipulation ==
With the introduction of vehicle component movement we now have the ability to manipulate parts of the model independently on a per vehicle basis which includes hiding parts, moving parts and rotating parts relative to the vehicle they are currently on.

== The Abilities ==
Position: You can reposition a component relative to it's chassis or parent

Rotate: You can rotate the component around it's axis

Hide/Show: You can hide the component so it no longer shows or shows

==How it works==
Adding components is very simple if you have any previous modelling experience each model part can have a name this name acts as a unique identifier for the part.

for ease of use it is possible to add hidden by default components by prefixing this name with a # in the model file though it will not work on anything the game recognizes for instance wheels cannot be hidden by default so it might be best to prefix anything you wish to add.

like so:
''#''hellokitty

This can be re-shown any time and the shown flag is persistent across streaming unless you re-hide it after.

Any components need to be under the chassis dummy at least.

== Simple things ==
The scripting functions make things like adding wheels very easy it should be fairly easy to add and spin wheels by copying the rotation from others into your wheel each frame and you can hide the originals using the hide function if need be.

This could be useful for an insane amount of wheels on a tank!

or just making more than 2 props work on planes

Generally speaking things that spin are fairly easy to do it's more complex animations that require the hardest work but eventually there should be an animation library on google code when it's finished to help with this.

== An interesting idea ==
It should be theoretically possible to add different types of doors to one model e.g. gull wings and scissor doors which could work like so:

Hide the original door

say the rotation of your normal door is between 0 and 45 degrees so you use that as a base for your movement

take that rotation and apply it on another axis for a different type of door or split it between axis each frame to get smooth door movement of the new door ( BONUS: it even works with swinging doors! )

== James bond style ==
Guns, guns and ... rockets? are the order of the day secret panels with hidden rockets? no problem!

== More advanced ==
There are no limits on the amount of moving, hidden or showing parts and anything hidden will not be rendered so you can add thousands of parts hidden and you should not have to worry about them slowing anything down.

This means that there is nothing stopping anyone from making a fully transforming transformer robot which changes from a car to a robot but this will require a lot of work on both the modelling and scripting side.

[[Category:ID Lists]]

Weather

2017-01-01T18:44:18Z

JHXP: Reverted edits by Marcin778 (talk) to last revision by Tails

Weather can be changed using [[setWeather]] and [[setWeatherBlended]] functions. In GTA: SA, every weather has different parameters for the sunrise, morning, midday, noon, afternoon, sunset, night and midnight, so a weather can vary a lot deppending of the time of the day.

{{New feature|3|1.0|
Non-standard weather ID's between 20 and 255 are also supported, but they might be buggy at some moments of the day.
}}

MTA: SA has custom weather functions which can modify how a weather is rendered, but in this list the weathers are described without taking that into account. Also, using [[setWeatherBlended]] allows for more undocumented effects.

For a complete weather gallery, containing images of every weather ID (0 to 255) shot at every in-game hour, visit [http://dev.prineside.com/en/gtasa_weather_id/ this page].

==Default GTA: SA weathers (registered in timecyc.dat)==
{|class="wikitable" style="margin: 1em auto 1em auto;"
|-
! Weather ID || Name from ''timecyc.dat'' || Screenshots at 12:00 PM || Description
|-
! 0
| EXTRASUNNY_LA
| [[File:Weather 0.png|150px|thumb|center|Applies a heat haze effect]]
| rowspan="5" style="margin-left:10px; | In singleplayer, these are '''Los Santos specific weathers'''.<br>They are clear weathers, with blue sky and few clouds.
|-
! 1
| SUNNY_LA
| [[File:Weather 1.png|150px|thumb|center]]
|-
! 2
| EXTRASUNNY_SMOG_LA
| [[File:Weather 2.png|150px|thumb|center]]
|-
! 3
| SUNNY_SMOG_LA
| [[File:Weather 3.png|150px|thumb|center]]
|-
! 4
| CLOUDY_LA
| [[File:Weather 4.png|150px|thumb|center]]
|-
! 5
| SUNNY_SF
| [[File:Weather 5.png|150px|thumb|center]]
| rowspan="5" style="margin-left:10px; | In singleplayer, these are '''San Fierro specific weathers'''.<br>They are more diverse than Los Santos': some of them are clear, but others are rainy or foggy.
|-
! 6
| EXTRASUNNY_SF
| [[File:Weather 6.png|150px|thumb|center]]
|-
! 7
| CLOUDY_SF
| [[File:Weather 7.png|150px|thumb|center]]
|-
! 8
| RAINY_SF
| [[File:Weather 8.png|150px|thumb|center|Starts a thunderstorm, with rain and lighthings]]
|-
! 9
| FOGGY_SF
| [[File:Weather 9.png|150px|thumb|center|Starts a cloudy, dense fog]]
|-
! 10
| SUNNY_VEGAS
| [[File:Weather 10.png|150px|thumb|center]]
| rowspan="3" style="margin-left:10px; | In singleplayer, these are '''Las Venturas specific weathers'''.<br>They are clear, dry weathers.
|-
! 11
| EXTRASUNNY_VEGAS
| [[File:Weather 11.png|150px|thumb|center|Applies scorching hot weather, with a heat haze effect]]
|-
! 12
| CLOUDY_VEGAS
| [[File:Weather 12.png|150px|thumb|center]]
|-
! 13
| EXTRASUNNY_COUNTRYSIDE
| [[File:Weather 13.png|150px|thumb|center]]
| rowspan="4" style="margin-left:10px; | In singleplayer, these are '''Los Santos countryside specific weathers'''.<br>They are dull, hazy, diverse weathers, with rainy ones.
|-
! 14
| SUNNY_COUNTRYSIDE
| [[File:Weather 14.png|150px|thumb|center]]
|-
! 15
| CLOUDY_COUNTRYSIDE
| [[File:Weather 15.png|150px|thumb|center]]
|-
! 16
| RAINY_COUNTRYSIDE
| [[File:Weather 16.png|150px|thumb|center|Starts a thunderstorm]]
|-
! 17
| EXTRASUNNY_DESERT
| [[File:Weather 17.png|150px|thumb|center|Apply a heat haze effect]]
| rowspan="3" style="margin-left:10px; | In singleplayer, these are '''Bone County specific weathers'''.<br>They are clear, dry, scorching hot weathers.
|-
! 18
| SUNNY_DESERT
| [[File:Weather 18.png|150px|thumb|center|Apply a heat haze effect]]
|-
! 19
| SANDSTORM_DESERT
| [[File:Weather 19.png|150px|thumb|center|Starts a dense sandstorm]]
|-
! 20
| UNDERWATER
| [[File:Weather 20.png|150px|thumb|center]]
| style="margin-left:10px; | In singleplayer, this is probably the '''weather used internally when camera is underwater'''.<br>It is greenish and cloudy, so it appears to be a kind of contaminated weather.
|-
! 21
| EXTRACOLOURS_1
| [[File:Weather 21.png|150px|thumb|center|Adds a purple-ish color to the sky and objects]]
| rowspan="2" style="margin-left:10px; | In singleplayer, these are weathers '''used in interiors'''.<br>They are somewhat strange, dark weathers with gradiented skyline colors.
|-
! 22
| EXTRACOLOURS_2
| [[File:Weather 22.png|150px|thumb|center|Adds a black-white sky and a uniform light to objects]]
|-
|}

==Other weather IDs==
* '''23 to 26:''' Pale orange weather.
* '''27 to 29:''' Fresh blue weather.
* '''30 to 32:''' Dark, cloudy, teal weather.
* '''33:''' Dark, cloudy, brown weather.
* '''34:''' Blue/purple, regular weather.
* '''35:''' Dull brown weather.
* '''36 to 38:''' Bright, foggy, orange weather.
* '''39:''' Very bright weather. Night looks like day.
* '''40 to 42:''' Blue/purple, cloudy weather.
* '''43:''' Toxic, contaminated clouds weather.
* '''44:''' Black/white sky weather, similar to '''22'''.
* '''45 to 60:''' Normal seeming weather with graphical bugs at evening.
* '''100:''' Strange weather which makes objects disappear.
* '''118:''' Stormy weather with pink sky and crystal water.
* '''126 to 150:''' Horrible flashing red bugged weather.
* '''151 to 175:''' Far draw distance weather with pink, purple and turquoise clouds.

==See also==
[[id|ID lists]]

[[pl:Weather]]
[[ru:Weather]]
[[es:Climas]]
[[de:Wetter]]

[[Category:ID Lists]]

Material IDs

2017-01-01T18:44:15Z

JHXP: Reverted edits by Marcin778 (talk) to last revision by Cazomino05

=Introduction=
This is a list of GTA:SA's material ID numbers, as listed in the surfinfo.dat.

==Default==
* '''0:''' Default
* '''1:''' Tarmac
* '''2:''' Tarmac (fucked)
* '''3:''' Tarmac (really fucked)

==Concrete==
* '''4:''' Pavement
* '''5:''' Pavement (fucked)
* '''7:''' Concrete (fucked)
* '''8:''' Painted Ground
* '''34:''' Concrete (beach)
* '''89:''' Concrete
* '''127:''' Poolside
* '''135:''' Docklands
* '''136:''' Industrial
* '''137:''' Industrial Jetty
* '''138:''' Concrete (litter)
* '''139:''' Alley Rubbish
* '''144:''' Airport Ground
* '''165:''' Floor (concrete)

==Gravel==
* '''6:''' Gravel
* '''85:''' Roadside
* '''101:''' Rubble
* '''134:''' Building Site
* '''140:''' Junkyard Piles

==Grass==
* '''9:''' Grass (short lush)
* '''10:''' Grass (medium lush)
* '''11:''' Grass (long lush)
* '''12:''' Grass (short dry)
* '''13:''' Grass (medium dry)
* '''14:''' Grass (long dry)
* '''15:''' Golf Grass (rough)
* '''16:''' Golf Grass (smooth)
* '''17:''' Steep Slidy Grass
* '''20:''' Meadow
* '''80:''' Grass (short)
* '''81:''' Grass (meadow)
* '''82:''' Grass (dry)
* '''115:''' Grass (wee flowers)
* '''116:''' Grass (dry tall)
* '''117:''' Grass (lush tall)
* '''118:''' Grass (green mix)
* '''119:''' Grass (brown mix)
* '''120:''' Grass (low)
* '''121:''' Grass (rocky)
* '''122:''' Grass (small trees)
* '''125:''' Grass (weeds)
* '''146:''' Grass (light)
* '''147:''' Grass (lighter)
* '''148:''' Grass (lighter 2)
* '''149:''' Grass (mid 1)
* '''150:''' Grass (mid 2)
* '''151:''' Grass (dark)
* '''152:''' Grass (dark 2)
* '''153:''' Grass (dirt mix)
* '''160:''' Park Grass

==Dirt==
* '''19:''' Flower Bed
* '''21:''' Waste Ground
* '''22:''' Woodland Ground
* '''24:''' Mud (wet)
* '''25:''' Mud (dry)
* '''26:''' Dirt
* '''27:''' Dirt Track
* '''40:''' Corn Field
* '''83:''' Woodland
* '''84:''' Wood Dense
* '''87:''' Flowerbed
* '''88:''' Waste Ground
* '''100:''' Riverbed
* '''110:''' Marsh
* '''123:''' Dirt (rocky)
* '''124:''' Dirt (weeds)
* '''126:''' River Edge
* '''128:''' Forest (stumps)
* '''129:''' Forest (sticks)
* '''130:''' Forest (leaves)
* '''132:''' Forest (dry)
* '''133:''' Sparse Flowers
* '''141:''' Junkyard Ground
* '''142:''' Dump
* '''145:''' Cornfield
* '''155:''' Riverbed (shallow)
* '''156:''' Riverbed (weeds)

==Sand==
* '''28:''' Sand (deep)
* '''29:''' Sand (medium)
* '''30:''' Sand (compact)
* '''31:''' Sand (arid)
* '''32:''' Sand (more)
* '''33:''' Sand (beach)
* '''74:''' Sand
* '''75:''' Sand (dense)
* '''76:''' Sand (arid)
* '''77:''' Sand (compact)
* '''78:''' Sand (rocky)
* '''79:''' Sand (beach)
* '''86:''' Roadside Des
* '''96:''' Underwater (lush)
* '''97:''' Underwater (barren)
* '''98:''' Underwater (coral)
* '''99:''' Underwater (deep)
* '''131:''' Desert Rocks
* '''143:''' Cactus Dense
* '''157:''' Seaweed

==Glass==
* '''45:''' Glass
* '''46:''' Glass Windows (large)
* '''47:''' Glass Windows (small)
* '''175:''' Unbreakable Glass

==Wood==
* '''42:''' Wood (crates)
* '''43:''' Wood (solid)
* '''44:''' Wood (thin)
* '''70:''' Wood (bench)
* '''72:''' Floorboard
* '''73:''' Stairs (wood)
* '''172:''' Wood Picket Fence
* '''173:''' Wood Slatted Fence
* '''174:''' Wood Ranch Fence

==Metal==
* '''50:''' Garage Door
* '''51:''' Thick Metal Plate
* '''52:''' Scaffold Pole
* '''53:''' Lamp Post
* '''54:''' Metal Gate
* '''55:''' Metal Chain fence
* '''56:''' Girder
* '''57:''' Fire Hydrant
* '''58:''' Container
* '''59:''' News Vendor
* '''63:''' Car
* '''64:''' Car (panel)
* '''65:''' Car (moving component)
* '''162:''' Stairs (metal)
* '''164:''' Floor (metal)
* '''167:''' Thin Metal Sheet
* '''168:''' Metal Barrel
* '''171:''' Metal Dumpster

==Stone==
* '''18:''' Steep Cliff
* '''35:''' Rock (dry)
* '''36:''' Rock (wet)
* '''37:''' Rock (cliff)
* '''69:''' Transparent Stone
* '''109:''' Mountain
* '''154:''' Riverbed (stone)
* '''161:''' Stairs (stone)

==Vegetation==
* '''23:''' Vegetation
* '''41:''' Hedge
* '''111:''' Bushy
* '''112:''' Bushy (mix)
* '''113:''' Bushy (dry)
* '''114:''' Bushy (mid)

==Water==
* '''38:''' Water (riverbed)
* '''39:''' Water (shallow)

==Misc==
* '''48:''' Empty1
* '''49:''' Empty2
* '''60:''' Wheelbase
* '''61:''' Cardboard Box
* '''62:''' Ped
* '''66:''' Transparent Cloth
* '''67:''' Rubber
* '''68:''' Plastic
* '''71:''' Carpet
* '''90:''' Office Desk
* '''91:''' 711 Shelf 1
* '''92:''' 711 Shelf 2
* '''93:''' 711 Shelf 3
* '''94:''' Restuarant Table
* '''95:''' Bar Table
* '''102:''' Bedroom Floor
* '''103:''' Kitchen Floor
* '''104:''' Livingroom Floor
* '''105:''' corridor Floor
* '''106:''' 711 Floor
* '''107:''' Fast Food Floor
* '''108:''' Skanky Floor
* '''158:''' Door
* '''159:''' Plastic Barrier
* '''163:''' Stairs (carpet)
* '''166:''' Bin Bag
* '''169:''' Plastic Cone
* '''170:''' Plastic Dumpster
* '''176:''' Hay Bale
* '''177:''' Gore
* '''178:''' Rail Track

=Source=
The group names and readable material names have been extracted from Collision File Editor II by Steve M[http://www.steve-m.com/downloads/tools/colleditor2/].

[[Category:ID Lists]]

[[de:Material IDs]]

Interior IDs

2017-01-01T18:44:13Z

JHXP: Reverted edits by Marcin778 (talk) to last revision by Walid

San Andreas Interior ID list.
<br>
<br>
{| class="wikitable" style="width:50%; text-align:center;"
!colspan="6"|ID 0
|-
| '''Normal world'''
|-
|}
<br>
{| class="wikitable" style="width:50%;"
!colspan="6"|ID 1
|-
! scope="col"| Interior Name
! scope="col"| X
! scope="col"| Y
! scope="col"| Z
|-
| '''Ammu-nation 1''' || 289.7870 || -35.7190 || 1003.5160
|-
| '''Burglary House 1''' || 224.6351 || 1289.012 || 1082.141
|-
| '''The Wellcome Pump (Catalina?)''' || 681.65 || -452.86 || -25.62
|-
| '''Restaurant 1''' || 446.6941 || -9.7977 || 1000.7340
|-
| '''Caligulas Casino''' || 2235.2524 || 1708.5146 || 1010.6129
|-
| '''Denise's Place''' || 244.0892 || 304.8456 || 999.1484
|-
| '''Shamal cabin''' || 1.6127 || 34.7411 || 1199.0
|-
| '''Liberty City''' || -750.80 || 491.00 || 1371.70
|-
| '''Sweet's House''' || 2525.0420 || -1679.1150 || 1015.4990
|-
| '''Transfender''' || 621.7850 || -12.5417 || 1000.9220
|-
| '''Safe House 4''' || 2216.5400 || -1076.2900 || 1050.4840
|-
| '''Trials(Hyman Memorial?) Stadium''' || -1401.13 || 106.110 || 1032.273
|-
| '''Warehouse 1''' || 1405.3120 || -8.2928 || 1000.9130
|-
| '''Doherty Garage''' || -2042.42 || 178.59 || 28.84
|-
| '''Sindacco Abatoir''' || 963.6078 || 2108.3970 || 1011.0300
|-
| '''Sub Urban''' || 203.8173 || -46.5385 || 1001.8050
|-
| '''Wu Zi Mu's Betting place''' || -2159.9260 || 641.4587 || 1052.3820
|-
|}
<br>

{| class="wikitable" style="width:50%;"
!colspan="6"|ID 2
|-
! scope="col"| Interior Name
! scope="col"| X
! scope="col"| Y
! scope="col"| Z
|-
| '''Ryder's House''' || 2464.2110 || -1697.9520 || 1013.5080
|-
| '''Angel Pine Trailer''' || 0.3440 || -0.5140 || 1000.5490¨
|-
| '''The Pig Pen''' || 1213.4330 ||-6.6830 || 1000.9220
|-
| '''BDups Crack Palace''' || 1523.7510 || -46.0458 || 1002.1310
|-
| '''Big Smoke's Crack Palace''' || 2543.6610 || -1303.9320 || 1025.0700
|-
| '''Burglary House 2''' || 225.756 || 1240.000 || 1082.149
|-
| '''Burglary House 3''' || 447.470 || 1398.348 || 1084.305
|-
| '''Burglary House 4''' || 491.740 || 1400.541 || 1080.265
|-
| '''Katie's Place''' || 267.2290 || 304.7100 || 999.1480
|-
| '''Loco Low Co.''' || 612.5910 || -75.6370 || 997.9920
|-
| '''Reece's Barbershop''' || 612.5910 || -75.6370 || 997.9920
|-
|}

<br>
{| class="wikitable" style="width:50%;"
!colspan="6"|ID 3
|-
! scope="col"| Interior Name
! scope="col"| X
! scope="col"| Y
! scope="col"| Z
|-
| '''Jizzy's Pleasure Domes''' || -2636.7190 || 1402.9170 || 906.4609
|-
| '''Brothel''' || 940.6520 || -18.4860 || 1000.9300
|-
| '''Brothel 2''' || 967.5334 || -53.0245 || 1001.1250
|-
| '''BDups Apartment''' || 1527.38 || -11.02 || 1002.10
|-
| '''Bike School''' || 1494.3350 || 1305.6510 || 1093.2890
|-
| '''Big Spread Ranch''' || 1210.2570 || -29.2986 || 1000.8790
|-
| '''LV Tattoo Parlour''' || -204.4390 || -43.6520 || 1002.2990
|-
| '''LVPD HQ''' || 289.7703 || 171.7460 || 1007.1790
|-
| '''OG Loc's House''' || 516.8890 || -18.4120 || 1001.5650
|-
| '''Pro-Laps''' || 207.3560 || -138.0029 || 1003.3130
|-
| '''Las Venturas Planning Dep.''' || 374.6708 || 173.8050 || 1008.3893
|-
| '''Record Label Hallway''' || 1038.2190 || 6.9905 || 1001.2840
|-
| '''Driving School''' || -2027.9200 || -105.1830 || 1035.1720
|-
| '''Johnson House''' || 2496.0500 || -1693.9260 || 1014.7420
|-
| '''Budget Inn Motel Room'''
|-
| '''Burglary House 5''' || 234.733 || 1190.391 || 1080.258
|-
| '''Gay Gordo's Barbershop''' || 418.6530 || -82.6390 || 1001.8050
|-
| '''Helena's Place''' || 292.4459 || 308.7790 || 999.1484
|-
| '''Inside Track Betting''' || 826.8863 || 5.5091 || 1004.4830
|-
| '''Sex Shop''' || -106.7268 || -19.6444 || 1000.7190
|-
| '''Wheel Arch Angels''' || 614.3889 || -124.0991 || 997.9950
|-
|}

<br>
{| class="wikitable" style="width:50%;"
!colspan="6"|ID 4
|-
! scope="col"| Interior Name
! scope="col"| X
! scope="col"| Y
! scope="col"| Z
|-
| '''24/7 shop 1''' || -27.3769 || -27.6416 || 1003.5570
|-
| '''Ammu-Nation 2''' || 285.8000 || -84.5470 || 1001.5390
|-
| '''Burglary House 6''' || -262.91 || 1454.966 || 1084.367
|-
| '''Burglary House 7''' || 221.4296 || 1142.423 || 1082.609
|-
| '''Burglary House 8''' || 261.1168 || 1286.519 || 1080.258
|-
| '''Diner 2''' || 460.0 || -88.43 || 999.62
|-
| '''Dirtbike Stadium''' || -1435.8690 || -662.2505 || 1052.4650
|-
| '''Michelle's Place''' || 302.6404 || 304.8048 || 999.1484
|-
|}

<br>
{| class="wikitable" style="width:50%;"
!colspan="6"|ID 5
|-
! scope="col"| Interior Name
! scope="col"| X
! scope="col"| Y
! scope="col"| Z
|-
| '''Madd Dogg's Mansion''' || 1272.9116 || -768.9028 || 1090.5097
|-
| '''Well Stacked Pizza Co.''' || 377.7758 || -126.2766 || 1001.4920
|-
| '''Victim''' || 221.3310 || -6.6169 || 1005.1977
|-
| '''Burning Desire House''' || 2351.1540 || -1180.5770 || 1027.9770
|-
| '''Barbara's Place'''
|-
| '''Burglary House 9''' || 22.79996 || 1404.642 || 1084.43
|-
| '''Burglary House 10''' || 228.9003 || 1114.477 || 1080.992
|-
| '''Burglary House 11''' || 140.5631 || 1369.051 || 1083.864
|-
| '''The Crack Den''' || 322.1117 || 1119.3270 || 1083.8830
|-
| '''Police Station (Barbara's)''' || 322.72 || 306.43 || 999.15
|-
| '''Diner 1''' || 448.7435 || -110.0457 || 1000.0772
|-
| '''Ganton Gym''' || 768.0793 || 5.8606 || 1000.7160
|-
| '''Vank Hoff Hotel ''' || 2232.8210 || -1110.0180 || 1050.8830
|-
|}

<br>
{| class="wikitable" style="width:50%;"
!colspan="6"|ID 6
|-
! scope="col"| Interior Name
! scope="col"| X
! scope="col"| Y
! scope="col"| Z
|-
| '''Ammu-Nation 3''' || 297.4460 || -109.9680 || 1001.5160
|-
| '''Ammu-Nation 4''' || 317.2380 || -168.0520 || 999.5930
|-
| '''LSPD HQ ''' || 246.4510 || 65.5860 ||1003.6410
|-
| '''Safe House 3''' || 2333.0330 || -1073.9600 || 1049.0230
|-
| '''Safe House 5''' || 2194.2910 || -1204.0150 || 1049.0230
|-
| '''Safe House 6''' || 2308.8710 || -1210.7170 || 1049.0230
|-
| '''Cobra Marital Arts Gym''' || 774.0870 ||-47.9830 || 1000.5860
|-
| '''24/7 shop 2''' || -26.7180 || -55.9860 || 1003.5470
|-
| '''Millie's Bedroom''' || 344.5200 || 304.8210 || 999.1480
|-
| '''Fanny Batter's Brothel''' || 744.2710 || 1437.2530 || 1102.7030
|-
| '''Restaurant 2''' || 443.9810 || -65.2190 || 1050.0000
|-
| '''Burglary House 15''' || 234.319 || 1066.455 || 1084.208
|-
| '''Burglary House 16''' || -69.049 || 1354.056 || 1080.211
|-
|}

<br>

{| class="wikitable" style="width:50%;"
!colspan="6"|ID 7
|-
! scope="col"| Interior Name
! scope="col"| X
! scope="col"| Y
! scope="col"| Z
|-
| '''Ammu-Nation 5 (2 Floors)''' || 315.3850 || -142.2420 || 999.6010
|-
| '''8-Track Stadium''' || -1417.8720 || -276.4260 || 1051.1910
|-
| '''Below the Belt Gym''' || 774.2430 || -76.0090 || 1000.6540
|-
|}

<br>
{| class="wikitable" style="width:50%;"
!colspan="6"|ID 8
|-
! scope="col"| Interior Name
! scope="col"| X
! scope="col"| Y
! scope="col"| Z
|-
| '''Safe house 2'''
|-
| '''Colonel Fuhrberger's House''' || 2807.8990 || -1172.9210 || 1025.5700
|-
| '''Burglary House 22''' || -42.490 || 1407.644 || 1084.43
|-
|}

<br>
{| class="wikitable" style="width:50%;"
!colspan="6"|ID 9
|-
! scope="col"| Interior Name
! scope="col"| X
! scope="col"| Y
! scope="col"| Z
|-
| '''Unknown safe house''' || 2253.1740 || -1139.0100 || 1050.6330
|-
| '''Andromada Cargo hold''' || 315.48 || 984.13 || 1959.11
|-
| '''Burglary House 12''' || 85.32596 || 1323.585 || 1083.859
|-
| '''Burglary House 13''' || 260.3189 || 1239.663 || 1084.258
|-
| '''Cluckin' Bell''' || 365.67 || -11.61 || 1000.87
|-
|}

<br>
{| class="wikitable" style="width:50%;"
!colspan="6"|ID 10
|-
! scope="col"| Interior Name
! scope="col"| X
! scope="col"| Y
! scope="col"| Z
|-
| '''Four Dragons Casino''' || 2009.4140 || 1017.8990 || 994.4680
|-
| '''RC Zero's Battlefield''' || -975.5766 || 1061.1312 || 1345.6719
|-
| '''Burger Shot''' || 366.4220 || -73.4700 || 1001.5080
|-
| '''Burglary House 14''' || 21.241 || 1342.153 || 1084.375
|-
| '''Janitor room(Four Dragons Maintenance)''' || 1891.3960 ||1018.1260 || 31.8820
|-
| '''Safe House 1'''
|-
| '''Hashbury safe house''' || 2264.5231 || -1210.5229 || 1049.0234
|-
| '''24/7 shop 3''' || 6.0780 || -28.6330 || 1003.5490
|-
| '''Abandoned AC Tower''' || 419.6140 || 2536.6030 || 10.0000
|-
| '''SFPD HQ''' || 246.4410 || 112.1640 || 1003.2190
|-
|}

<br>
{| class="wikitable" style="width:50%;"
!colspan="6"|ID 11
|-
! scope="col"| Interior Name
! scope="col"| X
! scope="col"| Y
! scope="col"| Z
|-
| '''The Four Dragons Office''' || 2011.6030 || 1017.0230 || 39.0910
|-
| '''Los Santos safe house'''
|-
| '''Ten Green Bottles Bar''' || 502.3310 || -70.6820 || 998.7570
|-
|}

<br>
{| class="wikitable" style="width:50%;"
!colspan="6"|ID 12
|-
! scope="col"| Interior Name
! scope="col"| X
! scope="col"| Y
! scope="col"| Z
|-
| '''Budget Inn Motel Room'''
|-
| '''The Casino''' || 1132.9450 || -8.6750 || 1000.6800
|-
| '''Macisla's Barbershop''' || 411.6410 || -51.8460 || 1001.8980
|-
| '''Safe house 7''' || 2237.2970 || -1077.9250 || 1049.0230
|-
| '''Modern safe house''' || 2324.4990 || -1147.0710 || 1050.7100
|-
|}

<br>
{| class="wikitable" style="width:50%;"
!colspan="6"|ID 13
|-
! scope="col"| Interior Name
! scope="col"| X
! scope="col"| Y
! scope="col"| Z
|-
|'''LS Atrium''' || 1724.33 || -1625.784 || 20.211
|-
|'''CJ's Garage''' || -2043.966 || 172.932 || 28.835
|-
|}

<br>
{| class="wikitable" style="width:50%;"
!colspan="6"|ID 14
|-
! scope="col"| Interior Name
! scope="col"| X
! scope="col"| Y
! scope="col"| Z
|-
| '''Kickstart Stadium''' || -1464.5360 || 1557.6900 || 1052.5310
|-
| '''Didier Sachs''' || 204.1789 || -165.8740 || 1000.5230
|-
| '''Francis Int. Airport (Front ext.)''' || -1827.1473 || 7.2074 || 1061.1435
|-
| '''Francis Int. Airport (Baggage Claim/Ticket Sales)''' || -1855.5687 || 41.2631 || 1061.1435
|-
| '''Wardrobe''' || 255.7190 || -41.1370 || 1002.0230
|-
|}

<br>
{| class="wikitable" style="width:50%;"
!colspan="6"|ID 15
|-
! scope="col"| Interior Name
! scope="col"| X
! scope="col"| Y
! scope="col"| Z
|-
| '''Binco''' || 207.5430 || -109.0040 || 1005.1330
|-
| '''Blood Bowl Stadium''' || -1394.20 || 987.62 || 1023.96
|-
| '''Jefferson Motel''' || 2217.6250 || -1150.6580 || 1025.7970
|-
| '''Burglary House 17''' || -285.711 || 1470.697 || 1084.375
|-
| '''Burglary House 18''' || 327.808 || 1479.74 || 1084.438
|-
| '''Burglary House 19''' || 375.572 || 1417.439 || 1081.328
|-
| '''Burglary House 20''' || 384.644 || 1471.479 || 1080.195
|-
| '''Burglary House 21''' || 295.467 || 1474.697 || 1080.258
|-
|}

<br>
{| class="wikitable" style="width:50%;"
!colspan="6"|ID 16
|-
! scope="col"| Interior Name
! scope="col"| X
! scope="col"| Y
! scope="col"| Z
|-
| '''24/7 shop 4''' || -25.3730 || -139.6540 || 1003.5470
|-
| '''LS Tattoo Parlour''' || -204.5580 || -25.6970 || 1002.2730
|-
| '''Sumoring? stadium''' || -1400 || 1250 || 1040
|-
|}

<br>
{| class="wikitable" style="width:50%;"
!colspan="6"|ID 17
|-
! scope="col"| Interior Name
! scope="col"| X
! scope="col"| Y
! scope="col"| Z
|-
| '''24/7 shop 5''' || -25.3930 || -185.9110 || 1003.5470
|-
| '''Club''' || 493.4687 || -23.0080 || 1000.6796
|-
| '''Rusty Brown's - Ring Donuts''' || 377.0030 || -192.5070 || 1000.6330
|-
| '''The Sherman's Dam Generator Hall''' || -942.1320 || 1849.1420 || 5.0050
|-
| '''Hemlock Tattoo''' || 377.0030 || -192.5070 || 1000.6330
|-
|}

<br>
{| class="wikitable" style="width:50%;"
!colspan="6"|ID 18
|-
! scope="col"| Interior Name
! scope="col"| X
! scope="col"| Y
! scope="col"| Z
|-
| '''Lil Probe Inn''' || -227.0280 || 1401.2290 || 27.7690
|-
| '''24/7 shop 6''' || -30.9460 || -89.6090 || 1003.5490
|-
| '''Atrium''' || 1726.1370 || -1645.2300 || 20.2260
|-
| '''Warehouse 2''' || 1296.6310 || 0.5920 || 1001.0230
|-
| '''Zip''' || 161.4620 || -91.3940 || 1001.8050
|-
|}

<br>
==Interior Functions==
*[[getElementInterior]]
*[[setElementInterior]]
==See Also==
[[id|ID Lists]]

[[Category:Scripting Concepts]]
[[Category:ID Lists]]

[[de:Interior IDs]]

Garage

2017-01-01T18:44:11Z

JHXP: Reverted edits by Marcin778 (talk) to last revision by Krisu477

Every openable garage in San Andreas can be opened or closed through the [[setGarageOpen]] function.

The garage IDs and their descriptions are listed below:
{{Garages}}

==Garage Functions==
{{Template:Garage_functions}}

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

[[Category:ID Lists]]
[[ru:Garage]]
[[de:Garage]]
[[pl:Garage]]

Character Skins

2017-01-01T18:44:08Z

JHXP: Reverted edits by Marcin778 (talk) to last revision by Tails

Skins that the player may use (pedestrian skins).

*[[All Skins Page]] - Not recommended for slow Internet
*[[Special Skins Page]] - New skins available after MTA 1.1
*[[Gang Skins]]
*[[Female Skins]]
*[[Male Skins]]
<syntaxhighlight lang="lua">
mixedSkins = {0, 1, 2, 7, 9, 10, 11, 12, 13, 14, 15, 16, 17, 18, 19, 20, 21, 22, 23, 24, 25, 26, 27, 28, 29, 30, 31, 32, 33, 34, 35, 36, 37, 38, 39, 40, 41, 43, 44, 45, 46, 47, 48, 49, 50, 51, 52, 53, 54, 55, 56, 57, 58, 59, 60, 61, 62, 63, 64, 66, 67, 68, 69, 70, 71, 72, 73, 75, 76, 77, 78, 79, 80, 81, 82, 83, 84, 85, 87, 88, 89, 90, 91, 92, 93, 94, 95, 96, 97, 98, 99, 100, 101, 102, 103, 104, 105, 106, 107, 108, 109, 110, 111, 112, 113, 114, 115, 116, 117, 118, 120, 121, 122, 123, 124, 125, 126, 127, 128, 129, 130, 131, 132, 133, 134, 135, 136, 137, 138, 139, 140, 141, 142, 143, 144, 145, 146, 147, 148, 150, 151, 152, 153, 154, 155, 156, 157, 158, 159, 160, 161, 162, 163, 164, 165, 166, 167, 168, 169, 170, 171, 172, 173, 174, 175, 176, 177, 178, 179, 180, 181, 182, 183, 184, 185, 186, 187, 188, 189, 190, 191, 192, 193, 194, 195, 196, 197, 198, 199, 200, 201, 202, 203, 204, 205, 206, 207, 209, 210, 211, 212, 213, 214, 215, 216, 217, 218, 219, 220, 221, 222, 223, 224, 225, 226, 227, 228, 229, 230, 231, 232, 233, 234, 235, 236, 237, 238, 239, 240, 241, 242, 243, 244, 245, 246, 247, 248, 249, 250, 251, 252, 253, 254, 255, 256, 257, 258, 259, 260, 261, 262, 263, 264, 265, 266, 267, 268, 269, 270, 271, 272, 274, 275, 276, 277, 278, 279, 280, 281, 282, 283, 284, 285, 286, 287, 288, 290, 291, 292, 293, 294, 295, 296, 297, 298, 299, 300, 301, 302, 303, 304, 305, 306, 307, 308, 309, 310, 311, 312}
maleSkins = {0, 1, 2, 7, 14, 15, 16, 17, 18, 19, 20, 21, 22, 23, 24, 25, 26, 27, 28, 29, 30, 32, 33, 34, 35, 36, 37, 43, 44, 45, 46, 47, 48, 49, 50, 51, 52, 57, 58, 59, 60, 61, 62, 66, 67, 68, 70, 71, 72, 73, 78, 79, 80, 81, 82, 83, 84, 94, 95, 96, 97, 98, 99, 100, 101, 102, 103, 104, 105, 106, 107, 108, 109, 110, 111, 112, 113, 114, 115, 116, 117, 118, 120, 121, 122, 123, 124, 125, 126, 127, 128, 132, 133, 134, 135, 136, 137, 142, 143, 144, 146, 147, 153, 154, 155, 156, 158, 159, 160, 161, 162, 163, 164, 165, 166, 167, 168, 170, 171, 173, 174, 175, 176, 177, 179, 180, 181, 182, 183, 184, 185, 186, 187, 188, 189, 200, 202, 203, 204, 206, 209, 210, 212, 213, 217, 220, 221, 222, 223, 227, 228, 229, 230, 234, 235, 236, 239, 240, 241, 242, 247, 248, 249, 250, 252, 253, 254, 255, 258, 259, 260, 261, 262, 264, 265, 266, 267, 268, 269, 270, 271, 272, 274, 275, 276, 277, 278, 279, 280, 281, 282, 283, 284, 285, 286, 287, 288, 290, 291, 292, 293, 294, 295, 296, 297, 299, 300, 301, 302, 303, 305, 306, 307, 308, 309, 310, 311, 312}
femaleSkins = {9, 10, 11, 12, 13, 31, 38, 39, 40, 41, 53, 54, 55, 56, 63, 64, 69, 75, 76, 77, 85, 87, 88, 89, 90, 91, 92, 93, 129, 130, 131, 138, 139, 140, 141, 145, 148, 150, 151, 152, 157, 169, 172, 178, 190, 191, 192, 193, 194, 195, 196, 197, 198, 199, 201, 205, 207, 211, 214, 215, 216, 218, 219, 224, 225, 226, 231, 232, 233, 237, 238, 243, 244, 245, 246, 251, 256, 257, 263, 298, 304}
</syntaxhighlight>



'''Sectioned Skin Pages:'''
----
*[[Skins Page 1]]: 7, 9-29
*[[Skins Page 2]]: 30-41, 43-52
*[[Skins Page 3]]: 53-64, 66-73, 75-76
*[[Skins Page 4]]: 77-85, 87-99
*[[Skins Page 5]]: 100-118, 120-122
*[[Skins Page 6]]: 123-144
*[[Skins Page 7]]: 145-148, 150-167
*[[Skins Page 8]]: 168-189
*[[Skins Page 9]]: 190-207, 209-212
*[[Skins Page 10]]: 213-234
*[[Skins Page 11]]: 235-238, 240-257
*[[Skins Page 12]]: 258-264, 274-288
*[[Skins Page 13]]: 290-312

==Notes:==
*Last valid skin ID: 312

*The following pairs of IDs produce same character (1st ID used in lists, 2nd disabled)
**118:119
**148:149

*Non-working IDs
**3 4 5 6 8 42 65 74 86 119 149 208 273 289

==Skin functions==
{{Template:Skin_functions}}

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

[[tr:Karakter Tipleri]]
[[it:Skin Personaggi]]
[[ru:Character Skins]]
[[es:Skins de Personajes]]
[[de:Charakterskins]]
[[zh-cn:角色皮肤]]

[[Category:ID Lists]]

Animations

2017-01-01T18:44:06Z

JHXP: Reverted edits by Marcin778 (talk) to last revision by Lexr128

__NOTOC__{{Animations}}
==airport==
* thrw_barl_thrw
==attractors==
* stepsit_in
* stepsit_loop
* stepsit_out
==bar==
* barcustom_get
* barcustom_loop
* barcustom_order
* barman_idle
* barserve_bottle
* barserve_give
* barserve_glass
* barserve_in
* barserve_loop
* barserve_order
* dnk_stndf_loop
* dnk_stndm_loop
==baseball==
* bat_1
* bat_2
* bat_3
* bat_4
* bat_block
* bat_hit_1
* bat_hit_2
* bat_hit_3
* bat_idle
* bat_m
* bat_part
==bd_fire==
* bd_fire1
* bd_fire2
* bd_fire3
* bd_gf_wave
* bd_panic_01
* bd_panic_02
* bd_panic_03
* bd_panic_04
* bd_panic_loop
* grlfrd_kiss_03
* m_smklean_loop
* playa_kiss_03
* wash_up
==beach==
* bather
* lay_bac_loop
* parksit_m_loop
* parksit_w_loop
* sitnwait_loop_w
==benchpress==
* gym_bp_celebrate
* gym_bp_down
* gym_bp_getoff
* gym_bp_geton
* gym_bp_up_a
* gym_bp_up_b
* gym_bp_up_smooth
==bf_injection==
* bf_getin_lhs
* bf_getin_rhs
* bf_getout_lhs
* bf_getout_rhs
==biked==
* biked_back
* biked_drivebyft
* biked_drivebylhs
* biked_drivebyrhs
* biked_fwd
* biked_getoffback
* biked_getofflhs
* biked_getoffrhs
* biked_hit
* biked_jumponl
* biked_jumponr
* biked_kick
* biked_left
* biked_passenger
* biked_pushes
* biked_ride
* biked_right
* biked_shuffle
* biked_still
==bikeh==
* bikeh_back
* bikeh_drivebyft
* bikeh_drivebylhs
* bikeh_drivebyrhs
* bikeh_fwd
* bikeh_getoffback
* bikeh_getofflhs
* bikeh_getoffrhs
* bikeh_hit
* bikeh_jumponl
* bikeh_jumponr
* bikeh_kick
* bikeh_left
* bikeh_passenger
* bikeh_pushes
* bikeh_ride
* bikeh_right
* bikeh_still
==bikeleap==
* bk_blnce_in
* bk_blnce_out
* bk_jmp
* bk_rdy_in
* bk_rdy_out
* struggle_cesar
* struggle_driver
* truck_driver
* truck_getin
==bikes==
* bikes_back
* bikes_drivebyft
* bikes_drivebylhs
* bikes_drivebyrhs
* bikes_fwd
* bikes_getoffback
* bikes_getofflhs
* bikes_getoffrhs
* bikes_hit
* bikes_jumponl
* bikes_jumponr
* bikes_kick
* bikes_left
* bikes_passenger
* bikes_pushes
* bikes_ride
* bikes_right
* bikes_snatch_l
* bikes_snatch_r
* bikes_still
==bikev==
* bikev_back
* bikev_drivebyft
* bikev_drivebylhs
* bikev_drivebyrhs
* bikev_fwd
* bikev_getoffback
* bikev_getofflhs
* bikev_getoffrhs
* bikev_hit
* bikev_jumponl
* bikev_jumponr
* bikev_kick
* bikev_left
* bikev_passenger
* bikev_pushes
* bikev_ride
* bikev_right
* bikev_still
==bike_dbz==
* pass_driveby_bwd
* pass_driveby_fwd
* pass_driveby_lhs
* pass_driveby_rhs
==bmx==
* bmx_back
* bmx_bunnyhop
* bmx_drivebyft
* bmx_driveby_lhs
* bmx_driveby_rhs
* bmx_fwd
* bmx_getoffback
* bmx_getofflhs
* bmx_getoffrhs
* bmx_jumponl
* bmx_jumponr
* bmx_left
* bmx_pedal
* bmx_pushes
* bmx_ride
* bmx_right
* bmx_sprint
* bmx_still
==bomber==
* bom_plant
* bom_plant_2idle
* bom_plant_crouch_in
* bom_plant_crouch_out
* bom_plant_in
* bom_plant_loop
==box==
* boxhipin
* boxhipup
* boxshdwn
* boxshup
* bxhipwlk
* bxhwlki
* bxshwlk
* bxshwlki
* bxwlko
* catch_box
==bsktball==
* bball_def_jump_shot
* bball_def_loop
* bball_def_stepl
* bball_def_stepr
* bball_dnk
* bball_dnk_gli
* bball_dnk_gli_o
* bball_dnk_lnch
* bball_dnk_lnch_o
* bball_dnk_lnd
* bball_dnk_o
* bball_idle
* bball_idle2
* bball_idle2_o
* bball_idleloop
* bball_idleloop_o
* bball_idle_o
* bball_jump_cancel
* bball_jump_cancel_o
* bball_jump_end
* bball_jump_shot
* bball_jump_shot_o
* bball_net_dnk_o
* bball_pickup
* bball_pickup_o
* bball_react_miss
* bball_react_score
* bball_run
* bball_run_o
* bball_skidstop_l
* bball_skidstop_l_o
* bball_skidstop_r
* bball_skidstop_r_o
* bball_walk
* bball_walkstop_l
* bball_walkstop_l_o
* bball_walkstop_r
* bball_walkstop_r_o
* bball_walk_o
* bball_walk_start
* bball_walk_start_o
==buddy==
* buddy_crouchfire
* buddy_crouchreload
* buddy_fire
* buddy_fire_poor
* buddy_reload
==bus==
* bus_close
* bus_getin_lhs
* bus_getin_rhs
* bus_getout_lhs
* bus_getout_rhs
* bus_jacked_lhs
* bus_open
* bus_open_rhs
* bus_pullout_lhs
==camera==
* camcrch_cmon
* camcrch_idleloop
* camcrch_stay
* camcrch_to_camstnd
* camstnd_cmon
* camstnd_idleloop
* camstnd_lkabt
* camstnd_to_camcrch
* piccrch_in
* piccrch_out
* piccrch_take
* picstnd_in
* picstnd_out
* picstnd_take
==car==
* fixn_car_loop
* fixn_car_out
* flag_drop
* sit_relaxed
* tap_hand
* tyd2car_bump
* tyd2car_high
* tyd2car_low
* tyd2car_med
* tyd2car_turnl
* tyd2car_turnr
==carry==
* crry_prtial
* liftup
* liftup05
* liftup105
* putdwn
* putdwn05
* putdwn105
==car_chat==
* carfone_in
* carfone_loopa
* carfone_loopa_to_b
* carfone_loopb
* carfone_loopb_to_a
* carfone_out
* car_sc1_bl
* car_sc1_br
* car_sc1_fl
* car_sc1_fr
* car_sc2_fl
* car_sc3_br
* car_sc3_fl
* car_sc3_fr
* car_sc4_bl
* car_sc4_br
* car_sc4_fl
* car_sc4_fr
* car_talkm_in
* car_talkm_loop
* car_talkm_out
==casino==
* cards_in
* cards_loop
* cards_lose
* cards_out
* cards_pick_01
* cards_pick_02
* cards_raise
* cards_win
* dealone
* manwinb
* manwind
* roulette_bet
* roulette_in
* roulette_loop
* roulette_lose
* roulette_out
* roulette_win
* slot_bet_01
* slot_bet_02
* slot_in
* slot_lose_out
* slot_plyr
* slot_wait
* slot_win_out
* wof
==chainsaw==
* csaw_1
* csaw_2
* csaw_3
* csaw_g
* csaw_hit_1
* csaw_hit_2
* csaw_hit_3
* csaw_part
* idle_csaw
* weapon_csaw
* weapon_csawlo
==choppa==
* choppa_back
* choppa_bunnyhop
* choppa_drivebyft
* choppa_driveby_lhs
* choppa_driveby_rhs
* choppa_fwd
* choppa_getoffback
* choppa_getofflhs
* choppa_getoffrhs
* choppa_jumponl
* choppa_jumponr
* choppa_left
* choppa_pedal
* choppa_pushes
* choppa_ride
* choppa_right
* choppa_sprint
* choppa_still
==clothes==
* clo_buy
* clo_in
* clo_out
* clo_pose_hat
* clo_pose_in
* clo_pose_in_o
* clo_pose_legs
* clo_pose_loop
* clo_pose_out
* clo_pose_out_o
* clo_pose_shoes
* clo_pose_torso
* clo_pose_watch
==coach==
* coach_inl
* coach_inr
* coach_opnl
* coach_opnr
* coach_outl
* coach_outr
==colt45==
* 2guns_crouchfire
* colt45_crouchfire
* colt45_crouchreload
* colt45_fire
* colt45_fire_2hands
* colt45_reload
* sawnoff_reload
==cop_ambient==
* copbrowse_in
* copbrowse_loop
* copbrowse_nod
* copbrowse_out
* copbrowse_shake
* coplook_in
* coplook_loop
* coplook_nod
* coplook_out
* coplook_shake
* coplook_think
* coplook_watch
==cop_dvbyz==
* cop_dvby_b
* cop_dvby_ft
* cop_dvby_l
* cop_dvby_r
==crack==
* bbalbat_idle_01
* bbalbat_idle_02
* crckdeth1
* crckdeth2
* crckdeth3
* crckdeth4
* crckidle1
* crckidle2
* crckidle3
* crckidle4
==crib==
* crib_console_loop
* crib_use_switch
* ped_console_loop
* ped_console_loose
* ped_console_win
==dam_jump==
* dam_dive_loop
* dam_land
* dam_launch
* jump_roll
* sf_jumpwall
==dancing==
* bd_clap
* bd_clap1
* dance_loop
* dan_down_a
* dan_left_a
* dan_loop_a
* dan_right_a
* dan_up_a
* dnce_m_a
* dnce_m_b
* dnce_m_c
* dnce_m_d
* dnce_m_e
==dealer==
* dealer_deal
* dealer_idle
* dealer_idle_01
* dealer_idle_02
* dealer_idle_03
* drugs_buy
* shop_pay
==dildo==
* dildo_1
* dildo_2
* dildo_3
* dildo_block
* dildo_g
* dildo_hit_1
* dildo_hit_2
* dildo_hit_3
* dildo_idle
==dodge==
* cover_dive_01
* cover_dive_02
* crushed
* crush_jump
==dozer==
* dozer_align_lhs
* dozer_align_rhs
* dozer_getin_lhs
* dozer_getin_rhs
* dozer_getout_lhs
* dozer_getout_rhs
* dozer_jacked_lhs
* dozer_jacked_rhs
* dozer_pullout_lhs
* dozer_pullout_rhs
==drivebys==
* gang_drivebylhs
* gang_drivebylhs_bwd
* gang_drivebylhs_fwd
* gang_drivebyrhs
* gang_drivebyrhs_bwd
* gang_drivebyrhs_fwd
* gang_drivebytop_lhs
* gang_drivebytop_rhs
==fat==
* fatidle
* fatidle_armed
* fatidle_csaw
* fatidle_rocket
* fatrun
* fatrun_armed
* fatrun_csaw
* fatrun_rocket
* fatsprint
* fatwalk
* fatwalkstart
* fatwalkstart_csaw
* fatwalkst_armed
* fatwalkst_rocket
* fatwalk_armed
* fatwalk_csaw
* fatwalk_rocket
* idle_tired
==fight_b==
* fightb_1
* fightb_2
* fightb_3
* fightb_block
* fightb_g
* fightb_idle
* fightb_m
* hitb_1
* hitb_2
* hitb_3
==fight_c==
* fightc_1
* fightc_2
* fightc_3
* fightc_block
* fightc_blocking
* fightc_g
* fightc_idle
* fightc_m
* fightc_spar
* hitc_1
* hitc_2
* hitc_3
==fight_d==
* fightd_1
* fightd_2
* fightd_3
* fightd_block
* fightd_g
* fightd_idle
* fightd_m
* hitd_1
* hitd_2
* hitd_3
==fight_e==
* fightkick
* fightkick_b
* hit_fightkick
* hit_fightkick_b
==finale==
* fin_climb_in
* fin_cop1_climbout2
* fin_cop1_loop
* fin_cop1_stomp
* fin_hang_l
* fin_hang_loop
* fin_hang_r
* fin_hang_slip
* fin_jump_on
* fin_land_car
* fin_land_die
* fin_legsup
* fin_legsup_l
* fin_legsup_loop
* fin_legsup_r
* fin_let_go
==finale2==
* fin_cop1_climbout
* fin_cop1_fall
* fin_cop1_loop
* fin_cop1_shot
* fin_cop1_swing
* fin_cop2_climbout
* fin_switch_p
* fin_switch_s
==flame==
* flame_fire
==flowers==
* flower_attack
* flower_attack_m
* flower_hit
==food==
* eat_burger
* eat_chicken
* eat_pizza
* eat_vomit_p
* eat_vomit_sk
* ff_dam_bkw
* ff_dam_fwd
* ff_dam_left
* ff_dam_right
* ff_die_bkw
* ff_die_fwd
* ff_die_left
* ff_die_right
* ff_sit_eat1
* ff_sit_eat2
* ff_sit_eat3
* ff_sit_in
* ff_sit_in_l
* ff_sit_in_r
* ff_sit_look
* ff_sit_loop
* ff_sit_out_180
* ff_sit_out_l_180
* ff_sit_out_r_180
* shp_thank
* shp_tray_in
* shp_tray_lift
* shp_tray_lift_in
* shp_tray_lift_loop
* shp_tray_lift_out
* shp_tray_out
* shp_tray_pose
* shp_tray_return
==freeweights==
* gym_barbell
* gym_free_a
* gym_free_b
* gym_free_celebrate
* gym_free_down
* gym_free_loop
* gym_free_pickup
* gym_free_putdown
* gym_free_up_smooth
==gangs==
* dealer_deal
* dealer_idle
* drnkbr_prtl
* drnkbr_prtl_f
* drugs_buy
* hndshkaa
* hndshkba
* hndshkca
* hndshkcb
* hndshkda
* hndshkea
* hndshkfa
* hndshkfa_swt
* invite_no
* invite_yes
* leanidle
* leanin
* leanout
* prtial_gngtlka
* prtial_gngtlkb
* prtial_gngtlkc
* prtial_gngtlkd
* prtial_gngtlke
* prtial_gngtlkf
* prtial_gngtlkg
* prtial_gngtlkh
* prtial_hndshk_01
* prtial_hndshk_biz_01
* shake_cara
* shake_cark
* shake_carsh
* smkcig_prtl
* smkcig_prtl_f
==ghands==
* gsign1
* gsign1lh
* gsign2
* gsign2lh
* gsign3
* gsign3lh
* gsign4
* gsign4lh
* gsign5
* gsign5lh
* lhgsign1
* lhgsign2
* lhgsign3
* lhgsign4
* lhgsign5
* rhgsign1
* rhgsign2
* rhgsign3
* rhgsign4
* rhgsign5
==ghetto_db==
* gdb_car2_ply
* gdb_car2_smo
* gdb_car2_swe
* gdb_car_ply
* gdb_car_ryd
* gdb_car_smo
* gdb_car_swe
==goggles==
* goggles_put_on
==graffiti==
* graffiti_chkout
* spraycan_fire
==graveyard==
* mrnf_loop
* mrnm_loop
* prst_loopa
==grenade==
* weapon_start_throw
* weapon_throw
* weapon_throwu
==gymnasium==
* gymshadowbox
* gym_bike_celebrate
* gym_bike_fast
* gym_bike_faster
* gym_bike_getoff
* gym_bike_geton
* gym_bike_pedal
* gym_bike_slow
* gym_bike_still
* gym_jog_falloff
* gym_shadowbox
* gym_tread_celebrate
* gym_tread_falloff
* gym_tread_getoff
* gym_tread_geton
* gym_tread_jog
* gym_tread_sprint
* gym_tread_tired
* gym_tread_walk
* gym_walk_falloff
* pedals_fast
* pedals_med
* pedals_slow
* pedals_still
==haircuts==
* brb_beard_01
* brb_buy
* brb_cut
* brb_cut_in
* brb_cut_out
* brb_hair_01
* brb_hair_02
* brb_in
* brb_loop
* brb_out
* brb_sit_in
* brb_sit_loop
* brb_sit_out
==heist9==
* cas_g2_gasko
* swt_wllpk_l
* swt_wllpk_l_back
* swt_wllpk_r
* swt_wllpk_r_back
* swt_wllshoot_in_l
* swt_wllshoot_in_r
* swt_wllshoot_out_l
* swt_wllshoot_out_r
* use_swipecard
==int_house==
* bed_in_l
* bed_in_r
* bed_loop_l
* bed_loop_r
* bed_out_l
* bed_out_r
* lou_in
* lou_loop
* lou_out
* wash_up
==int_office==
* ff_dam_fwd
* off_sit_2idle_180
* off_sit_bored_loop
* off_sit_crash
* off_sit_drink
* off_sit_idle_loop
* off_sit_in
* off_sit_read
* off_sit_type_loop
* off_sit_watch
==int_shop==
* shop_cashier
* shop_in
* shop_looka
* shop_lookb
* shop_loop
* shop_out
* shop_pay
* shop_shelf
==jst_buisness==
* girl_01
* girl_02
* player_01
* smoke_01
==kart==
* kart_getin_lhs
* kart_getin_rhs
* kart_getout_lhs
* kart_getout_rhs
==kissing==
* bd_gf_wave
* gfwave2
* gf_carargue_01
* gf_carargue_02
* gf_carspot
* gf_streetargue_01
* gf_streetargue_02
* gift_get
* gift_give
* grlfrd_kiss_01
* grlfrd_kiss_02
* grlfrd_kiss_03
* playa_kiss_01
* playa_kiss_02
* playa_kiss_03
==knife==
* kill_knife_ped_damage
* kill_knife_ped_die
* kill_knife_player
* kill_partial
* knife_1
* knife_2
* knife_3
* knife_4
* knife_block
* knife_g
* knife_hit_1
* knife_hit_2
* knife_hit_3
* knife_idle
* knife_part
* weapon_knifeidle
==lapdan1==
* lapdan_d
* lapdan_p
==lapdan2==
* lapdan_d
* lapdan_p
==lapdan3==
* lapdan_d
* lapdan_p
==lowrider==
* f_smklean_loop
* lrgirl_bdbnce
* lrgirl_hair
* lrgirl_hurry
* lrgirl_idleloop
* lrgirl_idle_to_l0
* lrgirl_l0_bnce
* lrgirl_l0_loop
* lrgirl_l0_to_l1
* lrgirl_l12_to_l0
* lrgirl_l1_bnce
* lrgirl_l1_loop
* lrgirl_l1_to_l2
* lrgirl_l2_bnce
* lrgirl_l2_loop
* lrgirl_l2_to_l3
* lrgirl_l345_to_l1
* lrgirl_l3_bnce
* lrgirl_l3_loop
* lrgirl_l3_to_l4
* lrgirl_l4_bnce
* lrgirl_l4_loop
* lrgirl_l4_to_l5
* lrgirl_l5_bnce
* lrgirl_l5_loop
* m_smklean_loop
* m_smkstnd_loop
* prtial_gngtlkb
* prtial_gngtlkc
* prtial_gngtlkd
* prtial_gngtlke
* prtial_gngtlkf
* prtial_gngtlkg
* prtial_gngtlkh
* rap_a_loop
* rap_b_loop
* rap_c_loop
* sit_relaxed
* tap_hand
==md_chase==
* carhit_hangon
* carhit_tumble
* donutdrop
* fen_choppa_l1
* fen_choppa_l2
* fen_choppa_l3
* fen_choppa_r1
* fen_choppa_r2
* fen_choppa_r3
* hangon_stun_loop
* hangon_stun_turn
* md_bike_2_hang
* md_bike_jmp_bl
* md_bike_jmp_f
* md_bike_lnd_bl
* md_bike_lnd_die_bl
* md_bike_lnd_die_f
* md_bike_lnd_f
* md_bike_lnd_roll
* md_bike_lnd_roll_f
* md_bike_punch
* md_bike_punch_f
* md_bike_shot_f
* md_hang_lnd_roll
* md_hang_loop
==md_end==
* end_sc1_ply
* end_sc1_ryd
* end_sc1_smo
* end_sc1_swe
* end_sc2_ply
* end_sc2_ryd
* end_sc2_smo
* end_sc2_swe
==medic==
* cpr
==misc==
* bitchslap
* bmx_celebrate
* bmx_comeon
* bmx_idleloop_01
* bmx_idleloop_02
* bmx_talkleft_in
* bmx_talkleft_loop
* bmx_talkleft_out
* bmx_talkright_in
* bmx_talkright_loop
* bmx_talkright_out
* bng_wndw
* bng_wndw_02
* case_pickup
* door_jet
* grab_l
* grab_r
* hiker_pose
* hiker_pose_l
* idle_chat_02
* kat_throw_k
* kat_throw_o
* kat_throw_p
* pass_rifle_o
* pass_rifle_ped
* pass_rifle_ply
* pickup_box
* plane_door
* plane_exit
* plane_hijack
* plunger_01
* plyrlean_loop
* plyr_shkhead
* run_dive
* scratchballs_01
* seat_lr
* seat_talk_01
* seat_talk_02
* seat_watch
* smalplane_door
* smlplane_door
==mtb==
* mtb_back
* mtb_bunnyhop
* mtb_drivebyft
* mtb_driveby_lhs
* mtb_driveby_rhs
* mtb_fwd
* mtb_getoffback
* mtb_getofflhs
* mtb_getoffrhs
* mtb_jumponl
* mtb_jumponr
* mtb_left
* mtb_pedal
* mtb_pushes
* mtb_ride
* mtb_right
* mtb_sprint
* mtb_still
==muscular==
* msclewalkst_armed
* msclewalkst_csaw
* mscle_rckt_run
* mscle_rckt_walkst
* mscle_run_csaw
* muscleidle
* muscleidle_armed
* muscleidle_csaw
* muscleidle_rocket
* musclerun
* musclerun_armed
* musclesprint
* musclewalk
* musclewalkstart
* musclewalk_armed
* musclewalk_csaw
* musclewalk_rocket
==nevada==
* nevada_getin
* nevada_getout
==on_lookers==
* lkaround_in
* lkaround_loop
* lkaround_out
* lkup_in
* lkup_loop
* lkup_out
* lkup_point
* panic_cower
* panic_hide
* panic_in
* panic_loop
* panic_out
* panic_point
* panic_shout
* pointup_in
* pointup_loop
* pointup_out
* pointup_shout
* point_in
* point_loop
* point_out
* shout_01
* shout_02
* shout_in
* shout_loop
* shout_out
* wave_in
* wave_loop
* wave_out
==otb==
* betslp_in
* betslp_lkabt
* betslp_loop
* betslp_out
* betslp_tnk
* wtchrace_cmon
* wtchrace_in
* wtchrace_loop
* wtchrace_lose
* wtchrace_out
* wtchrace_win
==parachute==
* fall_skydive
* fall_skydive_accel
* fall_skydive_die
* fall_skydive_l
* fall_skydive_r
* para_decel
* para_decel_o
* para_float
* para_float_o
* para_land
* para_land_o
* para_land_water
* para_land_water_o
* para_open
* para_open_o
* para_rip_land_o
* para_rip_loop_o
* para_rip_o
* para_steerl
* para_steerl_o
* para_steerr
* para_steerr_o
==park==
* tai_chi_in
* tai_chi_loop
* tai_chi_out
==paulnmac==
* piss_in
* piss_loop
* piss_out
* pnm_argue1_a
* pnm_argue1_b
* pnm_argue2_a
* pnm_argue2_b
* pnm_loop_a
* pnm_loop_b
* wank_in
* wank_loop
* wank_out
==ped==
* abseil
* arrestgun
* atm
* bike_elbowl
* bike_elbowr
* bike_fallr
* bike_fall_off
* bike_pickupl
* bike_pickupr
* bike_pullupl
* bike_pullupr
* bomber
* car_alignhi_lhs
* car_alignhi_rhs
* car_align_lhs
* car_align_rhs
* car_closedoorl_lhs
* car_closedoorl_rhs
* car_closedoor_lhs
* car_closedoor_rhs
* car_close_lhs
* car_close_rhs
* car_crawloutrhs
* car_dead_lhs
* car_dead_rhs
* car_doorlocked_lhs
* car_doorlocked_rhs
* car_fallout_lhs
* car_fallout_rhs
* car_getinl_lhs
* car_getinl_rhs
* car_getin_lhs
* car_getin_rhs
* car_getoutl_lhs
* car_getoutl_rhs
* car_getout_lhs
* car_getout_rhs
* car_hookertalk
* car_jackedlhs
* car_jackedrhs
* car_jumpin_lhs
* car_lb
* car_lb_pro
* car_lb_weak
* car_ljackedlhs
* car_ljackedrhs
* car_lshuffle_rhs
* car_lsit
* car_open_lhs
* car_open_rhs
* car_pulloutl_lhs
* car_pulloutl_rhs
* car_pullout_lhs
* car_pullout_rhs
* car_qjacked
* car_rolldoor
* car_rolldoorlo
* car_rollout_lhs
* car_rollout_rhs
* car_shuffle_rhs
* car_sit
* car_sitp
* car_sitplo
* car_sit_pro
* car_sit_weak
* car_tune_radio
* climb_idle
* climb_jump
* climb_jump2fall
* climb_jump_b
* climb_pull
* climb_stand
* climb_stand_finish
* cower
* crouch_roll_l
* crouch_roll_r
* dam_arml_frmbk
* dam_arml_frmft
* dam_arml_frmlt
* dam_armr_frmbk
* dam_armr_frmft
* dam_armr_frmrt
* dam_legl_frmbk
* dam_legl_frmft
* dam_legl_frmlt
* dam_legr_frmbk
* dam_legr_frmft
* dam_legr_frmrt
* dam_stomach_frmbk
* dam_stomach_frmft
* dam_stomach_frmlt
* dam_stomach_frmrt
* door_lhinge_o
* door_rhinge_o
* drivebyl_l
* drivebyl_r
* driveby_l
* driveby_r
* drive_boat
* drive_boat_back
* drive_boat_l
* drive_boat_r
* drive_l
* drive_lo_l
* drive_lo_r
* drive_l_pro
* drive_l_pro_slow
* drive_l_slow
* drive_l_weak
* drive_l_weak_slow
* drive_r
* drive_r_pro
* drive_r_pro_slow
* drive_r_slow
* drive_r_weak
* drive_r_weak_slow
* drive_truck
* drive_truck_back
* drive_truck_l
* drive_truck_r
* drown
* duck_cower
* endchat_01
* endchat_02
* endchat_03
* ev_dive
* ev_step
* facanger
* facgum
* facsurp
* facsurpm
* factalk
* facurios
* fall_back
* fall_collapse
* fall_fall
* fall_front
* fall_glide
* fall_land
* fall_skydive
* fight2idle
* fighta_1
* fighta_2
* fighta_3
* fighta_block
* fighta_g
* fighta_m
* fightidle
* fightshb
* fightshf
* fightsh_bwd
* fightsh_fwd
* fightsh_left
* fightsh_right
* flee_lkaround_01
* floor_hit
* floor_hit_f
* fucku
* gang_gunstand
* gas_cwr
* getup
* getup_front
* gum_eat
* guncrouchbwd
* guncrouchfwd
* gunmove_bwd
* gunmove_fwd
* gunmove_l
* gunmove_r
* gun_2_idle
* gun_butt
* gun_butt_crouch
* gun_stand
* handscower
* handsup
* hita_1
* hita_2
* hita_3
* hit_back
* hit_behind
* hit_front
* hit_gun_butt
* hit_l
* hit_r
* hit_walk
* hit_wall
* idlestance_fat
* idlestance_old
* idle_armed
* idle_chat
* idle_csaw
* idle_gang1
* idle_hbhb
* idle_rocket
* idle_stance
* idle_taxi
* idle_tired
* jetpack_idle
* jog_femalea
* jog_malea
* jump_glide
* jump_land
* jump_launch
* jump_launch_r
* kart_drive
* kart_l
* kart_lb
* kart_r
* kd_left
* kd_right
* ko_shot_face
* ko_shot_front
* ko_shot_stom
* ko_skid_back
* ko_skid_front
* ko_spin_l
* ko_spin_r
* pass_smoke_in_car
* phone_in
* phone_out
* phone_talk
* player_sneak
* player_sneak_walkstart
* roadcross
* roadcross_female
* roadcross_gang
* roadcross_old
* run_1armed
* run_armed
* run_civi
* run_csaw
* run_fat
* run_fatold
* run_gang1
* run_left
* run_old
* run_player
* run_right
* run_rocket
* run_stop
* run_stopr
* run_wuzi
* seat_down
* seat_idle
* seat_up
* shot_leftp
* shot_partial
* shot_partial_b
* shot_rightp
* shove_partial
* smoke_in_car
* sprint_civi
* sprint_panic
* sprint_wuzi
* swat_run
* swim_tread
* tap_hand
* tap_handp
* turn_180
* turn_l
* turn_r
* walk_armed
* walk_civi
* walk_csaw
* walk_doorpartial
* walk_drunk
* walk_fat
* walk_fatold
* walk_gang1
* walk_gang2
* walk_old
* walk_player
* walk_rocket
* walk_shuffle
* walk_start
* walk_start_armed
* walk_start_csaw
* walk_start_rocket
* walk_wuzi
* weapon_crouch
* woman_idlestance
* woman_run
* woman_runbusy
* woman_runfatold
* woman_runpanic
* woman_runsexy
* woman_walkbusy
* woman_walkfatold
* woman_walknorm
* woman_walkold
* woman_walkpro
* woman_walksexy
* woman_walkshop
* xpressscratch
==player_dvbys==
* plyr_drivebybwd
* plyr_drivebyfwd
* plyr_drivebylhs
* plyr_drivebyrhs
==playidles==
* shift
* shldr
* stretch
* strleg
* time
==police==
* coptraf_away
* coptraf_come
* coptraf_left
* coptraf_stop
* cop_getoutcar_lhs
* cop_move_fwd
* crm_drgbst_01
* door_kick
* plc_drgbst_01
* plc_drgbst_02
==pool==
* pool_chalkcue
* pool_idle_stance
* pool_long_shot
* pool_long_shot_o
* pool_long_start
* pool_long_start_o
* pool_med_shot
* pool_med_shot_o
* pool_med_start
* pool_med_start_o
* pool_place_white
* pool_short_shot
* pool_short_shot_o
* pool_short_start
* pool_short_start_o
* pool_walk
* pool_walk_start
* pool_xlong_shot
* pool_xlong_shot_o
* pool_xlong_start
* pool_xlong_start_o
==poor==
* winwash_start
* winwash_wash2beg
==python==
* python_crouchfire
* python_crouchreload
* python_fire
* python_fire_poor
* python_reload
==quad==
* quad_back
* quad_driveby_ft
* quad_driveby_lhs
* quad_driveby_rhs
* quad_fwd
* quad_getoff_b
* quad_getoff_lhs
* quad_getoff_rhs
* quad_geton_lhs
* quad_geton_rhs
* quad_hit
* quad_kick
* quad_left
* quad_passenger
* quad_reverse
* quad_ride
* quad_right
==quad_dbz==
* pass_driveby_bwd
* pass_driveby_fwd
* pass_driveby_lhs
* pass_driveby_rhs
==rapping==
* laugh_01
* rap_a_in
* rap_a_loop
* rap_a_out
* rap_b_in
* rap_b_loop
* rap_b_out
* rap_c_loop
==rifle==
* rifle_crouchfire
* rifle_crouchload
* rifle_fire
* rifle_fire_poor
* rifle_load
==riot==
* riot_angry
* riot_angry_b
* riot_challenge
* riot_chant
* riot_fuku
* riot_punches
* riot_shout
==rob_bank==
* cat_safe_end
* cat_safe_open
* cat_safe_open_o
* cat_safe_rob
* shp_handsup_scr
==rocket==
* idle_rocket
* rocketfire
* run_rocket
* walk_rocket
* walk_start_rocket
==rustler==
* plane_align_lhs
* plane_close
* plane_getin
* plane_getout
* plane_open
==ryder==
* ryd_beckon_01
* ryd_beckon_02
* ryd_beckon_03
* ryd_die_pt1
* ryd_die_pt2
* van_crate_l
* van_crate_r
* van_fall_l
* van_fall_r
* van_lean_l
* van_lean_r
* van_pickup_e
* van_pickup_s
* van_stand
* van_stand_crate
* van_throw
==scratching==
* scdldlp
* scdlulp
* scdrdlp
* scdrulp
* sclng_l
* sclng_r
* scmid_l
* scmid_r
* scshrtl
* scshrtr
* sc_ltor
* sc_rtol
==shamal==
* shamal_align
* shamal_getin_lhs
* shamal_getout_lhs
* shamal_open
==shop==
* rob_2idle
* rob_loop
* rob_loop_threat
* rob_shifty
* rob_stickup_in
* shp_duck
* shp_duck_aim
* shp_duck_fire
* shp_gun_aim
* shp_gun_duck
* shp_gun_fire
* shp_gun_grab
* shp_gun_threat
* shp_handsup_scr
* shp_jump_glide
* shp_jump_land
* shp_jump_launch
* shp_rob_givecash
* shp_rob_handsup
* shp_rob_react
* shp_serve_end
* shp_serve_idle
* shp_serve_loop
* shp_serve_start
* smoke_ryd
==shotgun==
* shotgun_crouchfire
* shotgun_fire
* shotgun_fire_poor
==silenced==
* crouchreload
* silencecrouchfire
* silence_fire
* silence_reload
==skate==
* skate_idle
* skate_run
* skate_sprint
==smoking==
* f_smklean_loop
* m_smklean_loop
* m_smkstnd_loop
* m_smk_drag
* m_smk_in
* m_smk_loop
* m_smk_out
* m_smk_tap
==sniper==
* weapon_sniper
==spraycan==
* spraycan_fire
* spraycan_full
==strip==
* ply_cash
* pun_cash
* pun_holler
* pun_loop
* strip_a
* strip_b
* strip_c
* strip_d
* strip_e
* strip_f
* strip_g
* str_a2b
* str_b2a
* str_b2c
* str_c1
* str_c2
* str_c2b
* str_loop_a
* str_loop_b
* str_loop_c
==sunbathe==
* batherdown
* batherup
* lay_bac_in
* lay_bac_out
* parksit_m_idlea
* parksit_m_idleb
* parksit_m_idlec
* parksit_m_in
* parksit_m_out
* parksit_w_idlea
* parksit_w_idleb
* parksit_w_idlec
* parksit_w_in
* parksit_w_out
* sbathe_f_lieb2sit
* sbathe_f_out
* sitnwait_in_w
* sitnwait_out_w
==swat==
* gnstwall_injurd
* jmp_wall1m_180
* rail_fall
* rail_fall_crawl
* swt_breach_01
* swt_breach_02
* swt_breach_03
* swt_go
* swt_lkt
* swt_sty
* swt_vent_01
* swt_vent_02
* swt_vnt_sht_die
* swt_vnt_sht_in
* swt_vnt_sht_loop
* swt_wllpk_l
* swt_wllpk_l_back
* swt_wllpk_r
* swt_wllpk_r_back
* swt_wllshoot_in_l
* swt_wllshoot_in_r
* swt_wllshoot_out_l
* swt_wllshoot_out_r
==sweet==
* ho_ass_slapped
* lafin_player
* lafin_sweet
* plyr_hndshldr_01
* sweet_ass_slap
* sweet_hndshldr_01
* sweet_injuredloop
==swim==
* swim_breast
* swim_crawl
* swim_dive_under
* swim_glide
* swim_jumpout
* swim_tread
* swim_under
==sword==
* sword_1
* sword_2
* sword_3
* sword_4
* sword_block
* sword_hit_1
* sword_hit_2
* sword_hit_3
* sword_idle
* sword_part
==tank==
* tank_align_lhs
* tank_close_lhs
* tank_doorlocked
* tank_getin_lhs
* tank_getout_lhs
* tank_open_lhs
==tattoos==
* tat_arml_in_o
* tat_arml_in_p
* tat_arml_in_t
* tat_arml_out_o
* tat_arml_out_p
* tat_arml_out_t
* tat_arml_pose_o
* tat_arml_pose_p
* tat_arml_pose_t
* tat_armr_in_o
* tat_armr_in_p
* tat_armr_in_t
* tat_armr_out_o
* tat_armr_out_p
* tat_armr_out_t
* tat_armr_pose_o
* tat_armr_pose_p
* tat_armr_pose_t
* tat_back_in_o
* tat_back_in_p
* tat_back_in_t
* tat_back_out_o
* tat_back_out_p
* tat_back_out_t
* tat_back_pose_o
* tat_back_pose_p
* tat_back_pose_t
* tat_back_sit_in_p
* tat_back_sit_loop_p
* tat_back_sit_out_p
* tat_bel_in_o
* tat_bel_in_t
* tat_bel_out_o
* tat_bel_out_t
* tat_bel_pose_o
* tat_bel_pose_t
* tat_che_in_o
* tat_che_in_p
* tat_che_in_t
* tat_che_out_o
* tat_che_out_p
* tat_che_out_t
* tat_che_pose_o
* tat_che_pose_p
* tat_che_pose_t
* tat_drop_o
* tat_idle_loop_o
* tat_idle_loop_t
* tat_sit_in_o
* tat_sit_in_p
* tat_sit_in_t
* tat_sit_loop_o
* tat_sit_loop_p
* tat_sit_loop_t
* tat_sit_out_o
* tat_sit_out_p
* tat_sit_out_t
==tec==
* tec_crouchfire
* tec_crouchreload
* tec_fire
* tec_reload
==train==
* tran_gtup
* tran_hng
* tran_ouch
* tran_stmb
==truck==
* truck_align_lhs
* truck_align_rhs
* truck_closedoor_lhs
* truck_closedoor_rhs
* truck_close_lhs
* truck_close_rhs
* truck_getin_lhs
* truck_getin_rhs
* truck_getout_lhs
* truck_getout_rhs
* truck_jackedlhs
* truck_jackedrhs
* truck_open_lhs
* truck_open_rhs
* truck_pullout_lhs
* truck_pullout_rhs
* truck_shuffle
==uzi==
* uzi_crouchfire
* uzi_crouchreload
* uzi_fire
* uzi_fire_poor
* uzi_reload
==van==
* van_close_back_lhs
* van_close_back_rhs
* van_getin_back_lhs
* van_getin_back_rhs
* van_getout_back_lhs
* van_getout_back_rhs
* van_open_back_lhs
* van_open_back_rhs
==vending==
* vend_drink2_p
* vend_drink_p
* vend_eat1_p
* vend_eat_p
* vend_use
* vend_use_pt2
==vortex==
* car_jumpin_lhs
* car_jumpin_rhs
* vortex_getout_lhs
* vortex_getout_rhs
==wayfarer==
* wf_back
* wf_drivebyft
* wf_drivebylhs
* wf_drivebyrhs
* wf_fwd
* wf_getoffback
* wf_getofflhs
* wf_getoffrhs
* wf_hit
* wf_jumponl
* wf_jumponr
* wf_kick
* wf_left
* wf_passenger
* wf_pushes
* wf_ride
* wf_right
* wf_still
==weapons==
* shp_1h_lift
* shp_1h_lift_end
* shp_1h_ret
* shp_1h_ret_s
* shp_2h_lift
* shp_2h_lift_end
* shp_2h_ret
* shp_2h_ret_s
* shp_ar_lift
* shp_ar_lift_end
* shp_ar_ret
* shp_ar_ret_s
* shp_g_lift_in
* shp_g_lift_out
* shp_tray_in
* shp_tray_out
* shp_tray_pose
==wuzi==
* cs_dead_guy
* cs_plyr_pt1
* cs_plyr_pt2
* cs_wuzi_pt1
* cs_wuzi_pt2
* walkstart_idle_01
* wuzi_follow
* wuzi_greet_plyr
* wuzi_greet_wuzi
* wuzi_grnd_chk
* wuzi_stand_loop
* wuzi_walk
<br>
==Animation Functions==
{{Animation_functions}}
==See Also==
[[id|ID Lists]]

[[Category:ID Lists]]

[[de:Animationen]]
[[zh-cn:动画]]

Writing Gamemodes

2017-01-01T18:44:04Z

JHXP: Reverted edits by Marcin778 (talk) to last revision by MrTasty

This guide tries to outline the process of how to write a proper gamemode. If you just started with scripting for MTA, you may want to check the other scripting tutorials at the [[Main Page]] first.
==Introduction==
A gamemode is a resource that, once started, controls all of the gameplay. This may include telling the players what to do, spawning players, creating teams, defining what the players have to do to win or to get points and much more. Examples are Race and Deathmatch.

==What does "proper gamemode" mean?==
To put it simply, a proper gamemode is one that makes full use of MTA's .map file system. This means that the gamemode code does not have any map-specific data hardcoded in it, like positions of players or cars. Instead, the gamemode should be able to load .map files which define these data. This way the gamemode can have multiple maps; also, people can create .map files for the gamemode with MTA's map editor, which is much more convenient than writing code.

An obvious example of a "proper gamemode" is MTA:Race. It allows usermade maps with lots of possibilities within the .map file. To alter spawnpoints, objects etc., the user doesn't need to edit the gamemode itself.

===Map Files===
Map files are basically XML documents with a .map extension. They define an environment to play one or more specific gamemodes in. They are however not supposed to change the rules of the game - those are defined by the gamemode.

Each element in a map corresponds to a node in the .map file. There is standard syntax for common things like spawnpoints, objects and vehicles; however, for "special", gamemode specific information, you need to invent your own syntax.

====Example====
Let's take a Capture the Flag gamemode as an example. A map for this gamemode needs to mainly define spawnpoints and flag locations, and eventually objects and vehicles. A simplified map file could look like this:
<syntaxhighlight lang="xml">
<map>
<spawnpoint id="spawnpoint1" posX="1959.5487060547" posY="-1714.4613037109" posZ="877.25219726563" rot="63.350006103516" model="0"/>
<pickup id="Armor 1" posX="1911.083984375" posY="-1658.8798828125" posZ="885.40216064453" type="armor" health="50" respawn="60000"/>
<flag posX="1959.5487060547" posY="-1714.4613037109" posZ="877.25219726563" team="blue" />
...
</map>
</syntaxhighlight>

Here you can see two MTA elements - a spawnpoint and a pickup. More importantly, this .map has a custom "flag" node which defines the position and color of the flag. The spawnpoint and pickup can be handled by existing external resources, custom elements have to be processed by the gamemode.

To summarize - we want mass mapper input as we saw in MTA:Race. Users should NOT have to touch the gamemode script itself at all.

====Example of getting the .map information====
As mentioned above, your gamemode needs de retrieve custom elements that are defined in a map file and process them. This is quite easy as demonstrated below.
<syntaxhighlight lang="lua">
-- retrieve a table with all flag elements
local flagElements = getElementsByType ( "flag" )
-- loop through them
for key, value in pairs(flagElements) do
-- get our info
local posX = getElementData ( value, "posX" )
local posY = getElementData ( value, "posY" )
local posZ = getElementData ( value, "posZ" )
local team = getElementData ( value, "team" )
-- create an object according to the flag position
createObject ( 1337, posX, posY, posZ )
-- output the team that we created a base for
outputChatBox ( "Base for team " .. team .. " created" )
end
</syntaxhighlight>
The [[getElementsByType]] function retrieves a table of all the elements of a certain type (the type corresponds to the node name in the .map file). This works for both custom types and built-in MTA types (like "vehicle" or "player").
[[getElementData]] can be used to retrieve the xml attributes set in the .map file.
In this simple example, an object is created at the flag's location and a message is outputted in the chatbox. In reality, you will of course need to do more during map loading, like in this case setting up collision shapes to detect players taking the flag.

==Map manager==
Having read the section above it should be clear that a gamemode should always consist of two parts:
* The gamemode resource that always stays the same
* Many different maps resources that give the gamemode map-specific information

Now instead of writing a map-loader for every single gamemode, the [[Map manager]] provides functions to load gamemodes and maps. Simply put, when you enter the correct command (for example 'gamemode ctf ctf-italy') it will start both resources 'ctf' and 'ctf-italy' while triggering an event ([[onGamemodeMapStart]]) to tell the 'ctf' resource that a map was loaded. The 'ctf' resource can then access the information 'ctf-italy' contains and start spawning players etc.

===How to use the mapmanager===
To use the mapmanager service, your gamemode resource has to be tagged as such first. More specifically you'll be setting the "type" attribute of its <info> tag to "gamemode" inside meta.xml. Also, you can set the "name" attribute to a friendly name (like "Capture the flag") that will be shown on ASE instead of the resource name.
<syntaxhighlight lang="xml">

<meta>
<info type="gamemode" name="Cow catapulting 2.0"/>
</meta>
</syntaxhighlight>

If your gamemode is going to load custom maps, you should add handlers for
* onGamemodeMapStart
* onGamemodeMapStop (if any unloading is necessary)
These are fired when a map for your gamemode is started or stopped, and pass the map resource as a parameter.
Within the handler function for these events you can extract all info you need from the resource's map files and configuration files.

====Example====
<syntaxhighlight lang="lua">
function startCtfMap( startedMap ) -- startedMap contains a reference to the resource of the map
local mapRoot = getResourceRootElement( startedMap ) -- get the root node of the started map
local flagElements = getElementsByType ( "flag" , mapRoot ) -- get all flags in the map and store them in a table
-- go on loading information like in the example above
-- spawn players etc.
end
addEventHandler("onGamemodeMapStart", getRootElement(), startCtfMap)
</syntaxhighlight>

===Making maps compatible===
Maps are separate resources. This is done so no editing of the gamemode resource is ever necessary in order to create a custom map, and also allows you to pack map-specific scripts/config files with them.

To make a map compatible with your gamemode, open its resource's meta.xml and tag it as well: the "type" attribute must be set to "map", and the "gamemodes" attribute must be a comma-separated list (no spaces) of gamemode resource names that the map works with.
<syntaxhighlight lang="xml">

<meta>
<info type="map" gamemodes="cowcatapult,assault,tdm"/>
</meta>
</syntaxhighlight>

Once you have everything set up, admins will use these two commands to start/stop gamemodes:
/gamemode gamemodeName [mapName] (optional parameter allows picking an initial map, defaults to none)
/changemap mapName [gamemodeName] (optional parameter specifies the gamemode to start the map with, defaults to the current one)

[[Map manager]] exports a few more access functions which you don't have to use, but may be useful.

==What else should you do==
There are several other resources that gamemodes should use/be compliant with.

===Helpmanager===
The helpmanager is ought to be the standard interface for players when they need help. If you use the helpmanager to display your gamemode's help, every player that used helpmanager before (e.g. in other gamemodes) will immediately know how to get there. It also displays help for different resources running resources in one window, if necessary.

There are basicially two ways to use the helpmanager:
* Provide a simple text that explains how to use your gamemode
* Request a GUI element from the helpmanager that will be displayed in its own tab in the helpmanager window and lets you add any GUI elements to it. This is the recommended way for gamemodes that need to display more complex information that needs its own GUI.

Read the [[Resource:Helpmanager|helpmanager help page]] for details on how to do it.

===Scoreboard===
Scoreboard displays players and teams currently ingame. You add custom columns to it to provide map specific information. For example the column 'points' in the 'ctf' gamemode could represent the player's points gained through kills or captures. As usual, see the [[Resource:Dxscoreboard|scoreboard help page]] for more information.

===Map cycler===
The map cycler controls what gamemodes and maps are played on a server. You can specifiy for example how many times in a row a map will be played until it switches to the next. To achieve this, you need to tell the map cycler when your gamemode finished (e.g. when a round ends).

[[it:Scrivere una gamemode]]
[[ru:Writing Gamemodes]]
[[de:Gamemodes schreiben]]
[[Category:Tutorials]]

Access Control List

2017-01-01T18:44:01Z

JHXP: Reverted edits by Marcin778 (talk) to last revision by Talidan

MTA includes a complete Access Control List (ACL) that allows you to secure and limit access to the server, its functions and resources in any number of ways.

The key concept of MTA's ACL (and ACLs in general) is that you're giving a specific object a set of rights. In MTA's case objects are one of two things - resources or users. There are numerous ''rights'' available in MTA - these mainly focus on server-side scripting functions.

What this essentially means is that the ACL allows you to choose exactly what functions a resource or user can perform. This can obviously be invaluable - for example preventing all your server's players from being able to ban each other, or preventing your new untested resources from doing the same.

Of course, ''with great power comes great responsibility'' and it is very easily possible to completely break resources - for example, disabling [[spawnPlayer]] for all resources would be a Bad Thing. Of course, there are situations when you might want to do this - if you want to force all your resources to use a spawn manager resource for example, but even this is somewhat draconian.

==Understanding the ACL==
There are two major components to the ACL: groups and ACL lists. They appear as '''<group name="">''' nodes and '''<acl name="" />''' nodes. Their purpose is to:<br \>
'''1.''' Grant users permission to control the server and use resource commands. Examples:''<br \>
*Allowing only admins to use the giveweapon function of freeroam
*Allowing all users to start a resource
'''2.''' Grant resources permission to use script functions and functions of other resources. Examples:<br \>
*Allowing a resource to use the restartResource function
*Allowing a resource to use the call function to use exported functions from another script

===Default Groups===
MTA has provided some default groups with increasing permissions. These groups are:
*'''Everyone'''
*'''Moderator'''
*'''SuperModerator'''
*'''Admin'''
*'''Console''' - This controls permissions of people who are using the console through '''<object name="user.Console" />'''
*'''RPC''' - Remote Procedure Call. Specifically grants access to [[callRemote]] only and disables commands of default resources. Check the function for details.
<br \>

To explain further, I will use the Everyone group as an example. By default it looks like this:
<syntaxhighlight lang="xml"> <group name="Everyone">
<acl name="Default" />
<object name="user.*" />
<object name="resource.*" />
</group>
</syntaxhighlight>
<br \>
You will first notice the acl name inside the group. It defines what permissions the group has. Users and resources in this group will have the permissions specified on the "Default" acl name list. ''Note: You will notice this group is special, in that it includes every user and resource by using a '''wildcard (*)''' where the user or resource name would be.''

Now, scroll further down the ACL and you will see the '''<acl name="Default" />''' listing. Note I have trimmed this list dramatically due to its length.

<syntaxhighlight lang="xml"> <acl name="Default">
<right name="command.start" access="false" />
<right name="command.stop" access="false" />
<right name="command.stopall" access="false" />
...etc etc...
<right name="function.executeCommandHandler" access="false" />
<right name="function.setPlayerMuted" access="false" />
<right name="function.restartResource" access="false" />
...etc etc...
<right name="general.adminpanel" access="false" />
<right name="general.tab_players" access="false" />
<right name="general.tab_resources" access="false" />
...etc etc...
<right name="command.freeze" access="false" />
<right name="command.shout" access="false" />
<right name="command.spectate" access="false" />
...etc etc...
</acl>
</syntaxhighlight>
<br \>
*'''Function''' entries are MTA scripting functions. For example, if a resource needed to use restartResource and was only in the 'Everyone' group (with the 'Default' list), it would be denied access to restartResource and fail to work correctly.
*'''Commands''' are created when a resource uses [[addCommandHandler]]. An example would be typing '''/createvehicle [vehicle]''' in the chatbox for the freeroam resource. This controls whether users in the group using this ACL can use the command. ''Note: commands have no effect on resources within the group. Commands are only related to users.''
**''General is a custom right name group created by the admin resource but it works on the same principles. The script works with them by using [[hasObjectPermissionTo]]''

You will notice some groups such as admin have multiple '''<acl name="" />''' nodes. An example is the admin group:
<syntaxhighlight lang="xml">
<group name="Admin">
<acl name="Moderator" />
<acl name="SuperModerator" />
<acl name="Admin" />
<acl name="RPC" />
<object name="resource.admin" />
<object name="resource.webadmin" />
<object name="user.Ransom" />
</group>
</syntaxhighlight>

This gives all the permissions defined in each '''<acl name="" />''' node in order of listing. So for example, the admin group makes sure all the permissions are given to admins by using all the lists. If there are any conflicts, the lowest entry wins. For example, pretend these 2 acls were in a group in the following order:

'''1.''' '''<acl name="Default">''' sets <right name="general.ModifyOtherObjects" access="false" /> <br/>
'''2.''' '''<acl name="Admin">''' sets <right name="general.ModifyOtherObjects" access="true" /> <br/>
'''3.''' For all users and resources in group admin: <right name="general.ModifyOtherObjects" access="true" /><br/>
<br/>

=== Resource Groups and ACLs ===
You will notice there are some other groups that came with MTA. These were defined by resources that came with MTA. If a resource wants to designate specific ACL rights not provided by the default MTA groups, it can create its own ACL name and a group to use it. I will show AMX's entry as an example. AMX is designed to emulate SA-MP scripts and it needs a certain set of permissions that doesn't fit the default groups well. It is shown below:

<syntaxhighlight lang="xml">
<group name="AMX">
<acl name="AMX" />
<object name="resource.amx" />
</group>

<acl name="AMX">
<right name="general.ModifyOtherObjects" access="true" />
<right name="function.startResource" access="true" />
<right name="function.stopResource" access="true" />
<right name="general.adminpanel" access="false" />
...etc etc...
<right name="command.kick" access="false" />
<right name="command.freeze" access="false" />
<right name="command.mute" access="false" />
...etc etc...
</acl>
</syntaxhighlight>

==Modifying the ACL==
There are three ways you can modify the ACL - how you do it depends who you are.

===HTTP Interface===
You can use the [[Resource/webadmin|webadmin]] http interface to modify the ACL in your web browser. This is by far the easiest way to do so. Just make sure the ''webadmin'' resource is started on your server and visit ''<nowiki>http://ServerIP:HttpPort/</nowiki>''. You can then use the two sections - ACLs and Groups. ACLs allows you to create your Access Control Lists - lists of rights. Groups allow you to group together collections of users and assign ACLs to them. For example, the ACLs section allows you to specify that the Admin ACL has access to the ''start'' console command. You can the go to the Groups section and create an Admin ''group'' that has access to your Admin ''acl''. You can then add users to your Admin ''group''.

===XML file===
You can modify the ACL.xml file manually. This has a fairly straightforward syntax, but it can get a bit confusing at times. If you do it while the server is running, don't forget to call the scripting function [[aclReload]] ("start runcode", "run aclReload()") so the new ACL is loaded, or otherwise stop your server before modifying. This also prevents your changes from being accidentally overwritten by the server.

===Scripting functions===
You can use a large number of ACL scripting functions to modify the ACL on the fly. Of course, you can (and really should!) limit access to the ACL functions with the ACL. Note that the '''admin resource''' that comes with MTA can be used to manage the ACL from the resources tab. You must be setup as admin to use the admin panel. [http://wiki.multitheftauto.com/wiki/Admin Click here for admin setup instructions].

==See Also==
{{ACL functions}}
[[Category:Scripting Concepts]]
[[ru:Access Control List]]
[[Category:Tutorials]]

Meta.xml

2017-01-01T18:43:59Z

JHXP: Reverted edits by Marcin778 (talk) to last revision by Necktrox

The ''meta.xml'' file presents MTA with a set of metadata, such as the resource's name, the scripts to include, and which files to precache for sending to clients among other things. It is also the scope of "elements". It is written in XML, which is based on HTML and is the parent of XHTML.

=Tags=
XML is a textual data format which is widely used for the representation of data. MTA uses an XML-based language to describe the metadata for resources by using the tags below:

*'''<info />''' Information about this resource, possible parameters include (any arbitrary parameters can be used and read using [[getResourceInfo]]):
** '''author:''' The author of this resource
** '''version:''' The version of this resource
** '''name:''' The name of this resource
** '''description:''' A brief description of this resource
** '''type:''' The type of this resource, that can be "gamemode", "script", "map" or "misc".
** '''gamemodes:''' The gamemodes to be compatible with the resource. It must be the name of the gamemode resource, not the gamemode name. If you want it to be compatible with multiple gamemodes, it must be in a comma-separated list without spaces. (e.g. gamemodes="test1,test2").
*'''<script />''' Source code for this resource, possible parameters are:
** '''src:''' The file name of the source code
** '''type:''' The type of source code: "client", "server" or "shared".
**'''cache:''' When the script file type is "client", this setting controls whether the file is saved on the clients' hard drive. Default is "true". Using "false" will mean the file is not saved. ''(Note: cache=false files are started at the client first, so lua file load order might differ when mixing cache settings)''
**'''validate:''' If set to "false", compatibility checks are skipped.
*'''<map />''' The map for a gamemode, possible parameters are:
**'''src:''' .map file name (can be path too eg. "maps/filename.map")
**'''dimension:''' Dimension in which the map will be loaded (optional)
*'''<file />''' A client-side file. Generally these are images, .txd, .col, .dff or .xml files. They'll be downloaded by clients when the resources is started (or on join)
**'''src:''' client-side file name (can be path too eg. "images/image.png")

*'''<include />''' Include resources that this resource will use
**'''resource:''' Resource name that you want to start with this resource
**'''minversion:''' Minimum version that '''resource''' needs to be (optional)
**'''maxversion:''' Maximum version that '''resource''' needs to be (optional)
*'''<config />''' Config file (.xml) can be accessed by resource, possible parameters are:
**'''src:''' The file name of the config file
**'''type:''' The type of the config file: "client" or "server"
*'''<export />''' This exports functions from this resource, so other resources can use them with [[call]]
**'''function:''' The function name
**'''type''' Whether function is exported server-side or client-side (valid values are: "client", "server" and "shared")
**'''http:''' Can the function be called via HTTP (true/false)
*'''<html />'''
**'''src:''' The filename for the HTTP file (can be a path)
**'''default:''' The html file is one that is shown by default when visiting /resourceName/ on the server. Only one html can be default, the rest are ignored. (true/false)
**'''raw:''' The html file is not parsed by the Lua interpreter and is treated as binary data. Must be used for binary files (images mainly) (true/false)
*'''<settings> <setting name="" value=""/> </settings>:''' Most gamemodes use [[settings system]] to let server admins to configure it how they like. For instance you could set round time and then use [[get]] and [[set]] to get the value or change it, respectively.
*'''<min_mta_version />''' Minimum version requirements for this resource to run correctly. When authoring resources, the minimum version should usually be set to the current released version of MTA:SA (which at the moment is "{{Current Version|full}}"). See example for example.
**'''client:''' The minimum client version
**'''server:''' The minimum server version
*'''<aclrequest />''' A list of [[Access_Control_List|ACL]] rights this resource will need.
{{New items|3.0132|1.3.1 r4141|
*'''<sync_map_element_data />''' Controls whether map [[Element_data|element data]] such as "PosX" and "DoubleSided" are transferred to the client. This data is usually not required by most gamemodes or resources. (Map Editor and Interiors require this to be not set to false to work). When set in a gamemode meta.xml, the setting will apply to all maps loaded by that resource.
**'''false:''' Disable transfer of map element data for all resources. This can reduce map download times considerably.
**'''true:''' Enable transfer of map element data for all resources. (If '''false''' and '''true''' are set in different resources, true will have priority and all resources will transfer map element data)
}}
{{New items|3.0140|1.4.0 r5313|
*'''<oop/>''' OOP - Please refer to [[OOP]] for documentation.
**'''false:''' Disable OOP.
**'''true:''' Enable OOP.
}}
{{New feature/item|3.0150|1.5.0|7308|
*'''<download_priority_group/>''' If not set, the download priority group for a resource defaults to 0. If this is set higher than 0, then the resource will be downloaded and started on the client earlier than other resources. If set to less than 0, the resource will be downloaded and started on the client later than other resources.
}}

== Example ==
Heres an example of a meta file using some of the tags mentioned:
{{#tag:syntaxhighlight |
<meta>
<info author="Slothman" type="gamemode" name="Stealth" />
<config src="help.xml" type="client"/>

<download_priority_group>0</download_priority_group>
<min_mta_version client="{{Current Version|full}}" server="{{Current Version|full}}" />

<sync_map_element_data>false</sync_map_element_data>

<script src="stealthmain_server.lua" />
<script src="noiseblip.lua" />
<script src="mission_timer.lua" />
<script src="gadgets_server.lua" />
<script src="gadgets_client.lua" type="client"/>
<script src="stealthmain_client.lua" type="client" validate="true"/>
<script src="noisebar.lua" type="client"/>
<script src="spycam.lua" type="client"/>
<script src="riemann_z_demonstration.lua" type="client" cache="false"/>
<map src="base.map" dimension="1"/>

<file src="riot_shield.txd" />
<file src="riot_shield.dff" />
<file src="riot_shield.col" />
<file src="armor.png"/>
<file src="camera.png"/>
<file src="cloak.png" />
<file src="goggles.png" />
<file src="mine.png" />
<file src="radar.png" />
<file src="shield.png" />

<include resource="scoreboard" />
<include resource="killmessages" />
<include resource="maplimits" />

<export function="exampleExport1" type="server" />
<export function="exampleExport2" type="client" />
<export function="exampleExport3" type="shared" />

<settings>
<setting name="roundlimit" value="[6]" /> 
<setting name="teamdamage" value="[1]" /> 
<setting name="teambalance" value="[1]" /> 
<setting name="spazammo" value="[25]" /> 
<setting name="m4ammo" value="[100]" />
<setting name="shotgunammo" value="[25]" />
<setting name="sniperammo" value="[20]" />
<setting name="ak47ammo" value="[120]" />
<setting name="rifleammo" value="[40]" />
<setting name="deserteagleammo" value="[45]" />
<setting name="pistolammo" value="[132]" />
<setting name="uziammo" value="[150]" />
<setting name="tec9ammo" value="[150]" />
<setting name="silencedammo" value="[65]" />
<setting name="grenadeammo" value="[4]" />
<setting name="satchelammo" value="[4]" />
<setting name="teargasammo" value="[4]" />
<setting name="molatovammo" value="[4]" />
<setting name="isAllowedToShoot" value="true" />
</settings>

<aclrequest>
<right name="function.startResource" access="true" />
<right name="function.stopResource" access="true" />
<right name="function.setPlayerMuted" access="true" />
</aclrequest>
</meta>
|lang="xml"}}
[[Category:Scripting Concepts]]
[[cs:Meta.xml]]
[[de:Meta.xml]]
[[es:Sobre el archivo "meta.xml"]]
[[it:Meta.xml]]
[[pl:Meta.xml]]
[[ru:Meta.xml]]

Resource Web Access

2017-01-01T18:43:57Z

JHXP: Reverted edits by Marcin778 (talk) to last revision by Talidan

The Multi Theft Auto Server provides a web interface that resources can use in a variety of ways. This document's purpose is to explain what these ways are and how to go about using them.

==Overview==
There are two key parts that make up this system. The first is a standard web server that allows web browsers to request pages and files you have in a resource. The second is a system for allowing web browsers to call functions you have exported from your resource.

==Pages==
===Specifying a file in the meta===
You can specify in your resource's meta file that certain files are accessible through the web server. To do this, you add a line:
<syntaxhighlight lang="xml">
<html src="filename.ext" />
</syntaxhighlight>
You can then access this file from your web browser by visiting: http://host:port/resourcename/filename.ext<br/>
For example, on a locally hosted server using default http port with webmap started: http://127.0.0.1:22005/webmap/map.htm

===Binary files===
Despite the misleading name, files specified using the html node can be of any type. If they are binary files (like images, zip files) then you need to specify this in the meta file, by adding ''raw="true"'' to the ''html'' node. This means that the files are not preprocessed before being sent to the web browser.

For example:
<syntaxhighlight lang="xml">
<html src="image.gif" raw="true" />
</syntaxhighlight>

===Parsed files===
If a file is not specified in the meta file as "raw", then it is passed through a pre-processor before it is returned to the client. This pre-processor works much like PHP or ASP, but uses LUA. You can embed standard MTA scripts within HTML pages, controlling the output. Almost all standard MTA functions work, plus a number of special [[Template:HTTP functions|HTTP Functions]], such as [[httpWrite]], a function that outputs text to the buffer.

For example:
<syntaxhighlight lang="html4strict">
<html>
<body>
This resource is called <* httpWrite( getResourceName(getThisResource()) ) *>
</body>
<html>
</syntaxhighlight>

There is a shorthand (in common with PHP and ASP) for this code, meaning that you can also write the above code as:

<syntaxhighlight lang="html4strict">
<html>
<body>
This resource is called <* = getResourceName(getThisResource()) *>
</body>
<html>
</syntaxhighlight>

Aside from HTTP functions, embedded Lua has access to the following environment variables that contain information about how the page was requested:
* table '''requestHeaders''': This is a table containing all the headers that were requested with the page. You can set returned headers using [[httpSetResponseHeader]].
* table '''form''': This is a table containing all the form data submitted to the page using HTTP POST combined with any variables passed in the querystring with HTTP GET.
* table '''cookies''': This is a table of all the cookies. You can modify cookies using [[httpSetResponseCookie]].
* string '''hostname''': This is a string containing the IP address or hostname that requested the page.
* string '''url''': This is the URL of the page.
* account '''user''': This is the account of the current user.

It's important to note that parsed files are run in a separate virtual machine from the rest of your resource's code. As such, if you want to call a function in your resource's main code, you need to export the function and use the [[call]] function from your parsed file.

==Calls==
You can specify that certain exported functions in your resource are able to be called from the HTTP interface. All the SDKs (listed below) allow you to call these functions from a remote location.

To specify an exported http-accessible function, add the following to your meta.xml file:
<syntaxhighlight lang="xml">
<export function='functionName' http='true' />
</syntaxhighlight>

You can code your function just as you would any normal function, returning as many values as you want, including tables and resources and most importantly elements. You ''cannot'' however return other 'userdata' values such as [[xmlnode|xmlnodes]] or functions.

===Protocol===
{{note_box|You don't need to know this unless you're writing your own HTTP request code. You can just use one of the [[#SDK|SDKs listed below]].}}

Calls are done by requesting ''<nowiki>http://<your IP>:<your port>/<resource_name>/call/<exported_function_name></nowiki>'' using HTTP POST. The body of the request should be a JSON array of the arguments for the function.

The request will return a JSON array of the value(s) returned from the function as the HTTP response.

The server supports HTTP Basic authentication and you can configure access via the ACL and the built-in accounts system.

===Calls from the HTTP web interface===
Using calls is probably easiest from the web interface and can be done almost seamlessly.

First, add this to your meta.xml file:
<syntaxhighlight lang="xml">
<include resource="ajax" />
</syntaxhighlight>

Secondly, add the following to the <head> section of the page you want to call from:
<syntaxhighlight lang="lua">
<* = exports.ajax:start(getResourceName(getThisResource())) *>
</syntaxhighlight>

Finally, you can create a javascript block in your page and call your functions almost as if they were local. The only difference is that the calls are aysnchronous - you should specify a callback function as the last argument for your call. This is called when the function returns.

Here's a simple example.

'''meta.xml'''
<syntaxhighlight lang="xml">
<meta>
<include resource="ajax" />
<script src='code.lua' />
<html src='page.htm' default='true' />
<export function='showChatMessage' http='true' />
</meta>
</syntaxhighlight>

'''code.lua'''
<syntaxhighlight lang="lua">
function showChatMessage ( message )
outputChatBox ( message )
return 5;
end
</syntaxhighlight>

'''page.htm'''
<syntaxhighlight lang="html4strict">
<html>
<head>
<* = exports.ajax:start(getResourceName(getThisResource())) *>
<script type='text/javascript'>
function say() {
var message = document.getElementById('message')
showChatMessage ( message.value,
function ( number ) {
// the function has been called and returned something
message.value = "The function returned " + number;
}
);
}
</script>
</head>
<body>
<input type='text' id='message' /><input type='button' value='say' onclick='say();' />
</body>
</html>
</syntaxhighlight>

You can see (fairly complex) examples of how this can be done in the resources ''resourcebrowser'', ''resourcemanager'' and ''webadmin''.

==Securing the web interface==
The [[ACL]] has a number of rights that can affect what files can be accessed.
{{Deprecated feature|3.0139|1.3.1|
* general.http: If disabled, none of the http files can be accessed (except by game clients)
** '''Important Note''': ''If 'general.http' is enabled, http access to all resources (for that ACL) is enabled by default. To disable http access you have to explicitly block access to resources that contain exported http functions.''
** '''Important Note''': ''If 'general.http' is enabled on an ACL which has a user with no password (i.e. user.* or user.guest or user.http_guest), it is essential that you explicitly block access to resources that contain exported http functions.''
* resource.'''ResourceName''': If disabled, none of the files in the resource can be accessed
* resource.'''ResourceName'''.file.'''FileName''': If disabled, the file named cannot be accessed
* resource.'''ResourceName'''.function.'''FunctionName''': If disabled, the function cannot be called
These work as with other ACL rights - you can disable them for normal users and just enable them for Admin users, or any other group of users you wish.
}}
{{New_feature|3.0139|1.3.1|
* '''resource.ResourceName.http''': If enabled, the resource will be accessible from http://server_ip:22005/ResourceName/
This works as with other ACL rights - You can enable it just for Admin users, or any other group of users you wish.
}}

==SDK==
There are a number of so-called 'SDKs' available that allow you to interface with the server from other programming languages. With these you could (in theory) write whole gamemodes. In practice this is probably a bad idea, but it is useful for statistics and administration. The PHP SDK is the most developed version. Feel free to modify or create your own SDKs - if you do please send us a copy.

* [[JavaSDK|Java SDK]]
* [[Javascript SDK]]
* [[Perl SDK]]
* [[PHP SDK]]
* [[CSharp SDK|C# SDK]]

==See Also==
[[callRemote]] - Allows game servers to call functions on PHP pages (with the PHP SDK) and on other game servers.
[[Category:Scripting Concepts]]
[[ru:Resource Web Access]]
[[Category:Tutorials]]

Resources

2017-01-01T18:43:55Z

JHXP: Reverted edits by Marcin778 (talk) to last revision by Cristiano Cardoso

Resources are a key part of MTA. A resource is essentially a folder or zip file that contains a collection of files - including script files, plus a ''meta'' file that describes how the resource should be loaded. 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. Its worth remember though, that unlike programs on an operating system, there is no multi-tasking between resources.

==Terminology==
* '''Resource''' - A zip file or folder containing a meta.xml file and a number of resource items. These are placed in the ''mods/deathmatch/resources'' folder in the server directory.
* '''Resource item''' - A file contained within a resource, currently this can be a map, script, images etc.

==The Meta File==
''See main article [[Meta.xml]] for details''

The Meta file is the core of each the resource. It describes exactly what files in the resource should be used, and how. The following is an example that covers every option there is, your meta files can have as many or as few of these tags as you require:

<syntaxhighlight lang="xml">
<meta>
<info author="eAi" description="This is a basic CTF script" version="4"/>

<include resource="radarblips"/>
<include resource="markermanagement" />

<script src="ctf.lua" />
<script src="flag.lua" />
<script src="ctf_client.lua" type="client" />

<file src="model.dff" />
<file src="quitbutton.png" />
<file src="killed.png" />

<html src="test.htm" default="true"/>
<html src="logo.png" raw="true" />

<export function="multiply" http="true" />
<export function="getPlayerList" />
<export function="getElementOwner" type="client"/>

<config src="vehicle-list.xml" type="client" />
<config src="markerconfig.xml" type="server" />

<map src="somestuff.map" dimension="99" />
</meta>
</syntaxhighlight>
While a CTF map may have a meta.xml that looks like:
<syntaxhighlight lang="xml">
<meta>
<include resource="ctf" />
<map src="myuberl33tctfmap.map" />

<info author="Tom" instructions="this is uber l33t !!!!!1111111" type="map" />
</meta>
</syntaxhighlight>

Script/type, Config/type and File/type attributes specify if the script/resource should be sent to clients or not, and defaults to "server".

The include tag specifies other resources that should be started before this resoucre is started. In other words, if your resource is dependent on another, you can include it so that the other resource is started first,

Each resource has its own virtual machine (VM). This contains every script in the resource. This means that variables are not shared with other resources. The best way to communictate with other resources is by using the ''export'' tag and exporting a function. This will enable other resources to fire this function using the [[call]] scripting function.

Scripts sent to clients are started as soon as all the scripts have been downloaded.

Scripts are able to read and write to their own resource folder with functions such as [[xmlCreateFile]] and [[fileCreate]]. They can also read and write to other resources, but must have [[Access_Control_List|ACL]] access.

Each resource can only be loaded once, the server will ensure this. If a resource is included more than once, the same instance will be used by each resource that includes it.

==File storage==
Resource files can either be stored in a zip or a directory. This is located in:

server/mods/deathmatch/resources/ (if you've installed your server with the client)

or

mods/deathmatch/resources/ (for dedicated server installations)

Each resource can have a zip file, a directory or both. In the case of both existing, the directory has precedence over the zip file, as such files can be placed in the directory to over-ride the files in the zip file. This allows directories to be used for testing and developing of maps/scripts while zip files used by end-users.

==Other things to note==
*Resource names can't have dots in.
*If the resource does any file saving, the file names used should not be listed in the meta.xml
*Files listed in the meta.xml should be considered read only by your scripts. Do not modify them with xmlSaveFile, FileSave etc.
*When making a zip file of your resource, do not include save files. If your resource uses save files, they must be created by your resource when needed.
*When making a zip file of your resource, only include files that are listed in the meta.xml. Do not include 'example' save files, otherwise bad things will happen.
*We recommend avoiding spaces and exotic characters from resources names.

==Script functions==
The resource system can be manipulated by script. As such, the following Serverside scripting functions are provided:
{{Resource functions}}

The following events are also provided:
{{Resource_events}}

[[it:Introduzione alle Risorse]]
[[pt-br:Recursos]]
[[ru:Resources]]

Hibakeresés

2017-01-01T18:43:54Z

JHXP: Reverted edits by Marcin778 (talk) to last revision by AlexTMjugador

When scripting you will often come across problems that are not immediately apparent. This page tries to point out some basic strategies to locate the error.

==Debug console==
MTA features a built-in debug console that shows debug messages output from MTA functions or from scripts. Keeping it mind that you should have administrator access (unless you modify the ACL to change this), you can open the debug console by typing ''debugscript *x*'' in the console, where ''x'' is the debug level:
* '''1:''' only errors
* '''2:''' errors and warnings
* '''3:''' errors, warnings and info messages
By typing ''debugscript 3'' all messages are visible. Level 3 and level 2 are recommended for most occasions. You should have ''debugscript'' enabled whenever you are testing your scripts as it will help you easily detect and solve typos and other issues.

===Example===
This example code has two errors:
<syntaxhighlight lang="lua">
function SayHello(message, player)
if (getPlayerName(player) == "Fedor")
outputChatbox("Hello Fedor")
end
end
addEventHandler("onChatMessage", root, SayHello)
</syntaxhighlight>
When the script this piece of code is in is tried to be loaded, debugscript will output something similiar to this:
:{{Debug info|Loading script failed: myResource\script.lua:2: 'then' expected near ´outputChatbox'}}
This means the script could not be parsed because there was a syntax error. It shows the script path relative to the resource directory so you can identify to script where the error originated from. After the filename it shows a colon and a number, this number presents the line number - this is so you can find out where in your script the error is - it is very helpful for large scripts. After that is the error message, which varies depending on the error made. Looking at the error message, we can easily determine that the error originated from the resource '''myResource''' and line two of the script file '''script.lua'''. The error message is very clear, we forgot the "then"! We can easily fix that!
<syntaxhighlight lang="lua">
function SayHello(message, player)
if (getPlayerName(player) == "Fedor") then
outputChatbox("Hello Fedor")
end
end
addEventHandler("onChatMessage", root, SayHello)
</syntaxhighlight>
Now the script will load fine and won't output any errors until a player with the name 'Fedor' says something in the chat. At that moment, the debug console will output:
:{{Debug error|myResource\script.lua:2: attempt to call global 'outputChatbox' (a nil value)}}
This error means that the function '''outputChatbox''' is a nil value, that is - it doesn't exist! This is because the function is actually called [[outputChatBox]], not [[outputChatbox]] - take care of that capital B.:
<syntaxhighlight lang="lua">
function SayHello(message, player)
if (getPlayerName(player) == "Fedor") then
outputChatBox("Hello Fedor")
end
end
addEventHandler("onChatMessage", root, SayHello)
</syntaxhighlight>

Of course, this is just an example and I've only skimmed the surface of error messages. There are plenty of other messages and scenarios, but you should get the general idea.

==Server & client debug logging==
====Server====
Navigate to: ''(MTA root folder)>server>mods>deathmatch''

There are two nearly identical files:

*The local.conf is the settings for the "host game" menu item in the main menu of MTA. This is a quick and easy way of starting a temporary server from inside the client. When the client is turned off the server will also turn off.

*The mtaserver.conf is used when "MTA Server.exe" is executed from (MTA root folder)>server. This runs the server in its own console window which does not need the client to exist or to be run. This is can be useful if you're interested in hosting servers for a longer time period or if you want to experiment with a real world console.

Depending on which way you host, you will want to edit those files. The settings in question are:

<syntaxhighlight lang="xml">
<scriptdebuglogfile>logs/scripts.log</scriptdebuglogfile>


<scriptdebugloglevel>0</scriptdebugloglevel></syntaxhighlight>

You want to make sure you have a log name specified. Also you want to specify what level of errors will be logged. If it is 0 nothing will be logged. The levels were explained at the top of this article. If the logging level was changed to 3, then in this case all '''serverside''' script errors log to (MTA root folder)>server>mods>deathmatch>logs>scripts.log

====Client====
Navigate to: ''(MTA root folder)>server>clientscript.log''

This file logs all '''clientside''' script errors. This is set to log by default, no setup required.

==Debug strategies==
There are several strategies that support finding errors, apart from going through the code. Most of them include outputting debug messages, with have different information depending on the situtation.

===Useful functions===
There are some functions that may come in handy for debugging.
* [[outputDebugString]] or [[outputChatBox]] for outputting any information (use outputDebugString for technical output)
* [http://www.lua.org/manual/5.1/manual.html#pdf-tostring tostring()] on a variable to turn the value into a string. Useful if the value is not a number or string.
* [[getElementType]] to check the type of the MTA element.
* [[isElement]] to check if the MTA element exists.

===Add debugmessages to check ''if'', ''when'' or ''how often'' a section of code is executed===
A typical example would be verify whether an ''if''-section is executed or not. To do that, just add any message you will recognize later within the ''if''-section.
<syntaxhighlight lang="lua">
if (variable1 == variable2) then
outputDebugString("variable1 is the same as variable2!")
-- do anything
end
</syntaxhighlight>

Another application would be to check when variable values are modified. First search for all occurences of the variable being edited and add a message just beside it.

===Add debugmessages to check the ''value'' of a variable===
Let's say you want to create a marker, but it doesn't appear at the position you expect it to be. The first thing you might want to do is check if the [[createMarker]] function is executed. But while doing this, you can also check the values being used in the [[createMarker]] function in one run.
<syntaxhighlight lang="lua">
outputChatBox("posX is: "..x.." posY is: "..y.." posZ is: "..z)
createMarker(x,y,z)
</syntaxhighlight>
This would output all three variables that are used as coordinates for the marker. Assuming you read those from a map file, you can now compare the debug output to the desired values. The [http://www.lua.org/manual/5.1/manual.html#pdf-tostring tostring()] will ensure that the values of the variables can be concatenated (put together) as a string, even if it's a boolean value.

==Example==
Imagine you created a [[Colshape|collision shape]] somewhere and you want an action to perform after the player stays for ten seconds inside it, you would do this:
<syntaxhighlight lang="lua">
function colShapeHit(player)
-- set a timer to output a message (could as well execute another function)
-- store the timer id in a table, using the player as index
colshapeTimer[player] = setTimer(outputChatBox,10000,1,"The player stayed 10 seconds in the colshape!")
end
addEventHandler("onColShapeHit", root, colShapeHit)

function colShapeLeave(player)
-- kill the timer when the player leaves the colshape
killTimer(colshapeTimer[player])
end
addEventHandler("onColShapeLeave", root, colShapeLeave)
</syntaxhighlight>
When a player enters the colshape, debugscript outputs the following message:
:{{Debug error|..[path]: attempt to index global 'colshapeTimer' (a nil value)}}
This means you tried to index a table that does not exist (because the table is a nil value, it doesn't exist). In the example above, this is done when storing the timer id in the table. We need to add a check if the table exists and if it does not exist we should create it.

<syntaxhighlight lang="lua">
function colShapeHit(player)
if (colshapeTimer == nil) then
colshapeTimer = {}
end
-- set a timer to output a message (could as well execute another function)
-- store the timer id in a table, using the player as index
colshapeTimer[player] = setTimer(outputChatBox,10000,1,"The player stayed 10 seconds in the colshape!")
end
addEventHandler("onColShapeHit", root, colShapeHit)

function colShapeLeave(player)
-- kill the timer when the player leaves the colshape
killTimer(colshapeTimer[player])
end
addEventHandler("onColShapeLeave",root,colShapeLeave)
</syntaxhighlight>

Now we will still receive a warning when a player enters the colshape, waits for the message and leaves it again:

:{{Debug warning|[..]: Bad argument @ 'killTimer' Line: ..}}

Except for that (we will talk about that later) everything seems to work fine. A player enters the colshape, the timer is started, if he stays the message occurs, if he leaves the timer is killed.

===A more inconspicuous error===
But for some reason the message gets outputted twice when you stay in the colcircle while in a vehicle. Since it would appear some code is executed twice, we add debug messages to check this.

<syntaxhighlight lang="lua">
function colShapeHit(player)
if (colshapeTimer == nil) then
colshapeTimer = {}
end
-- add a debug message
outputDebugString("colShapeHit")
-- set a timer to output a message (could as well execute another function)
-- store the timer id in a table, using the player as index
colshapeTimer[player] = setTimer(outputChatBox,10000,1,"The player stayed 10 seconds in the colshape!")
end
addEventHandler("onColShapeHit",getRootElement(),colShapeHit)

function colShapeLeave(player)
-- add a debug message
outputDebugString("colShapeLeave")
-- kill the timer when the player leaves the colshape
killTimer(colshapeTimer[player])
end
addEventHandler("onColShapeLeave",getRootElement(),colShapeLeave)
</syntaxhighlight>

Now we notice that both handler functions get executed twice when we are in a vehicle, but only once when we are on-foot. It would appear the vehicle triggers the colshape as well. To confirm this theory, we ensure that the ''player'' variable actually holds a reference to a player element.

<syntaxhighlight lang="lua">
function colShapeHit(player)
if (colshapeTimer == nil) then
colshapeTimer = {}
end
-- add a debug message, with the element type
outputDebugString("colShapeHit "..getElementType(player))
-- set a timer to output a message (could as well execute another function)
-- store the timer id in a table, using the player as index
colshapeTimer[player] = setTimer(outputChatBox,10000,1,"The player stayed 10 seconds in the colshape!")
end
addEventHandler("onColShapeHit",getRootElement(),colShapeHit)

function colShapeLeave(player)
-- add a debug message, with the element type
outputDebugString("colShapeLeave "..getElementType(player))
-- kill the timer when the player leaves the colshape
killTimer(colshapeTimer[player])
end
addEventHandler("onColShapeLeave",getRootElement(),colShapeLeave)
</syntaxhighlight>

The debug messages tell us that one of the ''player'' variables is a player and that the other one is a vehicle element. Since we only want to react when a player enters the colshape, we add an ''if'' that will end the execution of the function if it's '''not''' an player element.

<syntaxhighlight lang="lua">
function colShapeHit(player)
if (colshapeTimer == nil) then
colshapeTimer = {}
end
-- add a check for the element type
if (getElementType(player) ~= "player") then return end
-- add a debug message, with the element type
outputDebugString("colShapeHit "..getElementType(player))
-- set a timer to output a message (could as well execute another function)
-- store the timer id in a table, using the player as index
colshapeTimer[player] = setTimer(outputChatBox,10000,1,"The player stayed 10 seconds in the colshape!")
end
addEventHandler("onColShapeHit",getRootElement(),colShapeHit)

function colShapeLeave(player)
-- add a check for the element type
if (getElementType(player) ~= "player") then return end
-- add a debug message, with the element type
outputDebugString("colShapeLeave "..getElementType(player))
-- kill the timer when the player leaves the colshape
killTimer(colshapeTimer[player])
end
addEventHandler("onColShapeLeave",getRootElement(),colShapeLeave)
</syntaxhighlight>

Now the script should work as desired, but it will still output the warning mentioned above. This happens because the timer we try to kill when a player leaves the colshape will not exist anymore when it has reached the 10 seconds (and therefore executed after the 10th second has completed). There are different ways to get rid of that warning (since you know that the timer might not exist anymore and you only want to kill it if it exists). One way would be to check if the timer referenced in the table really exists. To do this, we need to use [[isTimer]], which we will use when we kill the timer:
<syntaxhighlight lang="lua">
if (isTimer(colshapeTimer[player])) then
killTimer(colshapeTimer[player])
end
</syntaxhighlight>

So the complete working code would be:
<syntaxhighlight lang="lua">
function colShapeHit(player)
if (colshapeTimer == nil) then
colshapeTimer = {}
end
-- add a check for the element type
if (getElementType(player) ~= "player") then return end
-- add a debug message, with the element type
outputDebugString("colShapeHit "..getElementType(player))
-- set a timer to output a message (could as well execute another function)
-- store the timer id in a table, using the player as index
colshapeTimer[player] = setTimer(outputChatBox,10000,1,"The player stayed 10 seconds in the colshape!")
end
addEventHandler("onColShapeHit",getRootElement(),colShapeHit)

function colShapeLeave(player)
-- add a check for the element type
if (getElementType(player) ~= "player") then return end
-- add a debug message, with the element type
outputDebugString("colShapeLeave "..getElementType(player))
-- kill the timer when the player leaves the colshape
if (isTimer(colshapeTimer[player])) then
killTimer(colshapeTimer[player])
end
end
addEventHandler("onColShapeLeave",getRootElement(),colShapeLeave)
</syntaxhighlight>

==Debugging Performance Issues==

If your server is using up more resources than it should or you just want to make sure your scripts are efficient, you can find the source of the issue by using a great tool that comes with the default resource package called [[Resource:Performancebrowser|performancebrowser]]. You can start it with ''''start performancebrowser''''. If it doesn't exist then you can get the latest resources from the [https://github.com/multitheftauto/mtasa-resources GitHub repository]. This tool provides an incredible amount of information for performance debugging. Memory leaks, element leaks and CPU intensive scripts are all easily findable via performancebrowser. If you use the ''''d'''' option in Lua timing you can see which functions are using up the CPU.

To access performancebrowser you will need to go to your web browser and enter the address: http://serverIPHere:serverHTTPPortHere/performancebrowser/ Note that the / at the end is required. So for example: http://127.0.0.1:22005/performancebrowser/ You will then need to login with an in-game admin account or any account that has access to ''''resource.performancebrowser.http'''' and ''''resource.ajax.http''''. Most of the information you will need are in the categories Lua timing and Lua memory, look for values that are much higher than other values.

===Examples of scripts that could cause performance problems===

Adding data to a table but never removing it. This would take months/years before it causes a problem though.
<syntaxhighlight lang="lua">
local someData = {}

function storeData()
someData[source] = true
-- There is no handling for when a player quits, this is considered a memory leak
-- Using the Lua timing tab you can detect the RAM usage of each resource.
end
addEventHandler("onPlayerJoin", root, storeData)
</syntaxhighlight>

Element leaking is possible if you use temporary colshapes for whatever reason and may not destroy them. This would cause bandwidth, CPU and memory performance issues over time.
<syntaxhighlight lang="lua">
function useTemporaryCol()
local col = createColCircle(some code here)
if (normally this should happen) then
destroyElement(col)
end
-- But sometimes it didn't so the script ended but the collision area remained and over time
-- you may end up with hundreds to thousands of pointless collision areas.
-- The Lua timing tab allows you to see the amount of elements each script has created.
end
</syntaxhighlight>

High CPU usage resulting in the server FPS dropping so much that the server is unplayable. In under 24 hours this can create havoc on a very busy server. The amount of "refs" in the Lua timing detect this type of build up, surprisingly the Lua timing tab didn't help in this case but Lua memory did.
<syntaxhighlight lang="lua">
addEventHandler("onPlayerJoin", root, function()
-- Code for joiner
addEventHandler("onPlayerQuit", root, function()
-- Code for when they have quit
-- See the problem? It's bound to root which the event handler is being added again and again and again
end)
end)
</syntaxhighlight>

A function uses up a lot of your CPU because whatever it does takes a long time. This is just some function that takes a long time to complete. Without performancebrowser you'd have no idea its the cause but with performancebrowser you can see that a resource is using lots of CPU in the Lua timing tab. If you then enter: ''''d'''' into the options edit box it will even tell you what file name and first line of the function that is using up so much CPU.
<syntaxhighlight lang="lua">
function someDodgyCode()
for i=1, 100000 do
-- some code
end
end
</syntaxhighlight>

[[it:Guida al Debug]]
[[Category:Scripting Concepts]]
[[ru:Debugging]]
[[Category:Tutorials]]

Introduction to Scripting the GUI

2017-01-01T18:43:52Z

JHXP: Reverted edits by Marcin778 (talk) to last revision by Strix

One important feature in MTA:SA is the ability to script customized GUI (Graphic User Interface). The GUI consists of windows, button, edit boxes, check boxes... Almost every standard form components in graphical environments. They can be displayed while the user is in game, and used for inputs and outputs in place of traditional commands.

[[Image:AdminGUI.png|thumb|Admin Console GUI]]

==A tutorial to make a login window==
In this tutorial we'll make a simple login window, with two input boxes and a button. The window appears when the player joins the game, and once the button is clicked, the player is spawned. The tutorial will continue the gamemode we made in [[Scripting Introduction|Introduction to Scripting]] ''(If you have used the [[Scripting Introduction|Introduction to Scripting]], you will need to remove or comment the [[spawnPlayer]] line in the "joinHandler" function in your code, as we will be replacing it with a gui alternative in this tutorial)''. We'll also take a look at client-side scripting.

===Draw the window===
All the GUI must be made client side. It is also a good practice to keep all the client scripts in a separate folder.

Browse to /Your MTA Server/mods/deathmatch/resources/myserver/ directory, and create a folder named "client". Under /client/ directory, create a text file and name it "gui.lua".

In this file we will write a funtion that draws the window. To create a window we will use [[guiCreateWindow]]:
<syntaxhighlight lang="lua">
function createLoginWindow()
-- define the X and Y positions of the window
local X = 0.375
local Y = 0.375
-- define the width and height of the window
local Width = 0.25
local Height = 0.25
-- create the window and save its element value into the variable 'wdwLogin'
-- click on the function's name to read its documentation
wdwLogin = guiCreateWindow(X, Y, Width, Height, "Please Log In", true)
end
</syntaxhighlight>

===Relative and Absolute===
Note that the final argument passed to guiCreateWindow in the above example is ''true''. This indicates that the coordinates and dimensions of the window are '''relative''', meaning they are a ''percentage'' of the total screen size. This means that if the far left side of the screen is 0, and the far right is 1, an X position of 0.5 would represent the centre point of the screen. Similarly, if the top of the screen is 0 and the bottom is 1, a Y position of 0.2 would be 20% of the way down the screen. The same principles apply to both Width and Height as well (with a Width value of 0.5 meaning the window will be half as wide as the screen).

The alternative to using relative values is using '''absolute''' (by passing ''false'' instead of true to guiCreateWindow). Absolute values are calculated as the total number of pixels from the top-left corner of the parent (if no gui element parent is specified, the parent is the screen itself). If we assume a screen resolution of 1920x1200, the far left side of the screen being 0 pixels and the far right being 1920 pixels, an X position of 960 will represent the centre point of the screen. Similarly, if the top of the screen is 0 pixels and the bottom is 1200, a Y position of 20 would be 20 pixels down from the top of the screen. The same principles apply to both Width and Height as well (with a Width value of 50 meaning the window will be 50 pixels wide). ''You can use [[guiGetScreenSize]] and a little maths to calculate certain absolute positions.''

The differences between using relative and absolute values is quite simple; gui created using absolute values will always remain exactly the same pixel size and position, while gui created using relative values will always be a percentage of its parent's size.

Absolute is generally easier to maintain when editing code by hand, however your choice of type depends on the situation you are using it for.

For the purposes of this introduction we will be using relative values.

===Adding the components===
Next, we'll add the text labels (saying "username:" and "password:"), edit boxes (for entering your data) and a button to log in.

To create buttons we use [[guiCreateButton]] and to create edit boxes use [[guiCreateEdit]]:

'''Note that we are now writing more code for our existing 'createLoginWindow' function. This is not a new function and is meant to replace what you already have.'''
<syntaxhighlight lang="lua">
function createLoginWindow()
local X = 0.375
local Y = 0.375
local Width = 0.25
local Height = 0.25
wdwLogin = guiCreateWindow(X, Y, Width, Height, "Please Log In", true)

-- define new X and Y positions for the first label
X = 0.0825
Y = 0.2
-- define new Width and Height values for the first label
Width = 0.25
Height = 0.25
-- create the first label, note the final argument passed is 'wdwLogin' meaning the window
-- we created above is the parent of this label (so all the position and size values are now relative to the position of that window)
guiCreateLabel(X, Y, Width, Height, "Username", true, wdwLogin)
-- alter the Y value, so the second label is slightly below the first
Y = 0.5
guiCreateLabel(X, Y, Width, Height, "Password", true, wdwLogin)

X = 0.415
Y = 0.2
Width = 0.5
Height = 0.15
edtUser = guiCreateEdit(X, Y, Width, Height, "", true, wdwLogin)
Y = 0.5
edtPass = guiCreateEdit(X, Y, Width, Height, "", true, wdwLogin)
-- set the maximum character length for the username and password fields to 50
guiEditSetMaxLength(edtUser, 50)
guiEditSetMaxLength(edtPass, 50)

X = 0.415
Y = 0.7
Width = 0.25
Height = 0.2
btnLogin = guiCreateButton(X, Y, Width, Height, "Log In", true, wdwLogin)

-- make the window invisible
guiSetVisible(wdwLogin, false)
end
</syntaxhighlight>
Note that every GUI component created is a child of the window, this is done by specifying the parent element (wdwLogin, in this case) when creating the component.

This is very useful because not only does it mean that all the components are attached to the window and will move with it, but also that any changes done to the parent window will be applied down the tree to these child components. For example, we can now hide all of the GUI we just created by simply hiding the window:
<syntaxhighlight lang="lua">
guiSetVisible(wdwLogin, false) --hides all the GUI we made so we can show them to the player at the appropriate moment.
</syntaxhighlight>

===Using the function we wrote===
The createLoginWindow function is now complete, but it won't do anything until we call it. It is recommended to create all GUI when the client resource starts, hide them, and show them to the player later when needed. Therefore, we'll write an event handler for "[[onClientResourceStart]]" to create the window:
<syntaxhighlight lang="lua">
-- attach the event handler to the root element of the resource
-- this means it will only trigger when its own resource is started
addEventHandler("onClientResourceStart", getResourceRootElement(),
function ()
createLoginWindow()
end
)
</syntaxhighlight>

As this is a log in window, we now need to show the window when the player joins the game.
This can be done using the same event, "[[onClientResourceStart]]", so we can modify the above code to include showing the window:

'''Note that we are now writing more code for our existing 'onClientResourceStart' handler. This is not a new event handler and is meant to replace what you already have.'''
<syntaxhighlight lang="lua">
addEventHandler("onClientResourceStart", getResourceRootElement(),
function ()
-- create the log in window and its components
createLoginWindow()

-- output a brief welcome message to the player
outputChatBox("Welcome to My MTA:SA Server, please log in.")

-- if the GUI was successfully created, then show the GUI to the player
if (wdwLogin ~= nil) then
guiSetVisible(wdwLogin, true)
else
-- if the GUI hasnt been properly created, tell the player
outputChatBox("An unexpected error has occurred and the log in GUI has not been created.")
end

-- enable the players cursor (so they can select and click on the components)
showCursor(true)
-- set the input focus onto the GUI, allowing players (for example) to press 'T' without the chatbox opening
guiSetInputEnabled(true)
end
)
</syntaxhighlight>

Note that we have a simple security check before making the window visible, so in the unlikely event that the window has not been created, meaning wdwLogin is not a valid element, we don't get an error and just inform the player what has happened.
In the next step, we will create the button functionality for the log in button.

==Scripting the button==
Now that we have created our GUI and shown it to the player, we need to make it work.

===Detecting the click===
When the player clicks on any part of the GUI, the event "[[onClientGUIClick]]" will be triggered for the GUI component you clicked on. This allows us to easily detect any clicks on the GUI elements we want to use.
For example, we can attach the event to the btnLogin button to catch any clicks on it:
<syntaxhighlight lang="lua">
-- attach the event onClientGUIClick to btnLogin and set it to trigger the 'clientSubmitLogin' function
addEventHandler("onClientGUIClick", btnLogin, clientSubmitLogin, false)
</syntaxhighlight>
'''Note the final argument passed is "false". This indicates that the event will only trigger directly on btnLogin, not if the event has propagated up or down the tree. Setting this to "true" while attaching to gui elements will mean that clicking on any element in the same branch will trigger this event.'''

This line of code can now be added inside the createLoginWindow function. It is a common mistake to try and attach events to non-existant GUI elements, so make sure you always attach your events '''after''' the gui element (in this case, the button) has been created:

'''Note that we are now writing more code for our existing 'createLoginWindow' function.'''
<syntaxhighlight lang="lua">
function createLoginWindow()
-- create all our GUI elements
...

-- now add our onClientGUIClick event to the button we just created
addEventHandler("onClientGUIClick", btnLogin, clientSubmitLogin, false)
</syntaxhighlight>

===Managing the click===
Now that we can detect when the player clicks on the button, we need to write code to manage what happens when they do.
In our [[onClientGUIClick]] event handle, we told it to call the function clientSubmitLogin whenever btnLogin is clicked.
Therefore, we can now use the function clientSubmitLogin to control what happens when the button is clicked:
<syntaxhighlight lang="lua">
-- create the function and define the 'button' and 'state' parameters
-- (these are passed automatically by onClientGUIClick)
function clientSubmitLogin(button,state)
-- if our login button was clicked with the left mouse button, and the state of the mouse button is up
if button == "left" and state == "up" then
-- move the input focus back onto the game (allowing players to move around, open the chatbox, etc)
guiSetInputEnabled(false)
-- hide the window and all the components
guiSetVisible(wdwLogin, false)
-- hide the mouse cursor
showCursor(false)
end
end
</syntaxhighlight>
Now, when the button is clicked, the window will be hidden and all controls will be returned to the player. Next, we will tell the server to allow the player to spawn.

===Triggering the server===
Triggering the server can be done using [[triggerServerEvent]]. This allows you to trigger a specified event on the server from the client. The same can be done in reverse using [[triggerClientEvent]].
Here, we use the [[triggerServerEvent]] function to call our own custom event on the server, named "submitLogin", which will then control the spawning of the player serverside.

'''Note that we are now writing more code for our existing 'clientSubmitLogin' function. This is not a new function and is meant to replace what you already have.'''
<syntaxhighlight lang="lua">
function clientSubmitLogin(button,state)
if button == "left" and state == "up" then
-- get the text entered in the 'username' field
local username = guiGetText(edtUser)
-- get the text entered in the 'password' field
local password = guiGetText(edtPass)

-- if the username and password both exist
if username and password then
-- trigger the server event 'submitLogin' and pass the username and password to it
triggerServerEvent("submitLogin", getRootElement(), username, password)

-- hide the gui, hide the cursor and return control to the player
guiSetInputEnabled(false)
guiSetVisible(wdwLogin, false)
showCursor(false)
else
-- otherwise, output a message to the player, do not trigger the server
-- and do not hide the gui
outputChatBox("Please enter a username and password.")
end
end
end
</syntaxhighlight>

===Creating the serverside event===
At this point we now have all the code needed on the client side, so open up your serverside 'script.lua' file (from the [[Scripting Introduction|Introduction to Scripting]]) or another suitable serverside file to work with.

On the server side, recall that we are spawning the player as soon as they login.
So, first of all, we will need to define the custom event that we used before on the client. This can be done using [[addEvent]] and [[addEventHandler]].
<syntaxhighlight lang="lua">
-- create our loginHandler function, with username and password parameters (passed from the client gui)
function loginHandler(username,password)

end

-- define our custom event, and allow it to be triggered from the client ('true')
addEvent("submitLogin",true)
-- add an event handler so that when submitLogin is triggered, the function loginHandler is called
addEventHandler("submitLogin",root,loginHandler)
</syntaxhighlight>

===Logging in===
Now we have a function that is called through the custom event 'submitLogin', we can start to work on logging in and spawning the player, using our 'loginHandler' function:
<syntaxhighlight lang="lua">
function loginHandler(username,password)
-- check that the username and password are correct
if username == "user" and password == "apple" then
-- the player has successfully logged in, so spawn them
if (client) then
spawnPlayer(client, 1959.55, -1714.46, 10)
fadeCamera(client, true)
setCameraTarget(client, client)
outputChatBox("Welcome to My Server.", client)
end
else
-- if the username or password are not correct, output a message to the player
outputChatBox("Invalid username and password. Please re-connect and try again.",client)
end
end

addEvent("submitLogin",true)
addEventHandler("submitLogin",root,loginHandler)
</syntaxhighlight>
'''For the purposes of this tutorial, a very basic username and password system is shown. For a more comprehensive alternative, you can use the Account System or a MySQL database.'''

Also note the use of the variable "client", it's an internal variable used by MTA to identify the player who triggered the event.

Finally, do not forget to include the new gui.lua file in the meta.xml of the main resource, and label it as a client script:
<syntaxhighlight lang="xml">
<script src="client/gui.lua" type="client" />
</syntaxhighlight>

At this point, we now have a basic login window that checks the player's username and password when the login button is clicked. If they are correct, the player is automatically spawned.

For further help with GUI, see the [[:Category:GUI_Tutorials|GUI tutorials]].

[[Category:GUI_Tutorials]]
[[it:Introduzione_allo_scripting_della_GUI]]
[[ru:Introduction to Scripting the GUI]]
[[es:Introducción a la Programación de GUI]]

Places To Chat

2017-01-01T18:43:50Z

JHXP: Reverted edits by Marcin778 (talk) to last revision by Tomc0

There are a number of ways you can chat with other MTA players. Whether you want to discuss your gaming techniques, arrange clan matches, or even join a clan, there's always somewhere to go.
Of course you can chat with some people whilst playing via the ingame chat. But there are many places where a large proportion of the MTA community often visit. Some of these are described below.

== Forums ==
The first place you are likely to come across is the official MTA Community Forums. These are found at [http://forum.mtasa.com http://forum.mtasa.com]. You are free to browse around and read what other people have to say, but to put your own point of view across and start your own discussions, you will have to Register at the forums. This is free and can be done by clicking the Register link at the top of the page.

The forums are split up into a number of categories and sub-forums. These organise all the topics, and you should make sure that before you start your own topic, you are in the right forum. Also, before making any posts, be sure to read the [http://forum.mtasa.com/viewtopic.php?f=15&t=15740#p219286 rules].

== IRC (Internet Relay Chat) ==
For an instant response to whatever you have to say, the best place is IRC. IRC is a chat network similar to any other chat rooms you find on the internet. The best Windows client for IRC is mIRC, which you can find [http://www.mirc.com here]. Download, install, configure the settings and you are ready to go.
The connection information you need is:<br>
'''Server -''' [irc://irc.gtanet.com/mta irc.gtanet.com/mta]<br>
'''Port -''' 6667<br>
Once you have connected and received the MOTD (message of the day), to join the MTA discussion, type /join #mta
This takes you into the MTA ''channel'', which you would know as a room in other chat networks.
Make sure you read the mIRC help files if you are unsure.
For more specific help for the server commands, go to the window you first had when connecting, and type /helpop for a list of help categories.

=== Scripting Help ===
There is an IRC Channel available for help with MTA Scripting. You can find it at #mta.scripting on GTANet (irc.multitheftauto.com).

==== How To Get Help ====
* Try to find your Answer on the [[Main Page]], especially on its upper part
* Ask your question once and only repeat it after a reasonable amount of time, given the channel is busy and people just coming online won't see your question else (like 10 minutes). NOT after 10 seconds.
* Your question should at least contain:
** What are you trying to do.
** What have you done so far.
** What exactly doesn't work/is your problem. What errors are occuring.
** Maybe a code snippet with an explanation using [http://mta.pastebin.com mta.pastebin.com] (''code snippet means the relevant parts, NOT the whole script'')

== Other ==
These aren't all the places/ways of talking with other members of the MTA community. There are many many more forums than the official MTA one, for example [http://www.gtaforums.com GTAForums] which is the most popular unofficial GTA community forum. Although not just MTA discussion, online play is a popular topic of discussion.

Please feel free to edit this page if you have something else to add.

[[es:Places_To_Chat_ES]]
[[ru:Places To Chat]]
[[hu:Places To Chat]]

[[Category:Support]]

How you can help

2017-01-01T18:43:48Z

JHXP: Reverted edits by Marcin778 (talk) to last revision by ThePiotrek

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

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

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

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

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

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

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

==Grant==
You can donate MTA:SA [https://mtasa.com/donate/manage.php here]

[[pl:Jak możesz pomóc]]
[[ru:How you can help]]
[[es:Cómo puedes ayudar]]
[[hu:How you can help]]
[[tr:Nasıl yardımcı olabilirsiniz]]

Scripting Introduction

2017-01-01T18:43:46Z

JHXP: Reverted edits by Marcin778 (talk) to last revision by MTANeXuS

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://www.sublimetext.com/ Sublime Text], [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===
[[Event|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:'''
* [[OOP_Introduction|OOP Scripting Introduction]]
* [[Advanced Topics]]
* [[Script_security|Script security]]
* [[Scripting Introduction Urdu]]
[[es:Introducción a la Programación]]
[[it:Introduzione allo scripting]]
[[nl:Scripting_introductie]]
[[pt-br:Introdução ao Scripting]]
[[ru:Scripting Introduction]]
[[hu:Scripting Intorduction]]
[[ar:مقدمه_في_البرمجه]]
[[zh-cn:脚本编写介绍]]
[[Category:Tutorials]]

Category:Needs Checking

2017-01-01T18:43:44Z

JHXP: Reverted edits by Marcin778 (talk) to last revision by Winky-

These are functions that need to be checked to ensure they do work as specified. If there are any problems with a function, attach a note to the top of the page and describe the problems. Use this format:

<nowiki>{{Needs_Checking|STATE_PROBLEM_HERE}}</nowiki>

Result:
{{MessageBox|
bordercolorhex = 0026FF |
bordertype = dotted |
bgcolorhex = CCCCFF |
image = File:Dialog-information.png |
title = This article needs checking. |
subtext = '''Reason:''' STATE_PROBLEM_HERE |

}}
This is a template, that is specially designed to automatically add the pages it is used on to the Needs_Checking category. For this reason, '''DO NOT manually add <nowiki>[[Category:Needs Checking]]</nowiki>'''.

<div style="border:3px solid red;margin-bottom:3px;padding-left:10px;"><div style="float:right;padding-right:5px;font-weight:bold;"></div>
''Note: This category is for functions that are missing extra information (ie clothes catalogue for argument), function incorrectly, or may be incorrectly written. Also use it to note undefined 'dictionary' pages for words (ie "id" "radians"). Functions that are missing sections goto "incomplete category" list. Even if there is a needs checking note as well.''
</div>
<noinclude>[[Category:Maintenance]]</noinclude>

Category:Needs Example

2017-01-01T18:43:42Z

JHXP: Reverted edits by Marcin778 (talk) to last revision by MeowCola

This is a category with pages which require examples to be written or tested. The rest of the documentation for these pages should be complete.

Add this code to Example section. Set "client" for clientside example and "server" for serverside.
<pre>
<section name="Client" class="client" show="true">
--Explain what the code does
<syntaxhighlight lang="lua">
-- Add example
</syntaxhighlight>
</section>
</pre>

[[Category:Maintenance]]

[[ru:Category:Needs Example]]

Category:Incomplete

2017-01-01T18:43:40Z

JHXP: Reverted edits by Marcin778 (talk) to last revision by OpenIDUser32

This is a list of functions that need to be documented. To list a function as incomplete, add the following to the function's page:

<nowiki>[[Category:Incomplete]]</nowiki>

[[Category:Maintenance]]

Branches

2017-01-01T18:43:38Z

JHXP: Reverted edits by Marcin778 (talk) to last revision by Qaisjp

== Weapon Creation ==
Weapon creation is a branch for creating weapon elements which can fire bullets and do not require ped/players assigned to them.
{| class="wikitable" style="width: auto; table-layout: fixed;"
|-
|'''Status'''
|<span style="color:green">Merged - 1.3.1</span>
|-
|'''Branch'''
|[https://github.com/multitheftauto/mtasa-blue/tree/weapon-creation Weapon-Creation]
|-
|'''Branch version'''
|1.4
|}

=== Functions ===
{{Client_weapon_creation_functions}}

=== General Notes ===
Created entities are for all intent and purpose objects so any object function will work on them like attachElements, setElementAlpha and such.

=== Media ===
* http://youtu.be/LN1nZZnzlms

== Custom Animations ==
Custom Animations is a branch for loading animations from .ifp files
{| class="wikitable" style="width: auto; table-layout: fixed;"
|-
|'''Status'''
|<span style="color:red">Abandoned</span>
|-
|'''Branch'''
|[https://github.com/multitheftauto/mtasa-blue/tree/Custom-Animations Custom-Animations]
|-
|'''Branch version'''
|1.4
|}

=== Functions ===
* [[engineLoadIFP]]
* [[engineUnloadIFP]]

=== Media ===
* http://youtu.be/D9YfVPiJniU

=== General Notes ===
See [[User:Cazomino05]] for bugs.

== Custom Weapon Stats ==
Custom Weapon Stats is a branch to allow people to edit one of each weapons "properties" for each skill level
so for example an M4 at Pro level can have 1000 damage and an M4 at standard level can have 0.

{| class="wikitable" style="width: auto; table-layout: fixed;"
|-
|'''Status'''
|<span style="color:green">Merged - 1.3.1</span>
|-
|'''Branch'''
|[https://github.com/multitheftauto/mtasa-blue/tree/Custom-Weapon-Stats Custom-Weapon-Stats]
|-
|'''Branch version'''
|1.4
|}

=== Functions ===
* [[getWeaponProperty]]
* [[setWeaponProperty]]

=== Media ===
* http://youtu.be/M1dQWpDFq98
* http://youtu.be/xfdEvpcuk7s
* http://youtu.be/eDU06fZiU9M

=== General Notes ===
None.

== Analog Control States ==
Analog Control States is a branch that is designed to allow proper setting and management of controls and therefore allows for setting of controls to be between the range of 0 and 1 rather than true/false

This only works for certain properties such as left/right

{| class="wikitable" style="width: auto; table-layout: fixed;"
|-
|'''Status'''
|<span style="color:green">Merged - 1.3.1</span>
|-
|'''Branch'''
|[https://github.com/multitheftauto/mtasa-blue/tree/Analog-Control-States Analog-Control-States]
|-
|'''Branch version'''
|1.4
|}

=== Functions ===
* [[setAnalogControlState]]
* [[getAnalogControlState]]

=== Media ===
None.

=== General Notes ===
None.

== Custom-Vehicle-Sirens ==
Custom Vehicle Sirens allows adding sirens to any individual vehicle in the game for instance to add an undercover sultan.

{| class="wikitable" style="width: auto; table-layout: fixed;"
|-
|'''Status'''
|<span style="color:green">Merged - 1.3.1</span>
|-
|'''Branch'''
|[https://github.com/multitheftauto/mtasa-blue/tree/Custom-Vehicle-Sirens Custom-Vehicle-Sirens]
|-
|'''Branch version'''
|1.4
|}

=== Functions ===
* [[SetVehicleSirens]]
* [[GetVehicleSirens]]
* [[RemoveVehicleSirens]]
* [[GetVehicleSirenParams]]
* [[AddVehicleSirens]]

=== Media ===
* http://youtu.be/zjJdLCtKccA
* http://youtu.be/ZJDrVf3qSm0
* http://youtu.be/1J0_v85FioA
* http://youtu.be/X3zE6hZOx4c

=== General Notes ===
None.

== Custom-Train-Tracks ==
See the main page for this branch ([[Custom Train Tracks]]) for more information.
{{:Custom_Train_Tracks}}

== Awesomium ==
Possibility to create ingame browser.

{| class="wikitable" style="width: auto; table-layout: fixed;"
|-
|'''Status'''
|<span style="color:green">Merged - 1.5</span>
|-
|'''Branch'''
|[https://github.com/multitheftauto/mtasa-blue/tree/awesomium Awesomium]
|-
|'''Branch version'''
|1.5
|}

=== Functions ===
See [[User:Jusonex]].

=== Media ===
* http://youtu.be/9w2qU6mZDh8
* http://youtu.be/qvqc1ScZSbM
* http://youtu.be/cyUw1F6uBig

=== General notes ===
See [[User:Jusonex]].

[[Category: Development]]

Coding guidelines

2017-01-01T18:43:36Z

JHXP: Reverted edits by Marcin778 (talk) to last revision by Arran Fortuna

= Introduction =

So you've decided to become a contributor to our project. Excellent! But before we can start accepting your code, there are a couple of things you should know about how we work. These are mostly guidelines and rules as to how your code should be structured and how it can be committed without upsetting any fellow contributors.

= Code repository =

== Structure ==
Our code repository uses Git and is structured into number of different directories, which serve different purposes:

* '''Client'''
* '''Server'''
* '''Shared''': contains code shared between both the client and the server
* '''irc''': bot code for the Multi Theft Auto IRC channels
* '''m4'''
* '''utils''': utilities used to automate certain tasks
* '''vendor''': unmodified third-party code and libraries (optionally linked to the appropriate third-party Git repository through Git submodules).

Our branches contain groundbreaking research, radical ideas and other work-in-progress that is meant to be merged into the trunk at a later point, but also contains project milestones:

* The master branch is the main development branch (containing the latest, bleeding-edge code)
* Project milestones are kept away from the trunk for stability reasons, but the latest version branch can be used by any regular player who has enabled nightly builds. Make sure that only well tested code is added to the latest version branch.

== Gaining and Losing Commit access ==
Commit access is granted after patches have been submitted, and the coder has proven to be competent. The subject matter of the patches does not matter, we are more interested in whether if you are granted commit access, you will be capable of maintaining a high standard of code and remaining cohesive with other project contributors.

Patches can be submitted using [https://github.com/multitheftauto/mtasa-blue/pull/new GitHub's pull request system]. Usually commit access is gained after 2-3 patches, but this is not fixed and depends on the extent of the contributions. This requires you to fork our repository and make commits to your own branch first.

After gaining commit access, if the contributor's commits are of a consistently low standard, or the user fails to stick to the rules, their commit access will be stripped and will be required to submit pull requests again.

== Committing code ==
Keep in mind that your commits should initially be fixing or implementing existing issues on our [http://bugs.mtasa.com bug tracker]. The [http://bugs.mtasa.com/roadmap_page.php roadmap] is particularly important since it allows contributors to track down priority issues.

Please follow these guidelines for all your contributions:
* Commits should be thoroughly tested when added to master. Commits that 'need to be fixed later' which directly affect the state of the mod will be reverted other than in exceptional circumstances.
* If writing unstable or experimental code, a private branch should be added in your own fork. Branches should not be "personal" to each user. This means that a branch should be created for a new feature, not for a user specific playground.
* Commit messages should always give a clear indication of the content of the change, without having to look at the code at all. Where appropriate, include the Mantis Issue number in your log message and keep your log messages consistent, e.g. '''Fix #1234: description and notes here'''. [http://chris.beams.io/posts/git-commit/ Follow the seven rules identified here.]
* When committing updates to previous commits, include the previous commit SHA (and a summarised commit message) in the new commit message. Doing this will help identify related commits if they are viewed at a later date.

== Ratings and comments ==
Ratings and comments are open for the public to review code and provide feedback. Please be mature and civilised when posting comments. Developers should try to review other contributor's commits and provide feedback as much as possible.

Make sure you make appropriate use of the GitHub Reactions feature to rate commits or express agreement/disagreement to a comment. This avoids spammy comments such as "+1", "-1", "Nice one!", etc.

Since you can only react to comments, not commits, feel free to create the initial "+1" comment in response to a commit. However, future reactions to a commit should be to the first response comment.

== What to code ==
Generally, developers should try to stick to the [http://bugs.mtasa.com/roadmap_page.php roadmap] when coding. This lists the issues required to be resolved for the next release. Of course, if you're interested in something else, feel free to experiment and submit it.

== Style ==
* We use 4 spaces instead of tabs.
* Hungarian notation for variable names.
float fValue; // Local variable
unsigned char m_ucValue; // Class member variable
char ms_cValue; // Class static variable
bool g_bCrashTwiceAnHour; // Global variable
char* szUsername; // Zero terminated string
SString strUsername; // String
CVector vecPosition; // 3D Vector
* Lower camel case for variable names of types like custom structs and enums:
SSomeStruct valueOne;
ESomeEnum m_valueTwo;
* Function names use UpperCamelCase:
void UpperCamelCase( void )
* A space between almost everything:
int iResult = 2 + 4 * GetValue() + 123;
* A space between a function name and the open parenthesis is optional:
void OkOne ( void )
void OkTwo( void )
OkThree ();
OkFour();
* Functions with no arguments are declared and defined with ( void ), and called with ()
void MyTest( void );
void MyTest( void ) { return; }
MyTest();
* Functions and member variables of classes/structs are all lined up in neat columns:
void FunctionOne ( void );
void FunctionTwo ( void );
float fValue;
* For anything else, follow the style of the code that already exists.

* Tip: In Visual Studio go to Tools -> Options -> Text Editor -> C/C++ -> Formatting -> Spacing and you can configure it to automatically apply the right spacing.

== Coding info ==
Check out the [[Coding info]] page and feel free to add more coding info to it.

[[Category: Development]]

Building MTASA Server on GNU Linux

2017-01-01T18:43:34Z

JHXP: Reverted edits by Marcin778 (talk) to last revision by CiBeR

{{Needs Checking|Confirm steps work.}}

== Installing and Running MTASA server on Linux ==
{{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] and see [[Installing and Running MTASA Server on GNU_Linux]]}}


== 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 {{Current Version|master}} if you are compiling from the trunk, or the net.so from {{Current Version|full}} if you are compiling the {{Current Version|full}} branch. Be sure the read the top of ''Server/version.h'' as it contains directions on how to compile the different build types.

=== 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

* '''libreadline5-dev:''' contains the readline library (version 5)
* '''libncurses5-dev:''' contains software for controlling writing to the console screen
* '''libncursesw5-dev:''' contains support for wide characters

* '''libmysqlclient-dev:''' contains the MySQL library
* '''git:''' contains the git client used to check out our code repository
To install these packages through apt, use the apt-get install <package list> command as in the following example (execute as root):

apt-get install build-essential automake libtool
apt-get install libreadline5-dev libncurses5-dev libncursesw5-dev
apt-get install libmysqlclient-dev git

Note: On Debian 8 systems please use this: '''apt-get install build-essential automake libtool libreadline-gplv2-dev libncurses5-dev libncursesw5-dev libmysqlclient-dev git'''
=== 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:


* '''git:''' contains the git client used to check out our code repository
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:

emerge -v git sqlite
USE=“net-misc/curl ssl” emerge -v curl

=== Fedora ===

You will need these packages to be able to successfully compile a MTA server on Fedora:
* '''glibc-devel:'''

* '''readline-devel:''' contains the readline library

* '''git:''' contains the git 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):

yum install glibc-devel readline-devel git

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

'''Downloading the source.'''

First you need to download the source. Either clone as show below or [https://github.com/multitheftauto/mtasa-blue/archive/master.zip download a zip snapshot]

git clone <nowiki>https</nowiki>://github.com/multitheftauto/mtasa-blue.git mtasa-blue
cd mtasa-blue

Then compile it thus:

./mta-build.sh

Then copy the configuration files, network module and resources into '''Bin/server''' by running this command:

./mta-install.sh

And the server should be ready in '''Bin/server'''

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

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]

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

Resource:Editor

2017-01-01T18:43:32Z

JHXP: Reverted edits by Marcin778 (talk) to last revision by AgEnT x19

{{Resource page}}
The MTA:SA map editor allows you to create maps for gamemodes.

==Starting==
To start the editor, simply click the "Map editor" menu item in the main MTA menu.

==Menus==
Once the editor has started, you are presented with two menu bars: the main menu at the top, and the element menu in the lower left.

===Main menu===
These are the buttons in the main menu:
* [[Image:Editor_New.png]] Create a new map.
* [[Image:Editor_Open.png]] Open an existing map.
* [[Image:Editor_Save.png]] Save the map you're working on.
* [[Image:Editor_Save_as.png]] Save your map under a different name.
* [[Image:Editor_Options.png]] Alter general map editor settings.
* [[Image:Editor_Undo.png]] Undo the last action.
* [[Image:Editor_Redo.png]] Restore the last undone action.
* [[Image:Editor_Locations.png]] Stored game world locations. The editor comes with a great list of San Andreas Interior locations but you can also add your own interior and non-interior locations to the list.
* [[Image:Editor_Current_elements.png]] List all the elements the map contains (objects, vehicles, markers, pickups etc.)
* [[Image:Editor_Map_settings.png]] Map specific settings, like time of day, gravity etc. Here you can also specify what gamemodes the map is compatible with.
* [[Image:Editor_Definitions.png]] Load [[Resource:Editor/EDF|editor definition files (EDF)]] that you want to use.
* [[Image:Editor_Test.png]] Go into play mode to try out the map. This will load up the gamemode the map is made for.

===Element menu===
The element menu is used to add new elements to the map.
* [[Image:Editor_Vehicle.png]] Create a new vehicle.
* [[Image:Editor_Object.png]] Create a new object (buildings, roads and other scenery).
* [[Image:Editor_Pickup.png]] Create a new pickup (health, armor, weapons and custom).
* [[Image:Editor_Marker.png]] Create a new marker (checkpoint, ring, cylinder, arrow and corona).
* [[File:Crosshair.png‎]] Select world object.
Additionally, if you have [[Resource:Editor/EDF|editor definitions loaded]], you can roll the mousewheel in this menu to bring up custom elements.

==Using the editor==
This section explains how to create and modify maps.

===Moving around the map===
When you initially start the editor, you are in ''camera mode''. You are able to use the '''WSAD''' keys to move the camera and the mouse to pan the camera. While moving around, you can hold '''ALT''' to move more slowly or '''SHIFT''' to go faster.

To access the editor's interface and control panel you need to switch to ''cursor mode''. You can toggle between cursor mode and camera mode with the '''F''' key. When in cursor mode, your view is fixed, and you can use the mouse cursor to manipulate elements and use the graphical interface.

Camera mode can be recognized by a crosshair in the center of the screen. You can use it to select and move elements just like in cursor mode.

[[Image:Editor_Crosshair.png|center]]

===Starting a new map===
* Start the editor, or if it is already started, click the ''New'' menu button.
* Click the ''Map settings'' button. In the ''Meta'' tab, fill in the Name and Author fields with the name of the map and your name respectively. Also open the ''Gamemodes'' tab and add the gamemodes your map is meant for (they will be moved to the ''Added gamemodes'' list). You can do this by selecting them and clicking ''Add'', or by double clicking them. Click OK when you're done.
[[Image:Editor_Mapsettings.png|center]]
* Click the ''Definitions'' window and add the resources of which you want to use the custom elements. These will consist of the gamemodes you selected in the ''Map settings'' window, plus eventual additional resources. For more information about editor definitions, see [[Resource:Editor/EDF|EDF]]. Click OK when you're done.

===Creating new elements===
Adding elements to your map, such as vehicles and objects, is very straightforward.
* If you are in camera mode, switch to cursor mode first by pressing '''F'''.
* Click the button in the element menu that represents what you want. E.g., click the button with a car on it to add a vehicle.
* A new element of the selected type will be created and attached to your cursor. Move it to the location where you want it and '''left click''' to drop it off.

[[Image:Editor_Addelem.png|center]]

To create custom elements that are specific to a resource, hover the cursor over the element menu and turn the scroll wheel until the desired resource comes up. Note that for this to work, you first have to add the [[Resource:Editor/EDF|EDF]] file of the resource in the ''Definitions'' window.

[[Image:Editor_Selectedf.png|center]]

===Selecting===
* '''Left click''' an element to select it in ''keyboard mode''.
* '''Right click''' it to select it in ''mouse mode''.
* Press the '''Spacebar''' or click in an empty area to deselect.

The selected element, if any, is denoted by a yellow cone marker. Elements (particularly objects) with poor collisions can be detected easier by enabling ''High sensitivity mode'', by pressing the '''E''' key. This increases detection at the expense of accuracy.

The ''Current elements'' dialog can also be used to select elements. Double-clicking an item within the list will select it in ''Keyboard mode''.

===Moving===
Moving elements can be done in several ways.

'''With the mouse'''
* Simply drag and drop with the '''left mouse button'''.
Or:
* Select the element in mouse mode ('''right click'''), move it to where you want it, and click to drop it off.

You can also adjust the ''Hold distance'' of an element toward and away from the camera by switching to camera mode, '''right clicking''' the element, and rolling the '''mouse wheel'''.

'''With the keyboard'''
* Select the element in keyboard mode ('''left click''').
* Use the '''arrow keys''' to move the element in the horizontal plane, and '''PgUp'''/'''PgDn''' to move it vertically. Hold '''ALT''' to decrease the movement speed, or '''SHIFT''' to increase it.

By default, elements move relative to the camera and are not locked to any axes. This can be disabled in the ''Options'' menu.

===Rotating===
'''With the mouse'''

You can rotate selected elements around the Z axis with the mouse wheel.
* Select the element in keyboard mode ('''left click''') and roll the mouse wheel while holding '''Left CTRL'''.
Or:
* Select the element in mouse mode ('''right click'''), hold '''CTRL''', and roll the mouse wheel.

'''With the keyboard'''
* Select the element in keyboard mode ('''left click''').
* While holding '''CTRL''' (the selection marker will turn green), use the '''arrow keys''' and '''PgUp'''/'''PgDn''' to rotate the element around the different axes.

With both methods you can additionally hold '''ALT''' to decrease the rotation speed or '''SHIFT''' to increase it.

[[Image:Editor_Rotateelem.png|center]]

===Changing model and other properties===
Most elements have a variety of options that can be altered to change their appearance and behaviour. Examples are the model, color and visual upgrades of a car.

* Open the properties window of an element by either double clicking it or by selecting it and pressing '''F3'''.
* Make any alterations that you want. For example, to change the model of a car or object, click the '''Browse''' button next to "model" to open the model browser.
* Click OK when you're done.

[[Image:Editor_Props.png|center]]

===Cloning===
You can clone an element by selecting it and pressing '''C'''.

* In mouse mode the cloned element will be attached to your cursor. '''Left click''' to place it in the map.
* In keyboard mode the cloned element will be cloned in the identical position.

If you hold '''CTRL''' while clicking, the element will be cloned again and will again be attached to the cursor. This way you can easily place large quantities of something.

Alternatively you can use the ''Pullout'' button located in the bottom-right corner of the properties box to clone an element.

===Deleting===
Simply select the element and press '''DEL''' ''(Delete)''.

Alternatively you can use the ''Pullout'' button located in the bottom-right corner of the properties box to delete an element.

==Creating maps for specific gamemodes==
To make a map for a specific gamemode, you have to do two things:
* Click the '''Map Settings''' button in the top menu, go to the '''Gamemodes''' tab and add any gamemodes that your map is to be used with.
* You will likely also need to add one or more [[Resource:Editor/EDF|Editor Definition Files]]. These will allow you to place gamemode specific elements in the map, like spawnpoints, race checkpoints, or CTF flags. You can add EDF's by clicking the '''Definitions''' menu button and adding the relevant gamemodes.

==Controls==
Here is a list of all default controls. To change them please go to the MTA Settings menu while the Editor is started.

===Camera===
{|
|-
| camera_move_forwards
| '''w'''
|-
| camera_move_backwards
| '''s'''
|-
| camera_move_left
| '''a'''
|-
| camera_move_right
| '''d'''
|-
| high_sensitivity_mode
| '''e'''
|}

===Cloning===
{|
|-
| clone_selected_element
| '''c'''
|-
| clone_drop_modifier
| '''lctrl''' || ''(Left CTRL)''
|}

===Element manipulation===
{|
|-
| element_move_forward
| '''arrow_u''' || ''(Arrow key Up)''
|-
| element_move_backward
| '''arrow_d''' || ''(Arrow key Down)''
|-
| element_move_left
| '''arrow_l''' || ''(Arrow key Left)''
|-
| element_move_right
| '''arrow_r''' || ''(Arrow key Right)''
|-
| element_move_downwards
| '''pgdn''' || ''(Page Down)''
|-
| element_move_upwards
| '''pgup''' || ''(Page Up)''
|-
| zoom_in
| '''mouse_wheel_down'''
|-
| zoom_out
| '''mouse_wheel_up'''
|-
| quick_rotate_increase
| '''mod_rotate''' + '''mouse_wheel_up''' || ''(Left CTRL + Mouse wheel Up)''
|-
| quick_rotate_decrease
| '''mod_rotate''' + '''mouse_wheel_down''' || ''(Left CTRL + Mouse wheel Down)''
|-
| mod_rotate
| '''lctrl''' || ''(Left CTRL)''
|-
| mod_slow_speed
| '''lalt''' || ''(Left ALT)''
|-
| mod_fast_speed
| '''lshift''' || ''(Left SHIFT)''
|-
| destroy_selected_element
| '''delete'''
|-
| drop_selected_element
| '''space'''
|-
| pickup_selected_element
| '''F2'''
|-
| reset_rotation
| '''mod_rotate''' + '''r''' || ''(Left CTRL + R)''
|}

===GUI===
{|
| toggle_gui_display
| '''F4'''
|-
| toggle_cursor
| '''f'''
|-
| select_target_keyboard
| '''mouse1''' || ''(Left Mouse button)''
|-
| select_target_mouse
| '''mouse2''' || ''(Right Mouse button)''
|-
| edf_next
| '''mouse_wheel_up'''
|-
| edf_prev
| '''mouse_wheel_down'''
|-
| undo
| '''Ctrl''' + '''z'''
|-
| redo
| '''Ctrl''' + '''y'''
|-
| properties_toggle
| '''F3'''
|-
| browser_up
| '''arrow_u''' || ''(Arrow key Up)''
|-
| browser_down
| '''arrow_d''' || ''(Arrow key Down)''
|-
| browser_zoom_in
| '''mouse_wheel_up'''
|-
| browser_zoom_out
| '''mouse_wheel_down'''
|-
| browser_confirm
| '''enter'''
|-
| currentelements_up
| '''num_8''' || ''(Numpad key 8)''
|-
| currentelements_down
| '''num_2''' || ''(Numpad key 2)''
|-
| toggle_test
| '''F5'''
|}

==Multiplayer==
The editor is built with both serverside and clientside components, and therefore supports multiplayer out of the box. To use the editor in multiplayer with other players, simply copy all of the editor's resources into your server, start the '''editor''' resource and allow other players to join.

Please note that currently the editor lacks any permissions system, so all users have access to every function.

==Plugins & External resources==
{{Main|Resource:Editor/Plugins}}

The editor allows basic importing of elements from external resources. This is useful for resources that may have to manipulate an element in a specific way that cannot be performed by the editor. For example, a map resource which uses custom models (and has a script to import these models) cannot be manipulated by default within the editor.

By using the '''import <resourceName>''' command in console the resource's elements can be imported within the editor.

==FAQ==
==== I get a black screen when launching the Map Editor ====

Usually this is caused due to incorrect installation of Map Editor resources. If you are using a stable MTASA client, please install it again and make sure that you use Client and Server install option.

If you are using a nightly build, to get it working right you need to download latest [http://code.google.com/p/multitheftauto/wiki/NightlyBuilds?tm=2 resources (step 3)], unpack the archive and put its contents in:
''MTA San Andreas\server\mods\deathmatch\resources'' , where ''MTA San Andreas'' is a folder where you've installed MTA San Andreas (default location: C:\Program Files\MTA San Andreas).

Putting them in this path: MTA San Andreas\mods\deathmatch\resources '''is a common mistake''' - it won't work if you put them there. So make sure to put them in the ''italic'' path above.

If this issue still occurs, even when you've checked the note above and verified that you've installed it correctly, it might be because you've got an outdated '''acl.xml''' file. You can download the default one [http://multitheftauto.googlecode.com/svn/trunk/MTA10_Server/mods/deathmatch/acl.xml here]. It should be placed in '''server/mods/deathmatch/''' in your MTA: San Andreas installation directory.

==== I get an "Could not start the local server. See console for details" when using the "Map Editor" button ====
This is because you do not have a valid editor.conf installed. You can download the default one [http://multitheftauto.googlecode.com/svn/trunk/MTA10_Server/mods/deathmatch/editor.conf here]. It should be placed in '''server/mods/deathmatch/''' in your MTA: San Andreas installation directory.

==== I have saved a map but cannot find it in my server's resources directory, despite the Editor itself being able to see it ====
This is due to the fact that Vista/7 limits write-access for non-admin processes in Program Files directory. Files get written in the "VirtualStore" directory instead of real Program Files folder. You should be able to locate your map resource in a similar directory to:
C:\Users\<USERNAME>\AppData\Local\VirtualStore\Program Files\MTA San Andreas\server\mods\deathmatch\resources\

Running the Server/MTA San Andreas with Administrative rights will allow the map to be saved to the proper location.

==== I have some other problem with the map editor ====

Sometimes resetting the map editor will solve certain issues. The easiest way to do that is install MTA:SA to a brand new folder. Otherwise you can try the following steps:
::1. Go to the resources folder, '''server/mods/deathmatch/resources/''' and delete the '''editor_dump''' directory
::2. Go to the resources folder, '''server/mods/deathmatch/resources/''' and delete the '''editor_test''' directory

==== I have found a bug or have a suggestion/feedback for the map editor ====
Please use the official [http://bugs.mtasa.com bugtracker] for reporting bugs. Feel free to also join us on [http://www.multitheftauto.com/irc.html IRC].

[[ru:Resource:Editor]]
[[es:Resource:Editor]]

Server Manual

2017-01-01T18:43:31Z

JHXP: Reverted edits by Marcin778 (talk) to last revision by Ccw

__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]
* [[Installing and Running MTASA Server on GNU Linux]]
* [[Building MTASA Server on GNU Linux]]

Should you have any problems with errors when starting the server some common problems and solutions are listed here:
* [[Building MTASA Server on GNU Linux#Troubleshooting]]

===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 client console (F8) 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>

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. ''<nowiki>http://www.myserver.tld/directory</nowiki>'' rather than ''<nowiki>http://www.myserver.tld/directory/</nowiki>'')<br />
'''Note 3''': The web server must use 'ContentType: application/octet-stream' for Lua files. Most web servers will do this by default, or you can add the following line to the .htaccess file:<br />
<div style="padding: 10px">
<syntaxhighlight lang="xml">AddType application/octet-stream .lua
</syntaxhighlight></div>

Instructions on how to install and configure Nginx as an external web server for MTA is here: [[Installing and Configuring Nginx as an External Web Server]]

==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]]
[[pt-br:Manual do Servidor]]
[[hu:Server Manual]]

[[Category:Support]]

Upgrading from MTA:Race

2017-01-01T18:43:29Z

JHXP: Reverted edits by Marcin778 (talk) to last revision by AlexTMjugador

__NOTOC__
MTASA:Race was the first Multi Theft Auto release for Grand Theft Auto San Andreas. Since its release, we've seen thousands of maps and a vast, active community develop and mature. Despite this, for everything there is a time to move on. Multi Theft Auto: San Andreas {{padleft:|3|{{Current Version|full}}}}, in conjunction with the latest version of the [[Resource:Race]] gamemode provides a stable platform for server admins and gamers alike to upgrade to the most powerful GTA Race experience yet.

== Why upgrade? ==
Although it may seem that its safer to stick what works, the release of {{padleft:|3|{{Current Version|full}}}} will provide a significant step-up in the multiplayer experience.

=== Scripting ===
With the arrival of MTA:SA {{padleft:|3|{{Current Version|full}}}}, comes a powerful and flexible Lua scripting interface. This surpasses previous scripting abilities of Race servers in every single way. By utilising the Lua script interface, server admins and players alike can take advantage of features such as:
* '''Fully fledged built-in scripting.''' No more external mIRC clients to run your Admin interface
* '''Take full advantage of the Plugins system of Race.''' By developing Lua plugins, the bounds to extend Race are limitless. Examples that are included in the release package are the Traffic Sensor, which uses HUD to display when cars are behind you, and a Top Times plugin, which displays the person with the best record in a certain race.
* '''Extend the possibilities of any map.''' By attaching a Lua script to your map, you can have virtually anything happen during gameplay. Custom models, moving objects, timed explosives and upside down gravity tracks are all possibilities by taking advantage of scripting.
* '''Full customisability.''' Customisable UI, along with a possibility to add custom pictures, objects, sounds, and vehicle models, specific to your server. Imagine being able to display your server's logo during gameplay on the screen.

=== Gameplay ===
The MTA:SA {{padleft:|3|{{Current Version|full}}}} platform is much more versatile and therefore makes the gameplay experience superior to MTA:Race. On top of this, the Race gamemode has had hundreds of improvements to make the racing experience much more fun.
* Have up to '''4096 players''' in your Race server. That's a lot more than ''32''. You may wonder "How on earth do 4096 people fit on the track?". No problem, the latest Race offers a '''ghostmode''' feature so that high player counts are feasable.
* Support for newest Microsoft Windows operating systems like Windows Vista, Windows 2008, Windows 7, Windows 8/8.1 and Windows 10 in both x86 and x64 flavours. Due to the open-source nature of MTA:SA {{padleft:|3|{{Current Version|full}}}}, compatiblity is mantained constantly.
* Much more accurate vehicle synchronisation. When switching to {{padleft:|3|{{Current Version|full}}}}, the first thing racers will notice is the amazing vehicle synchronisation. It now is incredibly smooth, and synced much more precisely - an essential to any racing game.
* The Traffic Sensor addon means nearby opponents are displayed on the screen. At last, you can be aware of which way those tailgating opponents are challenging you!
* The all new open-sourced [[Resource:Editor|Map Editor]] means you can create your race maps with ease.
* MTA:SA {{padleft:|3|{{Current Version|full}}}} provides a single mod for '''all''' your online GTA needs.

=== Server owner's paradise ===
With the latest Race, server owner's are in control: you are able to customise the Race experience. Become a truly unique server.
* '''Improved ingame Admin.''' MTA:SA {{padleft:|3|{{Current Version|full}}}} offers an ingame Admin interface where you can easily point and click to effortlessly moderate a server.
* '''Improved stability, performance and bandwidth usage'''. The {{padleft:|3|{{Current Version|full}}}} and Race platform have been tested extremely thoroughly, and this has meant the bar has been raised much higher than the original MTA:Race. Bandwidth has been paid special attention to, and upgrading server owners will reap the benefits of optimized bandwidth usage for their servers.
* '''Framelimiter'''. We've all seen it - that frustrating FPS limit in MTA:Race. The arrival of {{padleft:|3|{{Current Version|full}}}} means server owners can set the FPS limit of their particular server.
* '''Customisability'''. As mentioned several times - everything is in your control. Using Lua you can modify and improve the open-source Race experience. The new Plugins system means you can easily add or remove components that extend MTA:Race

=== Community ===
If you ever have any issues, we'll be happy to assist you in our forums. The growing amount of scripters for MTA:SA {{padleft:|3|{{Current Version|full}}}} has also meant we have a much more alive and vibrant community than previously with MTA:Race.

== How do I upgrade ==
=== Race players ===
Upgrading your client to MTA:SA {{padleft:|3|{{Current Version|full}}}} is simple. And better yet, you have nothing to lose. MTA:SA {{padleft:|3|{{Current Version|full}}}} can be installed alongside your original MTA:Race installation without conflict.

All you have to do is head to the [http://www.mtasa.com/ download page] and install MTA:SA {{padleft:|3|{{Current Version|full}}}}.

=== Server Owners ===
Server owners can easily upgrade to MTA:SA {{padleft:|3|{{Current Version|full}}}}. Races are fully compatible after a short upgrade process. Simply install the latest server package, and use our [http://files.mtasa.com/apps/1.0/raceconv.zip batch converter] to convert your maps into MTA:SA {{padleft:|3|{{Current Version|full}}}} resource format. From then on, your converted maps work with the [[Resource:race|race gamemode]] and can be managed through the [[Resource:mapmanager|map manager]] and the [[Resource:votemanager|vote manager]].

[[pt-br:Migrando do MTA:Race ao MTA:SA 1.3]]
[[ru:Upgrading from MTA:Race]]

[[Category:Support]]

Known Issues - FAQ

2017-01-01T18:43:27Z

JHXP: Reverted edits by Marcin778 (talk) to last revision by JHXP

{{Note_box|Before you check the known issues make sure everything is [[Up-to-date]].}}
Post here your proposed Q&A, regarding the known problems with MTA:SA and their solutions, especially the problems we are encountering now, that might be also encountered by users in the final release. You are also welcome to edit them grammar/style wise.

* [[Resource:Editor#FAQ|Map editor FAQ/known issues can be found here.]]<br>
* [[MTA 0.5r2 Known Issues|Known issues for MTA 0.5r2 can be found here.]]

== Client ==
=== General ===
==== I have the Steam version of GTA San Andreas. How can I play MTASA? ====
:The Steam version of GTASA is currently incompatible with MTASA, just like it is with some other mods. However, it can be made to work with it.

:'''If you just want to play the newest version of the mod, all you need to do is download the mod from our home page and then install it'''. The installer will detect your Steam's GTASA installation and will make some adjustments automatically.
:No original files are modified in the process, so the single player mode will work the same way as it did before.

:If you want to play some older MTA:SA version (1.3.2 or older), follow a few simple steps, and the Steam version will be compatible with it:
:* '''Option 1:''' Find a '''GTA SA 1.00 No CD''' (Google will give useful results). You should obtain a 1.00 Cracked/NoCd EXE, not a Disc image. Any HOODLUM release will work fine.
:** Open the download with Winrar or other similar archive tools, and inside there should be a gta_sa.exe. Place this file inside your installation directory. This is normally '''C:\Program Files\Steam\steamapps\common\grand theft auto san andreas'''. No files need to be replaced during this process.
:This procedure will not affect your Steam version of GTASA, but will allow MTASA to boot alongside it.
:* '''Option 2:''' Use the unofficial [http://forums.steampowered.com/forums/showthread.php?t=1952458 steam downgrade patch], be sure to downgrade to 1.0 and not 1.01.

==== Does MTASA work with v1.01 or v2.00 of GTA San Andreas? ====
:No. It can be made to work with them however - please see [http://forum.multitheftauto.com/viewtopic.php?t=15151 this forum topic] for instructions on patching the exe.

==== Initial black screen/hanging GTA splash screens ====
:* '''MTA shows a permanent black screen or hanging GTA splash screens.'''

:It may be necessary that during/after the logo splash screens in Grand Theft Auto you have to give some input in order to skip the videos correctly. Try to click your left-mouse button a few times, or tapping a few keys.

:* '''MTA shows a permanent black screen after the GTA splash screens (possibly with text in the bottom right corner).'''

:This can be related to a lack of support for DirectX or video card features, on your system, which are needed to run the dynamically rendered menu. This dynamic menu is enabled by default. You can disable it by opening your [[coreconfig.xml]] configuration file located in the ''GTA San Andreas\MTA'' directory, and changing the value of ''menu_options'' to ''248''.

==== Halt after MTA splash screen ====
:* '''Nothing happens after the 'Stop playing with yourself' splash screen'''

:If you use nVidia GeForce, try turning off nView Desktop Manager before starting MTA.

:Also try deleting GTA San Andreas settings file ("gta_sa.set") in "Documents\GTA San Andreas User Files" folder.

:If it all fails and you run Kaspersky Anti-Virus or Internet Security, make sure status of "multi theft auto.exe" in not restricted. Other anti-virus software may block MTA from running.

==== Crash after MTA splash screen ====
:* '''MTA crashes after the 'Stop playing with yourself' logo. Both single player and the MTA: Race ran fine before.'''

:Try downloading the latest DirectX Runtime files from [http://www.microsoft.com/downloads/details.aspx?FamilyID=2da43d38-db71-4c1b-bc6a-9b6652cd92a3&DisplayLang=en Microsoft]. Also check in Task Manager, if :gta_sa.exe process isn't already running.

:If you run at any substandard resolutions (e.g. 960x720), try to change your resolution to a commonly supported one (e.g. 640×480, 800×600, 1024×768, 1152×864, 1280×1024) by launching Grand Theft Auto: San Andreas in normal mode, setting the new resolution and exiting.

:If you are a user of Windows Vista or Windows 7, try the following:
:* Enable Windows XP SP3 compatiblity mode for both Multi Theft Auto.exe and gta_sa.exe, setting their privilege level to "Run this program as an administrator".
:* Configure Data Execution Prevention: Use the setting ''Turn DEP for all programs and services except those I select''. Click ''add'' and find "Multi Theft Auto.exe" and "gta_sa.exe" and add them.
:* Run MTASA as administrator.

==== "Data files have been modified" ====
:* '''You receive an error stating "San Andreas data files have been modified"'''
:You can fix this by [http://updatesa.mtasa.com/sa/files/GTASA-data-1.0.4.exe installing this patch]. If that doesn't work, try reinstalling GTA San Andreas.


==== Crash after connecting to any server ====
:* '''MTASA crashes upon connecting to any server. Single player runs fine.'''

:Single player mods can affect the way MTA:SA works, potentially causing crashes - you should always use a clean GTASA install for MTA:SA.

:This might also occur on non-modded installs, when your GTASA executable is in an unsupported by MTA:SA version (eg. 1.0 German or Australian). To resolve this, use [http://forum.multitheftauto.com/viewtopic.php?f=89&t=15151 our converter].

==== Controls not working ====
:* '''My controls don't seem to work as they should.'''

:Try using the 'copygtacontrols' command in the console.

==== Incorrect models ====
:* '''Woman model's breasts look awkward ingame / I'm seeing odd, spider-like shaped player models.'''

:This is caused by the way GTA handles player stats. To fix this, be sure to set both fat and muscles player stats to 0, when you're changing player skin.

==== Incorrect drive-by functionality ====
:* '''Drivebys arent working as they should'''

:Drivebys are handled by script, and will change depending on the loaded gamemode.

==== Unsaved settings ====
:* '''My MTA setting(s) didn't get saved (...) I crashed.'''

:First, configure the MTA the way you want to, then exit the game and launch it again. Settings should get saved. Alternatively, try removing the coreconfig.xml file, then configure it and quit the game.

==== Gamepad support ====
:* '''MTA doesn't recognise my gamepad'''

:Ensure that your controller is the first controller recognised by Windows (MTA will only use the first controller). You can configure your gamepad in options in MTASA's main menu.

==== Free mouselook not working properly ====
:* '''MTA doesnt recognise my mouse'''

:Some people got problems with their mouse in MTA. They can use it in the menu, connect to a server, but they can't use the mouse for free look.
:This problem can be solved by entering a server, click your Win/Windows key at your keyboard once, and then click your mouse.
:If that doesn't work try starting GTA in Singleplayer, go to options > controler setup and set "Configuration" to "Mouse + Keys" instead of "Joypad".

==== Server browser not working ====
:* '''The in-game server browser shows "Loading" but does not come up with any servers'''

:Depending on the type and status of the internet connection you are using, it can take up to a few seconds for the server browser to retrieve all the servers. Please wait a little longer for the results to appear.

:If all else fails, you can logon to [http://www.game-monitor.com/search.php?game=mta GameMonitor], and click the green play icon to play on that server.

==== Invalid serial number ====
:* '''I am getting an 'Invalid serial number' error when trying to launch or play the game'''

:You are running an outdated version of Multi Theft Auto. Head over to the [http://mtasa.com/ main page] and download the latest version of Multi Theft Auto.

==== 'Network module not compatible!' on MTA:SA launch ====
:* '''I am getting 'Network module not compatible!' error message upon launching MTA:SA

:This could mean that your MTA:SA install is incomplete or broken. Reinstall it.

==== 'No such mod installed (deathmatch)' ====
:* '''I am getting a 'No such mod installed (deathmatch)' error message when trying to connect to any server

:'''Option 1:''' Simply re-install MTA. <br>
:'''Option 2:''' Run both gta_sa.exe and Multi Theft Auto.exe with administrator privileges.

==== D3dx9_**.dll is not found ====
:* '''When I start Multi Theft Auto: San Andreas I am getting an error D3dx9_**.dll (** = a number) cannot be found.

:This means that DirectX 9 is not installed or not up to date.
:To install/update DirectX download the [http://www.microsoft.com/downloads/details.aspx?displaylang=en&FamilyID=2da43d38-db71-4c1b-bc6a-9b6652cd92a3 DirectX End-User Runtime Web Installer] from the Microsoft download site.

==== CRC mismatch ====
:* '''When joining a server, the chatbox shows 'CRC mismatch'
:This is a server problem. Tell the owner to look at the server section of this page.

==== 'Error loading netc.dll module! (Error 14001)' on MTA:SA launch ====
:* Full error message:
:''Error loading netc.dll module! (Error 14001: The application has failed to start because its side-by-side configuration is incorrect. Please see the application event log for more detail.)''

:Make sure you have installed Microsoft Visual C++ 2008 regular and SP1 redistributable packages (x86):

:[http://www.microsoft.com/downloads/details.aspx?FamilyID=9b2da534-3e03-4391-8a4d-074b9f2bc1bf&displaylang=en Microsoft Visual C++ 2008 Redistributable package (x86)]

:[http://www.microsoft.com/download/en/details.aspx?id=5582 Microsoft Visual C++ 2008 SP1 Redistributable package (x86)]

==== 'Error 1935. An error occurred during the installation of assembly 'Microsoft.VC90.ATL...' ====
: Download the 'Fix it' helper from here: [http://support.microsoft.com/default.aspx?scid=kb;en-us;946414]

==== Your virus scanner warns you about MTA:SA ====
:* '''Your virus scanner informs you that the MTA:SA or setup executable is a virus or malware.'''
:MTA does '''NOT''' contain any viruses, malware, adware or spyware. You should re-download MTASA [http://mtasa.com here] if you doubt the validity of your copy of MTA.

==== When downloading large maps, progress halts ====
:* '''When downloading large maps, progress often halts, while transmission is still taking place.'''
:This issue is fixed in [http://forum.mtasa.com/viewtopic.php?f=31&t=39555#p402093 MTA:SA 1.3].

=== Windows Vista® / Windows 7-specific ===

==== Crash on connect ====
:* '''I seem to crash whenever I connect to a server just before I go in-game on Vista'''

:This seems to be an issue with the Microsoft DirectX April 2006 SDK Redistributable DLL file (d3dx9_30.dll) when running in compatibility mode. Please make sure that compatibility mode is competely turned off for '''both''' your GTA_SA.exe and Multi Theft Auto.exe executables.

==== Clock manipulation error ====
:* '''I am getting 'Clock manipulation detected!' error message upon launching MTA:SA

:This is caused by incorrect system date/time being set (which could be a result of wrong settings or a faulty battery on the pc's motherboard). Setting time and date again should fix the problem.

:It might also happen if you are using an AMD Athlon 64 X2 processor with some old drivers. Update them at [http://support.amd.com/us/Pages/drivers.aspx AMD's site].

==== Halt on launch ====
:* '''When I launch MTA:SA, nothing happens (GTA_SA.exe is running but not loading up)

:Run MTA:SA with Administrator privileges. To do this, right click on the installer executable, choose 'Properties', go into 'Compatibility' tab and tick the check box on the last field and try again.

==== General GTA problems ====
:* '''I have unexplainable GTA problems or crashes'''

:Make sure your computer as well as your GTA install meet the [[Deathmatch_Client_Manual#System_requirements|minimum requirements]] and that you are not running in any 98/2000/XP/2003 compatibility modes.

:Also try the solutions from these pages:
:* http://www.gtaforums.com/index.php?showtopic=273549&view=findpost&p=4537502
:* http://pullmonkey.com/2007/4/30/how-i-got-gta-san-andreas-to-work-with-a-crappy-os-vista

==== Performance Issues Sandy Bridge / Second Generation Intel Core ====
:* '''Slow MTA performance on Sandy Bridge Processors while other games and San Andreas Singleplayer run fine.'''
:There seems to be a issue in combination with the Windows power profile running in power saving mode, you can solve this issue by changing the power profile to high performance when playing MTA:SA.
:* Topic about this issue: [http://forum.mtasa.com/viewtopic.php?f=104&t=31745 Sandy Bridge performance issues?]

== Server ==

=== General ===
==== Fatal error 3 ====
:* '''I'm getting ''Fatal Error 3'' whenever I connect to my server'''

:This error happens when the server you are trying to connect to is unable to provide you the required downloads, because it does not have http downloading enabled. Be sure to set the '''httpdownload''' configuration tag in your configuration to '''1'''.
==== Download error 9: Error downloading requested files ====
:* '''I'm getting ''Download Error 9: Error downloading requested files'' whenever I connect to my server'''

:This error happens when the server you are trying to connect to is unable to provide you with a valid link. This results in a 404 (Not found) HTTP error and an error at your end.

:* If you are running the built-in server ('''httpserver''' is set to '''1''' and '''httpdownloadurl''' is empty), make sure that your HTTP server is accessible (you can try to access it by using a browser) for everyone.

:* If you have configured an external web server ('''httpdownloadurl''' is set to your custom URL), make sure that your HTTP is accessible and make sure you have read the [[Deathmatch_Server_Manual#Configuring_an_external_web_server | Configuring an external web server]] guide.

==== CRC mismatch ====
:* '''When clients join my server, their chatbox shows 'CRC mismatch'
:CRC mismatch occurs when either:
:* The server files have been changed, but the resource has not been restarted/refreshed
:* An external http server is being used and the files are not synchronized

==== Accounts missing ====
:The file ''accounts.xml'' is not used from 1.0.4, it has been replaced by a file called ''internal.db''. To ensure your old accounts information is migrated:
:*Stop the server
:*Make sure your old ''accounts.xml'' is correct
:*Delete ''internal.db''
:*Start the server

==== Resources missing ====
:From 1.0.4, resource names cannot contain dots.

==== Download error 28 ====
:Try closing anti-virus or firewall applications. If it then works, try adding an exception to your firewall to allow your http port through.

==== Accounts disappearing ====
:Account information (or anything else) not being saved correctly can be caused by database corruption. From build 2836, the server checks the integrity of the sqlite database files on startup. If it reports a database error, please read [[How to repair the database files]].
:If you are running an earlier version and are having troubles such as accounts disappearing, you should upgrade your server to the [http://nightly.multitheftauto.com/ lastest build]

=== Windows-related ===
:No known reported issues in {{Current Version|full}}.

=== Linux-related ===
====Default nohup creates infinitely big nohup.out====

:Temporary fix, disable the nohup file: 'nohup ./mta_server > /dev/null &'

[[es:Problemas Conocidos - FAQ]]
[[it:Bugs noti e FAQ]]
[[ru:Known Issues - FAQ]]
[[de:Known Issues - FAQ]]
[[pt-br:Soluções de Problemas - FAQ]]
[[hu:Known Issues - FAQ]]
[[zh-cn:已知问题 - 常见问题]]

[[Category:Support]]

Resource:Battlefield

2017-01-01T18:42:25Z

JHXP: Reverted edits by Marcin778 (talk) to last revision by Winky-

<pageclass class="resource" subcaption="Resource"></pageclass>
<removeNamespaceName></removeNamespaceName>
<lowercasetitle></lowercasetitle>
{{Outdated|Resource not included in recent MTA distributions.}}
A resource based on the 'Bad Company 2' Battlefield game. Right now it is only a wordpad document of ideas. Hopefully I can get more contributers with time.

==Functions==
*Server
**Squad Functions
***[[Resource:battlefield/createSquad|createSquad]]
***[[Resource:battlefield/getSquad|getSquad]]
***[[Resource:battlefield/getSquadShortn|getSquadShortn]]
***[[Resource:battlefield/getSquadName|getSquadName]]
***[[Resource:battlefield/getSquadTeam|getSquadTeam]]
**Player Functions
***[[Resource:battlefield/setPlayerSquad|setPlayerSquad]]
***[[Resource:battlefield/getPlayerSquad|getPlayerSquad]]
***[[Resource:battlefield/isPlayerSpotted|isPlayerSpotted]]
***[[Resource:battlefield/setPlayerSpotted|setPlayerSpotted]]
**Vehicle Functions
***[[Resource:battlefield/isVehicleSpotted|isVehicleSpotted]]
***[[Resource:battlefield/setVehicleSpotted|setVehicleSpotted]]
*Client

==Events==
Nothing here yet. :)
[[Category:Resource]]

Resource:Assault

2017-01-01T18:42:23Z

JHXP: Reverted edits by Marcin778 (talk) to last revision by Vincent

{{Resource page}}
Assault is an objective-based team gamemode that should be similiar to Unreal Tournament's Assault. One team attacks, while the other defends. When the attacking team reached the final objective or the time runs out, the round ends and sides are switched. The team that reaches the final objective faster wins the game, if both can't reach it in the timelimit, the game ends tied.

You can easily create your own Assault maps by placing spawnareas and objectives, and of course objects, vehicles and pickups like on any other map. The default objectives are simple checkpoints you have to enter, but the exported functions allow scripters to create whole new types of objectives. See the documentation for details.

=How does a game work=
* Waiting for players before each new round for a certain amount of seconds or if enough players have joined
** Let players select their team
* Spawn players according to their team
* team1 has to attack and reach one or more objectives (marker), while team2 defends the objectives
** if team1 reached an objective, teamspawns may be at another location, according to the next objective
* if the final objective is reached, the first round ends and team2 has to attack (on the same map)
** the timelimit for the second round should be the time team1 needed to reach the final objective

===Winning===
* If team2 doesn't reach the objective in the timelimit, meaning team1 was faster, team1 wins.
* If team2 is able to reach the objective in the timelimit, meaning team2 was faster, team2 wins.
* If team1 and team2 aren't able to reach the objective within the timelimit, game ends tied.

=Creating an Assault map=
Assault should work with the mapmanager, so additional maps can easily be created. It also triggers events for map specific scripts and provides functions to trigger custom objectives.

If you want to create a simple map without additional code or custom objectives, you may want to skip to the [[#Map Elements]].

=Events/Functions=

<syntaxhighlight lang="lua">onAssaultObjectiveReached ( table objectiveReached, table players )</syntaxhighlight>
Triggers when an objective is successful (when it turns red).
* '''objectiveReached:''' A table with all the attributes supplied in the map file (see [[#Objectives|Map Elements]])
* '''players:''' A table of all players that were in the marker when it was activated

<syntaxhighlight lang="lua">onAssaultStartRound ( team attacker )</syntaxhighlight>
Triggers when a round actually starts (player spawns), 'attacker' is the team that attacks.
* '''attacker:''' A team element consisting the attacking team

<syntaxhighlight lang="lua">onAssaultCreateObjective ( table objectiveToCreate )</syntaxhighlight>
Triggers when a objective is created or should be created if it's a custom objective, instead of creating the marker when it would be a normal one
* '''objectiveToCreate:''' A table with all the attributes supplied in the map file (see [[#Objectives|Map Elements]])

<syntaxhighlight lang="lua">onAssaultEndRound( bool conquered )</syntaxhighlight>
Triggers when the round ends (time up or base conquered)
* '''conquered:''' If the attacker was successful in completing the objectives, true otherwise false.

<syntaxhighlight lang="lua">bool triggerObjective( string objectiveId, [table players] )</syntaxhighlight>
Used to trigger an objective. Returns ''true'' if it can be triggered, ''false'' otherwise.
* '''objectiveId:''' ''(required)'' The id (like defined in the .map file) of the objective.
* '''players:''' A table of all players that were reponsible for activating the objective

''Please note that you have to use [[Call]] with exported functions.''

=General Assault Settings=
'''(as of version 1.1)'''

These settings can be specified in Assault's ''meta.xml'' [[Settings system|settings]].
* '''teamBalance''': Defines how many more players can be in either team respectively. For example when you set it to '1' while Team Blue has 2 players and Team Red has 1 player, new players couldn't join Team Blue. If you had set it to '2' in the same situtation, one more player could join Team Blue. (''default: 1'')

=Map Elements=
To create an Assault map, all of these elements are obligatory.

==General Map Settings==
'''(as of version 1.1, in version 1.0 only some settings can be set in the meta.xml)'''

All these settings can be specified in the ''meta.xml'' [[Settings system|settings]] or the ''assaultSettings'' element in the mapfile. The ''meta.xml'' settings will always overrule the mapfile settings.

To specifiy the settings in the ''meta.xml'' file, it may look like this:
<syntaxhighlight lang="xml">
<meta>
<info author="driver2" type="map" gamemodes="assault" />
<map src="as-area51.map" />
<script src="as-area51.lua" />

<settings>
<setting name="#author" value="driver2" />
<setting name="#timelimit" value="300" />

</settings>
</meta>
</syntaxhighlight>
To specifiy the settings in the mapfile, put the ''assaultSettings'' in your mapfile:
<syntaxhighlight lang="xml">
<assaultSettings timelimit="(int=300)"
finishType="(string)" finishObjective="(string)"
time="(time=12:00)" weather="(int=0)"
author="{string=''}" description="{string=''}" />
</syntaxhighlight>

====Required Attributes====
''none''

====Optional Attributes====
* '''finishObjective:''' Specifies the objective (id) that has to be reached by the attackers in order to finish the round. If left empty, all objectives have to be reached.
* '''finishType:''' You ''can'' specify the '''finishType''' in addition to the '''finishObjective''' (''in version 1.0 this is required'')
** '''"objective":''' when a certain objective is reached
** '''"all":''' when all objectives are reached

If there is a '''timelimit''', '''time''', '''weather''', '''author''' or '''description''' [[Settings system|setting]] specified in the meta file, it will overule the attribute in this element (version 1.0)
* '''timelimit:''' duration of one round in seconds ''(default: 300)''
* '''time:''' time hours:minutes ''(default: 12:00)''
* '''weather:''' weather id ''(default: 0)''
* '''author:''' the map author ''(default: "")''
* '''description:''' map description ''(default: "")''
* '''defenderText:''' The text that is displayed at the bottom of the screen, telling the defenders what to do. If this text is defined here, it will be set as default for the map, but can be overwritten by single objectives by specifying the according attribute in its element. ''(default: "Prevent attackers from reaching their objectives!")''
* '''attackMessage:''' The message that is shown once an attacker spawns ''(default: "Assault the base!")''
* '''defendMessage:''' The message that is shown once a defender spawns ''(default: "Defend the base!")''
* '''conqueredMessage:''' This message replaces a part of the message that is shown when the attackers successfully reached their objectives ''(default: "conquered the base")''
** This messages replaces the following part enclosed by brackets (example): "Red [conquered the base] in 4:39"
* '''defendedMessage:''' This message replaces a part of the message that is shown when the defenders successfully defended the objectives ''(default: "defended the base")''
** This messages replaces the following part enclosed by brackets (example): "Blue [defended the base]. Blue wins."

It is recommended that you change the above messages only if the default messages make no or little sense for your map, in order to keep the messages (almost) the same for all maps.

==Objectives==
<syntaxhighlight lang="xml"><objective name="(string)" description="(string)" successText="(string)" id="(string)" req="(string)"
posX="(float)" posY="(float)" posZ="(float)" stay="{int=0}"
forcedRespawn="{string=none}" markerType="{string=cylinder}" captureType="{string=foot}" /></syntaxhighlight>

The order of the objectives in the .map file matters. It is responsible for the order the objectives are displayed on the hud, as well as in the GUI.

====Required Attributes====
* '''posX, posY, posZ: (required)''' position of the objective

====Optional Attributes====
* '''name:''' the name of the objective, used for the objective list on the screen
* '''description:''' may be used in the help windows and is displayed at the bottom of the screen to tell the attacker what to do
* '''successText:''' shown when the objective is reached, use ~team~ as a variable for the attacker's team name
** ''default:'' Objective '''name''' reached
** If '''name''' and '''successText''' are both not given, no message at all will appear when the objective is reached
* '''id:''' unique identification for the objective
* '''req:''' objectives required for this objective, ids seperated by comma, e.g. req="door,room1,room2"
* '''type:''' the type of the objective
** '''"checkpoint":''' ''(default)'' assault creates a checkpoint at the location, which has to be activated by the attacker by walking into it
** '''"custom":''' assault does nothing about it except waiting for another script to trigger it (see other assault maps for how it's done)
* '''forcedRespawn'''
** '''"both":''' make all players respawn, as soon as the objective is created
** other values may come
* '''markerType:''' defines the type of the marker used to mark the objective (see [[CreateMarker]] for details on the values)
* '''captureType:''' defines how the objective can be activated
** '''"both":''' on foot and in a vehicle
** '''"foot":''' only while on foot
** '''"vehicle":''' only while in a vehicle
* '''stay:''' number of seconds the player needs to stay in the objective
* '''stayText:''' the text that is shown above the progress bar while being in the objective
* '''defenderDescription:''' This text is shown at the bottom of the screen to tell the defenders what to do ''(default: the '''defenderText''' attribute of the [[#Assault Settings]] element)''
* '''successTextForDefender:''' This attribute can overwrite the '''successText''' attribute for defenders

==Spawngroups==
<syntaxhighlight lang="xml">
<spawngroup type="(string)" req="(string)">
- put spawnareas here -
</spawngroup>
</syntaxhighlight>

A spawngroup is a collection of one or several spawnareas. One of the spawnareas will be randomly selected on spawn. You can use this to let attacking players attack from different sides or to let some players spawn with different weapons for example. Always the last spawngroup (from the order in the mapfile) that meets the 'req' requirements is used to spawn players.

====Required Attributes====
* '''type:'''
** '''"attacker":''' a spawngroup for the attacking team
** '''"defender":''' a spawngroup for the defending team

====Optional Attributes====
* '''req:''' objective ids seperated by comma required for this checkpoint to work

==Spawnareas==
<syntaxhighlight lang="xml">
<spawnarea posX="(float)" posY="(float)" posZ="(float)" sizeX="(int=2)" sizeY="(int=2)" skins="{int,int=0}" weapons="{int,int;int,int=''}" radius="{int=2}" shape="{string=circle}" />
</syntaxhighlight>

A spawnarea is a rectangle or circle in which players are spawned randomly. It is defined by one point and two size values or the radius.

====Required Attributes====
* '''posX, posY, posZ:''' position

====Optional Attributes====
* '''skins:''' list of skins of which one is randomly chosen, seperated by comma, range of skins seperated by hyphen (e.g. 10,14,20-24 would be 10,14,20,21,22,23,24)
* '''weapons:''' weapon1,ammo1;weapon2,ammo2;weapon3,ammo3..
* '''shape'''
** '''"circle": (default)''' a circle
** '''"rectangle":''' a rectangle
* '''sizeX, sizeY:''' if shape="rectangle", the maximum number that will be added to the X or Y coordinate
* '''radius:''' if shape="circle", radius of the circle

==Cameras==
You need to define one camera of each type in a valid assault map.
<syntaxhighlight lang="xml"><camera type="(string)" posX="(float)" posY="(float)" posZ="(float)" targetX="(float)" targetY="(float)" targetZ="(float)" /></syntaxhighlight>

====Required Attributes====
* '''posX, posY, posZ, targetX, targetY, targetZ:''' position and look at
* '''type:''' defines the type of the camera, when it will be used
** '''"spawn":''' after selecting the team and before spawning
** '''"selectTeam":''' select Team screen
** '''"finish":''' when the last objective is reached

====Optional Attributes====
(none)

==Additional Information==
* If you don't want a specific vehicle to be respawned by assault, set it's Elementdata item 'noRespawn' to ''true'' by script or add the attribute noRespawn="1" to the element in the mapfile. Remember that it will never be automatically respawned then, so if you want to have it return to it's original place, for example after the round ends or when it is destroyed, you have to respawn it yourself.

[[ru:Resource:Assault]]