Multi Theft Auto: Wiki - User contributions [en]

PT-BR/Introdução ao Scripting

2012-05-22T22:53:32Z

Stanley Sathler .: /* Sobre os lançadores de comandos (responsáveis por criar os comandos) */

Os recursos (resources) são uma "chave" do MTA. Um recurso é uma pasta ou um arquivo comprimido (em .zip, e não em .rar) contendo um conjunto de arquivos, juntos a um ''meta.xml'' que informa ao servidor como/quais recursos devem ser carregados e quais arquivos estes possuem. Um recurso pode ser visto como um programa de computador, onde pode ser iniciado/interrompido a qualquer momento, além de poder rodar junto a diversos outros recursos ao mesmo tempo.

Tudo relacionado a scripting (programação em linguagem Lua, neste caso) tem relação com os recursos, afinal, os recursos nada mais são do que, normalmente, um conjunto de scripts escritos em Lua destinados a realizar alguma tarefa. O que um recurso define é se determinados arquivos definem um gamemode (estilo de jogo, como corrida, deathmatch, entre outros), um mapa ou qualquer outra coisa. O MTA já vem por padrão com alguns recursos interessantes que você pode, além de reaproveitá-los, adaptá-los às suas necessidades (como por exemplo, um limitador de áreas que impede que um jogador se afaste de um determinado local, ou scripts que criam objetos "pegáveis" no mapa, como colete e armas). {{tip|Para facilitar seus primeiros passos na programação em linguagem Lua, é recomendado que se utilize um editor de textos com highlight, ou seja, "cores" para cada comando. Isso facilita a leitura e escrita de qualquer código independente da linguagem. Muito utilizado e recomendado por nós é o [http://notepad-plus.sourceforge.net/uk/site.htm Notepad++] ou [http://luaedit.sourceforge.net/ LuaEdit]. Há também um editor de códigos (criado por fãs do MTA) com foco na linguagem Lua para o MTA: [[MTASE|MTA Script Editor]] (ainda em fase de desenvolvimento, mas você já pode testá-lo). }}

==Criando nosso primeiro script==
Nós primeiro vamos aprender a criar um script que permita que o jogador ande pela cidade, passo-a-passo.
===Onde estão todos os scripts?===
Vamos dar uma olhada na estrutura dos scripts. Vá até a pasta de instalação do seu MTA (padrão: C:\Arquivo de Programas\MTA San Andreas 1.x\) e siga os passos abaixo:

/server/mods/deathmatch/resources/

Você irá ver diversos arquivos .zip, que são os simples scripts que vêm por padrão junto ao MTA. Cada arquivo é um "recurso", e eles serão todos descompactados e carregados pelo servidor quando ele for iniciado. Para criar seu próprio resource, simplesmente crie uma pasta com um nome de sua preferência. Nós iremos usar o nome "myserver" para este tutorial.

Após a criação da pasta (myserver), acessamos-a:

/server/mods/deathmatch/resources/myserver/

===Identificando seu recurso===
Para que o servidor reconheça os arquivos de um determinado recurso (para carregá-los), um arquivo ''meta.xml'' deve ser criado, contendo uma lista de todo o conteúdo do recurso. O arquivo ''meta.xml'' deve ser salvo na pasta principal (nesse caso, na pasta "myserver"). Então, abra um editor de textos (recomenda-se o Notepad++) e salve-o com o nome de "meta.xml".

Entre com as seguintes linhas no arquivo ''meta.xml'':
<syntaxhighlight lang="xml">
<meta>
<info author="Seu_Nome" type="gamemode" name="Meu_Servidor" description="Meu primeiro recurso" />
<script src="script.lua" />
</meta>
</syntaxhighlight>

Na tag ''<info />'', existe o campo ''"type"'', que indica que o recurso criado é um ''gamemode''. Pode também ser um ''map'' (mapa), que iremos explicar depois.
Um gamemode é o que você precisa para criar um servidor independente.

A tag ''<script />'' indica o caminho dos arquivos (escritos em Lua) presentes no seu recurso. O do exemplo (script.lua), criaremos no próximo passo.

===Criando um script simples===
Observe que na tag ''<script />'' anterior, o arquivo .lua está presente na pasta principal do recurso (e não em uma subpasta). Então precisamos salvar o script na pasta principal, assim como indicado na tag. Salve o seguinte código no arquivo 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("Bem-vindo ao meu servidor!", source)
end
addEventHandler("onPlayerJoin", getRootElement(), joinHandler)
</syntaxhighlight>
O script irá gerar o seu personagem (seu boneco) nas coordenadas (x, y, z) especificadas assim que você entrar no jogo. Note que a função ''fadeCamera()'' precisa ser usada ou, do contrário, a tela ficará preta (e você não verá nada). Outra função é a ''setCameraTarget()'', que foca a câmera do jogo no seu personagem (do contrário, a câmera estaria virada para o céu).

A variável '''source''' representa o elemento responsável pela chamada do evento (você verá mais sobre eventos mais adiante). Assim, quando um jogador entra no jogo, o evento "onPlayerJoin" é chamado e, em seguida, chama a função. O evento automaticamente define o jogador na variável ''source'' (obs: a variável ''source'' armazena sempre o elemento que chamou determinado evento. Ou seja, nem sempre ''source'' será o jogador. Cuidado com isso.)

Se olharmos bem para o [[addEventHandler]], veremos 3 argumentos: 'onPlayerJoin', que indica o evento que chamará a função (no caso, esse evento é chamado assim que o jogador entra no jogo, logo, a função é chamada assim que o jogador entra no jogo); 'getRootElement()', que indica quem poderá chamar o evento (ou seja, todos os elementos, incluindo todos os jogadores); 'joinHandler', que indica o nome da função que será chamada quando o evento for chamado. Maiores detalhes serão explicados mais adiante. Vamos agora simplesmente rodar nosso servidor e testar nosso script.

===Executando o script===
Para iniciar o servidor, simplesmente execute o arquivo "MTA Server.exe" (presente na pasta de instalação do MTA:SA). Primeiramente é mostrada uma lista com os principais status do seu servidor; observe o número da porta, que você irá precisar quando entrar no jogo. Logo após, o servidor carrega todos os resources (caso todos estejam corretos) que estão presentes no diretório /resource/ e então "fica pronto para aceitar conexões" (ready to accept connections!).

Antes de se conectar ao seu servidor, você precisa executar o gamemode que criou. Para isso, digite no console (a janela do MTA Server.exe) o comando ''gamemode myserver'' (obs: "myserver" é o nome da pasta que você criou no início deste tutorial e, consequentemente, o nome do seu recurso) e pressione Enter. O servidor irá carregar o gamemode que você criou e irá mostrar os erros (caso existam) do seu script. Agora você pode se conectar ao seu servidor de duas diferentes maneiras: clicando em "Quick Connect" e inserindo o endereço IP do seu servidor e o número da porta, ou clicando em "Server Browser", acessando a aba "Local" e clicando duas vezes no seu servidor. Se tudo correr bem, seu personagem será criado nas coordenadas especificadas.

No próximo tópico iremos criar um comando para que o jogador possa gerar um veículo ao seu lado. Se preferir (embora não recomendado caso seja iniciante), você pode visitar alguns scripts mais avançados clicando [[Map manager|aqui]], ou prossiga com este tutorial. Outra parte interessante deste tutorial é [[PT-BR/Introducao_ao_GUI|Iniciando com GUIs]], no qual aborda a criação de interfaces gráficas (janelas, botões, etc) para seus scripts.

==Criando um comando simples==
Vamos voltar ao arquivo ''script.lua'' (abra-o novamente). Como mencionado anteriormente, vamos criar agora um comando (para executá-lo, digite no chat ''/seucomando'') que irá gerar um carro ao lado do seu personagem. Antes de tudo precisamos criar uma função que iremos chamar posteriormente e um [[addCommandHandler]](), responsável por criar o comando.

<syntaxhighlight lang="lua">
-- cria a funcao que sera chamada pelo comando. Os argumentos sao: thePlayer, command, vehicleModel
function createVehicleForPlayer(thePlayer, command, vehicleModel)
-- cria um veiculo
end

-- cria um lancador de comandos
addCommandHandler("createvehicle", createVehicleForPlayer)
</syntaxhighlight>
''Nota: Você pode clicar nas funções dos códigos para obter uma explicação de cada uma delas.

====Sobre os lançadores de comandos (responsáveis por criar os comandos)====
O primeiro argumento do [[addCommandHandler]] é o nome do comando que o jogador precisará digitar (no exemplo, ele precisará digitar no chat ''/createvehicle <argumento>''. O segundo argumento é a função que será chamada quando o comando for digitado (nesse caso, a função ''createVehicleForPlayer()''.

Se você já possui alguma experiência em programação, sabe que você chama uma função desta forma:

<syntaxhighlight lang="lua">
nomeDaFuncao(argumento1, argumento2, argumento3, ..)
</syntaxhighlight>
<syntaxhighlight lang="lua">
nomeDaFuncao(thePlayer, commandName, argumento3, ..)
</syntaxhighlight>

Se observarmos bem o exemplo acima, podemos ver que o argumento1 é o jogador (quem digita o comando) e o argumento2 é o nome do comando (nesse caso, ''createvehicle''). O argumento3 é o argumento digitado depois do comando (por exemplo, se o jogador digitou ''/createvehicle Infernus'', então a variável argumento3 irá armazenar o texto "Infernus"). Nunca se esqueça que os dois primeiros argumentos são padrões (ou seja, precisam existir), mas você pode nomeá-los com outro nome (mas isto não é necessário agora).

Nós chamamos a função [[addCommandHandler]], que chama a função ''createVehicleForPlayer''.

Por exemplo: alguém digita "createvehicle 468" no chat para gerar uma Sanchez (468 é o ID da Sanchez. Veja mais [[Vehicle_IDs|aqui]]), então o lançador de comandos (quando dizemos "lançador de comandos", é o mesmo que "criador de comandos") chama a função createVehicleForPlayer(), como '''se''' nós tivéssemos a seguinte linha no script:

<syntaxhighlight lang="lua">
createVehicleForPlayer(thePlayer,"createvehicle","468") -- thePlayer é o jogador que digitou o comando
</syntaxhighlight>

Como podemos ver, a função fornece alguns parâmetros: o jogador quem chamou o comando (armazenado na variável thePlayer), o comando que o jogador executou (nesse caso, "createvehicle") e o ID do veículo desejado (nesse caso, "468", referente à Sanchez). Os primeiros dois parâmetros são padrões nos lançadores de comando. Ou seja, sempre que usarmos o addCommandHandler(), teremos automaticamente essas duas primeiras variáveis. Assim, toda função que você desejar chamar usando [[addCommandHandler]] deverá possuir esses dois primeiros parâmetros caso você deseje usar um terceiro parâmetro (por exemplo, colocar uma variável para armazenar o ID do veículo).

''Nota: você precisa adicionar o lançador de comandos DEPOIS que escrever uma função (depois do "end" da função que será chamada) ou, do contrário, a função não será encontrada.''

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

PT-BR/Introdução ao Scripting

2012-05-22T22:35:18Z

Stanley Sathler .:

Os recursos (resources) são uma "chave" do MTA. Um recurso é uma pasta ou um arquivo comprimido (em .zip, e não em .rar) contendo um conjunto de arquivos, juntos a um ''meta.xml'' que informa ao servidor como/quais recursos devem ser carregados e quais arquivos estes possuem. Um recurso pode ser visto como um programa de computador, onde pode ser iniciado/interrompido a qualquer momento, além de poder rodar junto a diversos outros recursos ao mesmo tempo.

Tudo relacionado a scripting (programação em linguagem Lua, neste caso) tem relação com os recursos, afinal, os recursos nada mais são do que, normalmente, um conjunto de scripts escritos em Lua destinados a realizar alguma tarefa. O que um recurso define é se determinados arquivos definem um gamemode (estilo de jogo, como corrida, deathmatch, entre outros), um mapa ou qualquer outra coisa. O MTA já vem por padrão com alguns recursos interessantes que você pode, além de reaproveitá-los, adaptá-los às suas necessidades (como por exemplo, um limitador de áreas que impede que um jogador se afaste de um determinado local, ou scripts que criam objetos "pegáveis" no mapa, como colete e armas). {{tip|Para facilitar seus primeiros passos na programação em linguagem Lua, é recomendado que se utilize um editor de textos com highlight, ou seja, "cores" para cada comando. Isso facilita a leitura e escrita de qualquer código independente da linguagem. Muito utilizado e recomendado por nós é o [http://notepad-plus.sourceforge.net/uk/site.htm Notepad++] ou [http://luaedit.sourceforge.net/ LuaEdit]. Há também um editor de códigos (criado por fãs do MTA) com foco na linguagem Lua para o MTA: [[MTASE|MTA Script Editor]] (ainda em fase de desenvolvimento, mas você já pode testá-lo). }}

==Criando nosso primeiro script==
Nós primeiro vamos aprender a criar um script que permita que o jogador ande pela cidade, passo-a-passo.
===Onde estão todos os scripts?===
Vamos dar uma olhada na estrutura dos scripts. Vá até a pasta de instalação do seu MTA (padrão: C:\Arquivo de Programas\MTA San Andreas 1.x\) e siga os passos abaixo:

/server/mods/deathmatch/resources/

Você irá ver diversos arquivos .zip, que são os simples scripts que vêm por padrão junto ao MTA. Cada arquivo é um "recurso", e eles serão todos descompactados e carregados pelo servidor quando ele for iniciado. Para criar seu próprio resource, simplesmente crie uma pasta com um nome de sua preferência. Nós iremos usar o nome "myserver" para este tutorial.

Após a criação da pasta (myserver), acessamos-a:

/server/mods/deathmatch/resources/myserver/

===Identificando seu recurso===
Para que o servidor reconheça os arquivos de um determinado recurso (para carregá-los), um arquivo ''meta.xml'' deve ser criado, contendo uma lista de todo o conteúdo do recurso. O arquivo ''meta.xml'' deve ser salvo na pasta principal (nesse caso, na pasta "myserver"). Então, abra um editor de textos (recomenda-se o Notepad++) e salve-o com o nome de "meta.xml".

Entre com as seguintes linhas no arquivo ''meta.xml'':
<syntaxhighlight lang="xml">
<meta>
<info author="Seu_Nome" type="gamemode" name="Meu_Servidor" description="Meu primeiro recurso" />
<script src="script.lua" />
</meta>
</syntaxhighlight>

Na tag ''<info />'', existe o campo ''"type"'', que indica que o recurso criado é um ''gamemode''. Pode também ser um ''map'' (mapa), que iremos explicar depois.
Um gamemode é o que você precisa para criar um servidor independente.

A tag ''<script />'' indica o caminho dos arquivos (escritos em Lua) presentes no seu recurso. O do exemplo (script.lua), criaremos no próximo passo.

===Criando um script simples===
Observe que na tag ''<script />'' anterior, o arquivo .lua está presente na pasta principal do recurso (e não em uma subpasta). Então precisamos salvar o script na pasta principal, assim como indicado na tag. Salve o seguinte código no arquivo 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("Bem-vindo ao meu servidor!", source)
end
addEventHandler("onPlayerJoin", getRootElement(), joinHandler)
</syntaxhighlight>
O script irá gerar o seu personagem (seu boneco) nas coordenadas (x, y, z) especificadas assim que você entrar no jogo. Note que a função ''fadeCamera()'' precisa ser usada ou, do contrário, a tela ficará preta (e você não verá nada). Outra função é a ''setCameraTarget()'', que foca a câmera do jogo no seu personagem (do contrário, a câmera estaria virada para o céu).

A variável '''source''' representa o elemento responsável pela chamada do evento (você verá mais sobre eventos mais adiante). Assim, quando um jogador entra no jogo, o evento "onPlayerJoin" é chamado e, em seguida, chama a função. O evento automaticamente define o jogador na variável ''source'' (obs: a variável ''source'' armazena sempre o elemento que chamou determinado evento. Ou seja, nem sempre ''source'' será o jogador. Cuidado com isso.)

Se olharmos bem para o [[addEventHandler]], veremos 3 argumentos: 'onPlayerJoin', que indica o evento que chamará a função (no caso, esse evento é chamado assim que o jogador entra no jogo, logo, a função é chamada assim que o jogador entra no jogo); 'getRootElement()', que indica quem poderá chamar o evento (ou seja, todos os elementos, incluindo todos os jogadores); 'joinHandler', que indica o nome da função que será chamada quando o evento for chamado. Maiores detalhes serão explicados mais adiante. Vamos agora simplesmente rodar nosso servidor e testar nosso script.

===Executando o script===
Para iniciar o servidor, simplesmente execute o arquivo "MTA Server.exe" (presente na pasta de instalação do MTA:SA). Primeiramente é mostrada uma lista com os principais status do seu servidor; observe o número da porta, que você irá precisar quando entrar no jogo. Logo após, o servidor carrega todos os resources (caso todos estejam corretos) que estão presentes no diretório /resource/ e então "fica pronto para aceitar conexões" (ready to accept connections!).

Antes de se conectar ao seu servidor, você precisa executar o gamemode que criou. Para isso, digite no console (a janela do MTA Server.exe) o comando ''gamemode myserver'' (obs: "myserver" é o nome da pasta que você criou no início deste tutorial e, consequentemente, o nome do seu recurso) e pressione Enter. O servidor irá carregar o gamemode que você criou e irá mostrar os erros (caso existam) do seu script. Agora você pode se conectar ao seu servidor de duas diferentes maneiras: clicando em "Quick Connect" e inserindo o endereço IP do seu servidor e o número da porta, ou clicando em "Server Browser", acessando a aba "Local" e clicando duas vezes no seu servidor. Se tudo correr bem, seu personagem será criado nas coordenadas especificadas.

No próximo tópico iremos criar um comando para que o jogador possa gerar um veículo ao seu lado. Se preferir (embora não recomendado caso seja iniciante), você pode visitar alguns scripts mais avançados clicando [[Map manager|aqui]], ou prossiga com este tutorial. Outra parte interessante deste tutorial é [[PT-BR/Introducao_ao_GUI|Iniciando com GUIs]], no qual aborda a criação de interfaces gráficas (janelas, botões, etc) para seus scripts.

==Criando um comando simples==
Vamos voltar ao arquivo ''script.lua'' (abra-o novamente). Como mencionado anteriormente, vamos criar agora um comando (para executá-lo, digite no chat ''/seucomando'') que irá gerar um carro ao lado do seu personagem. Antes de tudo precisamos criar uma função que iremos chamar posteriormente e um [[addCommandHandler]](), responsável por criar o comando.

<syntaxhighlight lang="lua">
-- cria a funcao que sera chamada pelo comando. Os argumentos sao: thePlayer, command, vehicleModel
function createVehicleForPlayer(thePlayer, command, vehicleModel)
-- cria um veiculo
end

-- cria um lancador de comandos
addCommandHandler("createvehicle", createVehicleForPlayer)
</syntaxhighlight>
''Nota: Você pode clicar nas funções dos códigos para obter uma explicação de cada uma delas.

====Sobre os lançadores de comandos (responsáveis por criar os comandos)====
O primeiro argumento do [[addCommandHandler]] é o nome do comando que o jogador precisará digitar (no exemplo, ele precisará digitar no chat ''/createvehicle <argumento>''. O segundo argumento é a função que será chamada quando o comando for digitado (nesse caso, a função ''createVehicleForPlayer()''.

Se você já possui alguma experiência em programação, sabe que você chama uma função desta forma:

<syntaxhighlight lang="lua">
nomeDaFuncao(argumento1, argumento2, argumento3, ..)
</syntaxhighlight>
<syntaxhighlight lang="lua">
nomeDaFuncao(thePlayer, commandName, argumento3, ..)
</syntaxhighlight>

Se observarmos bem o exemplo acima, podemos ver que o argumento1 é o jogador (quem digita o comando) e o argumento2 é o nome do comando (nesse caso, ''createvehicle''). O argumento3 é o argumento digitado depois do comando (por exemplo, se o jogador digitou ''/createvehicle Infernus'', então a variável argumento3 irá armazenar o texto "Infernus"). Nunca se esqueça que os dois primeiros argumentos são padrões (ou seja, precisam existir), mas você pode nomeá-los com outro nome (mas isto não é necessário agora).

Nós chamamos a função [[addCommandHandler]], que chama a função ''createVehicleForPlayer''.

Por exemplo: alguém digita "createvehicle 468" no chat para gerar uma Sanchez (468 é o ID da Sanchez. Veja mais [[Vehicle_IDs|aqui]]), então o lançador de comandos (quando dizemos "lançador de comandos", é o mesmo que "criador de comandos") chama a função createVehicleForPlayer(), como '''se''' nós tivéssemos a seguinte linha no script:

<syntaxhighlight lang="lua">
createVehicleForPlayer(thePlayer,"createvehicle","468") -- thePlayer e o jogador que digitou o comando
</syntaxhighlight>
As we can see, it provides several parameters: the player who called the command, the command he entered and whatever text he had after that, in this case "468" as vehicle id for the Sanchez. The first two parameters are the same with all command handlers, which you can read on the [[addEventHandler]] page. For this fact, you always have to define at least those two parameters to use any after that (for example to process text that was entered after the command, like in our example the vehicle model id).

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

PT-BR/Introdução ao Scripting

2012-05-22T22:34:45Z

Stanley Sathler .:

Os recursos (resources) são uma "chave" do MTA. Um recurso é uma pasta ou um arquivo comprimido (em .zip, e não em .rar) contendo um conjunto de arquivos, juntos a um ''meta.xml'' que informa ao servidor como/quais recursos devem ser carregados e quais arquivos estes possuem. Um recurso pode ser visto como um programa de computador, onde pode ser iniciado/interrompido a qualquer momento, além de poder rodar junto a diversos outros recursos ao mesmo tempo.

Tudo relacionado a scripting (programação em linguagem Lua, neste caso) tem relação com os recursos, afinal, os recursos nada mais são do que, normalmente, um conjunto de scripts escritos em Lua destinados a realizar alguma tarefa. O que um recurso define é se determinados arquivos definem um gamemode (estilo de jogo, como corrida, deathmatch, entre outros), um mapa ou qualquer outra coisa. O MTA já vem por padrão com alguns recursos interessantes que você pode, além de reaproveitá-los, adaptá-los às suas necessidades (como por exemplo, um limitador de áreas que impede que um jogador se afaste de um determinado local, ou scripts que criam objetos "pegáveis" no mapa, como colete e armas). {{tip|Para facilitar seus primeiros passos na programação em linguagem Lua, é recomendado que se utilize um editor de textos com highlight, ou seja, "cores" para cada comando. Isso facilita a leitura e escrita de qualquer código independente da linguagem. Muito utilizado e recomendado por nós é o [http://notepad-plus.sourceforge.net/uk/site.htm Notepad++] ou [http://luaedit.sourceforge.net/ LuaEdit]. Há também um editor de códigos (criado por fãs do MTA) com foco na linguagem Lua para o MTA: [[MTASE|MTA Script Editor]] (ainda em fase de desenvolvimento, mas você já pode testá-lo).

==Criando nosso primeiro script==
Nós primeiro vamos aprender a criar um script que permita que o jogador ande pela cidade, passo-a-passo.
===Onde estão todos os scripts?===
Vamos dar uma olhada na estrutura dos scripts. Vá até a pasta de instalação do seu MTA (padrão: C:\Arquivo de Programas\MTA San Andreas 1.x\) e siga os passos abaixo:

/server/mods/deathmatch/resources/

Você irá ver diversos arquivos .zip, que são os simples scripts que vêm por padrão junto ao MTA. Cada arquivo é um "recurso", e eles serão todos descompactados e carregados pelo servidor quando ele for iniciado. Para criar seu próprio resource, simplesmente crie uma pasta com um nome de sua preferência. Nós iremos usar o nome "myserver" para este tutorial.

Após a criação da pasta (myserver), acessamos-a:

/server/mods/deathmatch/resources/myserver/

===Identificando seu recurso===
Para que o servidor reconheça os arquivos de um determinado recurso (para carregá-los), um arquivo ''meta.xml'' deve ser criado, contendo uma lista de todo o conteúdo do recurso. O arquivo ''meta.xml'' deve ser salvo na pasta principal (nesse caso, na pasta "myserver"). Então, abra um editor de textos (recomenda-se o Notepad++) e salve-o com o nome de "meta.xml".

Entre com as seguintes linhas no arquivo ''meta.xml'':
<syntaxhighlight lang="xml">
<meta>
<info author="Seu_Nome" type="gamemode" name="Meu_Servidor" description="Meu primeiro recurso" />
<script src="script.lua" />
</meta>
</syntaxhighlight>

Na tag ''<info />'', existe o campo ''"type"'', que indica que o recurso criado é um ''gamemode''. Pode também ser um ''map'' (mapa), que iremos explicar depois.
Um gamemode é o que você precisa para criar um servidor independente.

A tag ''<script />'' indica o caminho dos arquivos (escritos em Lua) presentes no seu recurso. O do exemplo (script.lua), criaremos no próximo passo.

===Criando um script simples===
Observe que na tag ''<script />'' anterior, o arquivo .lua está presente na pasta principal do recurso (e não em uma subpasta). Então precisamos salvar o script na pasta principal, assim como indicado na tag. Salve o seguinte código no arquivo 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("Bem-vindo ao meu servidor!", source)
end
addEventHandler("onPlayerJoin", getRootElement(), joinHandler)
</syntaxhighlight>
O script irá gerar o seu personagem (seu boneco) nas coordenadas (x, y, z) especificadas assim que você entrar no jogo. Note que a função ''fadeCamera()'' precisa ser usada ou, do contrário, a tela ficará preta (e você não verá nada). Outra função é a ''setCameraTarget()'', que foca a câmera do jogo no seu personagem (do contrário, a câmera estaria virada para o céu).

A variável '''source''' representa o elemento responsável pela chamada do evento (você verá mais sobre eventos mais adiante). Assim, quando um jogador entra no jogo, o evento "onPlayerJoin" é chamado e, em seguida, chama a função. O evento automaticamente define o jogador na variável ''source'' (obs: a variável ''source'' armazena sempre o elemento que chamou determinado evento. Ou seja, nem sempre ''source'' será o jogador. Cuidado com isso.)

Se olharmos bem para o [[addEventHandler]], veremos 3 argumentos: 'onPlayerJoin', que indica o evento que chamará a função (no caso, esse evento é chamado assim que o jogador entra no jogo, logo, a função é chamada assim que o jogador entra no jogo); 'getRootElement()', que indica quem poderá chamar o evento (ou seja, todos os elementos, incluindo todos os jogadores); 'joinHandler', que indica o nome da função que será chamada quando o evento for chamado. Maiores detalhes serão explicados mais adiante. Vamos agora simplesmente rodar nosso servidor e testar nosso script.

===Executando o script===
Para iniciar o servidor, simplesmente execute o arquivo "MTA Server.exe" (presente na pasta de instalação do MTA:SA). Primeiramente é mostrada uma lista com os principais status do seu servidor; observe o número da porta, que você irá precisar quando entrar no jogo. Logo após, o servidor carrega todos os resources (caso todos estejam corretos) que estão presentes no diretório /resource/ e então "fica pronto para aceitar conexões" (ready to accept connections!).

Antes de se conectar ao seu servidor, você precisa executar o gamemode que criou. Para isso, digite no console (a janela do MTA Server.exe) o comando ''gamemode myserver'' (obs: "myserver" é o nome da pasta que você criou no início deste tutorial e, consequentemente, o nome do seu recurso) e pressione Enter. O servidor irá carregar o gamemode que você criou e irá mostrar os erros (caso existam) do seu script. Agora você pode se conectar ao seu servidor de duas diferentes maneiras: clicando em "Quick Connect" e inserindo o endereço IP do seu servidor e o número da porta, ou clicando em "Server Browser", acessando a aba "Local" e clicando duas vezes no seu servidor. Se tudo correr bem, seu personagem será criado nas coordenadas especificadas.

No próximo tópico iremos criar um comando para que o jogador possa gerar um veículo ao seu lado. Se preferir (embora não recomendado caso seja iniciante), você pode visitar alguns scripts mais avançados clicando [[Map manager|aqui]], ou prossiga com este tutorial. Outra parte interessante deste tutorial é [[PT-BR/Introducao_ao_GUI|Iniciando com GUIs]], no qual aborda a criação de interfaces gráficas (janelas, botões, etc) para seus scripts.

==Criando um comando simples==
Vamos voltar ao arquivo ''script.lua'' (abra-o novamente). Como mencionado anteriormente, vamos criar agora um comando (para executá-lo, digite no chat ''/seucomando'') que irá gerar um carro ao lado do seu personagem. Antes de tudo precisamos criar uma função que iremos chamar posteriormente e um [[addCommandHandler]](), responsável por criar o comando.

<syntaxhighlight lang="lua">
-- cria a funcao que sera chamada pelo comando. Os argumentos sao: thePlayer, command, vehicleModel
function createVehicleForPlayer(thePlayer, command, vehicleModel)
-- cria um veiculo
end

-- cria um lancador de comandos
addCommandHandler("createvehicle", createVehicleForPlayer)
</syntaxhighlight>
''Nota: Você pode clicar nas funções dos códigos para obter uma explicação de cada uma delas.

====Sobre os lançadores de comandos (responsáveis por criar os comandos)====
O primeiro argumento do [[addCommandHandler]] é o nome do comando que o jogador precisará digitar (no exemplo, ele precisará digitar no chat ''/createvehicle <argumento>''. O segundo argumento é a função que será chamada quando o comando for digitado (nesse caso, a função ''createVehicleForPlayer()''.

Se você já possui alguma experiência em programação, sabe que você chama uma função desta forma:

<syntaxhighlight lang="lua">
nomeDaFuncao(argumento1, argumento2, argumento3, ..)
</syntaxhighlight>
<syntaxhighlight lang="lua">
nomeDaFuncao(thePlayer, commandName, argumento3, ..)
</syntaxhighlight>

Se observarmos bem o exemplo acima, podemos ver que o argumento1 é o jogador (quem digita o comando) e o argumento2 é o nome do comando (nesse caso, ''createvehicle''). O argumento3 é o argumento digitado depois do comando (por exemplo, se o jogador digitou ''/createvehicle Infernus'', então a variável argumento3 irá armazenar o texto "Infernus"). Nunca se esqueça que os dois primeiros argumentos são padrões (ou seja, precisam existir), mas você pode nomeá-los com outro nome (mas isto não é necessário agora).

Nós chamamos a função [[addCommandHandler]], que chama a função ''createVehicleForPlayer''.

Por exemplo: alguém digita "createvehicle 468" no chat para gerar uma Sanchez (468 é o ID da Sanchez. Veja mais [[Vehicle_IDs|aqui]]), então o lançador de comandos (quando dizemos "lançador de comandos", é o mesmo que "criador de comandos") chama a função createVehicleForPlayer(), como '''se''' nós tivéssemos a seguinte linha no script:

<syntaxhighlight lang="lua">
createVehicleForPlayer(thePlayer,"createvehicle","468") -- thePlayer e o jogador que digitou o comando
</syntaxhighlight>
As we can see, it provides several parameters: the player who called the command, the command he entered and whatever text he had after that, in this case "468" as vehicle id for the Sanchez. The first two parameters are the same with all command handlers, which you can read on the [[addEventHandler]] page. For this fact, you always have to define at least those two parameters to use any after that (for example to process text that was entered after the command, like in our example the vehicle model id).

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

Página Inicial

2012-05-20T23:17:23Z

Stanley Sathler .:

{| width="100%" cellspacing="0" cellpadding="0"
| colspan="2" |
<div style="border: 1px solid #D8D8D8; padding: 5px; height: 130px;">
[[File:Mtalogo.png|left|100px]]'''Bem Vindo ao Multi Theft Auto wiki em Português.''' Aqui você encontra toda a informação sobre o uso do Multi Theft Auto.

Há muitas [[How you can help|coisas em que você pode nos ajudar]] para melhorar o MTA, como criar um mapa, um modo de jogo (gamemode), documentar as funções de programação, escrever códigos como exemplo, fazer tutoriais ou somente jogar o MTA e reportar falhas/bugs que encontrar.

Se você tem alguma pergunta ou problema em relação à programação, sinta-se a vontade para nos comunicar em nosso [[IRC Channel|Canal 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>Jogar</h3>
<div style="background: #FFEEAA; border: 1px solid #FFCD19;">
[[File:Go-down.png|link=http://mtasa.com/]] ''' [http://mtasa.com/ Download Multi Theft Auto: San Andreas {{Current Version|full}}]'''</div>
* [[Image:iBR.png|Em Português|20px]] [[PT-BR/Manual_do_Cliente|Manual do Cliente]]
* [[Image:iUS.png|Em Inglês|20px]] [[Changes_in_{{padleft:|3|{{Current Version|full}}}}| Mudanças na versão {{padleft:|3|{{Current Version|full}}}}]]
* [[Image:iBR.png|Em Português|20px]] [[PT-BR/Soluções_de_Problemas_-_FAQ|Solução de Problemas (FAQ)]]
* [[Image:iUS.png|Em Inglês|20px]] [[Upgrading_from_MTA:Race|Migrando do MTA:Race ao MTA:SA {{padleft:|3|{{Current Version|full}}}}]]
* [[Image:iBR.png|Em Inglês|20px]] [[PT-BR/Manual_do_Servidor|Manual do Servidor]]
* [[Image:iUS.png|Em Inglês|20px]] [[Map manager|Map Manager]]

<h3>Editor de Mapas</h3>
* [[Image:iUS.png|Em Inglês|20px]] [[Resource:Editor|Manual do Editor]]
* [[Image:iUS.png|Em Inglês|20px]] [[Resource:Editor/EDF|Formato de Definições do Editor (EDF)]]
* [[Image:iUS.png|Em Inglês|20px]] [[Resource:Editor/Plugins|Extensões para o Editor]]
* [[Image:iUS.png|Em Inglês|20px]] [[Resource:Editor#FAQ|Perguntas Frequentes]]
</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>Banco de Dados</h3>
Esta sessão abrange todo tipo de conteúdo referente à scripts em LUA e recursos para o MTA.
* [[File:iUS.png|Em Inglês|20px]] [[:Category:Resource|Catálogo de Recursos]] - Ótimos exemplos para aprender à programar com eficiência.
* [[File:iUS.png|Em Inglês|20px]] [[Client side scripts|Scripts do Cliente]]
* [[File:iUS.png|Em Inglês|20px]] [[Modules|Módulos]]
</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>Desenvolvendo o Multi Theft Auto</h3>
[[File:Go-down.png|link=http://nightly.mtasa.com/]] [http://nightly.mtasa.com/ Nightly builds]
* [[File:iUS.png|Em Inglês|20px]] [[Compiling_MTASA|Compilando o MTASA no Windows]]
* [[File:iUS.png|Em Inglês|20px]] [[Building_MTASA_Server_on_Mac_OS_X|Compilando o MTASA no Mac OS X]]
* [[File:iUS.png|Em Inglês|20px]] [[Building_MTASA_Server_on_GNU_Linux|Compilando o MTASA no GNU/Linux]]
* [[File:iUS.png|Em Inglês|20px]] [[Coding guidelines|Guia do Desenvolvedor]]
* [[File:iUS.png|Em Inglês|20px]] [http://code.google.com/p/mtasa-blue Google Code SVN]
* [[File:iUS.png|Em Inglês|20px]] [[Roadmap|Roteiro para versões futuras]]
* [[File:iUS.png|Em Inglês|20px]] [http://bugs.mtasa.com/ Bugtracker Central de Bugs]
</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>Wiki - Como você pode ajudar</h3>
* Terminar os documentários de [[:Category:Incomplete|funções incompletas]].
* [[:Category:Needs_Example |Adicionar exemplos para funções e eventos]].
* Revisar e verificar as [[:Category:Needs Checking|páginas que necessitam de revisão]].
* Escrever tutoriais para ajudar novatos.
* Traduzir as páginas do Wiki.
</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>Comunidade</h3>
* [[File:iUS.png|Em Inglês|20px]] [http://forum.multitheftauto.com/ Forum]
* [[Image:iBR.png|Em Português|20px]] [http://forum.multitheftauto.com/viewforum.php?f=120&sid=79576f41173f69a47135647007d58d64 Fórum em Português]
* [[File:iUS.png|Em Inglês|20px]] IRC: [irc://irc.multitheftauto.com/mta irc.multitheftauto.com #mta]
* [[File:iUS.png|Em Inglês|20px]] [http://community.mtasa.com/ MTA Community] - Compartilhe e baixe recursos.
* [[File:iUS.png|Em Inglês|20px]] [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>Scripting</h3>
* [[File:iBR.png|Em Português|20px]] [[PT-BR/Introducao_ao_Scripting|Introdução ao Scripting]] - (Em processo de tradução)
* [[File:iUS.png|Em Inglês|20px]] [[Introduction to Scripting the GUI|Introdução ao GUI Scripting]]
* [[File:iUS.png|Em Inglês|20px]] [[Debugging|Depuração]] - Como achar erros em seus Scripts
* [[File:iUS.png|Em Inglês|20px]] [[Resources|Introdução aos Recursos]]
** [[File:iUS.png|Em Inglês|20px]] [[Resource Web Access| Acesso Web via Recursos ]] - Como fazemos páginas de internet via recursos
** [[File:iUS.png|Em Inglês|20px]] [[:Category:Resource|Catálogo de Recursos]]
** [[File:iUS.png|Em Inglês|20px]] [[Meta.xml|O arquivo meta.xml]] - Dentro de cada recurso, há um arquivo chamado meta o indentificando
** [[File:iUS.png|Em Inglês|20px]] [[ACL]] - Access Control List, isto é importantíssimo para scripts complexos funcionarem
* [[File:iUS.png|Em Inglês|20px]] [[Writing_Gamemodes|Programando um modo de Jogo]]
* [[File:iUS.png|Em Inglês|20px]] [[Useful_Functions|Funções úteis]]
<div style="float:right; width: 32px;">[[File:start-here.png|link=]]</div>
<h3>Ajuda geral em Lua</h3>
Páginas criadas para ajudar à entender o Lua
* [[Image:iBR.png|Em Português|20px]] [http://www.lua.org/portugues.html Introdução a linguagem Lua]
* [[Image:iBR.png|Em Português|20px]] [http://www.lua.org/manual/5.1/pt/ Manual "Programando em Lua"]
* [[File:iUS.png|Em Inglês|20px]] [http://lua-users.org/wiki/TutorialDirectory Lua Wiki em inglês]
* [[File:iUS.png|Em Inglês|20px]] [http://nixstaller.berlios.de/manual/0.2/nixstaller_9.html Um Guia geral de 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>Referência</h3>
* [[File:iUS.png|Em Inglês|20px]] [[Client Scripting Functions|Funções do Cliente]]
* [[File:iUS.png|Em Inglês|20px]] [[Client Scripting Events|Eventos do Cliente]]
* [[File:iUS.png|Em Inglês|20px]] [[Server Scripting Functions|Funções do Servidor]]
* [[File:iUS.png|Em Inglês|20px]] [[Server Scripting Events|Eventos do Servidor]]

* [[File:iUS.png|Em Inglês|20px]] [[MTA Classes]] - Descrições detalhadas de todos os tipos de coisas que o MTA usa
** [[File:iUS.png|Em Inglês|20px]] [[Element|Elementos do MTA]] / [[Element tree|Hierarquia dos Elementos]]
</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>[[Id|Lista de ID's]]</h3>
*[[Animations|Animações]]
*[[Character Skins|Skins de Pedestres]]
*[[CJ_Clothes|Roupas do CJ]]
*[[Garage|Garagens]]
*[[Interior IDs|Interiores]]
*[[Material IDs|Materiais]]
*[[Projectiles|Projéteis]]
*[[Radar Blips|Ponteiros do Radar]]
*[[Sounds|Efeitos Sonoros]]
*[[Vehicle IDs|Veículos]]
*[[Vehicle Colors|Cores para Veículos]]
*[[Vehicle Upgrades|Asessórios para Veículos]]
*[[Vehicle variants|Vehicle Variants]]
*[[Weapons|Armas]]
*[[Weather|Climas]]
</div>

<div style="border: 1px dotted #D8D8D8; padding:4px 8px 8px 8px; margin:10px;">
<div style="float:right; width: 32px;">[[File:pBR.png|32px]]</div>

<h3>Sobre a Tradução</h3>
* Tradutores:
** <span style="color: blue">RaceXtreme</span>
** <span style="color: blue">StanleySathler</span>
É importante que todos colaborem para que nossa página em português fique melhor a cada dia!

[[File:Osi symbol.png|75px|link=http://opensource.org/]]
'''Multi Theft Auto''' é um projeto '''Open Source'''. <br>
Isso significa que todos nós podemos contribuir para fazer um Multi Theft Auto muito melhor!
</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>'''Sobre Multi Theft Auto'''</li>
<li>[[Archive|Museu]]</li>
<li>[[Press Coverage|Eventos]]</li>
<li>[http://code.google.com/p/mtasa-blue/people/list Desenvolvedores]</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|Solução de Problemas]]</li>
</ul>
<ul style="list-style: none; width: 200px; float: left;">
<li>'''Status do Wiki'''</li>
<li>{{NUMBEROFARTICLES}} Artigos</li>
<li>{{NUMBEROFPAGES}} Páginas</li>
<li>{{NUMBEROFUSERS}} Usuários Registrados</li>
</ul>
</div>
|}

__NOTOC__
__NOEDITSECTION__
{{Languages list|pt-br}}

Página Inicial

2012-05-20T23:16:02Z

Stanley Sathler .:

{| width="100%" cellspacing="0" cellpadding="0"
| colspan="2" |
<div style="border: 1px solid #D8D8D8; padding: 5px; height: 130px;">
[[File:Mtalogo.png|left|100px]]'''Bem Vindo ao Multi Theft Auto wiki em Português.''' Aqui você encontra toda a informação sobre o uso do Multi Theft Auto.

Há muitas [[How you can help|coisas em que você pode nos ajudar]] para melhorar o MTA, como criar um mapa, um modo de jogo (gamemode), documentar as funções de programação, escrever códigos como exemplo, fazer tutoriais ou somente jogar o MTA e reportar falhas/bugs que encontrar.

Se você tem alguma pergunta ou problema em relação à programação, sinta-se a vontade para nos comunicar em nosso [[IRC Channel|Canal 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>Jogar</h3>
<div style="background: #FFEEAA; border: 1px solid #FFCD19;">
[[File:Go-down.png|link=http://mtasa.com/]] ''' [http://mtasa.com/ Download Multi Theft Auto: San Andreas {{Current Version|full}}]'''</div>
* [[Image:iBR.png|Em Português|20px]] [[PT-BR/Manual_do_Cliente|Manual do Cliente]]
* [[Image:iUS.png|Em Inglês|20px]] [[Changes_in_{{padleft:|3|{{Current Version|full}}}}| Mudanças na versão {{padleft:|3|{{Current Version|full}}}}]]
* [[Image:iBR.png|Em Português|20px]] [[PT-BR/Soluções_de_Problemas_-_FAQ|Solução de Problemas (FAQ)]]
* [[Image:iUS.png|Em Inglês|20px]] [[Upgrading_from_MTA:Race|Migrando do MTA:Race ao MTA:SA {{padleft:|3|{{Current Version|full}}}}]]
* [[Image:iBR.png|Em Inglês|20px]] [[PT-BR/Manual_do_Servidor|Manual do Servidor]]
* [[Image:iUS.png|Em Inglês|20px]] [[Map manager|Map Manager]]

<h3>Editor de Mapas</h3>
* [[Image:iUS.png|Em Inglês|20px]] [[Resource:Editor|Manual do Editor]]
* [[Image:iUS.png|Em Inglês|20px]] [[Resource:Editor/EDF|Formato de Definições do Editor (EDF)]]
* [[Image:iUS.png|Em Inglês|20px]] [[Resource:Editor/Plugins|Extensões para o Editor]]
* [[Image:iUS.png|Em Inglês|20px]] [[Resource:Editor#FAQ|Perguntas Frequentes]]
</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>Banco de Dados</h3>
Esta sessão abrange todo tipo de conteúdo referente à scripts em LUA e recursos para o MTA.
* [[File:iUS.png|Em Inglês|20px]] [[:Category:Resource|Catálogo de Recursos]] - Ótimos exemplos para aprender à programar com eficiência.
* [[File:iUS.png|Em Inglês|20px]] [[Client side scripts|Scripts do Cliente]]
* [[File:iUS.png|Em Inglês|20px]] [[Modules|Módulos]]
</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>Desenvolvendo o Multi Theft Auto</h3>
[[File:Go-down.png|link=http://nightly.mtasa.com/]] [http://nightly.mtasa.com/ Nightly builds]
* [[File:iUS.png|Em Inglês|20px]] [[Compiling_MTASA|Compilando o MTASA no Windows]]
* [[File:iUS.png|Em Inglês|20px]] [[Building_MTASA_Server_on_Mac_OS_X|Compilando o MTASA no Mac OS X]]
* [[File:iUS.png|Em Inglês|20px]] [[Building_MTASA_Server_on_GNU_Linux|Compilando o MTASA no GNU/Linux]]
* [[File:iUS.png|Em Inglês|20px]] [[Coding guidelines|Guia do Desenvolvedor]]
* [[File:iUS.png|Em Inglês|20px]] [http://code.google.com/p/mtasa-blue Google Code SVN]
* [[File:iUS.png|Em Inglês|20px]] [[Roadmap|Roteiro para versões futuras]]
* [[File:iUS.png|Em Inglês|20px]] [http://bugs.mtasa.com/ Bugtracker Central de Bugs]
</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>Wiki - Como você pode ajudar</h3>
* Terminar os documentários de [[:Category:Incomplete|funções incompletas]].
* [[:Category:Needs_Example |Adicionar exemplos para funções e eventos]].
* Revisar e verificar as [[:Category:Needs Checking|páginas que necessitam de revisão]].
* Escrever tutoriais para ajudar novatos.
* Traduzir as páginas do Wiki.
</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>Comunidade</h3>
* [[File:iUS.png|Em Inglês|20px]] [http://forum.multitheftauto.com/ Forum]
* [[Image:iBR.png|Em Português|20px]] [http://forum.multitheftauto.com/viewforum.php?f=120&sid=79576f41173f69a47135647007d58d64 Fórum em Português]
* [[File:iUS.png|Em Inglês|20px]] IRC: [irc://irc.multitheftauto.com/mta irc.multitheftauto.com #mta]
* [[File:iUS.png|Em Inglês|20px]] [http://community.mtasa.com/ MTA Community] - Compartilhe e baixe recursos.
* [[File:iUS.png|Em Inglês|20px]] [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>Scripting</h3>
* [[File:iBR.png|Em processo de tradução|20px]] [[PT-BR/Introducao_ao_Scripting|Introdução ao Scripting]]
* [[File:iUS.png|Em Inglês|20px]] [[Introduction to Scripting the GUI|Introdução ao GUI Scripting]]
* [[File:iUS.png|Em Inglês|20px]] [[Debugging|Depuração]] - Como achar erros em seus Scripts
* [[File:iUS.png|Em Inglês|20px]] [[Resources|Introdução aos Recursos]]
** [[File:iUS.png|Em Inglês|20px]] [[Resource Web Access| Acesso Web via Recursos ]] - Como fazemos páginas de internet via recursos
** [[File:iUS.png|Em Inglês|20px]] [[:Category:Resource|Catálogo de Recursos]]
** [[File:iUS.png|Em Inglês|20px]] [[Meta.xml|O arquivo meta.xml]] - Dentro de cada recurso, há um arquivo chamado meta o indentificando
** [[File:iUS.png|Em Inglês|20px]] [[ACL]] - Access Control List, isto é importantíssimo para scripts complexos funcionarem
* [[File:iUS.png|Em Inglês|20px]] [[Writing_Gamemodes|Programando um modo de Jogo]]
* [[File:iUS.png|Em Inglês|20px]] [[Useful_Functions|Funções úteis]]
<div style="float:right; width: 32px;">[[File:start-here.png|link=]]</div>
<h3>Ajuda geral em Lua</h3>
Páginas criadas para ajudar à entender o Lua
* [[Image:iBR.png|Em Português|20px]] [http://www.lua.org/portugues.html Introdução a linguagem Lua]
* [[Image:iBR.png|Em Português|20px]] [http://www.lua.org/manual/5.1/pt/ Manual "Programando em Lua"]
* [[File:iUS.png|Em Inglês|20px]] [http://lua-users.org/wiki/TutorialDirectory Lua Wiki em inglês]
* [[File:iUS.png|Em Inglês|20px]] [http://nixstaller.berlios.de/manual/0.2/nixstaller_9.html Um Guia geral de 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>Referência</h3>
* [[File:iUS.png|Em Inglês|20px]] [[Client Scripting Functions|Funções do Cliente]]
* [[File:iUS.png|Em Inglês|20px]] [[Client Scripting Events|Eventos do Cliente]]
* [[File:iUS.png|Em Inglês|20px]] [[Server Scripting Functions|Funções do Servidor]]
* [[File:iUS.png|Em Inglês|20px]] [[Server Scripting Events|Eventos do Servidor]]

* [[File:iUS.png|Em Inglês|20px]] [[MTA Classes]] - Descrições detalhadas de todos os tipos de coisas que o MTA usa
** [[File:iUS.png|Em Inglês|20px]] [[Element|Elementos do MTA]] / [[Element tree|Hierarquia dos Elementos]]
</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>[[Id|Lista de ID's]]</h3>
*[[Animations|Animações]]
*[[Character Skins|Skins de Pedestres]]
*[[CJ_Clothes|Roupas do CJ]]
*[[Garage|Garagens]]
*[[Interior IDs|Interiores]]
*[[Material IDs|Materiais]]
*[[Projectiles|Projéteis]]
*[[Radar Blips|Ponteiros do Radar]]
*[[Sounds|Efeitos Sonoros]]
*[[Vehicle IDs|Veículos]]
*[[Vehicle Colors|Cores para Veículos]]
*[[Vehicle Upgrades|Asessórios para Veículos]]
*[[Vehicle variants|Vehicle Variants]]
*[[Weapons|Armas]]
*[[Weather|Climas]]
</div>

<div style="border: 1px dotted #D8D8D8; padding:4px 8px 8px 8px; margin:10px;">
<div style="float:right; width: 32px;">[[File:pBR.png|32px]]</div>

<h3>Sobre a Tradução</h3>
* Tradutores:
** <span style="color: blue">RaceXtreme</span>
** <span style="color: blue">StanleySathler</span>
É importante que todos colaborem para que nossa página em português fique melhor a cada dia!

[[File:Osi symbol.png|75px|link=http://opensource.org/]]
'''Multi Theft Auto''' é um projeto '''Open Source'''. <br>
Isso significa que todos nós podemos contribuir para fazer um Multi Theft Auto muito melhor!
</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>'''Sobre Multi Theft Auto'''</li>
<li>[[Archive|Museu]]</li>
<li>[[Press Coverage|Eventos]]</li>
<li>[http://code.google.com/p/mtasa-blue/people/list Desenvolvedores]</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|Solução de Problemas]]</li>
</ul>
<ul style="list-style: none; width: 200px; float: left;">
<li>'''Status do Wiki'''</li>
<li>{{NUMBEROFARTICLES}} Artigos</li>
<li>{{NUMBEROFPAGES}} Páginas</li>
<li>{{NUMBEROFUSERS}} Usuários Registrados</li>
</ul>
</div>
|}

__NOTOC__
__NOEDITSECTION__
{{Languages list|pt-br}}

PT-BR/Introdução ao Scripting

2012-05-20T23:14:23Z

Stanley Sathler .: /* Creating a simple command */

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

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

==Criando nosso primeiro script==
Nós primeiro vamos aprender a criar um script que permita que o jogador ande pela cidade, passo-a-passo.
===Onde estão todos os scripts?===
Vamos dar uma olhada na estrutura dos scripts. Vá até a pasta de instalação do seu MTA (padrão: C:\Arquivo de Programas\MTA San Andreas 1.x\) e siga os passos abaixo:

/server/mods/deathmatch/resources/

Você irá ver diversos arquivos .zip, que são os simples scripts que vêm por padrão junto ao MTA. Cada arquivo é um "recurso", e eles serão todos descompactados e carregados pelo servidor quando ele for iniciado. Para criar seu próprio resource, simplesmente crie uma pasta com um nome de sua preferência. Nós iremos usar o nome "myserver" para este tutorial.

Após a criação da pasta (myserver), acessamos-a:

/server/mods/deathmatch/resources/myserver/

===Identificando seu recurso===
Para que o servidor reconheça os arquivos de um determinado recurso (para carregá-los), um arquivo ''meta.xml'' deve ser criado, contendo uma lista de todo o conteúdo do recurso. O arquivo ''meta.xml'' deve ser salvo na pasta principal (nesse caso, na pasta "myserver"). Então, abra um editor de textos (recomenda-se o Notepad++) e salve-o com o nome de "meta.xml".

Entre com as seguintes linhas no arquivo ''meta.xml'':
<syntaxhighlight lang="xml">
<meta>
<info author="Seu_Nome" type="gamemode" name="Meu_Servidor" description="Meu primeiro recurso" />
<script src="script.lua" />
</meta>
</syntaxhighlight>

Na tag ''<info />'', existe o campo ''"type"'', que indica que o recurso criado é um ''gamemode''. Pode também ser um ''map'' (mapa), que iremos explicar depois.
Um gamemode é o que você precisa para criar um servidor independente.

A tag ''<script />'' indica o caminho dos arquivos (escritos em Lua) presentes no seu recurso. O do exemplo (script.lua), criaremos no próximo passo.

===Criando um script simples===
Observe que na tag ''<script />'' anterior, o arquivo .lua está presente na pasta principal do recurso (e não em uma subpasta). Então precisamos salvar o script na pasta principal, assim como indicado na tag. Salve o seguinte código no arquivo 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("Bem-vindo ao meu servidor!", source)
end
addEventHandler("onPlayerJoin", getRootElement(), joinHandler)
</syntaxhighlight>
O script irá gerar o seu personagem (seu boneco) nas coordenadas (x, y, z) especificadas assim que você entrar no jogo. Note que a função ''fadeCamera()'' precisa ser usada ou, do contrário, a tela ficará preta (e você não verá nada). Outra função é a ''setCameraTarget()'', que foca a câmera do jogo no seu personagem (do contrário, a câmera estaria virada para o céu).

A variável '''source''' representa o elemento responsável pela chamada do evento (você verá mais sobre eventos mais adiante). Assim, quando um jogador entra no jogo, o evento "onPlayerJoin" é chamado e, em seguida, chama a função. O evento automaticamente define o jogador na variável ''source'' (obs: a variável ''source'' armazena sempre o elemento que chamou determinado evento. Ou seja, nem sempre ''source'' será o jogador. Cuidado com isso.)

Se olharmos bem para o [[addEventHandler]], veremos 3 argumentos: 'onPlayerJoin', que indica o evento que chamará a função (no caso, esse evento é chamado assim que o jogador entra no jogo, logo, a função é chamada assim que o jogador entra no jogo); 'getRootElement()', que indica quem poderá chamar o evento (ou seja, todos os elementos, incluindo todos os jogadores); 'joinHandler', que indica o nome da função que será chamada quando o evento for chamado. Maiores detalhes serão explicados mais adiante. Vamos agora simplesmente rodar nosso servidor e testar nosso script.

===Executando o script===
Para iniciar o servidor, simplesmente execute o arquivo "MTA Server.exe" (presente na pasta de instalação do MTA:SA). Primeiramente é mostrada uma lista com os principais status do seu servidor; observe o número da porta, que você irá precisar quando entrar no jogo. Logo após, o servidor carrega todos os resources (caso todos estejam corretos) que estão presentes no diretório /resource/ e então "fica pronto para aceitar conexões" (ready to accept connections!).

Antes de se conectar ao seu servidor, você precisa executar o gamemode que criou. Para isso, digite no console (a janela do MTA Server.exe) o comando ''gamemode myserver'' (obs: "myserver" é o nome da pasta que você criou no início deste tutorial e, consequentemente, o nome do seu recurso) e pressione Enter. O servidor irá carregar o gamemode que você criou e irá mostrar os erros (caso existam) do seu script. Agora você pode se conectar ao seu servidor de duas diferentes maneiras: clicando em "Quick Connect" e inserindo o endereço IP do seu servidor e o número da porta, ou clicando em "Server Browser", acessando a aba "Local" e clicando duas vezes no seu servidor. Se tudo correr bem, seu personagem será criado nas coordenadas especificadas.

No próximo tópico iremos criar um comando para que o jogador possa gerar um veículo ao seu lado. Se preferir (embora não recomendado caso seja iniciante), você pode visitar alguns scripts mais avançados clicando [[Map manager|aqui]], ou prossiga com este tutorial. Outra parte interessante deste tutorial é [[PT-BR/Introducao_ao_GUI|Iniciando com GUIs]], no qual aborda a criação de interfaces gráficas (janelas, botões, etc) para seus scripts.

==Criando um comando simples==
Vamos voltar ao arquivo ''script.lua'' (abra-o novamente). Como mencionado anteriormente, vamos criar agora um comando (para executá-lo, digite no chat ''/seucomando'') que irá gerar um carro ao lado do seu personagem. Antes de tudo precisamos criar uma função que iremos chamar posteriormente e um [[addCommandHandler]](), responsável por criar o comando.

<syntaxhighlight lang="lua">
-- cria a funcao que sera chamada pelo comando. Os argumentos sao: thePlayer, command, vehicleModel
function createVehicleForPlayer(thePlayer, command, vehicleModel)
-- cria um veiculo
end

-- cria um lancador de comandos
addCommandHandler("createvehicle", createVehicleForPlayer)
</syntaxhighlight>
''Nota: Você pode clicar nas funções dos códigos para obter uma explicação de cada uma delas.

====Sobre os lançadores de comandos (responsáveis por criar os comandos)====
O primeiro argumento do [[addCommandHandler]] é o nome do comando que o jogador precisará digitar (no exemplo, ele precisará digitar no chat ''/createvehicle <argumento>''. O segundo argumento é a função que será chamada quando o comando for digitado (nesse caso, a função ''createVehicleForPlayer()''.

Se você já possui alguma experiência em programação, sabe que você chama uma função desta forma:

<syntaxhighlight lang="lua">
nomeDaFuncao(argumento1, argumento2, argumento3, ..)
</syntaxhighlight>
<syntaxhighlight lang="lua">
nomeDaFuncao(thePlayer, commandName, argumento3, ..)
</syntaxhighlight>

Se observarmos bem o exemplo acima, podemos ver que o argumento1 é o jogador (quem digita o comando) e o argumento2 é o nome do comando (nesse caso, ''createvehicle''). O argumento3 é o argumento digitado depois do comando (por exemplo, se o jogador digitou ''/createvehicle Infernus'', então a variável argumento3 irá armazenar o texto "Infernus"). Nunca se esqueça que os dois primeiros argumentos são padrões (ou seja, precisam existir), mas você pode nomeá-los com outro nome (mas isto não é necessário agora).

Nós chamamos a função [[addCommandHandler]], que chama a função ''createVehicleForPlayer''.

Por exemplo: alguém digita "createvehicle 468" no chat para gerar uma Sanchez (468 é o ID da Sanchez. Veja mais [[Vehicle_IDs|aqui]]), então o lançador de comandos (quando dizemos "lançador de comandos", é o mesmo que "criador de comandos") chama a função createVehicleForPlayer(), como '''se''' nós tivéssemos a seguinte linha no script:

<syntaxhighlight lang="lua">
createVehicleForPlayer(thePlayer,"createvehicle","468") -- thePlayer e o jogador que digitou o comando
</syntaxhighlight>
As we can see, it provides several parameters: the player who called the command, the command he entered and whatever text he had after that, in this case "468" as vehicle id for the Sanchez. The first two parameters are the same with all command handlers, which you can read on the [[addEventHandler]] page. For this fact, you always have to define at least those two parameters to use any after that (for example to process text that was entered after the command, like in our example the vehicle model id).

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

PT-BR/Introdução ao Scripting

2012-05-20T22:58:24Z

Stanley Sathler .: /* Running the script */

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

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

==Criando nosso primeiro script==
Nós primeiro vamos aprender a criar um script que permita que o jogador ande pela cidade, passo-a-passo.
===Onde estão todos os scripts?===
Vamos dar uma olhada na estrutura dos scripts. Vá até a pasta de instalação do seu MTA (padrão: C:\Arquivo de Programas\MTA San Andreas 1.x\) e siga os passos abaixo:

/server/mods/deathmatch/resources/

Você irá ver diversos arquivos .zip, que são os simples scripts que vêm por padrão junto ao MTA. Cada arquivo é um "recurso", e eles serão todos descompactados e carregados pelo servidor quando ele for iniciado. Para criar seu próprio resource, simplesmente crie uma pasta com um nome de sua preferência. Nós iremos usar o nome "myserver" para este tutorial.

Após a criação da pasta (myserver), acessamos-a:

/server/mods/deathmatch/resources/myserver/

===Identificando seu recurso===
Para que o servidor reconheça os arquivos de um determinado recurso (para carregá-los), um arquivo ''meta.xml'' deve ser criado, contendo uma lista de todo o conteúdo do recurso. O arquivo ''meta.xml'' deve ser salvo na pasta principal (nesse caso, na pasta "myserver"). Então, abra um editor de textos (recomenda-se o Notepad++) e salve-o com o nome de "meta.xml".

Entre com as seguintes linhas no arquivo ''meta.xml'':
<syntaxhighlight lang="xml">
<meta>
<info author="Seu_Nome" type="gamemode" name="Meu_Servidor" description="Meu primeiro recurso" />
<script src="script.lua" />
</meta>
</syntaxhighlight>

Na tag ''<info />'', existe o campo ''"type"'', que indica que o recurso criado é um ''gamemode''. Pode também ser um ''map'' (mapa), que iremos explicar depois.
Um gamemode é o que você precisa para criar um servidor independente.

A tag ''<script />'' indica o caminho dos arquivos (escritos em Lua) presentes no seu recurso. O do exemplo (script.lua), criaremos no próximo passo.

===Criando um script simples===
Observe que na tag ''<script />'' anterior, o arquivo .lua está presente na pasta principal do recurso (e não em uma subpasta). Então precisamos salvar o script na pasta principal, assim como indicado na tag. Salve o seguinte código no arquivo 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("Bem-vindo ao meu servidor!", source)
end
addEventHandler("onPlayerJoin", getRootElement(), joinHandler)
</syntaxhighlight>
O script irá gerar o seu personagem (seu boneco) nas coordenadas (x, y, z) especificadas assim que você entrar no jogo. Note que a função ''fadeCamera()'' precisa ser usada ou, do contrário, a tela ficará preta (e você não verá nada). Outra função é a ''setCameraTarget()'', que foca a câmera do jogo no seu personagem (do contrário, a câmera estaria virada para o céu).

A variável '''source''' representa o elemento responsável pela chamada do evento (você verá mais sobre eventos mais adiante). Assim, quando um jogador entra no jogo, o evento "onPlayerJoin" é chamado e, em seguida, chama a função. O evento automaticamente define o jogador na variável ''source'' (obs: a variável ''source'' armazena sempre o elemento que chamou determinado evento. Ou seja, nem sempre ''source'' será o jogador. Cuidado com isso.)

Se olharmos bem para o [[addEventHandler]], veremos 3 argumentos: 'onPlayerJoin', que indica o evento que chamará a função (no caso, esse evento é chamado assim que o jogador entra no jogo, logo, a função é chamada assim que o jogador entra no jogo); 'getRootElement()', que indica quem poderá chamar o evento (ou seja, todos os elementos, incluindo todos os jogadores); 'joinHandler', que indica o nome da função que será chamada quando o evento for chamado. Maiores detalhes serão explicados mais adiante. Vamos agora simplesmente rodar nosso servidor e testar nosso script.

===Executando o script===
Para iniciar o servidor, simplesmente execute o arquivo "MTA Server.exe" (presente na pasta de instalação do MTA:SA). Primeiramente é mostrada uma lista com os principais status do seu servidor; observe o número da porta, que você irá precisar quando entrar no jogo. Logo após, o servidor carrega todos os resources (caso todos estejam corretos) que estão presentes no diretório /resource/ e então "fica pronto para aceitar conexões" (ready to accept connections!).

Antes de se conectar ao seu servidor, você precisa executar o gamemode que criou. Para isso, digite no console (a janela do MTA Server.exe) o comando ''gamemode myserver'' (obs: "myserver" é o nome da pasta que você criou no início deste tutorial e, consequentemente, o nome do seu recurso) e pressione Enter. O servidor irá carregar o gamemode que você criou e irá mostrar os erros (caso existam) do seu script. Agora você pode se conectar ao seu servidor de duas diferentes maneiras: clicando em "Quick Connect" e inserindo o endereço IP do seu servidor e o número da porta, ou clicando em "Server Browser", acessando a aba "Local" e clicando duas vezes no seu servidor. Se tudo correr bem, seu personagem será criado nas coordenadas especificadas.

No próximo tópico iremos criar um comando para que o jogador possa gerar um veículo ao seu lado. Se preferir (embora não recomendado caso seja iniciante), você pode visitar alguns scripts mais avançados clicando [[Map manager|aqui]], ou prossiga com este tutorial. Outra parte interessante deste tutorial é [[PT-BR/Introducao_ao_GUI|Iniciando com GUIs]], no qual aborda a criação de interfaces gráficas (janelas, botões, etc) para seus scripts.

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

PT-BR/Introdução ao Scripting

2012-05-20T22:45:58Z

Stanley Sathler .: /* Criando um script simples */

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

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

==Criando nosso primeiro script==
Nós primeiro vamos aprender a criar um script que permita que o jogador ande pela cidade, passo-a-passo.
===Onde estão todos os scripts?===
Vamos dar uma olhada na estrutura dos scripts. Vá até a pasta de instalação do seu MTA (padrão: C:\Arquivo de Programas\MTA San Andreas 1.x\) e siga os passos abaixo:

/server/mods/deathmatch/resources/

Você irá ver diversos arquivos .zip, que são os simples scripts que vêm por padrão junto ao MTA. Cada arquivo é um "recurso", e eles serão todos descompactados e carregados pelo servidor quando ele for iniciado. Para criar seu próprio resource, simplesmente crie uma pasta com um nome de sua preferência. Nós iremos usar o nome "myserver" para este tutorial.

Após a criação da pasta (myserver), acessamos-a:

/server/mods/deathmatch/resources/myserver/

===Identificando seu recurso===
Para que o servidor reconheça os arquivos de um determinado recurso (para carregá-los), um arquivo ''meta.xml'' deve ser criado, contendo uma lista de todo o conteúdo do recurso. O arquivo ''meta.xml'' deve ser salvo na pasta principal (nesse caso, na pasta "myserver"). Então, abra um editor de textos (recomenda-se o Notepad++) e salve-o com o nome de "meta.xml".

Entre com as seguintes linhas no arquivo ''meta.xml'':
<syntaxhighlight lang="xml">
<meta>
<info author="Seu_Nome" type="gamemode" name="Meu_Servidor" description="Meu primeiro recurso" />
<script src="script.lua" />
</meta>
</syntaxhighlight>

Na tag ''<info />'', existe o campo ''"type"'', que indica que o recurso criado é um ''gamemode''. Pode também ser um ''map'' (mapa), que iremos explicar depois.
Um gamemode é o que você precisa para criar um servidor independente.

A tag ''<script />'' indica o caminho dos arquivos (escritos em Lua) presentes no seu recurso. O do exemplo (script.lua), criaremos no próximo passo.

===Criando um script simples===
Observe que na tag ''<script />'' anterior, o arquivo .lua está presente na pasta principal do recurso (e não em uma subpasta). Então precisamos salvar o script na pasta principal, assim como indicado na tag. Salve o seguinte código no arquivo 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("Bem-vindo ao meu servidor!", source)
end
addEventHandler("onPlayerJoin", getRootElement(), joinHandler)
</syntaxhighlight>
O script irá gerar o seu personagem (seu boneco) nas coordenadas (x, y, z) especificadas assim que você entrar no jogo. Note que a função ''fadeCamera()'' precisa ser usada ou, do contrário, a tela ficará preta (e você não verá nada). Outra função é a ''setCameraTarget()'', que foca a câmera do jogo no seu personagem (do contrário, a câmera estaria virada para o céu).

A variável '''source''' representa o elemento responsável pela chamada do evento (você verá mais sobre eventos mais adiante). Assim, quando um jogador entra no jogo, o evento "onPlayerJoin" é chamado e, em seguida, chama a função. O evento automaticamente define o jogador na variável ''source'' (obs: a variável ''source'' armazena sempre o elemento que chamou determinado evento. Ou seja, nem sempre ''source'' será o jogador. Cuidado com isso.)

Se olharmos bem para o [[addEventHandler]], veremos 3 argumentos: 'onPlayerJoin', que indica o evento que chamará a função (no caso, esse evento é chamado assim que o jogador entra no jogo, logo, a função é chamada assim que o jogador entra no jogo); 'getRootElement()', que indica quem poderá chamar o evento (ou seja, todos os elementos, incluindo todos os jogadores); 'joinHandler', que indica o nome da função que será chamada quando o evento for chamado. Maiores detalhes serão explicados mais adiante. Vamos agora simplesmente rodar nosso servidor e testar nosso script.

===Running the script===
To get the server started, simply run the executable under the MTA DM 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 /resource/ directory, and then "ready to accept connections!"

Before you connect to the server, you must run the gamemode. Type "gamemode 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 DM 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:DM is drawn and scripted.

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

PT-BR/Introdução ao Scripting

2012-05-20T22:22:37Z

Stanley Sathler .:

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

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

==Criando nosso primeiro script==
Nós primeiro vamos aprender a criar um script que permita que o jogador ande pela cidade, passo-a-passo.
===Onde estão todos os scripts?===
Vamos dar uma olhada na estrutura dos scripts. Vá até a pasta de instalação do seu MTA (padrão: C:\Arquivo de Programas\MTA San Andreas 1.x\) e siga os passos abaixo:

/server/mods/deathmatch/resources/

Você irá ver diversos arquivos .zip, que são os simples scripts que vêm por padrão junto ao MTA. Cada arquivo é um "recurso", e eles serão todos descompactados e carregados pelo servidor quando ele for iniciado. Para criar seu próprio resource, simplesmente crie uma pasta com um nome de sua preferência. Nós iremos usar o nome "myserver" para este tutorial.

Após a criação da pasta (myserver), acessamos-a:

/server/mods/deathmatch/resources/myserver/

===Identificando seu recurso===
Para que o servidor reconheça os arquivos de um determinado recurso (para carregá-los), um arquivo ''meta.xml'' deve ser criado, contendo uma lista de todo o conteúdo do recurso. O arquivo ''meta.xml'' deve ser salvo na pasta principal (nesse caso, na pasta "myserver"). Então, abra um editor de textos (recomenda-se o Notepad++) e salve-o com o nome de "meta.xml".

Entre com as seguintes linhas no arquivo ''meta.xml'':
<syntaxhighlight lang="xml">
<meta>
<info author="Seu_Nome" type="gamemode" name="Meu_Servidor" description="Meu primeiro recurso" />
<script src="script.lua" />
</meta>
</syntaxhighlight>

Na tag ''<info />'', existe o campo ''"type"'', que indica que o recurso criado é um ''gamemode''. Pode também ser um ''map'' (mapa), que iremos explicar depois.
Um gamemode é o que você precisa para criar um servidor independente.

A tag ''<script />'' indica o caminho dos arquivos (escritos em Lua) presentes no seu recurso. O do exemplo (script.lua), criaremos no próximo passo.

===Criando um script simples===
Observe que na tag ''<script />'' anterior, o arquivo .lua está presente na pasta principal do recurso (e não em uma subpasta). Então precisamos salvar o script na pasta principal, assim como indicado na tag. Salve o seguinte código no arquivo 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 MTA DM 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 /resource/ directory, and then "ready to accept connections!"

Before you connect to the server, you must run the gamemode. Type "gamemode 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 DM 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:DM is drawn and scripted.

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

PT-BR/Introdução ao Scripting

2012-05-20T22:08:51Z

Stanley Sathler .: Created page with "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 resourc..."

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

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

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

/Your MTA Server/mods/deathmatch/resources/

You will see a lot of .zip files, which are the packaged sample scripts shipped with MTA DM. 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:

/Your MTA 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 DM 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 MTA DM 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 /resource/ directory, and then "ready to accept connections!"

Before you connect to the server, you must run the gamemode. Type "gamemode 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 DM 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:DM is drawn and scripted.

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

Página Inicial

2012-05-20T22:04:25Z

Stanley Sathler .:

{| width="100%" cellspacing="0" cellpadding="0"
| colspan="2" |
<div style="border: 1px solid #D8D8D8; padding: 5px; height: 130px;">
[[File:Mtalogo.png|left|100px]]'''Bem Vindo ao Multi Theft Auto wiki em Português.''' Aqui você encontra toda a informação sobre o uso do Multi Theft Auto.

Há muitas [[How you can help|coisas em que você pode nos ajudar]] para melhorar o MTA, como criar um mapa, um modo de jogo (gamemode), documentar as funções de programação, escrever códigos como exemplo, fazer tutoriais ou somente jogar o MTA e reportar falhas/bugs que encontrar.

Se você tem alguma pergunta ou problema em relação à programação, sinta-se a vontade para nos comunicar em nosso [[IRC Channel|Canal 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>Jogar</h3>
<div style="background: #FFEEAA; border: 1px solid #FFCD19;">
[[File:Go-down.png|link=http://mtasa.com/]] ''' [http://mtasa.com/ Download Multi Theft Auto: San Andreas {{Current Version|full}}]'''</div>
* [[Image:iBR.png|Em Português|20px]] [[PT-BR/Manual_do_Cliente|Manual do Cliente]]
* [[Image:iUS.png|Em Inglês|20px]] [[Changes_in_{{padleft:|3|{{Current Version|full}}}}| Mudanças na versão {{padleft:|3|{{Current Version|full}}}}]]
* [[Image:iBR.png|Em Português|20px]] [[PT-BR/Soluções_de_Problemas_-_FAQ|Solução de Problemas (FAQ)]]
* [[Image:iUS.png|Em Inglês|20px]] [[Upgrading_from_MTA:Race|Migrando do MTA:Race ao MTA:SA {{padleft:|3|{{Current Version|full}}}}]]
* [[Image:iBR.png|Em Inglês|20px]] [[PT-BR/Manual_do_Servidor|Manual do Servidor]]
* [[Image:iUS.png|Em Inglês|20px]] [[Map manager|Map Manager]]

<h3>Editor de Mapas</h3>
* [[Image:iUS.png|Em Inglês|20px]] [[Resource:Editor|Manual do Editor]]
* [[Image:iUS.png|Em Inglês|20px]] [[Resource:Editor/EDF|Formato de Definições do Editor (EDF)]]
* [[Image:iUS.png|Em Inglês|20px]] [[Resource:Editor/Plugins|Extensões para o Editor]]
* [[Image:iUS.png|Em Inglês|20px]] [[Resource:Editor#FAQ|Perguntas Frequentes]]
</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>Banco de Dados</h3>
Esta sessão abrange todo tipo de conteúdo referente à scripts em LUA e recursos para o MTA.
* [[File:iUS.png|Em Inglês|20px]] [[:Category:Resource|Catálogo de Recursos]] - Ótimos exemplos para aprender à programar com eficiência.
* [[File:iUS.png|Em Inglês|20px]] [[Client side scripts|Scripts do Cliente]]
* [[File:iUS.png|Em Inglês|20px]] [[Modules|Módulos]]
</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>Desenvolvendo o Multi Theft Auto</h3>
[[File:Go-down.png|link=http://nightly.mtasa.com/]] [http://nightly.mtasa.com/ Nightly builds]
* [[File:iUS.png|Em Inglês|20px]] [[Compiling_MTASA|Compilando o MTASA no Windows]]
* [[File:iUS.png|Em Inglês|20px]] [[Building_MTASA_Server_on_Mac_OS_X|Compilando o MTASA no Mac OS X]]
* [[File:iUS.png|Em Inglês|20px]] [[Building_MTASA_Server_on_GNU_Linux|Compilando o MTASA no GNU/Linux]]
* [[File:iUS.png|Em Inglês|20px]] [[Coding guidelines|Guia do Desenvolvedor]]
* [[File:iUS.png|Em Inglês|20px]] [http://code.google.com/p/mtasa-blue Google Code SVN]
* [[File:iUS.png|Em Inglês|20px]] [[Roadmap|Roteiro para versões futuras]]
* [[File:iUS.png|Em Inglês|20px]] [http://bugs.mtasa.com/ Bugtracker Central de Bugs]
</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>Wiki - Como você pode ajudar</h3>
* Terminar os documentários de [[:Category:Incomplete|funções incompletas]].
* [[:Category:Needs_Example |Adicionar exemplos para funções e eventos]].
* Revisar e verificar as [[:Category:Needs Checking|páginas que necessitam de revisão]].
* Escrever tutoriais para ajudar novatos.
* Traduzir as páginas do Wiki.
</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>Comunidade</h3>
* [[File:iUS.png|Em Inglês|20px]] [http://forum.multitheftauto.com/ Forum]
* [[Image:iBR.png|Em Português|20px]] [http://forum.multitheftauto.com/viewforum.php?f=120&sid=79576f41173f69a47135647007d58d64 Fórum em Português]
* [[File:iUS.png|Em Inglês|20px]] IRC: [irc://irc.multitheftauto.com/mta irc.multitheftauto.com #mta]
* [[File:iUS.png|Em Inglês|20px]] [http://community.mtasa.com/ MTA Community] - Compartilhe e baixe recursos.
* [[File:iUS.png|Em Inglês|20px]] [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>Scripting</h3>
* [[File:iUS.png|Em Inglês|20px]] [[Scripting Introduction|Introdução ao Scripting]]
* [[File:iUS.png|Em Inglês|20px]] [[Introduction to Scripting the GUI|Introdução ao GUI Scripting]]
* [[File:iUS.png|Em Inglês|20px]] [[Debugging|Depuração]] - Como achar erros em seus Scripts
* [[File:iUS.png|Em Inglês|20px]] [[Resources|Introdução aos Recursos]]
** [[File:iUS.png|Em Inglês|20px]] [[Resource Web Access| Acesso Web via Recursos ]] - Como fazemos páginas de internet via recursos
** [[File:iUS.png|Em Inglês|20px]] [[:Category:Resource|Catálogo de Recursos]]
** [[File:iUS.png|Em Inglês|20px]] [[Meta.xml|O arquivo meta.xml]] - Dentro de cada recurso, há um arquivo chamado meta o indentificando
** [[File:iUS.png|Em Inglês|20px]] [[ACL]] - Access Control List, isto é importantíssimo para scripts complexos funcionarem
* [[File:iUS.png|Em Inglês|20px]] [[Writing_Gamemodes|Programando um modo de Jogo]]
* [[File:iUS.png|Em Inglês|20px]] [[Useful_Functions|Funções úteis]]
<div style="float:right; width: 32px;">[[File:start-here.png|link=]]</div>
<h3>Ajuda geral em Lua</h3>
Páginas criadas para ajudar à entender o Lua
* [[Image:iBR.png|Em Português|20px]] [http://www.lua.org/portugues.html Introdução a linguagem Lua]
* [[Image:iBR.png|Em Português|20px]] [http://www.lua.org/manual/5.1/pt/ Manual "Programando em Lua"]
* [[File:iUS.png|Em Inglês|20px]] [http://lua-users.org/wiki/TutorialDirectory Lua Wiki em inglês]
* [[File:iUS.png|Em Inglês|20px]] [http://nixstaller.berlios.de/manual/0.2/nixstaller_9.html Um Guia geral de 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>Referência</h3>
* [[File:iUS.png|Em Inglês|20px]] [[Client Scripting Functions|Funções do Cliente]]
* [[File:iUS.png|Em Inglês|20px]] [[Client Scripting Events|Eventos do Cliente]]
* [[File:iUS.png|Em Inglês|20px]] [[Server Scripting Functions|Funções do Servidor]]
* [[File:iUS.png|Em Inglês|20px]] [[Server Scripting Events|Eventos do Servidor]]

* [[File:iUS.png|Em Inglês|20px]] [[MTA Classes]] - Descrições detalhadas de todos os tipos de coisas que o MTA usa
** [[File:iUS.png|Em Inglês|20px]] [[Element|Elementos do MTA]] / [[Element tree|Hierarquia dos Elementos]]
</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>[[Id|Lista de ID's]]</h3>
*[[Animations|Animações]]
*[[Character Skins|Skins de Pedestres]]
*[[CJ_Clothes|Roupas do CJ]]
*[[Garage|Garagens]]
*[[Interior IDs|Interiores]]
*[[Material IDs|Materiais]]
*[[Projectiles|Projéteis]]
*[[Radar Blips|Ponteiros do Radar]]
*[[Sounds|Efeitos Sonoros]]
*[[Vehicle IDs|Veículos]]
*[[Vehicle Colors|Cores para Veículos]]
*[[Vehicle Upgrades|Asessórios para Veículos]]
*[[Vehicle variants|Vehicle Variants]]
*[[Weapons|Armas]]
*[[Weather|Climas]]
</div>

<div style="border: 1px dotted #D8D8D8; padding:4px 8px 8px 8px; margin:10px;">
<div style="float:right; width: 32px;">[[File:pBR.png|32px]]</div>

<h3>Sobre a Tradução</h3>
* Tradutores:
** <span style="color: blue">RaceXtreme</span>
** <span style="color: blue">StanleySathler</span>
É importante que todos colaborem para que nossa página em português fique melhor a cada dia!

[[File:Osi symbol.png|75px|link=http://opensource.org/]]
'''Multi Theft Auto''' é um projeto '''Open Source'''. <br>
Isso significa que todos nós podemos contribuir para fazer um Multi Theft Auto muito melhor!
</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>'''Sobre Multi Theft Auto'''</li>
<li>[[Archive|Museu]]</li>
<li>[[Press Coverage|Eventos]]</li>
<li>[http://code.google.com/p/mtasa-blue/people/list Desenvolvedores]</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|Solução de Problemas]]</li>
</ul>
<ul style="list-style: none; width: 200px; float: left;">
<li>'''Status do Wiki'''</li>
<li>{{NUMBEROFARTICLES}} Artigos</li>
<li>{{NUMBEROFPAGES}} Páginas</li>
<li>{{NUMBEROFUSERS}} Usuários Registrados</li>
</ul>
</div>
|}

__NOTOC__
__NOEDITSECTION__
{{Languages list|pt-br}}

PT-BR/Manual do Servidor

2012-05-20T22:02:53Z

Stanley Sathler .: /* Using the web interface */

[[PT-BR/Manual_do_Servidor]]
==Introdução==
Configurar um servidor e disponibilizá-lo para que seus amigos joguem via Internet ou LAN é mais fácil do que parece. Neste artigo estaremos abordando os passos iniciais para que você possa criar o seu próprio servidor para o MTA.

==Instalando o servidor==
A primeira parte consiste na instalação do servidor. Abaixo há dois tópicos, abordando a instalação em plataformas Linux e Windows, respectivamente.

===Instalando no Linux===
Há diversas maneiras de instalar, configurar e iniciar um servidor no Linux:
* [[Image:iUS.png|Em Inglês|20px]] [[Building MTASA Server on GNU Linux|Configurando um Servidor de MTASA no GNU Linux (Em Inglês)]]
* [[Image:iUS.png|Em Inglês|20px]] [http://linux.mtasa.com Baixando o servidor para Linux]

===Instalando no Windows===
Instalar um servidor do MTA:SA no Windows é bem simples:
:*Vá para [http://mtasa.com/ página de download] do MTA:SA e baixe o instalador.
:*Após o término do download, execute o arquivo.
:*Clique em Next e depois em "I Agree".
:*Nesta etapa você pode selecionar os componentes que deseja ou não instalar:
:**Para instalar somente o servidor, mude a opção "Client and Server" para "Server Only"
:**Next para continuar.
:*Selecione a pasta na qual deseja instalar o servidor. Em seguida, Next.
:*Clique em Install.
:*Pronto!

''Qual a função do arquivo acl.xml (access control list)? Para saber mais, leia o artigo em:
* [[Image:iUS.png|Em Inglês|20px]] [[Access_Control_List|Access Control List]]''

==Configurando o servidor==
O servidor dedicado do Multi Theft Auto pode ser configurado através...

*De uma espécie de prompt de comando chamado '''console''', ou seja, um programa onde comandos não são enviados através de cliques, mas sim através de linhas de comando digitadas pelo usuário.
** Esse programa está localizado em "MTA San Andreas 1.3\server\MTA Server.exe".
** Ele é idêntico a janela ''cmd'' do windows.
** Enquanto este estiver executando, o servidor vai permanecer online, caso contrário, o servidor sai do ar.

*'''Do próprio jogo'''!
**Os comandos para configurar o servidor são enviados a partir do chat.
** Para que estes comandos sejam efetivamente enviados, é necessário o uso da "/" antes do comando em si, pois esta identifica que o que vem logo em seguida faz parte de um comando.. Exemplo "/addaccount".
*'''De um navegador de internet'''. Um website pode receber informações e configurar um servidor de MTA.

''Para que possa configurar um servidor do MTASA no jogo ou via website é necessário que pelo menos uma conta com privilégios de administrador seja adicionada no '''acl.xml'''.''

===Configurações Gerais===
Todas as configurações gerais podem ser encontradas no arquivo "[[Server_mtaserver.conf|'''mtaserver.conf''']]" localizado na pasta "mods/deathmatch/". Este arquivo pode ser visualizado em qualquer editor de texto.

Ele é bem simples e direto, toda variável tem uma [[Server_mtaserver.conf|descrição abordando o que esta faz e como usa-la]].

===Configurando as Portas===
Caso esteja executando um servidor a partir de seu computador e há um roteador entre a internet e sua máquina, então será necessário configurar 3 portas.

Antes de mais nada, abra o arquivo localizado em "mods/deathmatch/[[Server_mtaserver.conf|'''mtaserver.conf''']]" e procure pelas linhas citadas a seguir:
<syntaxhighlight lang="xml">
<serverport>22003</serverport>
<httpport>22005</httpport>
</syntaxhighlight>

Estas portas são necessárias para que o servidor inicie corretamente. Explicaremos com maiores detalhes mais a frente. Se deseja também que seu servidor apareça na lista de servidores do MTA (Server Browser, no menu), será preciso configurar mais uma porta chamada "ASE".

(Exemplo de como ativar/desativar a porta ASE):
<syntaxhighlight lang="xml">
<ase>1</ase> 
</syntaxhighlight>

Agora vamos liberar essas portas em seu roteador. Caso todas as portas estejam abertas ou você possui um roteador sem firewall, esta etapa é desnecessária.

Se você não sabe como abrir portas em seu roteador, visite [http://portforward.com/ este site], procure pelo modelo de seu roteador e siga as instruções.

Na maioria dos roteadores, há a opção de selecionar o tipo de porta: UDP ou TCP. A lista a seguir irá explicar qual porta é necessaria para que ela serve:

Porta principal do servidor: UDP (a porta padrão é 22003, mas você pode alterá-la no parâmetro <serverport> do mtaserver.config)
Porta HTTP: TCP (a porta padrão é 22005, mas você pode alterá-la no parâmetro <httpport> do mtaserver.config)
Porta ASE: UDP (esta é necessária caso deseje que o servidor apareça na lista de servidores do gamemonitor.com)

Para configurar a porta ASE, somamos 123 (cento e vinte e três) à porta padrão. Exemplo:

Porta padrão: 22003
ASE: 22003 + 123 = 22126

Boa sorte!

''Na ultima versão do servidor, ao se digitar o comando "/[[Server_Commands#openports|openports]]", os status de todas as portas serão mostrados.''

===Checagem dos clientes===
Todo jogador que entra em um servidor passa por várias "avaliações", também conhecidas como "Client Checks" (em inglês).
Esse processo é necessário, principalmente, para previnir trapaças no jogo, as quais são feitas através de trainers e/ou modificações realizadas nos arquivos originais do GTA SA.
Toda essas "avaliações" são dividias em diversos parâmetros, os quais são configuráveis através do arquivo [[Server_mtaserver.conf|'''mtaserver.conf''']] localizado em "mods/deathmatch".
Destacamos 2 delas como exemplo:

* O parâmetro '''client-file''' ...
** Habilita que um ou mais arquivos possam ser modificados no computador do jogador (exemplo: carmods.dat). Por padrão, o MTA não permite que nenhum arquivo da pasta "data" e "anim" do GTA SA seja modificado.
** Pertence a um grupo denominado Anti-Cheat, pois, por padrão, ele evita que um ou mais jogadores tenham vantagens sobre os outros. Todos os demais parâmetros que fazem parte desse grupo estão detalhados neste Guia [[Anti-cheat_guide|Anti-Cheat]].
* O parâmetro '''minclientversion'''...
** Estabelece que todos os jogadores usem uma versão igual ou superior a estipulada (exemplo: 1.3.0).
** Aqueles que estiverem usando uma versão inferior serão automaticamente desconectados do servidor.<br/>

Cada parâmetro contido no arquivo [[Server_mtaserver.conf|'''mtaserver.conf''']] tem um valor atribuido a ele. O que faz que o servidor ignore ou trabalhe de forma diferente ao realizar essas avaliações em cada jogador.

Se deseja definir uma versão mínima do MTA dos seus jogadores, procure pela linha:
<syntaxhighlight lang="xml">
<minclientversion></minclientversion>
</syntaxhighlight>
Use valores como: 1.1.1-9.02320

===Adicionando administradores===
É altamente recomendável adicionar, no mínimo, um administrador em seu servidor. Pois assim você poderá fazer uso de alguns recursos especiais, como o gerenciador Web ou alguns scripts que precisem acessar a lista ACL (painéis administrativos, por exemplo).

Para adicionar um administrador ao seu servidor, siga os seguintes passos:<br>
<ol>
<li>Enquanto o servidor estiver ligado (MTA Server.exe sendo executado), adicione uma nova conta digitando '''[[Server_Commands#addaccount|addaccount nome senha]]''' no console. Por exemplo, para adicionar o usuário Fulano você poderia digitar:
<div style="margin: 10px 10px 10px 10px;">
<syntaxhighlight lang="xml">
addaccount Fulano minhasenha123
</syntaxhighlight>
</div>
<div style="margin: 10px 10px 10px 20px;">
''Nota: Se você não tem acesso à janela do console, e o recurso "admin" está sendo executado, você pode adicionar uma nova conta digitando, no chat principal, o comando '''/register Fulano minhasenha123'''''
</div>
<li>O servidor deverá mostrar uma mensagem confirmando o registo da nova conta.
<li>A seguir, desligue o servidor digitando '''shutdown''' no console.
<li>Tenha certeza de que seu servidor foi desligado. Se ele continua online, as informações a seguir serão perdidas</li>
<li>Abra o arquivo 'mods/deathmatch/'acl.xml'''' com um Editor de Textos qualquer (pode ser o Bloco de Notas).
<li>Adicione a nova conta no grupo ''Admin'' usando a seguinte sintaxe do XML:
<div style="padding: 10px">
<syntaxhighlight lang="xml">
<acl>
...
<group name="Admin">
<acl name="Admin"/>
...
<object name="user.Fulano" />
</group>
...
</acl>
</syntaxhighlight>
</div>

Você pode adicionar o usuário criado no grupo que preferir. Cada grupo é linkado a um ACL ([[Acess Control List]]). Cada ACL contém uma série de ações que você pode ou não realizar dentro deste grupo (como kickar, banir, etc). Estes grupos existem para que diferentes usuários possam ter diferentes direitos em um servidor. O grupo ''Admin'' é apontado no ACL como um grupo poderoso (onde tudo é permitido). Já o grupo ''Everyone'', que significa ''Todos'', é apontado no ACL como um grupo com diversas restrições (ou seja, não podem kickar, banir, mutar, etc.).
</li>
<li>Pronto, você terminou! Agora você pode adicionar diversos usuários (sejam administradores ou usuários comuns). Dê uma olhada também nos outros grupos e ACLs disponíveis. O ACL é também acessível a partir do [[Acess_Control_List|Mecanismo de Scripting Lua]].<br>
É recomendado também que você dê uma olhada na interface Web. Iremos explicar como a seguir.
</li>
</ol>
'''Nota''': Existem também outras formas de adicionar contas e editar as permissões do servidor enquanto ele está sendo executado. "[[Server_Commands#addaccount|addaccount <usuário> <senha>]]" é um comando interno para adicionar contas, mas você vai precisar usar a interface Web para adicionar essas contas a um grupo/ACL específico.<br />

===Usando a interface Web===
O servidor dedicado (o servidor configurado em sua máquina) vem, por padrão, com alguns [[recursos]] em Lua que fornecem uma inteface Web de gerenciamento para seu servidor (melhor dizendo, permite que você gerencie seu servidor através de um site). O recurso pode ser usado para facilitar a manutenção de seu servidor, permitindo adicionar usuários, iniciar/pausar recursos, e muito mais.

A interface Web é habilitada por padrão e são servidos através do protocolo HTTP. Para ter certeza de que o servidor web está rodando na sua porta HTTP (que por padrão é a 22005), siga os seguintes passos:
<ol>
<li>Tenha certeza de que seu servidor foi pausado (ou desligado)
<li>Abra o arquivo 'mods/deathmatch/[[Server_mtaserver.conf|'''mtaserver.conf''']]' com um editor de textos qualquer</li>
<li>Verifique se o servidor HTTP está ativado:
<div style="padding: 10px">
<syntaxhighlight lang="xml">
<httpserver>1</httpserver>
</syntaxhighlight>
</div>
</li>
<li>Escolha a sua porta HTTP:
<div style="padding: 10px">
<syntaxhighlight lang="xml">
<httpport>22005</httpport>
</syntaxhighlight>
</div>
</li>
<li>Salve o arquivo e feche-o</li>
<li>Inicie seu servidor (MTA Server.exe)</li>
<li>Se você chegou a alterar os recursos que são iniciados por padrão com o seu servidor, então certifique-se de que os seguintes recursos foram iniciados:

# resourcebrowser
# resourcemanager
# webadmin
# webmap

Estes recursos são, por padrão, iniciados automaticamente com seu servidor, no caso de você ter instalado somente o servidor.
</li>
<li>Abra um navegador web (Internet Explorer 6 ou 7 não é suportado; 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] ou outros) e navegue até o endereço do servidor HTTP:
'''http://servidor:porta/'''. Por exemplo, se você está rodando o servidor localmente (no seu próprio computador) com a porta 22005 (padrão), use '''http://127.0.0.1:22005/'''.</li>
<li>Entre com o usuário e senha do administrador (que você adicionou nos passos anteriores).</li>
</ol>
<br />

Agora você deverá estar possibilitado de manipular seu servidor através do gerenciador Web.

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

==Useful Notes==

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

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

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

[[Category:Support]]

Página Inicial

2012-05-20T21:46:22Z

Stanley Sathler .:

{| width="100%" cellspacing="0" cellpadding="0"
| colspan="2" |
<div style="border: 1px solid #D8D8D8; padding: 5px; height: 130px;">
[[File:Mtalogo.png|left|100px]]'''Bem Vindo ao Multi Theft Auto wiki em Português.''' Aqui você encontra toda a informação sobre o uso do Multi Theft Auto.

Há muitas [[How you can help|coisas em que você pode nos ajudar]] para melhorar o MTA, como criar um mapa, um modo de jogo (gamemode), documentar as funções de programação, escrever códigos como exemplo, fazer tutoriais ou somente jogar o MTA e reportar falhas/bugs que encontrar.

Se você tem alguma pergunta ou problema em relação à programação, sinta-se a vontade para nos comunicar em nosso [[IRC Channel|Canal 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>Jogar</h3>
<div style="background: #FFEEAA; border: 1px solid #FFCD19;">
[[File:Go-down.png|link=http://mtasa.com/]] ''' [http://mtasa.com/ Download Multi Theft Auto: San Andreas {{Current Version|full}}]'''</div>
* [[Image:iBR.png|Em Português|20px]] [[PT-BR/Manual_do_Cliente|Manual do Cliente]]
* [[Image:iUS.png|Em Inglês|20px]] [[Changes_in_{{padleft:|3|{{Current Version|full}}}}| Mudanças na versão {{padleft:|3|{{Current Version|full}}}}]]
* [[Image:iBR.png|Em Português|20px]] [[PT-BR/Soluções_de_Problemas_-_FAQ|Solução de Problemas (FAQ)]]
* [[Image:iUS.png|Em Inglês|20px]] [[Upgrading_from_MTA:Race|Migrando do MTA:Race ao MTA:SA {{padleft:|3|{{Current Version|full}}}}]]
* [[Image:iBR.png|Em Inglês|20px]] [[Manual_do_Servidor|Manual do Servidor]]
* [[Image:iUS.png|Em Inglês|20px]] [[Map manager|Map Manager]]

<h3>Editor de Mapas</h3>
* [[Image:iUS.png|Em Inglês|20px]] [[Resource:Editor|Manual do Editor]]
* [[Image:iUS.png|Em Inglês|20px]] [[Resource:Editor/EDF|Formato de Definições do Editor (EDF)]]
* [[Image:iUS.png|Em Inglês|20px]] [[Resource:Editor/Plugins|Extensões para o Editor]]
* [[Image:iUS.png|Em Inglês|20px]] [[Resource:Editor#FAQ|Perguntas Frequentes]]
</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>Banco de Dados</h3>
Esta sessão abrange todo tipo de conteúdo referente à scripts em LUA e recursos para o MTA.
* [[File:iUS.png|Em Inglês|20px]] [[:Category:Resource|Catálogo de Recursos]] - Ótimos exemplos para aprender à programar com eficiência.
* [[File:iUS.png|Em Inglês|20px]] [[Client side scripts|Scripts do Cliente]]
* [[File:iUS.png|Em Inglês|20px]] [[Modules|Módulos]]
</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>Desenvolvendo o Multi Theft Auto</h3>
[[File:Go-down.png|link=http://nightly.mtasa.com/]] [http://nightly.mtasa.com/ Nightly builds]
* [[File:iUS.png|Em Inglês|20px]] [[Compiling_MTASA|Compilando o MTASA no Windows]]
* [[File:iUS.png|Em Inglês|20px]] [[Building_MTASA_Server_on_Mac_OS_X|Compilando o MTASA no Mac OS X]]
* [[File:iUS.png|Em Inglês|20px]] [[Building_MTASA_Server_on_GNU_Linux|Compilando o MTASA no GNU/Linux]]
* [[File:iUS.png|Em Inglês|20px]] [[Coding guidelines|Guia do Desenvolvedor]]
* [[File:iUS.png|Em Inglês|20px]] [http://code.google.com/p/mtasa-blue Google Code SVN]
* [[File:iUS.png|Em Inglês|20px]] [[Roadmap|Roteiro para versões futuras]]
* [[File:iUS.png|Em Inglês|20px]] [http://bugs.mtasa.com/ Bugtracker Central de Bugs]
</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>Wiki - Como você pode ajudar</h3>
* Terminar os documentários de [[:Category:Incomplete|funções incompletas]].
* [[:Category:Needs_Example |Adicionar exemplos para funções e eventos]].
* Revisar e verificar as [[:Category:Needs Checking|páginas que necessitam de revisão]].
* Escrever tutoriais para ajudar novatos.
* Traduzir as páginas do Wiki.
</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>Comunidade</h3>
* [[File:iUS.png|Em Inglês|20px]] [http://forum.multitheftauto.com/ Forum]
* [[Image:iBR.png|Em Português|20px]] [http://forum.multitheftauto.com/viewforum.php?f=120&sid=79576f41173f69a47135647007d58d64 Fórum em Português]
* [[File:iUS.png|Em Inglês|20px]] IRC: [irc://irc.multitheftauto.com/mta irc.multitheftauto.com #mta]
* [[File:iUS.png|Em Inglês|20px]] [http://community.mtasa.com/ MTA Community] - Compartilhe e baixe recursos.
* [[File:iUS.png|Em Inglês|20px]] [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>Scripting</h3>
* [[File:iUS.png|Em Inglês|20px]] [[Scripting Introduction|Introdução ao Scripting]]
* [[File:iUS.png|Em Inglês|20px]] [[Introduction to Scripting the GUI|Introdução ao GUI Scripting]]
* [[File:iUS.png|Em Inglês|20px]] [[Debugging|Depuração]] - Como achar erros em seus Scripts
* [[File:iUS.png|Em Inglês|20px]] [[Resources|Introdução aos Recursos]]
** [[File:iUS.png|Em Inglês|20px]] [[Resource Web Access| Acesso Web via Recursos ]] - Como fazemos páginas de internet via recursos
** [[File:iUS.png|Em Inglês|20px]] [[:Category:Resource|Catálogo de Recursos]]
** [[File:iUS.png|Em Inglês|20px]] [[Meta.xml|O arquivo meta.xml]] - Dentro de cada recurso, há um arquivo chamado meta o indentificando
** [[File:iUS.png|Em Inglês|20px]] [[ACL]] - Access Control List, isto é importantíssimo para scripts complexos funcionarem
* [[File:iUS.png|Em Inglês|20px]] [[Writing_Gamemodes|Programando um modo de Jogo]]
* [[File:iUS.png|Em Inglês|20px]] [[Useful_Functions|Funções úteis]]
<div style="float:right; width: 32px;">[[File:start-here.png|link=]]</div>
<h3>Ajuda geral em Lua</h3>
Páginas criadas para ajudar à entender o Lua
* [[Image:iBR.png|Em Português|20px]] [http://www.lua.org/portugues.html Introdução a linguagem Lua]
* [[Image:iBR.png|Em Português|20px]] [http://www.lua.org/manual/5.1/pt/ Manual "Programando em Lua"]
* [[File:iUS.png|Em Inglês|20px]] [http://lua-users.org/wiki/TutorialDirectory Lua Wiki em inglês]
* [[File:iUS.png|Em Inglês|20px]] [http://nixstaller.berlios.de/manual/0.2/nixstaller_9.html Um Guia geral de 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>Referência</h3>
* [[File:iUS.png|Em Inglês|20px]] [[Client Scripting Functions|Funções do Cliente]]
* [[File:iUS.png|Em Inglês|20px]] [[Client Scripting Events|Eventos do Cliente]]
* [[File:iUS.png|Em Inglês|20px]] [[Server Scripting Functions|Funções do Servidor]]
* [[File:iUS.png|Em Inglês|20px]] [[Server Scripting Events|Eventos do Servidor]]

* [[File:iUS.png|Em Inglês|20px]] [[MTA Classes]] - Descrições detalhadas de todos os tipos de coisas que o MTA usa
** [[File:iUS.png|Em Inglês|20px]] [[Element|Elementos do MTA]] / [[Element tree|Hierarquia dos Elementos]]
</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>[[Id|Lista de ID's]]</h3>
*[[Animations|Animações]]
*[[Character Skins|Skins de Pedestres]]
*[[CJ_Clothes|Roupas do CJ]]
*[[Garage|Garagens]]
*[[Interior IDs|Interiores]]
*[[Material IDs|Materiais]]
*[[Projectiles|Projéteis]]
*[[Radar Blips|Ponteiros do Radar]]
*[[Sounds|Efeitos Sonoros]]
*[[Vehicle IDs|Veículos]]
*[[Vehicle Colors|Cores para Veículos]]
*[[Vehicle Upgrades|Asessórios para Veículos]]
*[[Vehicle variants|Vehicle Variants]]
*[[Weapons|Armas]]
*[[Weather|Climas]]
</div>

<div style="border: 1px dotted #D8D8D8; padding:4px 8px 8px 8px; margin:10px;">
<div style="float:right; width: 32px;">[[File:pBR.png|32px]]</div>

<h3>Sobre a Tradução</h3>
* Tradutores:
** <span style="color: blue">RaceXtreme</span>
** <span style="color: blue">StanleySathler</span>
É importante que todos colaborem para que nossa página em português fique melhor a cada dia!

[[File:Osi symbol.png|75px|link=http://opensource.org/]]
'''Multi Theft Auto''' é um projeto '''Open Source'''. <br>
Isso significa que todos nós podemos contribuir para fazer um Multi Theft Auto muito melhor!
</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>'''Sobre Multi Theft Auto'''</li>
<li>[[Archive|Museu]]</li>
<li>[[Press Coverage|Eventos]]</li>
<li>[http://code.google.com/p/mtasa-blue/people/list Desenvolvedores]</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|Solução de Problemas]]</li>
</ul>
<ul style="list-style: none; width: 200px; float: left;">
<li>'''Status do Wiki'''</li>
<li>{{NUMBEROFARTICLES}} Artigos</li>
<li>{{NUMBEROFPAGES}} Páginas</li>
<li>{{NUMBEROFUSERS}} Usuários Registrados</li>
</ul>
</div>
|}

__NOTOC__
__NOEDITSECTION__
{{Languages list|pt-br}}

Server Manual

2012-05-20T21:43:09Z

Stanley Sathler .: /* Adding administrators */

__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:
* [[Building MTASA Server on GNU Linux]]
* [http://linux.mtasa.com Getting a 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>22004</serverport>
<httpport>22005</httpport>
</syntaxhighlight>

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

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

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

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

Main server port: UDP

HTTP Port: TCP

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

The ASE port is also simple to get:

ASE port = Main server port + 123

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

Good luck!

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

===Client Checks===

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

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

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

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

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

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

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

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

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

# resourcebrowser
# resourcemanager
# webadmin
# webmap

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

==Useful Notes==

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

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

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

[[Category:Support]]

PT-BR/Manual do Servidor

2012-05-20T21:40:18Z

Stanley Sathler .: /* Client Checks */

[[PT-BR/Manual_do_Servidor]]
==Introdução==
Configurar um servidor e disponibilizá-lo para que seus amigos joguem via Internet ou LAN é mais fácil do que parece. Neste artigo estaremos abordando os passos iniciais para que você possa criar o seu próprio servidor para o MTA.

==Instalando o servidor==
A primeira parte consiste na instalação do servidor. Abaixo há dois tópicos, abordando a instalação em plataformas Linux e Windows, respectivamente.

===Instalando no Linux===
Há diversas maneiras de instalar, configurar e iniciar um servidor no Linux:
* [[Image:iUS.png|Em Inglês|20px]] [[Building MTASA Server on GNU Linux|Configurando um Servidor de MTASA no GNU Linux (Em Inglês)]]
* [[Image:iUS.png|Em Inglês|20px]] [http://linux.mtasa.com Baixando o servidor para Linux]

===Instalando no Windows===
Instalar um servidor do MTA:SA no Windows é bem simples:
:*Vá para [http://mtasa.com/ página de download] do MTA:SA e baixe o instalador.
:*Após o término do download, execute o arquivo.
:*Clique em Next e depois em "I Agree".
:*Nesta etapa você pode selecionar os componentes que deseja ou não instalar:
:**Para instalar somente o servidor, mude a opção "Client and Server" para "Server Only"
:**Next para continuar.
:*Selecione a pasta na qual deseja instalar o servidor. Em seguida, Next.
:*Clique em Install.
:*Pronto!

''Qual a função do arquivo acl.xml (access control list)? Para saber mais, leia o artigo em:
* [[Image:iUS.png|Em Inglês|20px]] [[Access_Control_List|Access Control List]]''

==Configurando o servidor==
O servidor dedicado do Multi Theft Auto pode ser configurado através...

*De uma espécie de prompt de comando chamado '''console''', ou seja, um programa onde comandos não são enviados através de cliques, mas sim através de linhas de comando digitadas pelo usuário.
** Esse programa está localizado em "MTA San Andreas 1.3\server\MTA Server.exe".
** Ele é idêntico a janela ''cmd'' do windows.
** Enquanto este estiver executando, o servidor vai permanecer online, caso contrário, o servidor sai do ar.

*'''Do próprio jogo'''!
**Os comandos para configurar o servidor são enviados a partir do chat.
** Para que estes comandos sejam efetivamente enviados, é necessário o uso da "/" antes do comando em si, pois esta identifica que o que vem logo em seguida faz parte de um comando.. Exemplo "/addaccount".
*'''De um navegador de internet'''. Um website pode receber informações e configurar um servidor de MTA.

''Para que possa configurar um servidor do MTASA no jogo ou via website é necessário que pelo menos uma conta com privilégios de administrador seja adicionada no '''acl.xml'''.''

===Configurações Gerais===
Todas as configurações gerais podem ser encontradas no arquivo "[[Server_mtaserver.conf|'''mtaserver.conf''']]" localizado na pasta "mods/deathmatch/". Este arquivo pode ser visualizado em qualquer editor de texto.

Ele é bem simples e direto, toda variável tem uma [[Server_mtaserver.conf|descrição abordando o que esta faz e como usa-la]].

===Configurando as Portas===
Caso esteja executando um servidor a partir de seu computador e há um roteador entre a internet e sua máquina, então será necessário configurar 3 portas.

Antes de mais nada, abra o arquivo localizado em "mods/deathmatch/[[Server_mtaserver.conf|'''mtaserver.conf''']]" e procure pelas linhas citadas a seguir:
<syntaxhighlight lang="xml">
<serverport>22003</serverport>
<httpport>22005</httpport>
</syntaxhighlight>

Estas portas são necessárias para que o servidor inicie corretamente. Explicaremos com maiores detalhes mais a frente. Se deseja também que seu servidor apareça na lista de servidores do MTA (Server Browser, no menu), será preciso configurar mais uma porta chamada "ASE".

(Exemplo de como ativar/desativar a porta ASE):
<syntaxhighlight lang="xml">
<ase>1</ase> 
</syntaxhighlight>

Agora vamos liberar essas portas em seu roteador. Caso todas as portas estejam abertas ou você possui um roteador sem firewall, esta etapa é desnecessária.

Se você não sabe como abrir portas em seu roteador, visite [http://portforward.com/ este site], procure pelo modelo de seu roteador e siga as instruções.

Na maioria dos roteadores, há a opção de selecionar o tipo de porta: UDP ou TCP. A lista a seguir irá explicar qual porta é necessaria para que ela serve:

Porta principal do servidor: UDP (a porta padrão é 22003, mas você pode alterá-la no parâmetro <serverport> do mtaserver.config)
Porta HTTP: TCP (a porta padrão é 22005, mas você pode alterá-la no parâmetro <httpport> do mtaserver.config)
Porta ASE: UDP (esta é necessária caso deseje que o servidor apareça na lista de servidores do gamemonitor.com)

Para configurar a porta ASE, somamos 123 (cento e vinte e três) à porta padrão. Exemplo:

Porta padrão: 22003
ASE: 22003 + 123 = 22126

Boa sorte!

''Na ultima versão do servidor, ao se digitar o comando "/[[Server_Commands#openports|openports]]", os status de todas as portas serão mostrados.''

===Checagem dos clientes===
Todo jogador que entra em um servidor passa por várias "avaliações", também conhecidas como "Client Checks" (em inglês).
Esse processo é necessário, principalmente, para previnir trapaças no jogo, as quais são feitas através de trainers e/ou modificações realizadas nos arquivos originais do GTA SA.
Toda essas "avaliações" são dividias em diversos parâmetros, os quais são configuráveis através do arquivo [[Server_mtaserver.conf|'''mtaserver.conf''']] localizado em "mods/deathmatch".
Destacamos 2 delas como exemplo:

* O parâmetro '''client-file''' ...
** Habilita que um ou mais arquivos possam ser modificados no computador do jogador (exemplo: carmods.dat). Por padrão, o MTA não permite que nenhum arquivo da pasta "data" e "anim" do GTA SA seja modificado.
** Pertence a um grupo denominado Anti-Cheat, pois, por padrão, ele evita que um ou mais jogadores tenham vantagens sobre os outros. Todos os demais parâmetros que fazem parte desse grupo estão detalhados neste Guia [[Anti-cheat_guide|Anti-Cheat]].
* O parâmetro '''minclientversion'''...
** Estabelece que todos os jogadores usem uma versão igual ou superior a estipulada (exemplo: 1.3.0).
** Aqueles que estiverem usando uma versão inferior serão automaticamente desconectados do servidor.<br/>

Cada parâmetro contido no arquivo [[Server_mtaserver.conf|'''mtaserver.conf''']] tem um valor atribuido a ele. O que faz que o servidor ignore ou trabalhe de forma diferente ao realizar essas avaliações em cada jogador.

Se deseja definir uma versão mínima do MTA dos seus jogadores, procure pela linha:
<syntaxhighlight lang="xml">
<minclientversion></minclientversion>
</syntaxhighlight>
Use valores como: 1.1.1-9.02320

===Adicionando administradores===
É altamente recomendável adicionar, no mínimo, um administrador em seu servidor. Pois assim você poderá fazer uso de alguns recursos especiais, como o gerenciador Web ou alguns scripts que precisem acessar a lista ACL (painéis administrativos, por exemplo).

Para adicionar um administrador ao seu servidor, siga os seguintes passos:<br>
<ol>
<li>Enquanto o servidor estiver ligado (MTA Server.exe sendo executado), adicione uma nova conta digitando '''[[Server_Commands#addaccount|addaccount nome senha]]''' no console. Por exemplo, para adicionar o usuário Fulano você poderia digitar:
<div style="margin: 10px 10px 10px 10px;">
<syntaxhighlight lang="xml">
addaccount Fulano minhasenha123
</syntaxhighlight>
</div>
<div style="margin: 10px 10px 10px 20px;">
''Nota: Se você não tem acesso à janela do console, e o recurso "admin" está sendo executado, você pode adicionar uma nova conta digitando, no chat principal, o comando '''/register Fulano minhasenha123'''''
</div>
<li>O servidor deverá mostrar uma mensagem confirmando o registo da nova conta.
<li>A seguir, desligue o servidor digitando '''shutdown''' no console.
<li>Tenha certeza de que seu servidor foi desligado. Se ele continua online, as informações a seguir serão perdidas</li>
<li>Abra o arquivo 'mods/deathmatch/'acl.xml'''' com um Editor de Textos qualquer (pode ser o Bloco de Notas).
<li>Adicione a nova conta no grupo ''Admin'' usando a seguinte sintaxe do XML:
<div style="padding: 10px">
<syntaxhighlight lang="xml">
<acl>
...
<group name="Admin">
<acl name="Admin"/>
...
<object name="user.Fulano" />
</group>
...
</acl>
</syntaxhighlight>
</div>

Você pode adicionar o usuário criado no grupo que preferir. Cada grupo é linkado a um ACL ([[Acess Control List]]). Cada ACL contém uma série de ações que você pode ou não realizar dentro deste grupo (como kickar, banir, etc). Estes grupos existem para que diferentes usuários possam ter diferentes direitos em um servidor. O grupo ''Admin'' é apontado no ACL como um grupo poderoso (onde tudo é permitido). Já o grupo ''Everyone'', que significa ''Todos'', é apontado no ACL como um grupo com diversas restrições (ou seja, não podem kickar, banir, mutar, etc.).
</li>
<li>Pronto, você terminou! Agora você pode adicionar diversos usuários (sejam administradores ou usuários comuns). Dê uma olhada também nos outros grupos e ACLs disponíveis. O ACL é também acessível a partir do [[Acess_Control_List|Mecanismo de Scripting Lua]].<br>
É recomendado também que você dê uma olhada na interface Web. Iremos explicar como a seguir.
</li>
</ol>
'''Nota''': Existem também outras formas de adicionar contas e editar as permissões do servidor enquanto ele está sendo executado. "[[Server_Commands#addaccount|addaccount <usuário> <senha>]]" é um comando interno para adicionar contas, mas você vai precisar usar a interface Web para adicionar essas contas a um grupo/ACL específico.<br />

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

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

# resourcebrowser
# resourcemanager
# webadmin
# webmap

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

==Useful Notes==

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

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

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

[[Category:Support]]

Server Manual

2012-05-20T21:37:36Z

Stanley Sathler .: /* Adding administrators */

__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:
* [[Building MTASA Server on GNU Linux]]
* [http://linux.mtasa.com Getting a 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>22004</serverport>
<httpport>22005</httpport>
</syntaxhighlight>

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

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

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

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

Main server port: UDP

HTTP Port: TCP

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

The ASE port is also simple to get:

ASE port = Main server port + 123

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

Good luck!

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

===Client Checks===

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

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

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

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

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

Você pode adicionar o usuário criado no grupo que preferir. Cada grupo é linkado a um ACL ([[Acess Control List]]). Cada ACL contém uma série de ações que você pode ou não realizar dentro deste grupo (como kickar, banir, etc). Estes grupos existem para que diferentes usuários possam ter diferentes direitos em um servidor. O grupo ''Admin'' é apontado no ACL como um grupo poderoso (onde tudo é permitido). Já o grupo ''Everyone'', que significa ''Todos'', é apontado no ACL como um grupo com diversas restrições (ou seja, não podem kickar, banir, mutar, etc.).
</li>
<li>Pronto, você terminou! Agora você pode adicionar diversos usuários (sejam administradores ou usuários comuns). Dê uma olhada também nos outros grupos e ACLs disponíveis. O ACL é também acessível a partir do [[Acess_Control_List|Mecanismo de Scripting Lua]].<br>
É recomendado também que você dê uma olhada na interface Web. Iremos explicar como a seguir.
</li>
</ol>
'''Nota''': Existem também outras formas de adicionar contas e editar as permissões do servidor enquanto ele está sendo executado. "[[Server_Commands#addaccount|addaccount <usuário> <senha>]]" é um comando interno para adicionar contas, mas você vai precisar usar a interface Web para adicionar essas contas a um grupo/ACL específico.<br />

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

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

# resourcebrowser
# resourcemanager
# webadmin
# webmap

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

==Useful Notes==

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

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

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

[[Category:Support]]

PT-BR/Manual do Servidor

2012-05-20T21:23:37Z

Stanley Sathler .: /* Client Checks */

[[PT-BR/Manual_do_Servidor]]
==Introdução==
Configurar um servidor e disponibilizá-lo para que seus amigos joguem via Internet ou LAN é mais fácil do que parece. Neste artigo estaremos abordando os passos iniciais para que você possa criar o seu próprio servidor para o MTA.

==Instalando o servidor==
A primeira parte consiste na instalação do servidor. Abaixo há dois tópicos, abordando a instalação em plataformas Linux e Windows, respectivamente.

===Instalando no Linux===
Há diversas maneiras de instalar, configurar e iniciar um servidor no Linux:
* [[Image:iUS.png|Em Inglês|20px]] [[Building MTASA Server on GNU Linux|Configurando um Servidor de MTASA no GNU Linux (Em Inglês)]]
* [[Image:iUS.png|Em Inglês|20px]] [http://linux.mtasa.com Baixando o servidor para Linux]

===Instalando no Windows===
Instalar um servidor do MTA:SA no Windows é bem simples:
:*Vá para [http://mtasa.com/ página de download] do MTA:SA e baixe o instalador.
:*Após o término do download, execute o arquivo.
:*Clique em Next e depois em "I Agree".
:*Nesta etapa você pode selecionar os componentes que deseja ou não instalar:
:**Para instalar somente o servidor, mude a opção "Client and Server" para "Server Only"
:**Next para continuar.
:*Selecione a pasta na qual deseja instalar o servidor. Em seguida, Next.
:*Clique em Install.
:*Pronto!

''Qual a função do arquivo acl.xml (access control list)? Para saber mais, leia o artigo em:
* [[Image:iUS.png|Em Inglês|20px]] [[Access_Control_List|Access Control List]]''

==Configurando o servidor==
O servidor dedicado do Multi Theft Auto pode ser configurado através...

*De uma espécie de prompt de comando chamado '''console''', ou seja, um programa onde comandos não são enviados através de cliques, mas sim através de linhas de comando digitadas pelo usuário.
** Esse programa está localizado em "MTA San Andreas 1.3\server\MTA Server.exe".
** Ele é idêntico a janela ''cmd'' do windows.
** Enquanto este estiver executando, o servidor vai permanecer online, caso contrário, o servidor sai do ar.

*'''Do próprio jogo'''!
**Os comandos para configurar o servidor são enviados a partir do chat.
** Para que estes comandos sejam efetivamente enviados, é necessário o uso da "/" antes do comando em si, pois esta identifica que o que vem logo em seguida faz parte de um comando.. Exemplo "/addaccount".
*'''De um navegador de internet'''. Um website pode receber informações e configurar um servidor de MTA.

''Para que possa configurar um servidor do MTASA no jogo ou via website é necessário que pelo menos uma conta com privilégios de administrador seja adicionada no '''acl.xml'''.''

===Configurações Gerais===
Todas as configurações gerais podem ser encontradas no arquivo "[[Server_mtaserver.conf|'''mtaserver.conf''']]" localizado na pasta "mods/deathmatch/". Este arquivo pode ser visualizado em qualquer editor de texto.

Ele é bem simples e direto, toda variável tem uma [[Server_mtaserver.conf|descrição abordando o que esta faz e como usa-la]].

===Configurando as Portas===
Caso esteja executando um servidor a partir de seu computador e há um roteador entre a internet e sua máquina, então será necessário configurar 3 portas.

Antes de mais nada, abra o arquivo localizado em "mods/deathmatch/[[Server_mtaserver.conf|'''mtaserver.conf''']]" e procure pelas linhas citadas a seguir:
<syntaxhighlight lang="xml">
<serverport>22003</serverport>
<httpport>22005</httpport>
</syntaxhighlight>

Estas portas são necessárias para que o servidor inicie corretamente. Explicaremos com maiores detalhes mais a frente. Se deseja também que seu servidor apareça na lista de servidores do MTA (Server Browser, no menu), será preciso configurar mais uma porta chamada "ASE".

(Exemplo de como ativar/desativar a porta ASE):
<syntaxhighlight lang="xml">
<ase>1</ase> 
</syntaxhighlight>

Agora vamos liberar essas portas em seu roteador. Caso todas as portas estejam abertas ou você possui um roteador sem firewall, esta etapa é desnecessária.

Se você não sabe como abrir portas em seu roteador, visite [http://portforward.com/ este site], procure pelo modelo de seu roteador e siga as instruções.

Na maioria dos roteadores, há a opção de selecionar o tipo de porta: UDP ou TCP. A lista a seguir irá explicar qual porta é necessaria para que ela serve:

Porta principal do servidor: UDP (a porta padrão é 22003, mas você pode alterá-la no parâmetro <serverport> do mtaserver.config)
Porta HTTP: TCP (a porta padrão é 22005, mas você pode alterá-la no parâmetro <httpport> do mtaserver.config)
Porta ASE: UDP (esta é necessária caso deseje que o servidor apareça na lista de servidores do gamemonitor.com)

Para configurar a porta ASE, somamos 123 (cento e vinte e três) à porta padrão. Exemplo:

Porta padrão: 22003
ASE: 22003 + 123 = 22126

Boa sorte!

''Na ultima versão do servidor, ao se digitar o comando "/[[Server_Commands#openports|openports]]", os status de todas as portas serão mostrados.''

===Checagem dos clientes===
Todo jogador que entra em um servidor passa por várias "avaliações", também conhecidas como "Client Checks" (em inglês).
Esse processo é necessário, principalmente, para previnir trapaças no jogo, as quais são feitas através de trainers e/ou modificações realizadas nos arquivos originais do GTA SA.
Toda essas "avaliações" são dividias em diversos parâmetros, os quais são configuráveis através do arquivo [[Server_mtaserver.conf|'''mtaserver.conf''']] localizado em "mods/deathmatch".
Destacamos 2 delas como exemplo:

* O parâmetro '''client-file''' ...
** Habilita que um ou mais arquivos possam ser modificados no computador do jogador (exemplo: carmods.dat). Por padrão, o MTA não permite que nenhum arquivo da pasta "data" e "anim" do GTA SA seja modificado.
** Pertence a um grupo denominado Anti-Cheat, pois, por padrão, ele evita que um ou mais jogadores tenham vantagens sobre os outros. Todos os demais parâmetros que fazem parte desse grupo estão detalhados neste Guia [[Anti-cheat_guide|Anti-Cheat]].
* O parâmetro '''minclientversion'''...
** Estabelece que todos os jogadores usem uma versão igual ou superior a estipulada (exemplo: 1.3.0).
** Aqueles que estiverem usando uma versão inferior serão automaticamente desconectados do servidor.<br/>

Cada parâmetro contido no arquivo [[Server_mtaserver.conf|'''mtaserver.conf''']] tem um valor atribuido a ele. O que faz que o servidor ignore ou trabalhe de forma diferente ao realizar essas avaliações em cada jogador.

Se deseja definir uma versão mínima do MTA dos seus jogadores, procure pela linha:
<syntaxhighlight lang="xml">
<minclientversion></minclientversion>
</syntaxhighlight>
Use valores como: 1.1.1-9.02320

===Adicionando administradores===
É altamente recomendável adicionar, no mínimo, um administrador em seu servidor. Pois assim você poderá fazer uso de alguns recursos especiais, como o gerenciador Web ou alguns scripts que precisem acessar a lista ACL (painéis administrativos, por exemplo).

Para adicionar um administrador ao seu servidor, siga os seguintes passos:<br>
<ol>
<li>Enquanto o servidor estiver ligado (MTA Server.exe sendo executado), adicione uma nova conta digitando '''[[Server_Commands#addaccount|addaccount nome senha]]''' no console. Por exemplo, para adicionar o usuário Fulano você poderia digitar:
<div style="margin: 10px 10px 10px 10px;">
<syntaxhighlight lang="xml">
addaccount Fulano minhasenha123
</syntaxhighlight>
</div>
<div style="margin: 10px 10px 10px 20px;">
''Nota: Se você não tem acesso à janela do console, e o recurso "admin" está sendo executado, você pode adicionar uma nova conta digitando, no chat principal, o comando '''/register Fulano minhasenha123'''''
</div>
<li>O servidor deverá mostrar uma mensagem confirmando o registo da nova conta.
<li>A seguir, desligue o servidor digitando '''shutdown''' no console.
<li>Tenha certeza de que seu servidor foi desligado. Se ele continua online, as informações a seguir serão perdidas</li>
<li>Abra o arquivo 'mods/deathmatch/'acl.xml'''' com um Editor de Textos qualquer (pode ser o Bloco de Notas).
<li>Adicione a nova conta no grupo ''Admin'' usando a seguinte sintaxe do XML:
<div style="padding: 10px">
<syntaxhighlight lang="xml">
<acl>
...
<group name="Admin">
<acl name="Admin"/>
...
<object name="user.Fulano" />
</group>
...
</acl>
</syntaxhighlight>
</div>

You can actually add your user to any group you want. Each group is linked to an ACL ([[Access Control List]]). Each ACL contains a series of specific allowed or denied rights. These groups exist so different users can be assigned different rights. The ''Admin'' group points to the ''Admin'' ACL, which is empty (thus allowing all possible commands). The ''Everyone'' group points to the ''Default'' ACL that puts a series of restrictions on the available commands (to disallow regular players from using admin commands).
</li>
<li>
You're done! You can add as many administrators or users as you want this way, take a look at some of the other groups and ACLs for example. The ACL is also accessible through the [[Access_Control_List|Lua scripting engine]].<br>

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

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

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

# resourcebrowser
# resourcemanager
# webadmin
# webmap

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

==Useful Notes==

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

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

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

[[Category:Support]]

PT-BR/Manual do Servidor

2012-05-20T21:18:05Z

Stanley Sathler .: /* Client Checks */

[[PT-BR/Manual_do_Servidor]]
==Introdução==
Configurar um servidor e disponibilizá-lo para que seus amigos joguem via Internet ou LAN é mais fácil do que parece. Neste artigo estaremos abordando os passos iniciais para que você possa criar o seu próprio servidor para o MTA.

==Instalando o servidor==
A primeira parte consiste na instalação do servidor. Abaixo há dois tópicos, abordando a instalação em plataformas Linux e Windows, respectivamente.

===Instalando no Linux===
Há diversas maneiras de instalar, configurar e iniciar um servidor no Linux:
* [[Image:iUS.png|Em Inglês|20px]] [[Building MTASA Server on GNU Linux|Configurando um Servidor de MTASA no GNU Linux (Em Inglês)]]
* [[Image:iUS.png|Em Inglês|20px]] [http://linux.mtasa.com Baixando o servidor para Linux]

===Instalando no Windows===
Instalar um servidor do MTA:SA no Windows é bem simples:
:*Vá para [http://mtasa.com/ página de download] do MTA:SA e baixe o instalador.
:*Após o término do download, execute o arquivo.
:*Clique em Next e depois em "I Agree".
:*Nesta etapa você pode selecionar os componentes que deseja ou não instalar:
:**Para instalar somente o servidor, mude a opção "Client and Server" para "Server Only"
:**Next para continuar.
:*Selecione a pasta na qual deseja instalar o servidor. Em seguida, Next.
:*Clique em Install.
:*Pronto!

''Qual a função do arquivo acl.xml (access control list)? Para saber mais, leia o artigo em:
* [[Image:iUS.png|Em Inglês|20px]] [[Access_Control_List|Access Control List]]''

==Configurando o servidor==
O servidor dedicado do Multi Theft Auto pode ser configurado através...

*De uma espécie de prompt de comando chamado '''console''', ou seja, um programa onde comandos não são enviados através de cliques, mas sim através de linhas de comando digitadas pelo usuário.
** Esse programa está localizado em "MTA San Andreas 1.3\server\MTA Server.exe".
** Ele é idêntico a janela ''cmd'' do windows.
** Enquanto este estiver executando, o servidor vai permanecer online, caso contrário, o servidor sai do ar.

*'''Do próprio jogo'''!
**Os comandos para configurar o servidor são enviados a partir do chat.
** Para que estes comandos sejam efetivamente enviados, é necessário o uso da "/" antes do comando em si, pois esta identifica que o que vem logo em seguida faz parte de um comando.. Exemplo "/addaccount".
*'''De um navegador de internet'''. Um website pode receber informações e configurar um servidor de MTA.

''Para que possa configurar um servidor do MTASA no jogo ou via website é necessário que pelo menos uma conta com privilégios de administrador seja adicionada no '''acl.xml'''.''

===Configurações Gerais===
Todas as configurações gerais podem ser encontradas no arquivo "[[Server_mtaserver.conf|'''mtaserver.conf''']]" localizado na pasta "mods/deathmatch/". Este arquivo pode ser visualizado em qualquer editor de texto.

Ele é bem simples e direto, toda variável tem uma [[Server_mtaserver.conf|descrição abordando o que esta faz e como usa-la]].

===Configurando as Portas===
Caso esteja executando um servidor a partir de seu computador e há um roteador entre a internet e sua máquina, então será necessário configurar 3 portas.

Antes de mais nada, abra o arquivo localizado em "mods/deathmatch/[[Server_mtaserver.conf|'''mtaserver.conf''']]" e procure pelas linhas citadas a seguir:
<syntaxhighlight lang="xml">
<serverport>22003</serverport>
<httpport>22005</httpport>
</syntaxhighlight>

Estas portas são necessárias para que o servidor inicie corretamente. Explicaremos com maiores detalhes mais a frente. Se deseja também que seu servidor apareça na lista de servidores do MTA (Server Browser, no menu), será preciso configurar mais uma porta chamada "ASE".

(Exemplo de como ativar/desativar a porta ASE):
<syntaxhighlight lang="xml">
<ase>1</ase> 
</syntaxhighlight>

Agora vamos liberar essas portas em seu roteador. Caso todas as portas estejam abertas ou você possui um roteador sem firewall, esta etapa é desnecessária.

Se você não sabe como abrir portas em seu roteador, visite [http://portforward.com/ este site], procure pelo modelo de seu roteador e siga as instruções.

Na maioria dos roteadores, há a opção de selecionar o tipo de porta: UDP ou TCP. A lista a seguir irá explicar qual porta é necessaria para que ela serve:

Porta principal do servidor: UDP (a porta padrão é 22003, mas você pode alterá-la no parâmetro <serverport> do mtaserver.config)
Porta HTTP: TCP (a porta padrão é 22005, mas você pode alterá-la no parâmetro <httpport> do mtaserver.config)
Porta ASE: UDP (esta é necessária caso deseje que o servidor apareça na lista de servidores do gamemonitor.com)

Para configurar a porta ASE, somamos 123 (cento e vinte e três) à porta padrão. Exemplo:

Porta padrão: 22003
ASE: 22003 + 123 = 22126

Boa sorte!

''Na ultima versão do servidor, ao se digitar o comando "/[[Server_Commands#openports|openports]]", os status de todas as portas serão mostrados.''

===Client Checks===
Todo jogador que entra em um servidor passa por várias "avaliações", também conhecidas como "Client Checks" (em inglês).
Esse processo é necessário, principalmente, para previnir trapaças no jogo, as quais são feitas através de trainers e/ou modificações realizadas nos arquivos originais do GTA SA.
Toda essas "avaliações" são dividias em diversos parâmetros, os quais são configuráveis através do arquivo [[Server_mtaserver.conf|'''mtaserver.conf''']] localizado em "mods/deathmatch".
Destacamos 2 delas como exemplo:

* O parâmetro '''client-file''' ...
** Habilita que um ou mais arquivos possam ser modificados no computador do jogador (exemplo: carmods.dat). Por padrão, o MTA não permite que nenhum arquivo da pasta "data" e "anim" do GTA SA seja modificado.
** Pertence a um grupo denominado Anti-Cheat, pois, por padrão, ele evita que um ou mais jogadores tenham vantagens sobre os outros. Todos os demais parâmetros que fazem parte desse grupo estão detalhados neste Guia [[Anti-cheat_guide|Anti-Cheat]].
* O parâmetro '''minclientversion'''...
** Estabelece que todos os jogadores usem uma versão igual ou superior a estipulada (exemplo: 1.3.0).
** Aqueles que estiverem usando uma versão inferior serão automaticamente desconectados do servidor.<br/>

Cada parâmetro contido no arquivo [[Server_mtaserver.conf|'''mtaserver.conf''']] tem um valor atribuido a ele. O que faz que o servidor ignore ou trabalhe de forma diferente ao realizar essas avaliações em cada jogador.

<!--Se deseja definir uma versão mínima do MTA dos seus jogadores, procure pela linha:
<syntaxhighlight lang="xml">
<minclientversion></minclientversion>
</syntaxhighlight>
Use valores como: 1.1.1-9.02320

===Adicionando administradores===
É altamente recomendável adicionar, no mínimo, um administrador em seu servidor. Pois assim você poderá fazer uso de alguns recursos especiais, como o gerenciador Web ou alguns scripts que precisem acessar a lista ACL (painéis administrativos, por exemplo).

Para adicionar um administrador ao seu servidor, siga os seguintes passos:<br>
<ol>
<li>Enquanto o servidor estiver ligado (MTA Server.exe sendo executado), adicione uma nova conta digitando '''[[Server_Commands#addaccount|addaccount nome senha]]''' no console. Por exemplo, para adicionar o usuário Fulano você poderia digitar:
<div style="margin: 10px 10px 10px 10px;">
<syntaxhighlight lang="xml">
addaccount Fulano minhasenha123
</syntaxhighlight>
</div>
<div style="margin: 10px 10px 10px 20px;">
''Nota: Se você não tem acesso à janela do console, e o recurso "admin" está sendo executado, você pode adicionar uma nova conta digitando, no chat principal, o comando '''/register Fulano minhasenha123'''''
</div>
<li>O servidor deverá mostrar uma mensagem confirmando o registo da nova conta.
<li>A seguir, desligue o servidor digitando '''shutdown''' no console.
<li>Tenha certeza de que seu servidor foi desligado. Se ele continua online, as informações a seguir serão perdidas</li>
<li>Abra o arquivo 'mods/deathmatch/'acl.xml'''' com um Editor de Textos qualquer (pode ser o Bloco de Notas).
<li>Adicione a nova conta no grupo ''Admin'' usando a seguinte sintaxe do XML:
<div style="padding: 10px">
<syntaxhighlight lang="xml">
<acl>
...
<group name="Admin">
<acl name="Admin"/>
...
<object name="user.Fulano" />
</group>
...
</acl>
</syntaxhighlight>
</div>

You can actually add your user to any group you want. Each group is linked to an ACL ([[Access Control List]]). Each ACL contains a series of specific allowed or denied rights. These groups exist so different users can be assigned different rights. The ''Admin'' group points to the ''Admin'' ACL, which is empty (thus allowing all possible commands). The ''Everyone'' group points to the ''Default'' ACL that puts a series of restrictions on the available commands (to disallow regular players from using admin commands).
</li>
<li>
You're done! You can add as many administrators or users as you want this way, take a look at some of the other groups and ACLs for example. The ACL is also accessible through the [[Access_Control_List|Lua scripting engine]].<br>

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

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

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

# resourcebrowser
# resourcemanager
# webadmin
# webmap

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

==Useful Notes==

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

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

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

[[Category:Support]]

PT-BR/Manual do Servidor

2012-05-20T21:06:18Z

Stanley Sathler .: /* Configurando as Portas */

[[PT-BR/Manual_do_Servidor]]
==Introdução==
Configurar um servidor e disponibilizá-lo para que seus amigos joguem via Internet ou LAN é mais fácil do que parece. Neste artigo estaremos abordando os passos iniciais para que você possa criar o seu próprio servidor para o MTA.

==Instalando o servidor==
A primeira parte consiste na instalação do servidor. Abaixo há dois tópicos, abordando a instalação em plataformas Linux e Windows, respectivamente.

===Instalando no Linux===
Há diversas maneiras de instalar, configurar e iniciar um servidor no Linux:
* [[Image:iUS.png|Em Inglês|20px]] [[Building MTASA Server on GNU Linux|Configurando um Servidor de MTASA no GNU Linux (Em Inglês)]]
* [[Image:iUS.png|Em Inglês|20px]] [http://linux.mtasa.com Baixando o servidor para Linux]

===Instalando no Windows===
Instalar um servidor do MTA:SA no Windows é bem simples:
:*Vá para [http://mtasa.com/ página de download] do MTA:SA e baixe o instalador.
:*Após o término do download, execute o arquivo.
:*Clique em Next e depois em "I Agree".
:*Nesta etapa você pode selecionar os componentes que deseja ou não instalar:
:**Para instalar somente o servidor, mude a opção "Client and Server" para "Server Only"
:**Next para continuar.
:*Selecione a pasta na qual deseja instalar o servidor. Em seguida, Next.
:*Clique em Install.
:*Pronto!

''Qual a função do arquivo acl.xml (access control list)? Para saber mais, leia o artigo em:
* [[Image:iUS.png|Em Inglês|20px]] [[Access_Control_List|Access Control List]]''

==Configurando o servidor==
O servidor dedicado do Multi Theft Auto pode ser configurado através...

*De uma espécie de prompt de comando chamado '''console''', ou seja, um programa onde comandos não são enviados através de cliques, mas sim através de linhas de comando digitadas pelo usuário.
** Esse programa está localizado em "MTA San Andreas 1.3\server\MTA Server.exe".
** Ele é idêntico a janela ''cmd'' do windows.
** Enquanto este estiver executando, o servidor vai permanecer online, caso contrário, o servidor sai do ar.

*'''Do próprio jogo'''!
**Os comandos para configurar o servidor são enviados a partir do chat.
** Para que estes comandos sejam efetivamente enviados, é necessário o uso da "/" antes do comando em si, pois esta identifica que o que vem logo em seguida faz parte de um comando.. Exemplo "/addaccount".
*'''De um navegador de internet'''. Um website pode receber informações e configurar um servidor de MTA.

''Para que possa configurar um servidor do MTASA no jogo ou via website é necessário que pelo menos uma conta com privilégios de administrador seja adicionada no '''acl.xml'''.''

===Configurações Gerais===
Todas as configurações gerais podem ser encontradas no arquivo "[[Server_mtaserver.conf|'''mtaserver.conf''']]" localizado na pasta "mods/deathmatch/". Este arquivo pode ser visualizado em qualquer editor de texto.

Ele é bem simples e direto, toda variável tem uma [[Server_mtaserver.conf|descrição abordando o que esta faz e como usa-la]].

===Configurando as Portas===
Caso esteja executando um servidor a partir de seu computador e há um roteador entre a internet e sua máquina, então será necessário configurar 3 portas.

Antes de mais nada, abra o arquivo localizado em "mods/deathmatch/[[Server_mtaserver.conf|'''mtaserver.conf''']]" e procure pelas linhas citadas a seguir:
<syntaxhighlight lang="xml">
<serverport>22003</serverport>
<httpport>22005</httpport>
</syntaxhighlight>

Estas portas são necessárias para que o servidor inicie corretamente. Explicaremos com maiores detalhes mais a frente. Se deseja também que seu servidor apareça na lista de servidores do MTA (Server Browser, no menu), será preciso configurar mais uma porta chamada "ASE".

(Exemplo de como ativar/desativar a porta ASE):
<syntaxhighlight lang="xml">
<ase>1</ase> 
</syntaxhighlight>

Agora vamos liberar essas portas em seu roteador. Caso todas as portas estejam abertas ou você possui um roteador sem firewall, esta etapa é desnecessária.

Se você não sabe como abrir portas em seu roteador, visite [http://portforward.com/ este site], procure pelo modelo de seu roteador e siga as instruções.

Na maioria dos roteadores, há a opção de selecionar o tipo de porta: UDP ou TCP. A lista a seguir irá explicar qual porta é necessaria para que ela serve:

Porta principal do servidor: UDP (a porta padrão é 22003, mas você pode alterá-la no parâmetro <serverport> do mtaserver.config)
Porta HTTP: TCP (a porta padrão é 22005, mas você pode alterá-la no parâmetro <httpport> do mtaserver.config)
Porta ASE: UDP (esta é necessária caso deseje que o servidor apareça na lista de servidores do gamemonitor.com)

Para configurar a porta ASE, somamos 123 (cento e vinte e três) à porta padrão. Exemplo:

Porta padrão: 22003
ASE: 22003 + 123 = 22126

Boa sorte!

''Na ultima versão do servidor, ao se digitar o comando "/[[Server_Commands#openports|openports]]", os status de todas as portas serão mostrados.''

===Client Checks===
Todo jogador que entra em um servidor passa por várias "avaliações", também conhecido como "Client Checks" (em inglês).
Esse processo é necessário, principalmente, para previnir trapaças no jogo, as quais são feitas através de trainers e/ou modificações realizadas nos arquivos originais do GTA SA.
Toda essas "avaliações" são dividias em diversos parâmetros, os quais são configuráveis através do arquivo [[Server_mtaserver.conf|'''mtaserver.conf''']] localizado em "mods/deathmatch".
Destacamos 2 delas como exemplo:

* O parâmetro '''client-file''' ...
** habilita que um ou mais arquivos possam ser modificados no computador do jogador (exemplo: carmods.dat). Por padrão, o MTA não permite que nenhum arquivo da pasta "data" e "anim" do GTA SA seja modificado.
** pertênce a um grupo denominado Anti-Cheat, pois, por padrão, ele evita que um ou mais jogadores tenham vantagens sobre os outros. Todos os demais parâmetros que fazem parte desse grupo estão detalhados neste Guia [[Anti-cheat_guide|Anti-Cheat]].
* O parâmetro '''minclientversion'''...
** estabelece que todos os jogadores usem uma versão igual ou superior a estipulada (exemplo: 1.3.0).
** Aqueles que estiverem usando uma versão inferior serão automaticamente desconectados do servidor.<br/>

Cada parâmetro contido no arquivo [[Server_mtaserver.conf|'''mtaserver.conf''']] tem um valor atribuido a ele. O que faz que o servidor iginore ou aja de forma diferente ao relaziar essas avaliações em cada jogador.

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

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

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

You can actually add your user to any group you want. Each group is linked to an ACL ([[Access Control List]]). Each ACL contains a series of specific allowed or denied rights. These groups exist so different users can be assigned different rights. The ''Admin'' group points to the ''Admin'' ACL, which is empty (thus allowing all possible commands). The ''Everyone'' group points to the ''Default'' ACL that puts a series of restrictions on the available commands (to disallow regular players from using admin commands).
</li>
<li>
You're done! You can add as many administrators or users as you want this way, take a look at some of the other groups and ACLs for example. The ACL is also accessible through the [[Access_Control_List|Lua scripting engine]].<br>

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

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

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

# resourcebrowser
# resourcemanager
# webadmin
# webmap

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

==Useful Notes==

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

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

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

[[Category:Support]]

PT-BR/Manual do Servidor

2012-05-20T21:05:19Z

Stanley Sathler .: /* Configurando o servidor */

[[PT-BR/Manual_do_Servidor]]
==Introdução==
Configurar um servidor e disponibilizá-lo para que seus amigos joguem via Internet ou LAN é mais fácil do que parece. Neste artigo estaremos abordando os passos iniciais para que você possa criar o seu próprio servidor para o MTA.

==Instalando o servidor==
A primeira parte consiste na instalação do servidor. Abaixo há dois tópicos, abordando a instalação em plataformas Linux e Windows, respectivamente.

===Instalando no Linux===
Há diversas maneiras de instalar, configurar e iniciar um servidor no Linux:
* [[Image:iUS.png|Em Inglês|20px]] [[Building MTASA Server on GNU Linux|Configurando um Servidor de MTASA no GNU Linux (Em Inglês)]]
* [[Image:iUS.png|Em Inglês|20px]] [http://linux.mtasa.com Baixando o servidor para Linux]

===Instalando no Windows===
Instalar um servidor do MTA:SA no Windows é bem simples:
:*Vá para [http://mtasa.com/ página de download] do MTA:SA e baixe o instalador.
:*Após o término do download, execute o arquivo.
:*Clique em Next e depois em "I Agree".
:*Nesta etapa você pode selecionar os componentes que deseja ou não instalar:
:**Para instalar somente o servidor, mude a opção "Client and Server" para "Server Only"
:**Next para continuar.
:*Selecione a pasta na qual deseja instalar o servidor. Em seguida, Next.
:*Clique em Install.
:*Pronto!

''Qual a função do arquivo acl.xml (access control list)? Para saber mais, leia o artigo em:
* [[Image:iUS.png|Em Inglês|20px]] [[Access_Control_List|Access Control List]]''

==Configurando o servidor==
O servidor dedicado do Multi Theft Auto pode ser configurado através...

*De uma espécie de prompt de comando chamado '''console''', ou seja, um programa onde comandos não são enviados através de cliques, mas sim através de linhas de comando digitadas pelo usuário.
** Esse programa está localizado em "MTA San Andreas 1.3\server\MTA Server.exe".
** Ele é idêntico a janela ''cmd'' do windows.
** Enquanto este estiver executando, o servidor vai permanecer online, caso contrário, o servidor sai do ar.

*'''Do próprio jogo'''!
**Os comandos para configurar o servidor são enviados a partir do chat.
** Para que estes comandos sejam efetivamente enviados, é necessário o uso da "/" antes do comando em si, pois esta identifica que o que vem logo em seguida faz parte de um comando.. Exemplo "/addaccount".
*'''De um navegador de internet'''. Um website pode receber informações e configurar um servidor de MTA.

''Para que possa configurar um servidor do MTASA no jogo ou via website é necessário que pelo menos uma conta com privilégios de administrador seja adicionada no '''acl.xml'''.''

===Configurações Gerais===
Todas as configurações gerais podem ser encontradas no arquivo "[[Server_mtaserver.conf|'''mtaserver.conf''']]" localizado na pasta "mods/deathmatch/". Este arquivo pode ser visualizado em qualquer editor de texto.

Ele é bem simples e direto, toda variável tem uma [[Server_mtaserver.conf|descrição abordando o que esta faz e como usa-la]].

===Configurando as Portas===
Caso esteja executando um servidor a partir de seu computador e há um roteador entre a internet e sua máquina, então será necessário configurar 3 portas.

Antes de mais nada, abra o arquivo localizado em "mods/deathmatch/[[Server_mtaserver.conf|'''mtaserver.conf''']]" e procure pelas linhas citadas a seguir:
<syntaxhighlight lang="xml">
<serverport>22003</serverport>
<httpport>22005</httpport>
</syntaxhighlight>

Estas portas são necessárias para que o servidor inicie corretamente. Explicaremos com maiores detalhes mais a frente.
!Se deseja também que seu servidor apareça na lista de servidores do MTA (Server Browser, no menu), será preciso configurar mais uma porta chamada "ASE".

(Exemplo de como ativar/desativar a porta ASE):
<syntaxhighlight lang="xml">
<ase>1</ase> 
</syntaxhighlight>

Agora vamos liberar essas portas em seu roteador. Caso todas as portas estejam abertas ou você possui um roteador sem firewall, esta etapa é desnecessária.

Se você não sabe como abrir portas em seu roteador, visite [http://portforward.com/ este site], procure pelo modelo de seu roteador e siga as instruções.

Na maioria dos roteadores, há a opção de selecionar o tipo de porta: UDP ou TCP. A lista a seguir irá explicar qual porta é necessaria para que ela serve:

Porta principal do servidor: UDP (a porta padrão é 22003, mas você pode alterá-la no parâmetro <serverport> do mtaserver.config)
Porta HTTP: TCP (a porta padrão é 22005, mas você pode alterá-la no parâmetro <httpport> do mtaserver.config)
Porta ASE: UDP (esta é necessária caso deseje que o servidor apareça na lista de servidores do gamemonitor.com)

Para configurar a porta ASE, somamos 123 (cento e vinte e três) à porta padrão. Exemplo:

Porta padrão: 22003
ASE: 22003 + 123 = 22126

Boa sorte!

''Na ultima versão do servidor, ao se digitar o comando "/[[Server_Commands#openports|openports]]", os status de todas as portas serão mostrados.''

===Client Checks===
Todo jogador que entra em um servidor passa por várias "avaliações", também conhecido como "Client Checks" (em inglês).
Esse processo é necessário, principalmente, para previnir trapaças no jogo, as quais são feitas através de trainers e/ou modificações realizadas nos arquivos originais do GTA SA.
Toda essas "avaliações" são dividias em diversos parâmetros, os quais são configuráveis através do arquivo [[Server_mtaserver.conf|'''mtaserver.conf''']] localizado em "mods/deathmatch".
Destacamos 2 delas como exemplo:

* O parâmetro '''client-file''' ...
** habilita que um ou mais arquivos possam ser modificados no computador do jogador (exemplo: carmods.dat). Por padrão, o MTA não permite que nenhum arquivo da pasta "data" e "anim" do GTA SA seja modificado.
** pertênce a um grupo denominado Anti-Cheat, pois, por padrão, ele evita que um ou mais jogadores tenham vantagens sobre os outros. Todos os demais parâmetros que fazem parte desse grupo estão detalhados neste Guia [[Anti-cheat_guide|Anti-Cheat]].
* O parâmetro '''minclientversion'''...
** estabelece que todos os jogadores usem uma versão igual ou superior a estipulada (exemplo: 1.3.0).
** Aqueles que estiverem usando uma versão inferior serão automaticamente desconectados do servidor.<br/>

Cada parâmetro contido no arquivo [[Server_mtaserver.conf|'''mtaserver.conf''']] tem um valor atribuido a ele. O que faz que o servidor iginore ou aja de forma diferente ao relaziar essas avaliações em cada jogador.

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

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

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

You can actually add your user to any group you want. Each group is linked to an ACL ([[Access Control List]]). Each ACL contains a series of specific allowed or denied rights. These groups exist so different users can be assigned different rights. The ''Admin'' group points to the ''Admin'' ACL, which is empty (thus allowing all possible commands). The ''Everyone'' group points to the ''Default'' ACL that puts a series of restrictions on the available commands (to disallow regular players from using admin commands).
</li>
<li>
You're done! You can add as many administrators or users as you want this way, take a look at some of the other groups and ACLs for example. The ACL is also accessible through the [[Access_Control_List|Lua scripting engine]].<br>

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

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

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

# resourcebrowser
# resourcemanager
# webadmin
# webmap

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

==Useful Notes==

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

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

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

[[Category:Support]]

Página Inicial

2012-05-20T20:53:19Z

Stanley Sathler .:

{| width="100%" cellspacing="0" cellpadding="0"
| colspan="2" |
<div style="border: 1px solid #D8D8D8; padding: 5px; height: 130px;">
[[File:Mtalogo.png|left|100px]]'''Bem Vindo ao Multi Theft Auto wiki em Português.''' Aqui você encontra toda a informação sobre o uso do Multi Theft Auto.

Há muitas [[How you can help|coisas em que você pode nos ajudar]] para melhorar o MTA, como criar um mapa, um modo de jogo (gamemode), documentar as funções de programação, escrever códigos como exemplo, fazer tutoriais ou somente jogar o MTA e reportar falhas/bugs que encontrar.

Se você tem alguma pergunta ou problema em relação à programação, sinta-se a vontade para nos comunicar em nosso [[IRC Channel|Canal 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>Jogar</h3>
<div style="background: #FFEEAA; border: 1px solid #FFCD19;">
[[File:Go-down.png|link=http://mtasa.com/]] ''' [http://mtasa.com/ Download Multi Theft Auto: San Andreas {{Current Version|full}}]'''</div>
* [[Image:iBR.png|Em Português|20px]] [[PT-BR/Manual_do_Cliente|Manual do Cliente]]
* [[Image:iUS.png|Em Inglês|20px]] [[Changes_in_{{padleft:|3|{{Current Version|full}}}}| Mudanças na versão {{padleft:|3|{{Current Version|full}}}}]]
* [[Image:iBR.png|Em Português|20px]] [[PT-BR/Soluções_de_Problemas_-_FAQ|Solução de Problemas (FAQ)]]
* [[Image:iUS.png|Em Inglês|20px]] [[Upgrading_from_MTA:Race|Migrando do MTA:Race ao MTA:SA {{padleft:|3|{{Current Version|full}}}}]]
* [[Image:iUS.png|Em Inglês|20px]] [[Server Manual|Manual do Servidor]]
* [[Image:iUS.png|Em Inglês|20px]] [[Map manager|Map Manager]]

<h3>Editor de Mapas</h3>
* [[Image:iUS.png|Em Inglês|20px]] [[Resource:Editor|Manual do Editor]]
* [[Image:iUS.png|Em Inglês|20px]] [[Resource:Editor/EDF|Formato de Definições do Editor (EDF)]]
* [[Image:iUS.png|Em Inglês|20px]] [[Resource:Editor/Plugins|Extensões para o Editor]]
* [[Image:iUS.png|Em Inglês|20px]] [[Resource:Editor#FAQ|Perguntas Frequentes]]
</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>Banco de Dados</h3>
Esta sessão abrange todo tipo de conteúdo referente à scripts em LUA e recursos para o MTA.
* [[File:iUS.png|Em Inglês|20px]] [[:Category:Resource|Catálogo de Recursos]] - Ótimos exemplos para aprender à programar com eficiência.
* [[File:iUS.png|Em Inglês|20px]] [[Client side scripts|Scripts do Cliente]]
* [[File:iUS.png|Em Inglês|20px]] [[Modules|Módulos]]
</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>Desenvolvendo o Multi Theft Auto</h3>
[[File:Go-down.png|link=http://nightly.mtasa.com/]] [http://nightly.mtasa.com/ Nightly builds]
* [[File:iUS.png|Em Inglês|20px]] [[Compiling_MTASA|Compilando o MTASA no Windows]]
* [[File:iUS.png|Em Inglês|20px]] [[Building_MTASA_Server_on_Mac_OS_X|Compilando o MTASA no Mac OS X]]
* [[File:iUS.png|Em Inglês|20px]] [[Building_MTASA_Server_on_GNU_Linux|Compilando o MTASA no GNU/Linux]]
* [[File:iUS.png|Em Inglês|20px]] [[Coding guidelines|Guia do Desenvolvedor]]
* [[File:iUS.png|Em Inglês|20px]] [http://code.google.com/p/mtasa-blue Google Code SVN]
* [[File:iUS.png|Em Inglês|20px]] [[Roadmap|Roteiro para versões futuras]]
* [[File:iUS.png|Em Inglês|20px]] [http://bugs.mtasa.com/ Bugtracker Central de Bugs]
</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>Wiki - Como você pode ajudar</h3>
* Terminar os documentários de [[:Category:Incomplete|funções incompletas]].
* [[:Category:Needs_Example |Adicionar exemplos para funções e eventos]].
* Revisar e verificar as [[:Category:Needs Checking|páginas que necessitam de revisão]].
* Escrever tutoriais para ajudar novatos.
* Traduzir as páginas do Wiki.
</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>Comunidade</h3>
* [[File:iUS.png|Em Inglês|20px]] [http://forum.multitheftauto.com/ Forum]
* [[Image:iBR.png|Em Português|20px]] [http://forum.multitheftauto.com/viewforum.php?f=120&sid=79576f41173f69a47135647007d58d64 Fórum em Português]
* [[File:iUS.png|Em Inglês|20px]] IRC: [irc://irc.multitheftauto.com/mta irc.multitheftauto.com #mta]
* [[File:iUS.png|Em Inglês|20px]] [http://community.mtasa.com/ MTA Community] - Compartilhe e baixe recursos.
* [[File:iUS.png|Em Inglês|20px]] [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>Scripting</h3>
* [[File:iUS.png|Em Inglês|20px]] [[Scripting Introduction|Introdução ao Scripting]]
* [[File:iUS.png|Em Inglês|20px]] [[Introduction to Scripting the GUI|Introdução ao GUI Scripting]]
* [[File:iUS.png|Em Inglês|20px]] [[Debugging|Depuração]] - Como achar erros em seus Scripts
* [[File:iUS.png|Em Inglês|20px]] [[Resources|Introdução aos Recursos]]
** [[File:iUS.png|Em Inglês|20px]] [[Resource Web Access| Acesso Web via Recursos ]] - Como fazemos páginas de internet via recursos
** [[File:iUS.png|Em Inglês|20px]] [[:Category:Resource|Catálogo de Recursos]]
** [[File:iUS.png|Em Inglês|20px]] [[Meta.xml|O arquivo meta.xml]] - Dentro de cada recurso, há um arquivo chamado meta o indentificando
** [[File:iUS.png|Em Inglês|20px]] [[ACL]] - Access Control List, isto é importantíssimo para scripts complexos funcionarem
* [[File:iUS.png|Em Inglês|20px]] [[Writing_Gamemodes|Programando um modo de Jogo]]
* [[File:iUS.png|Em Inglês|20px]] [[Useful_Functions|Funções úteis]]
<div style="float:right; width: 32px;">[[File:start-here.png|link=]]</div>
<h3>Ajuda geral em Lua</h3>
Páginas criadas para ajudar à entender o Lua
* [[Image:iBR.png|Em Português|20px]] [http://www.lua.org/portugues.html Introdução a linguagem Lua]
* [[Image:iBR.png|Em Português|20px]] [http://www.lua.org/manual/5.1/pt/ Manual "Programando em Lua"]
* [[File:iUS.png|Em Inglês|20px]] [http://lua-users.org/wiki/TutorialDirectory Lua Wiki em inglês]
* [[File:iUS.png|Em Inglês|20px]] [http://nixstaller.berlios.de/manual/0.2/nixstaller_9.html Um Guia geral de 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>Referência</h3>
* [[File:iUS.png|Em Inglês|20px]] [[Client Scripting Functions|Funções do Cliente]]
* [[File:iUS.png|Em Inglês|20px]] [[Client Scripting Events|Eventos do Cliente]]
* [[File:iUS.png|Em Inglês|20px]] [[Server Scripting Functions|Funções do Servidor]]
* [[File:iUS.png|Em Inglês|20px]] [[Server Scripting Events|Eventos do Servidor]]

* [[File:iUS.png|Em Inglês|20px]] [[MTA Classes]] - Descrições detalhadas de todos os tipos de coisas que o MTA usa
** [[File:iUS.png|Em Inglês|20px]] [[Element|Elementos do MTA]] / [[Element tree|Hierarquia dos Elementos]]
</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>[[Id|Lista de ID's]]</h3>
*[[Animations|Animações]]
*[[Character Skins|Skins de Pedestres]]
*[[CJ_Clothes|Roupas do CJ]]
*[[Garage|Garagens]]
*[[Interior IDs|Interiores]]
*[[Material IDs|Materiais]]
*[[Projectiles|Projéteis]]
*[[Radar Blips|Ponteiros do Radar]]
*[[Sounds|Efeitos Sonoros]]
*[[Vehicle IDs|Veículos]]
*[[Vehicle Colors|Cores para Veículos]]
*[[Vehicle Upgrades|Asessórios para Veículos]]
*[[Vehicle variants|Vehicle Variants]]
*[[Weapons|Armas]]
*[[Weather|Climas]]
</div>

<div style="border: 1px dotted #D8D8D8; padding:4px 8px 8px 8px; margin:10px;">
<div style="float:right; width: 32px;">[[File:pBR.png|32px]]</div>

<h3>Sobre a Tradução</h3>
* Tradutores:
** <span style="color: blue">RaceXtreme</span>
** <span style="color: blue">StanleySathler</span>
É importante que todos colaborem para que nossa página em português fique melhor a cada dia!

[[File:Osi symbol.png|75px|link=http://opensource.org/]]
'''Multi Theft Auto''' é um projeto '''Open Source'''. <br>
Isso significa que todos nós podemos contribuir para fazer um Multi Theft Auto muito melhor!
</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>'''Sobre Multi Theft Auto'''</li>
<li>[[Archive|Museu]]</li>
<li>[[Press Coverage|Eventos]]</li>
<li>[http://code.google.com/p/mtasa-blue/people/list Desenvolvedores]</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|Solução de Problemas]]</li>
</ul>
<ul style="list-style: none; width: 200px; float: left;">
<li>'''Status do Wiki'''</li>
<li>{{NUMBEROFARTICLES}} Artigos</li>
<li>{{NUMBEROFPAGES}} Páginas</li>
<li>{{NUMBEROFUSERS}} Usuários Registrados</li>
</ul>
</div>
|}

__NOTOC__
__NOEDITSECTION__
{{Languages list|pt-br}}

PT-BR/Manual do Servidor

2012-05-20T20:50:03Z

Stanley Sathler .: /* Instalando o servidor */

[[PT-BR/Manual_do_Servidor]]
==Introdução==
Configurar um servidor e disponibilizá-lo para que seus amigos joguem via Internet ou LAN é mais fácil do que parece. Neste artigo estaremos abordando os passos iniciais para que você possa criar o seu próprio servidor para o MTA.

==Instalando o servidor==
A primeira parte consiste na instalação do servidor. Abaixo há dois tópicos, abordando a instalação em plataformas Linux e Windows, respectivamente.

===Instalando no Linux===
Há diversas maneiras de instalar, configurar e iniciar um servidor no Linux:
* [[Image:iUS.png|Em Inglês|20px]] [[Building MTASA Server on GNU Linux|Configurando um Servidor de MTASA no GNU Linux (Em Inglês)]]
* [[Image:iUS.png|Em Inglês|20px]] [http://linux.mtasa.com Baixando o servidor para Linux]

===Instalando no Windows===
Instalar um servidor do MTA:SA no Windows é bem simples:
:*Vá para [http://mtasa.com/ página de download] do MTA:SA e baixe o instalador.
:*Após o término do download, execute o arquivo.
:*Clique em Next e depois em "I Agree".
:*Nesta etapa você pode selecionar os componentes que deseja ou não instalar:
:**Para instalar somente o servidor, mude a opção "Client and Server" para "Server Only"
:**Next para continuar.
:*Selecione a pasta na qual deseja instalar o servidor. Em seguida, Next.
:*Clique em Install.
:*Pronto!

''Qual a função do arquivo acl.xml (access control list)? Para saber mais, leia o artigo em:
* [[Image:iUS.png|Em Inglês|20px]] [[Access_Control_List|Access Control List]]''

==Configurando o servidor==
O servidor dedicado do Multi Theft Auto pode ser configurado através...

*De uma espécie de prompt de comando chamado '''console''', ou seja, um programa onde comandos não são enviados através de cliques, mas sim através de linhas digitadas pelo usuario.
** Esse programa está localizado em "MTA San Andreas 1.3\server\MTA Server.exe".
** Ele é identico a janela ''cmd'' do windows.
** Enquanto este estiver execultando, o servidor vai permanecer online, caso contrário, o servidor sai do ar.
*'''Do prório jogo'''!
**Os comandos para configurar o servidor são enviados a partir do chat.
** Para que estes comandos sejam efetivamente enviados, é necessário o uso da "/" antes do comando em si, pois esta identifica que o que vem logo em seguida faz parte de um comando.. Exemplo "/addaccount".
*'''De um navegador de internet'''. Um website pode receber informações e configurar um servidor de MTA.

''Para que possa configurar um servidor do MTASA no jogo ou via website é necessário que pelomenos uma conta com privilégios de administrador seja adicionada no '''acl.xml'''.''

===Configuração Geral===
Todas as configurações gerais podem ser encontradas no arquivo "[[Server_mtaserver.conf|'''mtaserver.conf''']]" localizado na pasta "mods/deathmatch/". Este arquivo pode ser visualizado em qualquer editor de texto.

Ele é bem simples e direto, toda variável tem uma [[Server_mtaserver.conf|descrição abordando o que esta faz e como usa-la]].

===Port forwarding===

Se você execulta um servidor em seu computador e há um roteador entre a internet e seu computador, então você tem que configurar 3 portas.
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.

Antes de mais nada, abra o arquivo localizado em "mods/deathmatch/[[Server_mtaserver.conf|'''mtaserver.conf''']]" e procure pelas linhas citadas a seguir:
First of all open the file 'mods/deathmatch/[[Server_mtaserver.conf|'''mtaserver.conf''']]' and search for the next lines:
<syntaxhighlight lang="xml">
<serverport>22004</serverport>
<httpport>22005</httpport>
</syntaxhighlight>

Estas portas são necessárias para que o servidor inicie corretamente. Explicaremos como configura-las mais adiante.
!Mas se primeiro desejas que o servidor apareça no navegador de internet, então precisaremos configurar mais uma porta chamada ASE.
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.
(um simples exemplo de como ligar e desligar a porta ASE):
(quick example for how to turn ASE on or off):
<syntaxhighlight lang="xml">
<ase>1</ase> 
</syntaxhighlight>

Agora vamos liberar essas portas em seu roteador. Caso todas as portas estejam abertas ou você possui um roteador sem firewall, esta etapa é desnecessária.
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.

Se você não sabe como port forwarding funciona em seu roteador, viste [http://portforward.com/ este site], procure pelo modelo de seu roteador e siga as instruções.
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.

Na maioria dos roteadores, há a opção de selecionar o tipo de porta: UDP ou TCP. A lista a seguir irá explicar qual porta é necessaria para o que:
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:

Porta principal do servidor: UDP
Main server port: UDP

Porta HTTP: TCP
HTTP Port: TCP

Porta ASE: UDP (esta é necessária caso deseje que o servidor apareça na lista de servidores do gamemonitor.com).
ASE Port: UDP (this is needed if you want your server to appear in the server list)

A porta ASE é simples para se obter:
The ASE port is also simple to get:

Porta ASE = Porta principal do servidor + 123
ASE port = Main server port + 123

Então se a porta de seu servidor for 22003, então a porta ASE será no caso 22126.
So, if you have the main server port set to 22003, then the ASE port will be 22126.

Boa Sorte!

''Na ultima versão do servidor, ao se digitar o comando "/[[Server_Commands#openports|openports]]", os status de todas as portas serão mostrados.''
''In the latest version of the server, you can check the port status by using the server command [[Server_Commands#openports|openports]].''

===Client Checks===
Todo jogador que entra em um servidor passa por várias "avaliações", também conhecido como "Client Checks" (em inglês).
Esse processo é necessário, principalmente, para previnir trapaças no jogo, as quais são feitas através de trainers e/ou modificações realizadas nos arquivos originais do GTA SA.
Toda essas "avaliações" são dividias em diversos parâmetros, os quais são configuráveis através do arquivo [[Server_mtaserver.conf|'''mtaserver.conf''']] localizado em "mods/deathmatch".
Destacamos 2 delas como exemplo:

* O parâmetro '''client-file''' ...
** habilita que um ou mais arquivos possam ser modificados no computador do jogador (exemplo: carmods.dat). Por padrão, o MTA não permite que nenhum arquivo da pasta "data" e "anim" do GTA SA seja modificado.
** pertênce a um grupo denominado Anti-Cheat, pois, por padrão, ele evita que um ou mais jogadores tenham vantagens sobre os outros. Todos os demais parâmetros que fazem parte desse grupo estão detalhados neste Guia [[Anti-cheat_guide|Anti-Cheat]].
* O parâmetro '''minclientversion'''...
** estabelece que todos os jogadores usem uma versão igual ou superior a estipulada (exemplo: 1.3.0).
** Aqueles que estiverem usando uma versão inferior serão automaticamente desconectados do servidor.<br/>

Cada parâmetro contido no arquivo [[Server_mtaserver.conf|'''mtaserver.conf''']] tem um valor atribuido a ele. O que faz que o servidor iginore ou aja de forma diferente ao relaziar essas avaliações em cada jogador.

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

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

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

You can actually add your user to any group you want. Each group is linked to an ACL ([[Access Control List]]). Each ACL contains a series of specific allowed or denied rights. These groups exist so different users can be assigned different rights. The ''Admin'' group points to the ''Admin'' ACL, which is empty (thus allowing all possible commands). The ''Everyone'' group points to the ''Default'' ACL that puts a series of restrictions on the available commands (to disallow regular players from using admin commands).
</li>
<li>
You're done! You can add as many administrators or users as you want this way, take a look at some of the other groups and ACLs for example. The ACL is also accessible through the [[Access_Control_List|Lua scripting engine]].<br>

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

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

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

# resourcebrowser
# resourcemanager
# webadmin
# webmap

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

==Useful Notes==

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

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

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

[[Category:Support]]

PT-BR/Manual do Servidor

2012-05-20T20:47:09Z

Stanley Sathler .: /* Introdução */

[[PT-BR/Manual_do_Servidor]]
==Introdução==
Configurar um servidor e disponibilizá-lo para que seus amigos joguem via Internet ou LAN é mais fácil do que parece. Neste artigo estaremos abordando os passos iniciais para que você possa criar o seu próprio servidor para o MTA.

==Instalando o servidor==
A parte mais simples é instalar o servidor. A seguir há dois tópicos, um ensinando a instalar no Linux e outro ensinando a instalar no Windows.

===Instalando no Linux===
Há diversas maneiras de instalar, configurar e iniciar um servidor no Linux:
* [[Image:iUS.png|Em Inglês|20px]] [[Building MTASA Server on GNU Linux|Configurando um Servidor de MTASA no GNU Linux (Em Inglês)]]
* [[Image:iUS.png|Em Inglês|20px]] [http://linux.mtasa.com Baixando o servidor para Linux]

===Instalando no Windows===
Instalar um servidor do MTA:SA no Windows é bem simples:
:*Vá para [http://mtasa.com/ página de download] do MTASA e baixe o instalador.
:*Quando o download estiver concluído, abra o arquivo.
:*Clique em Next e depois em "I Agree".
:*Nesta etapa você pode selecionar componentes os quais desejas ou não instalar:
:**Para instalar somente o servidor, mude a opção "Client and Server" para "Server Only"
:**Next para continuar.
:*Selecione a pasta a qual deseja instalar o servidor. Em seguida, Next.
:*Clique em Install.
:*Pronto!

''Qual a função do arquivo acl.xml (access control list)? Para saber mais, leia o artigo em:
* [[Image:iUS.png|Em Inglês|20px]] [[Access_Control_List|Access Control List]]''

==Configurando o servidor==
O servidor dedicado do Multi Theft Auto pode ser configurado através...

*De uma espécie de prompt de comando chamado '''console''', ou seja, um programa onde comandos não são enviados através de cliques, mas sim através de linhas digitadas pelo usuario.
** Esse programa está localizado em "MTA San Andreas 1.3\server\MTA Server.exe".
** Ele é identico a janela ''cmd'' do windows.
** Enquanto este estiver execultando, o servidor vai permanecer online, caso contrário, o servidor sai do ar.
*'''Do prório jogo'''!
**Os comandos para configurar o servidor são enviados a partir do chat.
** Para que estes comandos sejam efetivamente enviados, é necessário o uso da "/" antes do comando em si, pois esta identifica que o que vem logo em seguida faz parte de um comando.. Exemplo "/addaccount".
*'''De um navegador de internet'''. Um website pode receber informações e configurar um servidor de MTA.

''Para que possa configurar um servidor do MTASA no jogo ou via website é necessário que pelomenos uma conta com privilégios de administrador seja adicionada no '''acl.xml'''.''

===Configuração Geral===
Todas as configurações gerais podem ser encontradas no arquivo "[[Server_mtaserver.conf|'''mtaserver.conf''']]" localizado na pasta "mods/deathmatch/". Este arquivo pode ser visualizado em qualquer editor de texto.

Ele é bem simples e direto, toda variável tem uma [[Server_mtaserver.conf|descrição abordando o que esta faz e como usa-la]].

===Port forwarding===

Se você execulta um servidor em seu computador e há um roteador entre a internet e seu computador, então você tem que configurar 3 portas.
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.

Antes de mais nada, abra o arquivo localizado em "mods/deathmatch/[[Server_mtaserver.conf|'''mtaserver.conf''']]" e procure pelas linhas citadas a seguir:
First of all open the file 'mods/deathmatch/[[Server_mtaserver.conf|'''mtaserver.conf''']]' and search for the next lines:
<syntaxhighlight lang="xml">
<serverport>22004</serverport>
<httpport>22005</httpport>
</syntaxhighlight>

Estas portas são necessárias para que o servidor inicie corretamente. Explicaremos como configura-las mais adiante.
!Mas se primeiro desejas que o servidor apareça no navegador de internet, então precisaremos configurar mais uma porta chamada ASE.
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.
(um simples exemplo de como ligar e desligar a porta ASE):
(quick example for how to turn ASE on or off):
<syntaxhighlight lang="xml">
<ase>1</ase> 
</syntaxhighlight>

Agora vamos liberar essas portas em seu roteador. Caso todas as portas estejam abertas ou você possui um roteador sem firewall, esta etapa é desnecessária.
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.

Se você não sabe como port forwarding funciona em seu roteador, viste [http://portforward.com/ este site], procure pelo modelo de seu roteador e siga as instruções.
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.

Na maioria dos roteadores, há a opção de selecionar o tipo de porta: UDP ou TCP. A lista a seguir irá explicar qual porta é necessaria para o que:
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:

Porta principal do servidor: UDP
Main server port: UDP

Porta HTTP: TCP
HTTP Port: TCP

Porta ASE: UDP (esta é necessária caso deseje que o servidor apareça na lista de servidores do gamemonitor.com).
ASE Port: UDP (this is needed if you want your server to appear in the server list)

A porta ASE é simples para se obter:
The ASE port is also simple to get:

Porta ASE = Porta principal do servidor + 123
ASE port = Main server port + 123

Então se a porta de seu servidor for 22003, então a porta ASE será no caso 22126.
So, if you have the main server port set to 22003, then the ASE port will be 22126.

Boa Sorte!

''Na ultima versão do servidor, ao se digitar o comando "/[[Server_Commands#openports|openports]]", os status de todas as portas serão mostrados.''
''In the latest version of the server, you can check the port status by using the server command [[Server_Commands#openports|openports]].''

===Client Checks===
Todo jogador que entra em um servidor passa por várias "avaliações", também conhecido como "Client Checks" (em inglês).
Esse processo é necessário, principalmente, para previnir trapaças no jogo, as quais são feitas através de trainers e/ou modificações realizadas nos arquivos originais do GTA SA.
Toda essas "avaliações" são dividias em diversos parâmetros, os quais são configuráveis através do arquivo [[Server_mtaserver.conf|'''mtaserver.conf''']] localizado em "mods/deathmatch".
Destacamos 2 delas como exemplo:

* O parâmetro '''client-file''' ...
** habilita que um ou mais arquivos possam ser modificados no computador do jogador (exemplo: carmods.dat). Por padrão, o MTA não permite que nenhum arquivo da pasta "data" e "anim" do GTA SA seja modificado.
** pertênce a um grupo denominado Anti-Cheat, pois, por padrão, ele evita que um ou mais jogadores tenham vantagens sobre os outros. Todos os demais parâmetros que fazem parte desse grupo estão detalhados neste Guia [[Anti-cheat_guide|Anti-Cheat]].
* O parâmetro '''minclientversion'''...
** estabelece que todos os jogadores usem uma versão igual ou superior a estipulada (exemplo: 1.3.0).
** Aqueles que estiverem usando uma versão inferior serão automaticamente desconectados do servidor.<br/>

Cada parâmetro contido no arquivo [[Server_mtaserver.conf|'''mtaserver.conf''']] tem um valor atribuido a ele. O que faz que o servidor iginore ou aja de forma diferente ao relaziar essas avaliações em cada jogador.

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

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

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

You can actually add your user to any group you want. Each group is linked to an ACL ([[Access Control List]]). Each ACL contains a series of specific allowed or denied rights. These groups exist so different users can be assigned different rights. The ''Admin'' group points to the ''Admin'' ACL, which is empty (thus allowing all possible commands). The ''Everyone'' group points to the ''Default'' ACL that puts a series of restrictions on the available commands (to disallow regular players from using admin commands).
</li>
<li>
You're done! You can add as many administrators or users as you want this way, take a look at some of the other groups and ACLs for example. The ACL is also accessible through the [[Access_Control_List|Lua scripting engine]].<br>

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

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

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

# resourcebrowser
# resourcemanager
# webadmin
# webmap

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

==Useful Notes==

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

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

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

[[Category:Support]]

Character Skins

2012-05-20T15:07:02Z

Stanley Sathler .: /* Notes: */

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

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

==Notes:==
*12 pages: 266 total.

*IDs 3-8 (except 7) are non-functional

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

*Non-working IDs
3-6
8
42
65
74
86
119
149
208
239
265-273

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

[[it:Skin Personaggi]]
[[ru:Character Skins]]
[[es:Skins de Personajes]]

[[Category:ID Lists]]

PT-BR/Manual do Servidor

2012-05-20T04:53:00Z

Stanley Sathler .: /* Introducao */

[[PT-BR/Manual_do_Servidor]]
==Introdução==
Criar um servidor para o MTA é tão fácil quanto parece. Neste artigo estaremos abordando os passos iniciais para que você possa criar o seu próprio servidor para o MTA.

PT-BR/Manual do Servidor

2012-05-20T04:47:09Z

Stanley Sathler .: /* Dando os primeiros passos */

==Introdução==
Criar um servidor para o MTA é tão fácil quanto parece. Neste artigo estaremos abordando os passos iniciais para que você possa criar o seu próprio servidor para o MTA.

PT-BR/Manual do Servidor

2012-05-20T04:43:10Z

Stanley Sathler .: Dando os primeiros passos

==Dando os primeiros passos==
Criar um servidor para o MTA é tão fácil quanto parece. Neste artigo estaremos abordando os passos iniciais para que você possa criar o seu próprio servidor para o MTA.

PT-BR/Manual do Cliente

2012-05-19T22:35:24Z

Stanley Sathler .: /* Instalando o Multi Theft Auto */

==Introdução==
Multi Theft Auto: San Andreas é a ultima de uma série de modificações criadas por fãns que habilitam o modo multiplayer para a série Grand Theft Auto (somente a versão PC). Para as versões GTA3 e Vice City, há antigas versões do MTA disponíveis, as quais estão descritas em [[Archive|Arquivos]]. MTA:SA não tem vinculos com a Rockstar Games ou Take 2 Interactive.

==Antes de começar==
<div style="border: 1px solid black; background: #FFFF99; float: right; width: 200px; padding: 5px; margin: 5px; margin-right: 0px;">
'''Nota:''' Windows 8 (Developer Preview) não é uma versão do windows suportada no momento! [[http://forum.mtasa.com/viewtopic.php?p=371531#p371531 por eAi]]
</div>
Antes de instalar o Multi Theft Auto: San Andreas, assegure-se de que não haja modificações instaladas em seu GTA:SA, caso contrário, estas irão entrar em conflito com o MTA. Se deseja preservar suas modificações (também conhecidos como "mods"), instale o GTA: San Andreas novamente em uma outra pasta em seu disco rígido e em seguida, instale o MTA nesta nova pasta.

Certifique de que você esteja utilizando o '''Windows XP''', '''Windows Vista''', '''Windows Server 2003''' ou '''Windows 7''' como seu sistema operacional e que seu computador seja capaz de rodar o jogo no modo single player. Se seu jogo está rodando nos requisitos minimos, ele ficará ainda mais lento no MTA, pois este exige maor processamento de sua máquina.

<div style="border: 1px dotted black; background: #6E91FA; float: center; width: 1180px; padding: 10px; margin: 5px; margin-left: 10px;">
'''Vale Lembrar:''' MTA:SA só funcionará no GTA:SA v1.0. Se você comprou o jogo recentemente, é provável que ele seja uma versão mais nova. Para mais informações, clique [[Known_Issues_-_FAQ#Does_MTASA_work_with_v1.01_or_v2.00_of_GTA_San_Andreas.3F|aqui]] (Em Inglês)
</div>

Lembre-se de visitar a página de [[Known_Issues_-_FAQ|Solução de Problemas]] (Em Inglês) se algum problema lhe ocorrer ou junte-se à nós no IRC @ irc://irc.multitheftauto.com/mta (Em Inglês)

===Requisitos do Sistema===
Os requisitos mínimos para Multi Theft Auto: San Andreas são um pouco superiores aos requisitos mínimos do Grand Theft Auto: San Andreas.
* '''Processador:''' Intel Pentium 4 or AMD Athlon XP
* '''Memória RAM:''' 512MB
* '''Memória de Video:''' 64 MB
* '''Chipset de Video:''' nVidia GeForce 4 series ou ATI Radeon 8xxx series
* '''Versão DirectX:''' 9.0 (Placa de Som e Placa de Video terão que ser compatíveis)
* '''Espaço:''' 3.7 GB livres em disco (3.6 GB para a instalação econômica do Grand Theft Auto)
* Grand Theft Auto: San Andreas versão 1.0 (Americana ou Européia) sem nenhuma modificação
* Teclado e Mouse
* Conexão de Banda Larga (para melhor jogabilidade online)

*Recomendações:
**Para aproveitar ao máximo o que o MTA tem a lhe oferecer, sua placa de vídeo deve ser compatível com o Pixel Shader 2.0. nVidia GeForce FX Series ou superior, ATI Radeon 9xxx Series ou superior são placas de vídeo que dão conta do recado.
**É recomendado mais que 512MB de memória RAM para melhor performance no jogo

==Instalando o Multi Theft Auto==

# Se você ainda não baixou o instalador do MTA:SA, acesse a página de download [http://mtasa.com aqui].
# Após o término do download, execute o arquivo. Vá em Next, leia os Termos de Licença (Em Inglês) e clique em "I Agree" para continuar.
# Agora você terá que escolher quais componentes deseja incluir na instalação:
#* '''Game client:''' Programa que faz você se conectar aos servidores do MTA para participar de partidas online. (este coponente é obrigatório)
#* '''Dedicated Server:''' São os arquivos necessários para criar seu servidor a partir de seu computador.
#** Core resources: São os recursos mais importantes para que seu servidor funcione de forma adequada.
#** Optional resources: São os recursos mais famosos do MTA como "race" (corrida), "Team Deathmatch" (combate entre times)...
#** Editor: O famoso editor para criar seus próprios mapas para os gamemodes "race", "assault" e etc.
#* '''Development:''' Só instale este coponente se você vai desenvolver módulos para o MTA. (Necessário conhecimento em C++)
# Quando terminar de escolher os componentes clique em Next. Agora, escolha a pasta onde deseja instalar o MTA (Não é necessário ser na pasta de seu SA)
# Next novamente para avançar. Clique no botão Browse para escolher o diretório onde seu San Andreas está instalado. O diretório padrão é: '''C:\Arquivos de Programas\Rockstar Games\GTA San Andreas\'''.
# E por fim vá em Install. Quando a instalação estiver concluída, aparecerá uma opção para iniciar o MTA, marque ou desmarque à vontade.
# Após clickar em '''Finish''', o ícone estará disponível no "Meu Iniciar" e também na sua área de trabalho quando estiver afim de jogar.

==Rodando o Jogo==
# Inicie o Multi Theft Auto clicando no ícone localizado em seu Desktop ou no Meu Iniciar (Dentro da pasta '''MTA: San Andreas {{Current Version|full}}''')
# O GTA: San Andreas irá inicar após de ser carregado e você vai se deparar com o menu principal do MTA:SA. Aqui você encontrará algumas opções como:

{| border="0" align="center"

| width="188" |
[[Image:Server_Browser.jpg|280px]]
| width="380" |
<font size="-1" face="tahoma,helvetica,arial,sans-serif">'''Browse servers''' – disponibiliza uma lista com os servidores disponíveis para jogar. </font>

<br />
|-
| width="188" |
[[Image:Host_Game.jpg|280px]]
| width="380" |
<font size="-1" face="tahoma,helvetica,arial,sans-serif">'''Host game''' – inicia um servidor local. </font>

<br />
|-
| width="188" |
[[Image:Menu_Settings.JPG|280px]]
| width="380" |
<font size="-1" face="tahoma,helvetica,arial,sans-serif">'''Settings '''– aqui você pode mudar seu nome no jogo, customizar os comandos do teclado e ajustar o video.</font>

<br /><br />
|-
| width="188" |
[[Image:About_Menu.jpg|280px]]
| width="380" |
<font size="-1" face="tahoma,helvetica,arial,sans-serif">'''About '''– mostra os créditos com os contribuidores do projeto.</font>

<br />
|-
| width="188" |
[[Image:Map_Editor.jpg|280px]]
| width="380" |
<font size="-1" face="tahoma,helvetica,arial,sans-serif">'''Map editor '''– aqui você pode criar seus próprios mapas, posicionando checkpoints, rampas, pickups e outros objetos. Estes mapas podem ser enviados à um servidor para que jogadores possam jogar uns contra os outros.</font>

<br /><br />
|-
| width="188" |
<br>
| width="380" |
<font size="-1" face="tahoma,helvetica,arial,sans-serif">'''Quit '''– faz você sair do jogo e retornar à sua área de trabalho.</font>

<br /><br />
|}

O caminho mais simples para se jogar é clicando em '''Browse Servers''' no menu. Se depois de um tempo nenhuma lista apareceu, clique no botão '''Refresh''' e o MTA irá procurar por servidores disponíveis, disponibilizando-os na tela.

<center>[[Image:BR_Client_Browser.jpg|600px]]</center>

* Na coluna '''Name''' estão os nomes dos servidores.
* Na coluna '''Players''' é mostrado o número de jogadores que estão conectados ao servidor e sua capacidade máxima no formato [Jogadores Conectados] / [Capacidade Máxima].
* A coluna '''Ping''' é o intervalo de tempo para que seu computador e o servidor se comuniquem. O valor é baseado no tempo que leva para que "pacotes" de dados sejam recebidos pelo servidor após serem enviados para seu pc. Então um ping maior indica que você terá travamentos em um servidor específico. No geral, servidores mais próximos de você são os que tem os menores pings.
**Ping é a mesma coisa do servidor te fazer perguntas e seu computador responder. Para que todas essas mensagens sejam entregues demora um certo intervalo de tempo. Se o servidor estiver no japão, com certeza seu ping será maior.
* A coluna '''Host''' é o enderesso de IP do servidor. Você pode usar este endereço no futuro para se conectar ao mesmo servidor via Quick Connect no menu principal.

Toda coluna pode ser clicada para organizar-la na ordem crescente ou decrescente. Exemplo: Clicando em cima da palavra '''Name''' obteremos os servidores começando com Z e terminando com A.

Para melhor experiência ao jogar, encontre um bom equilibrio entre jogadores e ping. Se o servidor tem muitos jogadores conectados você terá que ter um ping baixo e virse-versa.

Quando escolher um servidor, selecione-o e clique no botão '''Connect''' localizado no canto direito da janela. Se tudo der certo, vais se conectar ao servidor e automaticamente entrará no jogo.

==Como Jogar==

MTA:SA oferece um sistema que habilita os criadores de mapas manipularem vários elementos do GTA, resultando num modo de jogo totalmente inovador. O MTA utiliza vários aspectos do jogo normal (single player) mas há algumas pequenas diferenças:

Não há pedestres ou carros andando na rua. As únicas pessoas no mapa são seus oponentes ou aliados (se o jogo for do modo cooperativo). Ao precionar '''T''' no teclado, você pode falar com os outros jogadores usando o chat localizado no canto superior esquerdo da tela. Para falar somente com os membros de seu time, precione '''Y'''.

O Editor de mapas do MTA permite que usuários adicionem vários objetos do GTA em seus mapas incluindo ruas, barris explosíveis, rampas, prédios, colinas e muito mais. E não é só isso, objetos podem se mover, mudarem de aparência e desaparecerem por meio de scripts. Isso torna o mundo mais vivo, trás diversão garantida e infinitas formas de jogar.

Ao pressionar a tecla Tab vais aparecer um scoreboard. O scoreboard disponibiliza os nomes dos jogadores e seus respectivos pings por padrão. Mas scripts podem adicionar mais colunas à tabela dependendo das necessidades de cada modo de jogo. Por exemplo, o modo deathmath (mata-mata) vai, com certeza, precisar de uma coluna listando quantos assasinatos um certo jogador fez. Além disso há possibilidade de customizar mais ainda ao adicionar, por exemplo, uma coluna para o número de mortes que você tem ou à quanto tempo você jogou dependendo das necessidades de cada modo de jogo. Isso também depende totalmente de que o seu servidor necessita e de seu bom gosto, é claro.

==Comandos==

===do Jogador===

* F8 (ou a tecla Tilde) - Abre o Console
* F9 - Abre uma tela fornecendo o manual de como jogar. Isto varia de servidor para servidor.
* F11 - Mostra o mapa de San Andreas ''(a lista seguinte é para quando o mapa estiver visível)''
**numpad +/- - Lupa (Aumenta ou Diminui)
**numpad 2, 4, 6, 8 - move o mapa para baixo, esquerda, direita e cima, respectivamente.
**numpad 0 - alterna entre seguir o jogador (o mapa segue a localização do jogador no mapa) e modo livre (o mapa fica parado)
* F12 - Screenshot (tira uma foto da tela)
* T - Chat
* Y - Chat do time
* TAB - Abre uma lista contendo todos os jogadores conectados (Somente se o recurso [[Scoreboard]] estiver rodando no servidor)

===do Console===

O '''Console''' é uma janela a qual te habilita a obter informações, sair do jogo e desconectar de um servidor de uma maneira fácil e mais rápida.

<center>[[Image:BR_Client_Console.jpg|600px]]</center>

Precione '''~ (tilde)''' ou '''F8''' para acessar o '''Console'''. Digite um comando da lista abaixo com seus respectivos parâmetros (se requisitar) e precione Enter.

;'''maps''' :Disponibiliza uma lista com todos os mapas disponíveis no servidor.

;'''nick [seu nome]''' :Muda seu nome (nickname) para o qual você digitou no parâmetro.
> Exemplo - nick Cebolinha

;'''msg [nome] [mensagem]''' ou '''pm [nome] [mensagem]''' :Este manda uma mensagem somente para a pessoa a qual você especificou no parâmetro [nome]. Somente esta pessoa verá a mensagem. Ambos '''msg''' e '''pm''' podem ser utilizados.
> Exemplo - msg Cascão vamos atormentar a Mônica!

;'''quit''' ou '''exit''' :Disconecta do servidor e retorna para área de trabalho do Windows. Ambos fazem o mesmo que o "Quit" no menu principal.

;'''ver''' :Mostra a versão e os direitos autorais para este software(programa).

;'''sver''' :Mostra a versão do servidor que está conectado(a) no momento.

;'''time''' :Mostra a hora atual.

;'''disconnect''' :Disconecta do servidor e volta para o menu principal.

;'''say [texo]''' :Fale com os jogadores do chat enquanto o console está aberto.

;'''ignore [nome]''' :Simplesmente vais ignorar o jogador que desejas, ou seja, ele não vai mais te incomodar. Para voltar à receber mensagens deste jogador, digite '''ignore [nickname]''' novamente.
> Exemplo - como a Mônica não quer ser incomodada digitará: ignore Cebolinha

<div style="border: 1px dotted black; background: #6E91FA; float: center; width: 750px; padding: 5px; margin: 5px; margin-left: 10px;">
'''Dica:''' ''Podes usar estes comandos listados acima enquanto estiver no chat, botando uma "/" na frente. Exemplo: /time''
</div>

*A aba '''Binds''', no menu "settings", muda todos os controles do GTA e do MTA já pré-programados, como a tecla W para andar pra frente/acelerar ou a tecla T para falar no chat respectivamente.
*Ao digitar '''help''' no console, uma lista com todos os comandos pode ser visualizada.
*Os recursos que estão sendo execultado no momento podem também conter comandos novos. Ao digitar '''commands''' no console eles serão mostrados, se existirem.

==Códigos de Erros e seus significados==
'''Erros de Download'''<br>
0: UNKNOWN_ERROR<br>
1: INVALID_FILE_DESCRIPTORS<br>
2: INVALID_MAX_FILE_DESCRIPTOR<br>
3: INVALID_SELECT_RETURN<br>
4: INVALID_INITIAL_MULTI_PERFORM<br>
5: INVALID_MULTI_PERFORM_CODE<br>
6: INVALID_MULTI_PERFORM_CODE_NEW_DOWNLOADS<br>
7: UNEXPECTED_CURL_MESSAGE<br>
8: UNABLE_TO_CONNECT<br>
9: UNABLE_TO_DOWNLOAD_FILE<br>
10: FAILED_TO_INITIALIZE_DOWNLOAD<br>

'''Erros Fatais'''<br>
1: no local player model on ingame event<br>
2: no local player on ingame event<br>
3: server downloads disabled<br>
4: no local player model on player-list packet<br>
5: no local player on player-list packet<br>
6: invalid custom data length on entity-add packet<br>
7: invalid bitstream data on entity-add packet<br>
8: system entity on entity-add packet<br>
9: failed to create object on entity-add packet<br>
10: failed to create pickup on entity-add packet<br>
11: failed to create vehicle on entity-add packet<br>
12: invalid team-name length on entity-add packet<br>
13: invalid lua-event name length in lua-event packet<br>
14: invalid resource name length in resource-start packet<br>

'''Erros ao entrar no veículo'''<br>
1: script cancelled<br>
2: script cancelled (jack)<br>
3: current occupier is entering/exiting<br>
4: invalid seat<br>
5: not close enough<br>
6: already in a vehicle<br>
7: already entering/exiting<br>
8: invalid vehicle (trailer)<br>

==Jogando MTA no Linux==
Se o sistema operacional que você está usando for o Linux, siga o [[Client_on_Linux_Manual|Manual do Cliente - Linux]] para jogar MTA: San Andreas em seu computador!

[[es:Manual Cliente Deathmatch]]
[[de:MTA DM Client Anleitung]]
[[it:Manuale del Client]]
[[nl:Deathmatch Client Manual]]
[[ru:Deathmatch Client Manual]]

[[Category:Support]]

PT-BR/Manual do Cliente

2012-05-19T22:32:52Z

Stanley Sathler .: /* Antes de começar */

==Introdução==
Multi Theft Auto: San Andreas é a ultima de uma série de modificações criadas por fãns que habilitam o modo multiplayer para a série Grand Theft Auto (somente a versão PC). Para as versões GTA3 e Vice City, há antigas versões do MTA disponíveis, as quais estão descritas em [[Archive|Arquivos]]. MTA:SA não tem vinculos com a Rockstar Games ou Take 2 Interactive.

==Antes de começar==
<div style="border: 1px solid black; background: #FFFF99; float: right; width: 200px; padding: 5px; margin: 5px; margin-right: 0px;">
'''Nota:''' Windows 8 (Developer Preview) não é uma versão do windows suportada no momento! [[http://forum.mtasa.com/viewtopic.php?p=371531#p371531 por eAi]]
</div>
Antes de instalar o Multi Theft Auto: San Andreas, assegure-se de que não haja modificações instaladas em seu GTA:SA, caso contrário, estas irão entrar em conflito com o MTA. Se deseja preservar suas modificações (também conhecidos como "mods"), instale o GTA: San Andreas novamente em uma outra pasta em seu disco rígido e em seguida, instale o MTA nesta nova pasta.

Certifique de que você esteja utilizando o '''Windows XP''', '''Windows Vista''', '''Windows Server 2003''' ou '''Windows 7''' como seu sistema operacional e que seu computador seja capaz de rodar o jogo no modo single player. Se seu jogo está rodando nos requisitos minimos, ele ficará ainda mais lento no MTA, pois este exige maor processamento de sua máquina.

<div style="border: 1px dotted black; background: #6E91FA; float: center; width: 1180px; padding: 10px; margin: 5px; margin-left: 10px;">
'''Vale Lembrar:''' MTA:SA só funcionará no GTA:SA v1.0. Se você comprou o jogo recentemente, é provável que ele seja uma versão mais nova. Para mais informações, clique [[Known_Issues_-_FAQ#Does_MTASA_work_with_v1.01_or_v2.00_of_GTA_San_Andreas.3F|aqui]] (Em Inglês)
</div>

Lembre-se de visitar a página de [[Known_Issues_-_FAQ|Solução de Problemas]] (Em Inglês) se algum problema lhe ocorrer ou junte-se à nós no IRC @ irc://irc.multitheftauto.com/mta (Em Inglês)

===Requisitos do Sistema===
Os requisitos mínimos para Multi Theft Auto: San Andreas são um pouco superiores aos requisitos mínimos do Grand Theft Auto: San Andreas.
* '''Processador:''' Intel Pentium 4 or AMD Athlon XP
* '''Memória RAM:''' 512MB
* '''Memória de Video:''' 64 MB
* '''Chipset de Video:''' nVidia GeForce 4 series ou ATI Radeon 8xxx series
* '''Versão DirectX:''' 9.0 (Placa de Som e Placa de Video terão que ser compatíveis)
* '''Espaço:''' 3.7 GB livres em disco (3.6 GB para a instalação econômica do Grand Theft Auto)
* Grand Theft Auto: San Andreas versão 1.0 (Americana ou Européia) sem nenhuma modificação
* Teclado e Mouse
* Conexão de Banda Larga (para melhor jogabilidade online)

*Recomendações:
**Para aproveitar ao máximo o que o MTA tem a lhe oferecer, sua placa de vídeo deve ser compatível com o Pixel Shader 2.0. nVidia GeForce FX Series ou superior, ATI Radeon 9xxx Series ou superior são placas de vídeo que dão conta do recado.
**É recomendado mais que 512MB de memória RAM para melhor performance no jogo

==Instalando o Multi Theft Auto==

# Se você ainda não baixou o instalador do MTA:SA, acesse a página de download [http://mtasa.com aqui].
# Após de baixar, abra o arquivo. Vá em Next, leia os Termos de Licença (Em Inglês) e clique em "I Agree" para continuar.
# Agora você terá que escolher quais componentes desejas incluir na instalação:
#* '''Game client:''' Programa que faz você se conectar a servidores do MTA para participar de partidas online. (este coponente é obrigatório)
#* '''Dedicated Server:''' São os arquivos necessários para criar seu servidor a partir de seu computador.
#** Core resources: São os recursos mais importantes para que seu server funcione de forma adequada.
#** Optional resources: São os recursos mais famosos do MTA como "race" (corrida), "Team Deathmatch" (combate entre times)...
#** Editor: O famoso editor para criar seus próprios mapas para os gamemodes "race", "assault" e etc.
#* '''Development:''' Só instale este coponente se você vai desenvolver módulos para o MTA. (Necessário conhecimento em C++)
# Quando terminar de escolher os componentes clique em Next. Agora, escolha a pasta onde deseja instalar o MTA (Não é necessário ser na pasta de seu SA)
# Next novamente para avançar. Clique no botão Browse para escolher o diretório onde seu San Andreas está instalado. O diretório padrão é: '''C:\Arquivos de Programas\Rockstar Games\GTA San Andreas\'''.
# E por fim vá em Install. Quando a instalação estiver concluída, aparecerá uma opção para iniciar o MTA, marque ou desmarque à vontade.
# Após clickar em '''Finish''', o ícone estará disponível no "Meu Iniciar" e também na sua área de trabalho quando estiver afim de jogar.

==Rodando o Jogo==
# Inicie o Multi Theft Auto clicando no ícone localizado em seu Desktop ou no Meu Iniciar (Dentro da pasta '''MTA: San Andreas {{Current Version|full}}''')
# O GTA: San Andreas irá inicar após de ser carregado e você vai se deparar com o menu principal do MTA:SA. Aqui você encontrará algumas opções como:

{| border="0" align="center"

| width="188" |
[[Image:Server_Browser.jpg|280px]]
| width="380" |
<font size="-1" face="tahoma,helvetica,arial,sans-serif">'''Browse servers''' – disponibiliza uma lista com os servidores disponíveis para jogar. </font>

<br />
|-
| width="188" |
[[Image:Host_Game.jpg|280px]]
| width="380" |
<font size="-1" face="tahoma,helvetica,arial,sans-serif">'''Host game''' – inicia um servidor local. </font>

<br />
|-
| width="188" |
[[Image:Menu_Settings.JPG|280px]]
| width="380" |
<font size="-1" face="tahoma,helvetica,arial,sans-serif">'''Settings '''– aqui você pode mudar seu nome no jogo, customizar os comandos do teclado e ajustar o video.</font>

<br /><br />
|-
| width="188" |
[[Image:About_Menu.jpg|280px]]
| width="380" |
<font size="-1" face="tahoma,helvetica,arial,sans-serif">'''About '''– mostra os créditos com os contribuidores do projeto.</font>

<br />
|-
| width="188" |
[[Image:Map_Editor.jpg|280px]]
| width="380" |
<font size="-1" face="tahoma,helvetica,arial,sans-serif">'''Map editor '''– aqui você pode criar seus próprios mapas, posicionando checkpoints, rampas, pickups e outros objetos. Estes mapas podem ser enviados à um servidor para que jogadores possam jogar uns contra os outros.</font>

<br /><br />
|-
| width="188" |
<br>
| width="380" |
<font size="-1" face="tahoma,helvetica,arial,sans-serif">'''Quit '''– faz você sair do jogo e retornar à sua área de trabalho.</font>

<br /><br />
|}

O caminho mais simples para se jogar é clicando em '''Browse Servers''' no menu. Se depois de um tempo nenhuma lista apareceu, clique no botão '''Refresh''' e o MTA irá procurar por servidores disponíveis, disponibilizando-os na tela.

<center>[[Image:BR_Client_Browser.jpg|600px]]</center>

* Na coluna '''Name''' estão os nomes dos servidores.
* Na coluna '''Players''' é mostrado o número de jogadores que estão conectados ao servidor e sua capacidade máxima no formato [Jogadores Conectados] / [Capacidade Máxima].
* A coluna '''Ping''' é o intervalo de tempo para que seu computador e o servidor se comuniquem. O valor é baseado no tempo que leva para que "pacotes" de dados sejam recebidos pelo servidor após serem enviados para seu pc. Então um ping maior indica que você terá travamentos em um servidor específico. No geral, servidores mais próximos de você são os que tem os menores pings.
**Ping é a mesma coisa do servidor te fazer perguntas e seu computador responder. Para que todas essas mensagens sejam entregues demora um certo intervalo de tempo. Se o servidor estiver no japão, com certeza seu ping será maior.
* A coluna '''Host''' é o enderesso de IP do servidor. Você pode usar este endereço no futuro para se conectar ao mesmo servidor via Quick Connect no menu principal.

Toda coluna pode ser clicada para organizar-la na ordem crescente ou decrescente. Exemplo: Clicando em cima da palavra '''Name''' obteremos os servidores começando com Z e terminando com A.

Para melhor experiência ao jogar, encontre um bom equilibrio entre jogadores e ping. Se o servidor tem muitos jogadores conectados você terá que ter um ping baixo e virse-versa.

Quando escolher um servidor, selecione-o e clique no botão '''Connect''' localizado no canto direito da janela. Se tudo der certo, vais se conectar ao servidor e automaticamente entrará no jogo.

==Como Jogar==

MTA:SA oferece um sistema que habilita os criadores de mapas manipularem vários elementos do GTA, resultando num modo de jogo totalmente inovador. O MTA utiliza vários aspectos do jogo normal (single player) mas há algumas pequenas diferenças:

Não há pedestres ou carros andando na rua. As únicas pessoas no mapa são seus oponentes ou aliados (se o jogo for do modo cooperativo). Ao precionar '''T''' no teclado, você pode falar com os outros jogadores usando o chat localizado no canto superior esquerdo da tela. Para falar somente com os membros de seu time, precione '''Y'''.

O Editor de mapas do MTA permite que usuários adicionem vários objetos do GTA em seus mapas incluindo ruas, barris explosíveis, rampas, prédios, colinas e muito mais. E não é só isso, objetos podem se mover, mudarem de aparência e desaparecerem por meio de scripts. Isso torna o mundo mais vivo, trás diversão garantida e infinitas formas de jogar.

Ao pressionar a tecla Tab vais aparecer um scoreboard. O scoreboard disponibiliza os nomes dos jogadores e seus respectivos pings por padrão. Mas scripts podem adicionar mais colunas à tabela dependendo das necessidades de cada modo de jogo. Por exemplo, o modo deathmath (mata-mata) vai, com certeza, precisar de uma coluna listando quantos assasinatos um certo jogador fez. Além disso há possibilidade de customizar mais ainda ao adicionar, por exemplo, uma coluna para o número de mortes que você tem ou à quanto tempo você jogou dependendo das necessidades de cada modo de jogo. Isso também depende totalmente de que o seu servidor necessita e de seu bom gosto, é claro.

==Comandos==

===do Jogador===

* F8 (ou a tecla Tilde) - Abre o Console
* F9 - Abre uma tela fornecendo o manual de como jogar. Isto varia de servidor para servidor.
* F11 - Mostra o mapa de San Andreas ''(a lista seguinte é para quando o mapa estiver visível)''
**numpad +/- - Lupa (Aumenta ou Diminui)
**numpad 2, 4, 6, 8 - move o mapa para baixo, esquerda, direita e cima, respectivamente.
**numpad 0 - alterna entre seguir o jogador (o mapa segue a localização do jogador no mapa) e modo livre (o mapa fica parado)
* F12 - Screenshot (tira uma foto da tela)
* T - Chat
* Y - Chat do time
* TAB - Abre uma lista contendo todos os jogadores conectados (Somente se o recurso [[Scoreboard]] estiver rodando no servidor)

===do Console===

O '''Console''' é uma janela a qual te habilita a obter informações, sair do jogo e desconectar de um servidor de uma maneira fácil e mais rápida.

<center>[[Image:BR_Client_Console.jpg|600px]]</center>

Precione '''~ (tilde)''' ou '''F8''' para acessar o '''Console'''. Digite um comando da lista abaixo com seus respectivos parâmetros (se requisitar) e precione Enter.

;'''maps''' :Disponibiliza uma lista com todos os mapas disponíveis no servidor.

;'''nick [seu nome]''' :Muda seu nome (nickname) para o qual você digitou no parâmetro.
> Exemplo - nick Cebolinha

;'''msg [nome] [mensagem]''' ou '''pm [nome] [mensagem]''' :Este manda uma mensagem somente para a pessoa a qual você especificou no parâmetro [nome]. Somente esta pessoa verá a mensagem. Ambos '''msg''' e '''pm''' podem ser utilizados.
> Exemplo - msg Cascão vamos atormentar a Mônica!

;'''quit''' ou '''exit''' :Disconecta do servidor e retorna para área de trabalho do Windows. Ambos fazem o mesmo que o "Quit" no menu principal.

;'''ver''' :Mostra a versão e os direitos autorais para este software(programa).

;'''sver''' :Mostra a versão do servidor que está conectado(a) no momento.

;'''time''' :Mostra a hora atual.

;'''disconnect''' :Disconecta do servidor e volta para o menu principal.

;'''say [texo]''' :Fale com os jogadores do chat enquanto o console está aberto.

;'''ignore [nome]''' :Simplesmente vais ignorar o jogador que desejas, ou seja, ele não vai mais te incomodar. Para voltar à receber mensagens deste jogador, digite '''ignore [nickname]''' novamente.
> Exemplo - como a Mônica não quer ser incomodada digitará: ignore Cebolinha

<div style="border: 1px dotted black; background: #6E91FA; float: center; width: 750px; padding: 5px; margin: 5px; margin-left: 10px;">
'''Dica:''' ''Podes usar estes comandos listados acima enquanto estiver no chat, botando uma "/" na frente. Exemplo: /time''
</div>

*A aba '''Binds''', no menu "settings", muda todos os controles do GTA e do MTA já pré-programados, como a tecla W para andar pra frente/acelerar ou a tecla T para falar no chat respectivamente.
*Ao digitar '''help''' no console, uma lista com todos os comandos pode ser visualizada.
*Os recursos que estão sendo execultado no momento podem também conter comandos novos. Ao digitar '''commands''' no console eles serão mostrados, se existirem.

==Códigos de Erros e seus significados==
'''Erros de Download'''<br>
0: UNKNOWN_ERROR<br>
1: INVALID_FILE_DESCRIPTORS<br>
2: INVALID_MAX_FILE_DESCRIPTOR<br>
3: INVALID_SELECT_RETURN<br>
4: INVALID_INITIAL_MULTI_PERFORM<br>
5: INVALID_MULTI_PERFORM_CODE<br>
6: INVALID_MULTI_PERFORM_CODE_NEW_DOWNLOADS<br>
7: UNEXPECTED_CURL_MESSAGE<br>
8: UNABLE_TO_CONNECT<br>
9: UNABLE_TO_DOWNLOAD_FILE<br>
10: FAILED_TO_INITIALIZE_DOWNLOAD<br>

'''Erros Fatais'''<br>
1: no local player model on ingame event<br>
2: no local player on ingame event<br>
3: server downloads disabled<br>
4: no local player model on player-list packet<br>
5: no local player on player-list packet<br>
6: invalid custom data length on entity-add packet<br>
7: invalid bitstream data on entity-add packet<br>
8: system entity on entity-add packet<br>
9: failed to create object on entity-add packet<br>
10: failed to create pickup on entity-add packet<br>
11: failed to create vehicle on entity-add packet<br>
12: invalid team-name length on entity-add packet<br>
13: invalid lua-event name length in lua-event packet<br>
14: invalid resource name length in resource-start packet<br>

'''Erros ao entrar no veículo'''<br>
1: script cancelled<br>
2: script cancelled (jack)<br>
3: current occupier is entering/exiting<br>
4: invalid seat<br>
5: not close enough<br>
6: already in a vehicle<br>
7: already entering/exiting<br>
8: invalid vehicle (trailer)<br>

==Jogando MTA no Linux==
Se o sistema operacional que você está usando for o Linux, siga o [[Client_on_Linux_Manual|Manual do Cliente - Linux]] para jogar MTA: San Andreas em seu computador!

[[es:Manual Cliente Deathmatch]]
[[de:MTA DM Client Anleitung]]
[[it:Manuale del Client]]
[[nl:Deathmatch Client Manual]]
[[ru:Deathmatch Client Manual]]

[[Category:Support]]

Client Manual

2012-05-19T21:18:34Z

Stanley Sathler .: /* Introduction */

==Introduction==
Multi Theft Auto: San Andreas is the latest multiplayer modifications created by fans for Grand Theft Auto games (only for PC). If you are searching by GTA3 and Vice City versions, go to [[Archive]]. The Multi Theft Auto is not endorsed by Rockstar Games or Take 2 Interactive.

==Before you start==
{{Note_box|Windows 8 (Developer/Consumer Preview) is not supported at this time! [[http://forum.mtasa.com/viewtopic.php?p=371531#p371531 Note 1]][[http://forum.mtasa.com/viewtopic.php?f=104&t=37037 Note 2]]}}
Before you install Multi Theft Auto: San Andreas, first make sure that there are no modifications to GTA:SA installed. These will conflict with MTA. If you would like to keep your single player mods, you can create two installations by reinstalling San Andreas to a second folder on your hard drive.

Also make sure that you are running '''Windows XP''', '''Windows Vista''', '''Windows Server 2003''' or '''Windows 7''' and that your machine is capable of running the game in single player. Note that if you are running single player on the absolute minimum requirements, you will experience slowdowns in MTA as it takes up extra processing power.
{{Note|MTA:SA will only work on GTA:SA v1.0. If you bought the game recently, it is likely that you have a later version.''' [[Known_Issues_-_FAQ#Does_MTASA_work_with_v1.01_or_v2.00_of_GTA_San_Andreas.3F| More info]]}}

Make sure you head over to the [[Known_Issues_-_FAQ|Known Issues]] page if you have issues, or join us on IRC @ irc://irc.multitheftauto.com/mta

===System requirements===
The minimum system requirements for Multi Theft Auto: San Andreas are slightly higher than the original minimum requirements for Grand Theft Auto: San Andreas.
* Intel Pentium 4 or AMD Athlon XP
* 512MB DDR RAM
* Clean installation of Grand Theft Auto: San Andreas, version 1.0 (American or European)
* 3.7GB of free hard disk space (3.6GB for a minimum Grand Theft Auto installation)
* nVidia GeForce 4 series or ATI Radeon 8xxx series (64MB RAM and DirectX 9.0 compatible)
* DirectX 9.0 compatible sound card
* Keyboard and mouse
* Broadband internet access (for smooth online play)

For extra features, a pixel shader 2.0 compatible videocard (nVidia GeForce FX series or higher, ATI Radeon 9xxx series or higher) is recommended.

For extra loading performance, more RAM is recommended.

==Installing the game==

'''This section will need to be updated when we get an installer'''

# If you haven't already, download the MTA:SA client from the download page at mtasa.com.
# Run the installer. You will be asked which components to install:
#* '''Client''' interfaces with the game and is a required component.
#* '''MTA Server''' enables you to host your own home-brew server
#* '''MTA Server > Editor''' is used to create new maps, this is an optional component
# You are then asked for a folder in which to install the mod. This can by anywhere and doesn't have to be in you San Andreas directory.
# Next, you will be asked for the directory where you have San Andreas installed. The default location is: '''C:\Program Files\Rockstar Games\GTA San Andreas\'''.
# When the installation completes, you will be given the option to start MTA: San Andreas straight away. Choose your option and then press '''Finish'''.
# You will be able to launch MTA:DM from your Start Menu if you wish to play.

==Running the game==
# Start Multi Theft Auto by clicking the icon located in your Start Menu under '''MTA:San Andreas'''.
# GTA: San Andreas will start and once it is loaded, you will be presented with the MTA:SA main menu. Here you will find several options:

{| border="0" align="center"

| width="188" |
[[Image:Server_Browser.jpg|280px]]
| width="380" |
<font size="-1" face="tahoma,helvetica,arial,sans-serif">'''Browse servers''' – this allows you to receive a list of available servers to play on. </font>

<br />
|-
| width="188" |
[[Image:Host_Game.jpg|280px]]
| width="380" |
<font size="-1" face="tahoma,helvetica,arial,sans-serif">'''Host game''' – this allows you to start a local server. </font>

<br />
|-
| width="188" |
[[Image:Menu_Settings.JPG|280px]]
| width="380" |
<font size="-1" face="tahoma,helvetica,arial,sans-serif">'''Settings '''– this allows you to change your in-game nickname, customize controls and adjust display settings.</font>

<br /><br />
|-
| width="188" |
[[Image:About_Menu.jpg|280px]]
| width="380" |
<font size="-1" face="tahoma,helvetica,arial,sans-serif">'''About '''– this gives you a list of contributors to the project.</font>

<br />
|-
| width="188" |
[[Image:Map_Editor.jpg|280px]]
| width="380" |
<font size="-1" face="tahoma,helvetica,arial,sans-serif">'''Map editor '''– this allows you to create your own maps, complete with checkpoints, ramps, pickups and other objects. These can then be uploaded onto a server so that you can play them with other people.</font>

<br /><br />
|-
| width="188" |
<br>
| width="380" |
<font size="-1" face="tahoma,helvetica,arial,sans-serif">'''Quit '''– this returns you back to your Windows desktop.</font>

<br /><br />
|}

The easiest way to play the game is to click '''Browse Servers''' on the menu. If servers have not appeared already, press the '''Refresh''' button and MTA will scan for servers, displaying them as a list.

* Under the '''Name''' tab, each server's name is displayed.
* Under the '''Players''' tab, the number of players and the maximum capacity of the server is displayed, in the format of [Used Slots] / [Maximum Slots].
* The '''Ping''' tab displays the ping, or latency, between your machine and the server. Ping is a measure of the time it takes for "packets" of data to be received back from the server after sending them, so a higher ping means that you will experience more lag on that particular server. Generally, servers closest to your location should have the lowest pings.
* The '''Host''' is the IP address of the server. You can use this address in future to connect to the same server via the Quick Connect option on the main menu.

Each tab can be clicked to arrange the respective column in ascending or descending order.

For optimal performance and gameplay, look for the best balance between players and ping.

Once you have picked a server, select it and click the '''Connect''' button in the top right-hand corner of the dialog. If all goes well, you should connect to the server and automatically join the game.

==How to Play==

MTA:SA offers a comprehensive scripting system that allows map creators to customize many elements of the game in order to create their own innovative game modes. The game incorporates as many single player elements as possible but some aspects are different.

There are no pedestrians and no AI traffic on the road. The only other people on the map are your opponents, or allies if it is a team game. You can talk with them using the chatbox located in the left-hand corner of the screen by pressing '''T'''. To chat only to your team members, press '''Y'''.

MTA's map editor allows map creators to add various GTA objects to their maps including roads, exploding barrels, ramps, buildings, hills and more. Not only this, but the objects can be scripted to move, change model and disappear. This offers a great deal of fun and variation to the gameplay.

Holding Tab will display the scoreboard. By default, only names and pings are displayed, but scripts can add extra columns that are specific to the particular gamemode being played. For example, a deathmatch game mode would definitely have a column listing total kills, but the map creator may choose to add extra columns for the number of deaths you have and how long you have been playing for, in order to put your score into perspective.

==Controls==

===In-Game Keys===

* F8 (or Tilde Key) - Console
* F9 - In-game help
* F11 - Show SA map ''(the following list is for use when the map is up)''
**numpad /- - Zoom in and out
**numpad 4, 8, 6, 2 - move map left, up, right, down
**numpad 0 - toggle between attach to local player (map follows player blip) and free move (map stays stationary)
* F12 - Take a screenshot
* T - Chat
* Y - Team Chat
* TAB - Player List (if [[Scoreboard]] resource is running on the server)

==Console Commands==

'''bind defaults''' Binds control defaults in the settings menu

Press '''~ (tilde)''' or '''F8''' to access the console, then type a command followed by any neccessary parameters (if applicable) then press Enter.

;'''maps''' :This displays a list of all maps available on the server.

;'''nick [nickname]''' :This changes your nickname whilst in-game to whatever you specify in the parameters.

;'''msg [nickname] [message]''' or '''pm [nickname] [message]''' :This sends a private message to the person you specify in the [nickname] parameter. Only the person you specify can see the message. Both '''msg''' and '''pm''' perform the same function.

;'''quit''' or '''exit''' :This disconnects you from the server and returns you to the Windows desktop. Performs the same function as the Quit button on the main menu.

;'''ver''' :This displays the version number and copyright information for the software.

;'''sver''' :This displays the version number of the server you are connected to.

;'''time''' :This displays the current time.

;'''disconnect''' :This disconnects you from the server and returns you to the main menu.

;'''say [text]''' :This enables you to continue talking to people in the chat box whilst the console is open.

;'''ignore [nickname]''' :This will not display any text typed by the player you wish to ignore. To stop ignoring a player, type '''ignore [nickname]''' again.
{{Tip|You can use these commands in the chatbox by putting a / (forward slash) in front of them.}}

A list of console commands can be seen by typing '''help''' into the console and pressing Enter. The current map may also have extra commands which can be accessed by typing '''commands''' into the console.

For information on more commands see: [[Client Commands]]

==Error codes and their meanings==
'''Download errors'''<br>
0: UNKNOWN_ERROR<br>
1: INVALID_FILE_DESCRIPTORS<br>
2: INVALID_MAX_FILE_DESCRIPTOR<br>
3: INVALID_SELECT_RETURN<br>
4: INVALID_INITIAL_MULTI_PERFORM<br>
5: INVALID_MULTI_PERFORM_CODE<br>
6: INVALID_MULTI_PERFORM_CODE_NEW_DOWNLOADS<br>
7: UNEXPECTED_CURL_MESSAGE<br>
8: UNABLE_TO_CONNECT<br>
9: UNABLE_TO_DOWNLOAD_FILE<br>
10: FAILED_TO_INITIALIZE_DOWNLOAD<br>

'''Fatal errors'''<br>
1: no local player model on ingame event<br>
2: no local player on ingame event<br>
3: server downloads disabled<br>
4: no local player model on player-list packet<br>
5: no local player on player-list packet<br>
6: invalid custom data length on entity-add packet<br>
7: invalid bitstream data on entity-add packet<br>
8: system entity on entity-add packet<br>
9: failed to create object on entity-add packet<br>
10: failed to create pickup on entity-add packet<br>
11: failed to create vehicle on entity-add packet<br>
12: invalid team-name length on entity-add packet<br>
13: invalid lua-event name length in lua-event packet<br>
14: invalid resource name length in resource-start packet<br>

''''Unable to enter vehicle' errors'''<br>
1: script cancelled<br>
2: script cancelled (jack)<br>
3: current occupier is entering/exiting<br>
4: invalid seat<br>
5: not close enough<br>
6: already in a vehicle<br>
7: already entering/exiting<br>
8: invalid vehicle (trailer)<br>

==Special: Playing MTA on Linux?==
If you're one of those who have Linux as OS, and want to have the client working on Linux,
please read the [[Client_on_Linux_Manual|Client on Linux Manual]]

[[es:Manual Cliente Deathmatch]]
[[de:MTA DM Client Anleitung]]
[[it:Manuale del Client]]
[[nl:Deathmatch Client Manual]]
[[ru:Deathmatch Client Manual]]

[[Category:Support]]

Client Manual

2012-05-19T21:14:28Z

Stanley Sathler .: /* Introdução */

==Introdução==
Multi Theft Auto: San Andreas é o último de uma série de modificações multiplayer criadas por fãs para os jogos da série Grand Theft Auto (disponível somente para PC). Se deseja as versões para GTA3 e Vice City, vá em [[Archive]]. O Multi Theft Auto não é patrocinado pela Rockstar Games ou Take 2 Interactive.

==Before you start==
{{Note_box|Windows 8 (Developer/Consumer Preview) is not supported at this time! [[http://forum.mtasa.com/viewtopic.php?p=371531#p371531 Note 1]][[http://forum.mtasa.com/viewtopic.php?f=104&t=37037 Note 2]]}}
Before you install Multi Theft Auto: San Andreas, first make sure that there are no modifications to GTA:SA installed. These will conflict with MTA. If you would like to keep your single player mods, you can create two installations by reinstalling San Andreas to a second folder on your hard drive.

Also make sure that you are running '''Windows XP''', '''Windows Vista''', '''Windows Server 2003''' or '''Windows 7''' and that your machine is capable of running the game in single player. Note that if you are running single player on the absolute minimum requirements, you will experience slowdowns in MTA as it takes up extra processing power.
{{Note|MTA:SA will only work on GTA:SA v1.0. If you bought the game recently, it is likely that you have a later version.''' [[Known_Issues_-_FAQ#Does_MTASA_work_with_v1.01_or_v2.00_of_GTA_San_Andreas.3F| More info]]}}

Make sure you head over to the [[Known_Issues_-_FAQ|Known Issues]] page if you have issues, or join us on IRC @ irc://irc.multitheftauto.com/mta

===System requirements===
The minimum system requirements for Multi Theft Auto: San Andreas are slightly higher than the original minimum requirements for Grand Theft Auto: San Andreas.
* Intel Pentium 4 or AMD Athlon XP
* 512MB DDR RAM
* Clean installation of Grand Theft Auto: San Andreas, version 1.0 (American or European)
* 3.7GB of free hard disk space (3.6GB for a minimum Grand Theft Auto installation)
* nVidia GeForce 4 series or ATI Radeon 8xxx series (64MB RAM and DirectX 9.0 compatible)
* DirectX 9.0 compatible sound card
* Keyboard and mouse
* Broadband internet access (for smooth online play)

For extra features, a pixel shader 2.0 compatible videocard (nVidia GeForce FX series or higher, ATI Radeon 9xxx series or higher) is recommended.

For extra loading performance, more RAM is recommended.

==Installing the game==

'''This section will need to be updated when we get an installer'''

# If you haven't already, download the MTA:SA client from the download page at mtasa.com.
# Run the installer. You will be asked which components to install:
#* '''Client''' interfaces with the game and is a required component.
#* '''MTA Server''' enables you to host your own home-brew server
#* '''MTA Server > Editor''' is used to create new maps, this is an optional component
# You are then asked for a folder in which to install the mod. This can by anywhere and doesn't have to be in you San Andreas directory.
# Next, you will be asked for the directory where you have San Andreas installed. The default location is: '''C:\Program Files\Rockstar Games\GTA San Andreas\'''.
# When the installation completes, you will be given the option to start MTA: San Andreas straight away. Choose your option and then press '''Finish'''.
# You will be able to launch MTA:DM from your Start Menu if you wish to play.

==Running the game==
# Start Multi Theft Auto by clicking the icon located in your Start Menu under '''MTA:San Andreas'''.
# GTA: San Andreas will start and once it is loaded, you will be presented with the MTA:SA main menu. Here you will find several options:

{| border="0" align="center"

| width="188" |
[[Image:Server_Browser.jpg|280px]]
| width="380" |
<font size="-1" face="tahoma,helvetica,arial,sans-serif">'''Browse servers''' – this allows you to receive a list of available servers to play on. </font>

<br />
|-
| width="188" |
[[Image:Host_Game.jpg|280px]]
| width="380" |
<font size="-1" face="tahoma,helvetica,arial,sans-serif">'''Host game''' – this allows you to start a local server. </font>

<br />
|-
| width="188" |
[[Image:Menu_Settings.JPG|280px]]
| width="380" |
<font size="-1" face="tahoma,helvetica,arial,sans-serif">'''Settings '''– this allows you to change your in-game nickname, customize controls and adjust display settings.</font>

<br /><br />
|-
| width="188" |
[[Image:About_Menu.jpg|280px]]
| width="380" |
<font size="-1" face="tahoma,helvetica,arial,sans-serif">'''About '''– this gives you a list of contributors to the project.</font>

<br />
|-
| width="188" |
[[Image:Map_Editor.jpg|280px]]
| width="380" |
<font size="-1" face="tahoma,helvetica,arial,sans-serif">'''Map editor '''– this allows you to create your own maps, complete with checkpoints, ramps, pickups and other objects. These can then be uploaded onto a server so that you can play them with other people.</font>

<br /><br />
|-
| width="188" |
<br>
| width="380" |
<font size="-1" face="tahoma,helvetica,arial,sans-serif">'''Quit '''– this returns you back to your Windows desktop.</font>

<br /><br />
|}

The easiest way to play the game is to click '''Browse Servers''' on the menu. If servers have not appeared already, press the '''Refresh''' button and MTA will scan for servers, displaying them as a list.

* Under the '''Name''' tab, each server's name is displayed.
* Under the '''Players''' tab, the number of players and the maximum capacity of the server is displayed, in the format of [Used Slots] / [Maximum Slots].
* The '''Ping''' tab displays the ping, or latency, between your machine and the server. Ping is a measure of the time it takes for "packets" of data to be received back from the server after sending them, so a higher ping means that you will experience more lag on that particular server. Generally, servers closest to your location should have the lowest pings.
* The '''Host''' is the IP address of the server. You can use this address in future to connect to the same server via the Quick Connect option on the main menu.

Each tab can be clicked to arrange the respective column in ascending or descending order.

For optimal performance and gameplay, look for the best balance between players and ping.

Once you have picked a server, select it and click the '''Connect''' button in the top right-hand corner of the dialog. If all goes well, you should connect to the server and automatically join the game.

==How to Play==

MTA:SA offers a comprehensive scripting system that allows map creators to customize many elements of the game in order to create their own innovative game modes. The game incorporates as many single player elements as possible but some aspects are different.

There are no pedestrians and no AI traffic on the road. The only other people on the map are your opponents, or allies if it is a team game. You can talk with them using the chatbox located in the left-hand corner of the screen by pressing '''T'''. To chat only to your team members, press '''Y'''.

MTA's map editor allows map creators to add various GTA objects to their maps including roads, exploding barrels, ramps, buildings, hills and more. Not only this, but the objects can be scripted to move, change model and disappear. This offers a great deal of fun and variation to the gameplay.

Holding Tab will display the scoreboard. By default, only names and pings are displayed, but scripts can add extra columns that are specific to the particular gamemode being played. For example, a deathmatch game mode would definitely have a column listing total kills, but the map creator may choose to add extra columns for the number of deaths you have and how long you have been playing for, in order to put your score into perspective.

==Controls==

===In-Game Keys===

* F8 (or Tilde Key) - Console
* F9 - In-game help
* F11 - Show SA map ''(the following list is for use when the map is up)''
**numpad /- - Zoom in and out
**numpad 4, 8, 6, 2 - move map left, up, right, down
**numpad 0 - toggle between attach to local player (map follows player blip) and free move (map stays stationary)
* F12 - Take a screenshot
* T - Chat
* Y - Team Chat
* TAB - Player List (if [[Scoreboard]] resource is running on the server)

==Console Commands==

'''bind defaults''' Binds control defaults in the settings menu

Press '''~ (tilde)''' or '''F8''' to access the console, then type a command followed by any neccessary parameters (if applicable) then press Enter.

;'''maps''' :This displays a list of all maps available on the server.

;'''nick [nickname]''' :This changes your nickname whilst in-game to whatever you specify in the parameters.

;'''msg [nickname] [message]''' or '''pm [nickname] [message]''' :This sends a private message to the person you specify in the [nickname] parameter. Only the person you specify can see the message. Both '''msg''' and '''pm''' perform the same function.

;'''quit''' or '''exit''' :This disconnects you from the server and returns you to the Windows desktop. Performs the same function as the Quit button on the main menu.

;'''ver''' :This displays the version number and copyright information for the software.

;'''sver''' :This displays the version number of the server you are connected to.

;'''time''' :This displays the current time.

;'''disconnect''' :This disconnects you from the server and returns you to the main menu.

;'''say [text]''' :This enables you to continue talking to people in the chat box whilst the console is open.

;'''ignore [nickname]''' :This will not display any text typed by the player you wish to ignore. To stop ignoring a player, type '''ignore [nickname]''' again.
{{Tip|You can use these commands in the chatbox by putting a / (forward slash) in front of them.}}

A list of console commands can be seen by typing '''help''' into the console and pressing Enter. The current map may also have extra commands which can be accessed by typing '''commands''' into the console.

For information on more commands see: [[Client Commands]]

==Error codes and their meanings==
'''Download errors'''<br>
0: UNKNOWN_ERROR<br>
1: INVALID_FILE_DESCRIPTORS<br>
2: INVALID_MAX_FILE_DESCRIPTOR<br>
3: INVALID_SELECT_RETURN<br>
4: INVALID_INITIAL_MULTI_PERFORM<br>
5: INVALID_MULTI_PERFORM_CODE<br>
6: INVALID_MULTI_PERFORM_CODE_NEW_DOWNLOADS<br>
7: UNEXPECTED_CURL_MESSAGE<br>
8: UNABLE_TO_CONNECT<br>
9: UNABLE_TO_DOWNLOAD_FILE<br>
10: FAILED_TO_INITIALIZE_DOWNLOAD<br>

'''Fatal errors'''<br>
1: no local player model on ingame event<br>
2: no local player on ingame event<br>
3: server downloads disabled<br>
4: no local player model on player-list packet<br>
5: no local player on player-list packet<br>
6: invalid custom data length on entity-add packet<br>
7: invalid bitstream data on entity-add packet<br>
8: system entity on entity-add packet<br>
9: failed to create object on entity-add packet<br>
10: failed to create pickup on entity-add packet<br>
11: failed to create vehicle on entity-add packet<br>
12: invalid team-name length on entity-add packet<br>
13: invalid lua-event name length in lua-event packet<br>
14: invalid resource name length in resource-start packet<br>

''''Unable to enter vehicle' errors'''<br>
1: script cancelled<br>
2: script cancelled (jack)<br>
3: current occupier is entering/exiting<br>
4: invalid seat<br>
5: not close enough<br>
6: already in a vehicle<br>
7: already entering/exiting<br>
8: invalid vehicle (trailer)<br>

==Special: Playing MTA on Linux?==
If you're one of those who have Linux as OS, and want to have the client working on Linux,
please read the [[Client_on_Linux_Manual|Client on Linux Manual]]

[[es:Manual Cliente Deathmatch]]
[[de:MTA DM Client Anleitung]]
[[it:Manuale del Client]]
[[nl:Deathmatch Client Manual]]
[[ru:Deathmatch Client Manual]]

[[Category:Support]]

Client Manual

2012-05-19T21:14:06Z

Stanley Sathler .: /* Introdução */

==Introdução==
Multi Theft Auto: San Andreas é o último de uma série de modificações multiplayer criados por fãs para os jogos da série Grand Theft Auto (disponível somente para PC). Se deseja as versões para GTA3 e Vice City, vá em [[Archive]]. O Multi Theft Auto não é patrocinado pela Rockstar Games ou Take 2 Interactive.

==Before you start==
{{Note_box|Windows 8 (Developer/Consumer Preview) is not supported at this time! [[http://forum.mtasa.com/viewtopic.php?p=371531#p371531 Note 1]][[http://forum.mtasa.com/viewtopic.php?f=104&t=37037 Note 2]]}}
Before you install Multi Theft Auto: San Andreas, first make sure that there are no modifications to GTA:SA installed. These will conflict with MTA. If you would like to keep your single player mods, you can create two installations by reinstalling San Andreas to a second folder on your hard drive.

Also make sure that you are running '''Windows XP''', '''Windows Vista''', '''Windows Server 2003''' or '''Windows 7''' and that your machine is capable of running the game in single player. Note that if you are running single player on the absolute minimum requirements, you will experience slowdowns in MTA as it takes up extra processing power.
{{Note|MTA:SA will only work on GTA:SA v1.0. If you bought the game recently, it is likely that you have a later version.''' [[Known_Issues_-_FAQ#Does_MTASA_work_with_v1.01_or_v2.00_of_GTA_San_Andreas.3F| More info]]}}

Make sure you head over to the [[Known_Issues_-_FAQ|Known Issues]] page if you have issues, or join us on IRC @ irc://irc.multitheftauto.com/mta

===System requirements===
The minimum system requirements for Multi Theft Auto: San Andreas are slightly higher than the original minimum requirements for Grand Theft Auto: San Andreas.
* Intel Pentium 4 or AMD Athlon XP
* 512MB DDR RAM
* Clean installation of Grand Theft Auto: San Andreas, version 1.0 (American or European)
* 3.7GB of free hard disk space (3.6GB for a minimum Grand Theft Auto installation)
* nVidia GeForce 4 series or ATI Radeon 8xxx series (64MB RAM and DirectX 9.0 compatible)
* DirectX 9.0 compatible sound card
* Keyboard and mouse
* Broadband internet access (for smooth online play)

For extra features, a pixel shader 2.0 compatible videocard (nVidia GeForce FX series or higher, ATI Radeon 9xxx series or higher) is recommended.

For extra loading performance, more RAM is recommended.

==Installing the game==

'''This section will need to be updated when we get an installer'''

# If you haven't already, download the MTA:SA client from the download page at mtasa.com.
# Run the installer. You will be asked which components to install:
#* '''Client''' interfaces with the game and is a required component.
#* '''MTA Server''' enables you to host your own home-brew server
#* '''MTA Server > Editor''' is used to create new maps, this is an optional component
# You are then asked for a folder in which to install the mod. This can by anywhere and doesn't have to be in you San Andreas directory.
# Next, you will be asked for the directory where you have San Andreas installed. The default location is: '''C:\Program Files\Rockstar Games\GTA San Andreas\'''.
# When the installation completes, you will be given the option to start MTA: San Andreas straight away. Choose your option and then press '''Finish'''.
# You will be able to launch MTA:DM from your Start Menu if you wish to play.

==Running the game==
# Start Multi Theft Auto by clicking the icon located in your Start Menu under '''MTA:San Andreas'''.
# GTA: San Andreas will start and once it is loaded, you will be presented with the MTA:SA main menu. Here you will find several options:

{| border="0" align="center"

| width="188" |
[[Image:Server_Browser.jpg|280px]]
| width="380" |
<font size="-1" face="tahoma,helvetica,arial,sans-serif">'''Browse servers''' – this allows you to receive a list of available servers to play on. </font>

<br />
|-
| width="188" |
[[Image:Host_Game.jpg|280px]]
| width="380" |
<font size="-1" face="tahoma,helvetica,arial,sans-serif">'''Host game''' – this allows you to start a local server. </font>

<br />
|-
| width="188" |
[[Image:Menu_Settings.JPG|280px]]
| width="380" |
<font size="-1" face="tahoma,helvetica,arial,sans-serif">'''Settings '''– this allows you to change your in-game nickname, customize controls and adjust display settings.</font>

<br /><br />
|-
| width="188" |
[[Image:About_Menu.jpg|280px]]
| width="380" |
<font size="-1" face="tahoma,helvetica,arial,sans-serif">'''About '''– this gives you a list of contributors to the project.</font>

<br />
|-
| width="188" |
[[Image:Map_Editor.jpg|280px]]
| width="380" |
<font size="-1" face="tahoma,helvetica,arial,sans-serif">'''Map editor '''– this allows you to create your own maps, complete with checkpoints, ramps, pickups and other objects. These can then be uploaded onto a server so that you can play them with other people.</font>

<br /><br />
|-
| width="188" |
<br>
| width="380" |
<font size="-1" face="tahoma,helvetica,arial,sans-serif">'''Quit '''– this returns you back to your Windows desktop.</font>

<br /><br />
|}

The easiest way to play the game is to click '''Browse Servers''' on the menu. If servers have not appeared already, press the '''Refresh''' button and MTA will scan for servers, displaying them as a list.

* Under the '''Name''' tab, each server's name is displayed.
* Under the '''Players''' tab, the number of players and the maximum capacity of the server is displayed, in the format of [Used Slots] / [Maximum Slots].
* The '''Ping''' tab displays the ping, or latency, between your machine and the server. Ping is a measure of the time it takes for "packets" of data to be received back from the server after sending them, so a higher ping means that you will experience more lag on that particular server. Generally, servers closest to your location should have the lowest pings.
* The '''Host''' is the IP address of the server. You can use this address in future to connect to the same server via the Quick Connect option on the main menu.

Each tab can be clicked to arrange the respective column in ascending or descending order.

For optimal performance and gameplay, look for the best balance between players and ping.

Once you have picked a server, select it and click the '''Connect''' button in the top right-hand corner of the dialog. If all goes well, you should connect to the server and automatically join the game.

==How to Play==

MTA:SA offers a comprehensive scripting system that allows map creators to customize many elements of the game in order to create their own innovative game modes. The game incorporates as many single player elements as possible but some aspects are different.

There are no pedestrians and no AI traffic on the road. The only other people on the map are your opponents, or allies if it is a team game. You can talk with them using the chatbox located in the left-hand corner of the screen by pressing '''T'''. To chat only to your team members, press '''Y'''.

MTA's map editor allows map creators to add various GTA objects to their maps including roads, exploding barrels, ramps, buildings, hills and more. Not only this, but the objects can be scripted to move, change model and disappear. This offers a great deal of fun and variation to the gameplay.

Holding Tab will display the scoreboard. By default, only names and pings are displayed, but scripts can add extra columns that are specific to the particular gamemode being played. For example, a deathmatch game mode would definitely have a column listing total kills, but the map creator may choose to add extra columns for the number of deaths you have and how long you have been playing for, in order to put your score into perspective.

==Controls==

===In-Game Keys===

* F8 (or Tilde Key) - Console
* F9 - In-game help
* F11 - Show SA map ''(the following list is for use when the map is up)''
**numpad /- - Zoom in and out
**numpad 4, 8, 6, 2 - move map left, up, right, down
**numpad 0 - toggle between attach to local player (map follows player blip) and free move (map stays stationary)
* F12 - Take a screenshot
* T - Chat
* Y - Team Chat
* TAB - Player List (if [[Scoreboard]] resource is running on the server)

==Console Commands==

'''bind defaults''' Binds control defaults in the settings menu

Press '''~ (tilde)''' or '''F8''' to access the console, then type a command followed by any neccessary parameters (if applicable) then press Enter.

;'''maps''' :This displays a list of all maps available on the server.

;'''nick [nickname]''' :This changes your nickname whilst in-game to whatever you specify in the parameters.

;'''msg [nickname] [message]''' or '''pm [nickname] [message]''' :This sends a private message to the person you specify in the [nickname] parameter. Only the person you specify can see the message. Both '''msg''' and '''pm''' perform the same function.

;'''quit''' or '''exit''' :This disconnects you from the server and returns you to the Windows desktop. Performs the same function as the Quit button on the main menu.

;'''ver''' :This displays the version number and copyright information for the software.

;'''sver''' :This displays the version number of the server you are connected to.

;'''time''' :This displays the current time.

;'''disconnect''' :This disconnects you from the server and returns you to the main menu.

;'''say [text]''' :This enables you to continue talking to people in the chat box whilst the console is open.

;'''ignore [nickname]''' :This will not display any text typed by the player you wish to ignore. To stop ignoring a player, type '''ignore [nickname]''' again.
{{Tip|You can use these commands in the chatbox by putting a / (forward slash) in front of them.}}

A list of console commands can be seen by typing '''help''' into the console and pressing Enter. The current map may also have extra commands which can be accessed by typing '''commands''' into the console.

For information on more commands see: [[Client Commands]]

==Error codes and their meanings==
'''Download errors'''<br>
0: UNKNOWN_ERROR<br>
1: INVALID_FILE_DESCRIPTORS<br>
2: INVALID_MAX_FILE_DESCRIPTOR<br>
3: INVALID_SELECT_RETURN<br>
4: INVALID_INITIAL_MULTI_PERFORM<br>
5: INVALID_MULTI_PERFORM_CODE<br>
6: INVALID_MULTI_PERFORM_CODE_NEW_DOWNLOADS<br>
7: UNEXPECTED_CURL_MESSAGE<br>
8: UNABLE_TO_CONNECT<br>
9: UNABLE_TO_DOWNLOAD_FILE<br>
10: FAILED_TO_INITIALIZE_DOWNLOAD<br>

'''Fatal errors'''<br>
1: no local player model on ingame event<br>
2: no local player on ingame event<br>
3: server downloads disabled<br>
4: no local player model on player-list packet<br>
5: no local player on player-list packet<br>
6: invalid custom data length on entity-add packet<br>
7: invalid bitstream data on entity-add packet<br>
8: system entity on entity-add packet<br>
9: failed to create object on entity-add packet<br>
10: failed to create pickup on entity-add packet<br>
11: failed to create vehicle on entity-add packet<br>
12: invalid team-name length on entity-add packet<br>
13: invalid lua-event name length in lua-event packet<br>
14: invalid resource name length in resource-start packet<br>

''''Unable to enter vehicle' errors'''<br>
1: script cancelled<br>
2: script cancelled (jack)<br>
3: current occupier is entering/exiting<br>
4: invalid seat<br>
5: not close enough<br>
6: already in a vehicle<br>
7: already entering/exiting<br>
8: invalid vehicle (trailer)<br>

==Special: Playing MTA on Linux?==
If you're one of those who have Linux as OS, and want to have the client working on Linux,
please read the [[Client_on_Linux_Manual|Client on Linux Manual]]

[[es:Manual Cliente Deathmatch]]
[[de:MTA DM Client Anleitung]]
[[it:Manuale del Client]]
[[nl:Deathmatch Client Manual]]
[[ru:Deathmatch Client Manual]]

[[Category:Support]]

Client Manual

2012-05-19T21:13:15Z

Stanley Sathler .: /* Introdução */

==Introdução==
Multi Theft Auto: San Andreas is the latest in a series of fan-created multiplayer modifications for the Grand Theft Auto games (PC versions only). For the GTA3 and Vice City versions that run on the old core, go to the [[Archive]]. This mod is not endorsed by Rockstar Games or Take 2 Interactive.

Multi Theft Auto: San Andreas é o último de uma série de modificações multiplayer criados por fãs para os jogos da série Grand Theft Auto (disponível somente para PC). Se deseja as versões para GTA3 e Vice City, vá em [[Archive]]. O Multi Theft Auto não é patrocinado pela Rockstar Games ou Take 2 Interactive.

==Before you start==
{{Note_box|Windows 8 (Developer/Consumer Preview) is not supported at this time! [[http://forum.mtasa.com/viewtopic.php?p=371531#p371531 Note 1]][[http://forum.mtasa.com/viewtopic.php?f=104&t=37037 Note 2]]}}
Before you install Multi Theft Auto: San Andreas, first make sure that there are no modifications to GTA:SA installed. These will conflict with MTA. If you would like to keep your single player mods, you can create two installations by reinstalling San Andreas to a second folder on your hard drive.

Also make sure that you are running '''Windows XP''', '''Windows Vista''', '''Windows Server 2003''' or '''Windows 7''' and that your machine is capable of running the game in single player. Note that if you are running single player on the absolute minimum requirements, you will experience slowdowns in MTA as it takes up extra processing power.
{{Note|MTA:SA will only work on GTA:SA v1.0. If you bought the game recently, it is likely that you have a later version.''' [[Known_Issues_-_FAQ#Does_MTASA_work_with_v1.01_or_v2.00_of_GTA_San_Andreas.3F| More info]]}}

Make sure you head over to the [[Known_Issues_-_FAQ|Known Issues]] page if you have issues, or join us on IRC @ irc://irc.multitheftauto.com/mta

===System requirements===
The minimum system requirements for Multi Theft Auto: San Andreas are slightly higher than the original minimum requirements for Grand Theft Auto: San Andreas.
* Intel Pentium 4 or AMD Athlon XP
* 512MB DDR RAM
* Clean installation of Grand Theft Auto: San Andreas, version 1.0 (American or European)
* 3.7GB of free hard disk space (3.6GB for a minimum Grand Theft Auto installation)
* nVidia GeForce 4 series or ATI Radeon 8xxx series (64MB RAM and DirectX 9.0 compatible)
* DirectX 9.0 compatible sound card
* Keyboard and mouse
* Broadband internet access (for smooth online play)

For extra features, a pixel shader 2.0 compatible videocard (nVidia GeForce FX series or higher, ATI Radeon 9xxx series or higher) is recommended.

For extra loading performance, more RAM is recommended.

==Installing the game==

'''This section will need to be updated when we get an installer'''

# If you haven't already, download the MTA:SA client from the download page at mtasa.com.
# Run the installer. You will be asked which components to install:
#* '''Client''' interfaces with the game and is a required component.
#* '''MTA Server''' enables you to host your own home-brew server
#* '''MTA Server > Editor''' is used to create new maps, this is an optional component
# You are then asked for a folder in which to install the mod. This can by anywhere and doesn't have to be in you San Andreas directory.
# Next, you will be asked for the directory where you have San Andreas installed. The default location is: '''C:\Program Files\Rockstar Games\GTA San Andreas\'''.
# When the installation completes, you will be given the option to start MTA: San Andreas straight away. Choose your option and then press '''Finish'''.
# You will be able to launch MTA:DM from your Start Menu if you wish to play.

==Running the game==
# Start Multi Theft Auto by clicking the icon located in your Start Menu under '''MTA:San Andreas'''.
# GTA: San Andreas will start and once it is loaded, you will be presented with the MTA:SA main menu. Here you will find several options:

{| border="0" align="center"

| width="188" |
[[Image:Server_Browser.jpg|280px]]
| width="380" |
<font size="-1" face="tahoma,helvetica,arial,sans-serif">'''Browse servers''' – this allows you to receive a list of available servers to play on. </font>

<br />
|-
| width="188" |
[[Image:Host_Game.jpg|280px]]
| width="380" |
<font size="-1" face="tahoma,helvetica,arial,sans-serif">'''Host game''' – this allows you to start a local server. </font>

<br />
|-
| width="188" |
[[Image:Menu_Settings.JPG|280px]]
| width="380" |
<font size="-1" face="tahoma,helvetica,arial,sans-serif">'''Settings '''– this allows you to change your in-game nickname, customize controls and adjust display settings.</font>

<br /><br />
|-
| width="188" |
[[Image:About_Menu.jpg|280px]]
| width="380" |
<font size="-1" face="tahoma,helvetica,arial,sans-serif">'''About '''– this gives you a list of contributors to the project.</font>

<br />
|-
| width="188" |
[[Image:Map_Editor.jpg|280px]]
| width="380" |
<font size="-1" face="tahoma,helvetica,arial,sans-serif">'''Map editor '''– this allows you to create your own maps, complete with checkpoints, ramps, pickups and other objects. These can then be uploaded onto a server so that you can play them with other people.</font>

<br /><br />
|-
| width="188" |
<br>
| width="380" |
<font size="-1" face="tahoma,helvetica,arial,sans-serif">'''Quit '''– this returns you back to your Windows desktop.</font>

<br /><br />
|}

The easiest way to play the game is to click '''Browse Servers''' on the menu. If servers have not appeared already, press the '''Refresh''' button and MTA will scan for servers, displaying them as a list.

* Under the '''Name''' tab, each server's name is displayed.
* Under the '''Players''' tab, the number of players and the maximum capacity of the server is displayed, in the format of [Used Slots] / [Maximum Slots].
* The '''Ping''' tab displays the ping, or latency, between your machine and the server. Ping is a measure of the time it takes for "packets" of data to be received back from the server after sending them, so a higher ping means that you will experience more lag on that particular server. Generally, servers closest to your location should have the lowest pings.
* The '''Host''' is the IP address of the server. You can use this address in future to connect to the same server via the Quick Connect option on the main menu.

Each tab can be clicked to arrange the respective column in ascending or descending order.

For optimal performance and gameplay, look for the best balance between players and ping.

Once you have picked a server, select it and click the '''Connect''' button in the top right-hand corner of the dialog. If all goes well, you should connect to the server and automatically join the game.

==How to Play==

MTA:SA offers a comprehensive scripting system that allows map creators to customize many elements of the game in order to create their own innovative game modes. The game incorporates as many single player elements as possible but some aspects are different.

There are no pedestrians and no AI traffic on the road. The only other people on the map are your opponents, or allies if it is a team game. You can talk with them using the chatbox located in the left-hand corner of the screen by pressing '''T'''. To chat only to your team members, press '''Y'''.

MTA's map editor allows map creators to add various GTA objects to their maps including roads, exploding barrels, ramps, buildings, hills and more. Not only this, but the objects can be scripted to move, change model and disappear. This offers a great deal of fun and variation to the gameplay.

Holding Tab will display the scoreboard. By default, only names and pings are displayed, but scripts can add extra columns that are specific to the particular gamemode being played. For example, a deathmatch game mode would definitely have a column listing total kills, but the map creator may choose to add extra columns for the number of deaths you have and how long you have been playing for, in order to put your score into perspective.

==Controls==

===In-Game Keys===

* F8 (or Tilde Key) - Console
* F9 - In-game help
* F11 - Show SA map ''(the following list is for use when the map is up)''
**numpad /- - Zoom in and out
**numpad 4, 8, 6, 2 - move map left, up, right, down
**numpad 0 - toggle between attach to local player (map follows player blip) and free move (map stays stationary)
* F12 - Take a screenshot
* T - Chat
* Y - Team Chat
* TAB - Player List (if [[Scoreboard]] resource is running on the server)

==Console Commands==

'''bind defaults''' Binds control defaults in the settings menu

Press '''~ (tilde)''' or '''F8''' to access the console, then type a command followed by any neccessary parameters (if applicable) then press Enter.

;'''maps''' :This displays a list of all maps available on the server.

;'''nick [nickname]''' :This changes your nickname whilst in-game to whatever you specify in the parameters.

;'''msg [nickname] [message]''' or '''pm [nickname] [message]''' :This sends a private message to the person you specify in the [nickname] parameter. Only the person you specify can see the message. Both '''msg''' and '''pm''' perform the same function.

;'''quit''' or '''exit''' :This disconnects you from the server and returns you to the Windows desktop. Performs the same function as the Quit button on the main menu.

;'''ver''' :This displays the version number and copyright information for the software.

;'''sver''' :This displays the version number of the server you are connected to.

;'''time''' :This displays the current time.

;'''disconnect''' :This disconnects you from the server and returns you to the main menu.

;'''say [text]''' :This enables you to continue talking to people in the chat box whilst the console is open.

;'''ignore [nickname]''' :This will not display any text typed by the player you wish to ignore. To stop ignoring a player, type '''ignore [nickname]''' again.
{{Tip|You can use these commands in the chatbox by putting a / (forward slash) in front of them.}}

A list of console commands can be seen by typing '''help''' into the console and pressing Enter. The current map may also have extra commands which can be accessed by typing '''commands''' into the console.

For information on more commands see: [[Client Commands]]

==Error codes and their meanings==
'''Download errors'''<br>
0: UNKNOWN_ERROR<br>
1: INVALID_FILE_DESCRIPTORS<br>
2: INVALID_MAX_FILE_DESCRIPTOR<br>
3: INVALID_SELECT_RETURN<br>
4: INVALID_INITIAL_MULTI_PERFORM<br>
5: INVALID_MULTI_PERFORM_CODE<br>
6: INVALID_MULTI_PERFORM_CODE_NEW_DOWNLOADS<br>
7: UNEXPECTED_CURL_MESSAGE<br>
8: UNABLE_TO_CONNECT<br>
9: UNABLE_TO_DOWNLOAD_FILE<br>
10: FAILED_TO_INITIALIZE_DOWNLOAD<br>

'''Fatal errors'''<br>
1: no local player model on ingame event<br>
2: no local player on ingame event<br>
3: server downloads disabled<br>
4: no local player model on player-list packet<br>
5: no local player on player-list packet<br>
6: invalid custom data length on entity-add packet<br>
7: invalid bitstream data on entity-add packet<br>
8: system entity on entity-add packet<br>
9: failed to create object on entity-add packet<br>
10: failed to create pickup on entity-add packet<br>
11: failed to create vehicle on entity-add packet<br>
12: invalid team-name length on entity-add packet<br>
13: invalid lua-event name length in lua-event packet<br>
14: invalid resource name length in resource-start packet<br>

''''Unable to enter vehicle' errors'''<br>
1: script cancelled<br>
2: script cancelled (jack)<br>
3: current occupier is entering/exiting<br>
4: invalid seat<br>
5: not close enough<br>
6: already in a vehicle<br>
7: already entering/exiting<br>
8: invalid vehicle (trailer)<br>

==Special: Playing MTA on Linux?==
If you're one of those who have Linux as OS, and want to have the client working on Linux,
please read the [[Client_on_Linux_Manual|Client on Linux Manual]]

[[es:Manual Cliente Deathmatch]]
[[de:MTA DM Client Anleitung]]
[[it:Manuale del Client]]
[[nl:Deathmatch Client Manual]]
[[ru:Deathmatch Client Manual]]

[[Category:Support]]