Multi Theft Auto: Wiki - User contributions [en]

Getting MTA:SA to work with wine

2011-07-28T19:40:16Z

Tjong Tjong: /* Required fonts */

=== Installing MTA:SA ===

In order to install MTA:SA you will need the latest Wine version available to be able to install and run it.

'''Be sure you use Wine version 1.3 ([http://tinyurl.com/installWine1-3 Click on this link to check and install if needed] (Ubuntu-only)) '''

Once you installed MTA:SA you might need some missing fonts, this is not always the case,

but if the game doesn't start consider installing them.

==== Required fonts ====
These are the required fonts:

[http://merlin.neon-gaming.de/files/MTA-Fonts.7z verdana, tahoma, tahomabd]

Simply extract the fonts from the .7z archive to the 'Fonts' directory in the Windows directory inside your Wine directory.

=== Bugfixes ===

==== If MTA is not starting ====

If MTA doesn't start and you've already copied all the fonts needed,
you can try the following possible fixes:
* Try to start MTA:SA in a virtual desktop Go to WineConfig, choose the tab "Graphics" and select "Emulate a virtual desktop".

* Try to delete your gta_sa.set file which is located in the "GTA San Andreas User Files"-folder which can be found in your home directory. '''(Remember to create a copy, if you're playing San Andreas in singleplayer)'''

* Try to delete your MTA config file which is: "MTA San Andreas/MTA/coreconfig.xml" '''(Also remember to create a copy, if you don't want to lose your edited MTA configuration)'''

==== Crash when connecting ====

Sometimes the audio-server makes problems (could be related to pulseaudio),

in this case you've to go to WineConfig and choose the tab Audio,

then deselect "ALSA" and select "EsoundD". Save the settings and restart MTA.

Resource:Race

2011-02-01T16:21:45Z

Tjong Tjong: /* .map file */

{{Resource page}}
__NOTOC__
The "race" gamemode organizes sprint or freeroam races for one or more players. It supports both maps from MTA:Race and maps in the MTA:SA DM map syntax that were created in the map editor.

==Ingame==
Playing race is quite straightforward. If there are checkpoints, drive from checkpoint to checkpoint and be the first to reach the finish line within the time. If there are no checkpoints, just drive around and have fun.

In races you may encounter three types of pickups which will have an effect on your vehicle:
*'''Repair pickups:''' this pickup looks like a wrench. If you drive over it, your vehicle will be restored to full health.
*'''Nitrous oxide pickups:''' a red NOS bottle. After you drive over one you can press the fire button (by default the left mouse button) to get a temporary speed boost.
*'''Vehicle change pickups:''' these display the name of a vehicle above them. As soon as you drive over a pickup your vehicle will be changed.

Lastly, if you get stuck during a race, you can enter the /kill command in the chatbox to kill yourself and respawn at the previous checkpoint.

==Converting MTA:Race maps==
Use the [http://files.mtasa.com/apps/1.0/raceconv.zip batch converter] to convert all your MTA:Race maps into MTA:SA maps in one go.

==Map syntax==
You can create race maps using the new MTA:SA [[Resource:editor|map editor]]. The map syntax is given here for reference.

===.map file===
<syntaxhighlight lang="xml">
<map>

<spawnpoint posX="X" posY="Y" posZ="Z" rotation="Rotation in degrees" vehicle="Vehicle ID" id="spawnpointID" [ paintjob="paintjob ID" upgrades="comma-separated list of upgrades" ] />


<checkpoint posX="X" posY="Y" posZ="Z" color="#FF0000" id="textual or numeric checkpoint ID" nextid="ID of checkpoint after this one" [ size="checkpoint size" vehicle="vehicle ID to change into" type="checkpoint/ring/cylinder/arrow/corona" paintjob="paintjob ID" upgrades="comma-separated list of upgrades" ] />


<object posX="X" posY="Y" posZ="Z" rotX="in degrees" rotY="in degrees" rotZ="in degrees" model="model ID" id="objectID" />


<pickup posX="X" posY="Y" posZ="Z" type="repair|nitro|vehiclechange" id="pickupID" [ vehicle="vehicle ID" paintjob="paintjob ID" upgrades="comma-separated list of upgrades" ] />
</map>
</syntaxhighlight>

===meta.xml===
<syntaxhighlight lang="xml">
<meta>
<info type="map" gamemodes="race" name="Map name" author="Author name" description="Map description" version="Map version number"/>
<race src="Map file.map"/>
<settings>
<setting name="#optionName" value="optionValue"/>
...
</settings>
</meta>
</syntaxhighlight>
The <setting>s correspond to options in MTA:Race syntax. For example, <time>4:0</time> in MTA:Race syntax would correspond to <setting name="#time" value="4:0"/> in DM syntax.

==Addons==
A Race 'addon' is no different from any other script resource, except that is has addon="race" in the <info> section of it's meta.xml file. This is simply to allow Race to identify it and put it in the /config menu for you. Addons communicate with Race via events. The current list of Race events and what they do are here:

==Events for version 0.8.3==
'''Note:''' You may have to add the events in your script using addEvent() if you want to use them.
===Server===

{| class="wikitable" border="0"
|-
|width="200pt"|'''Name'''
|width="60pt"|'''Source'''
|'''Parameters'''
|}

{| class="wikitable" border="0"
|-
|width="200pt"|'''onPlayerReachCheckpoint'''
|width="60pt"|player
|<syntaxhighlight lang="lua">int checkpoint, int time_</syntaxhighlight>
|}

{| class="wikitable" border="0"
|-
|width="200pt"|'''onPlayerPickUpRacePickup'''
|width="60pt"|player
|<syntaxhighlight lang="lua">int/string pickupID, string pickupType, int vehicleModel</syntaxhighlight>
|}

{| class="wikitable" border="0"
|-
|width="200pt"|'''onMapStarting'''
|width="60pt"|
|<syntaxhighlight lang="lua">table mapInfo, table mapOptions, table gameOptions</syntaxhighlight>
|}

{| class="wikitable" border="0"
|-
|width="200pt"|'''onPlayerFinish'''
|width="60pt"|player
|height="20pt"|<syntaxhighlight lang="lua">int rank, int time</syntaxhighlight>
|}

{| class="wikitable" border="0"
|-
|width="200pt"|'''onPostFinish'''
|width="60pt"|
|height="38pt"|
|}

{| class="wikitable" border="0"
|-
|width="200pt"|'''onPollStarting'''
|width="60pt"|
|<syntaxhighlight lang="lua">table poll</syntaxhighlight>
|}

{| class="wikitable" border="0"
|-
|width="200pt"|'''onRaceStateChanging'''
|width="60pt"|
|<syntaxhighlight lang="lua">string newStateName, string oldStateName</syntaxhighlight>
|-
|}

{| class="wikitable" border="0"
|-
|width="200pt"|'''onPlayerRaceWasted'''
|width="60pt"|player
|<syntaxhighlight lang="lua">vehicle playersVehicle</syntaxhighlight>
|-
|}

===Client===

{| class="wikitable" border="0"
|-
|width="200pt"|'''onClientMapStarting'''
|width="60pt"|
|<syntaxhighlight lang="lua">table mapinfo</syntaxhighlight>
|-
|}

{| class="wikitable" border="0"
|-
|width="200pt"|'''onClientPlayerFinish'''
|width="60pt"|player
|height="38pt"|
|-
|}

{| class="wikitable" border="0"
|-
|width="200pt"|'''onClientPlayerOutOfTime'''
|width="60pt"|player
|height="38pt"|
|-
|}

{| class="wikitable" border="0"
|-
|width="200pt"|'''onClientMapStopping'''
|width="60pt"|
|height="38pt"|
|-
|}

{| class="wikitable" border="0"
|-
|width="200pt"|'''onClientScreenFadedOut'''
|width="60pt"|
|height="38pt"|
|-
|}

{| class="wikitable" border="0"
|-
|width="200pt"|'''onClientScreenFadedIn'''
|width="60pt"|
|height="38pt"|
|-
|}

==Events for version 0.8.3 in detail==
'''Note:''' You may have to add the events in your script using addEvent() if you want to use them.
===onPlayerReachCheckpoint===
Triggered when a player reaches any checkpoint but the last one.
====Parameters====
<syntaxhighlight lang="lua">int checkpoint, int time</syntaxhighlight>
*'''checkpoint:''' the number of the checkpoint the player went through. The first checkpoint has number 1.
*'''time:''' time since the race started, in milliseconds.

====Source====
The source is the player that reached the checkpoint.

===onPlayerFinish===
Triggered when a player reaches the last checkpoint (i.e. has finished the race)
====Parameters====
<syntaxhighlight lang="lua">int rank, int time</syntaxhighlight>
*'''rank:''' the player's rank. 1 means he won the race, 2 that he came in second place, etc.
*'''time:''' time since the race started, in milliseconds.

====Source====
The source is the player that finished the race.

===onPlayerPickUpRacePickup===
====Parameters====
<syntaxhighlight lang="lua">int/string pickupID, string pickupType, int vehicleModel</syntaxhighlight>
*'''pickupID:''' the number of the pickup in case of MTA:Race syntax (starting at 1), or the "id" attribute of the pickup in case of DM syntax.
*'''pickupType:''' the pickup type. Can be "nitro", "repair" or "vehiclechange".
*'''vehicleModel:''' if the pickup is of type vehiclechange, this is the vehicle model that it sets.

====Source====
The source is the player that picked up the pickup.

==Element data==
These element data are set on each player:
*'''race rank:''' the current position of the player in the race. 1 = first, 2 = second etc. Updated on a 1 second interval.
*'''race.checkpoint:''' the number of the checkpoint the player is ''heading for''. When the player spawns this number is 1, after he passed the first checkpoint it's 2, etc.
*'''race.finished:''' ''true'' if the player has finished, ''false'' if he's still racing.

This server only element data is set for the resource root element:
*'''info:''' which contains a table with these sub-tables: '''mapInfo''', '''mapOptions''' and '''gameOptions'''.

==Super Advanced Element data==
You can also set player element data to change the player collision status and render transparency:
<syntaxhighlight lang="lua">
e.g. setElementData( thePlayer, "overrideCollide.uniqueblah", 0, false ) -- Collide 'off' for this player
setElementData( thePlayer, "overrideCollide.uniqueblah", nil, false ) -- Collide 'default' for this player
setElementData( thePlayer, "overrideAlpha.uniqueblah", 120, false ) -- Alpha '120 maximum' for this player
setElementData( thePlayer, "overrideAlpha.uniqueblah", nil, false ) -- Alpha 'default' for this player
</syntaxhighlight>
Set 'uniqueblah' to whatever you like (up to 15 characters long)

==Exported Server functions==

{| class="wikitable" border="0"
|-
|width="80pt"|<syntaxhighlight lang="lua">int</syntaxhighlight>
|width="110pt"|'''getTimePassed'''
|height="38pt"|
|-
|}

{| class="wikitable" border="0"
|-
|width="80pt"|<syntaxhighlight lang="lua">int</syntaxhighlight>
|width="110pt"|'''getPlayerRank'''
|<syntaxhighlight lang="lua">player thePlayer</syntaxhighlight>
|-
|}

{| class="wikitable" border="0"
|-
|width="80pt"|<syntaxhighlight lang="lua">boolean</syntaxhighlight>
|width="110pt"|'''isPlayerFinished'''
|<syntaxhighlight lang="lua">player thePlayer</syntaxhighlight>
|-
|}

{| class="wikitable" border="0"
|-
|width="80pt"|<syntaxhighlight lang="lua">vehicle</syntaxhighlight>
|width="110pt"|'''getPlayerVehicle'''
|<syntaxhighlight lang="lua">player thePlayer</syntaxhighlight>
|-
|}

Getting MTA:SA to work with wine

2011-01-27T00:38:55Z

Tjong Tjong: Reuploaded Font-Files

=== Installing MTA:SA ===

In order to install MTA:SA you will need the latest Wine version available to be able to install and run it.

'''Be sure you use Wine version 1.3 ([http://tinyurl.com/installWine1-3 Click on this link to check and install if needed] (Ubuntu-only)) '''

Once you installed MTA:SA you might need some missing fonts, this is not always the case,

but if the game doesn't start consider installing them.

==== Required fonts ====
These are the required fonts:

[http://race.neon-gaming.de/MTA-Fonts.7z verdana, tahoma, tahomabd]

Simply extract the fonts from the .7z archive to the 'Fonts' directory in the Windows directory inside your Wine directory.

=== Bugfixes ===

==== If MTA is not starting ====

If MTA doesn't start and you've already copied all the fonts needed,
you can try the following possible fixes:
* Try to start MTA:SA in a virtual desktop Go to WineConfig, choose the tab "Graphics" and select "Emulate a virtual desktop".

* Try to delete your gta_sa.set file which is located in the "GTA San Andreas User Files"-folder which can be found in your home directory. '''(Remember to create a copy, if you're playing San Andreas in singleplayer)'''

* Try to delete your MTA config file which is: "MTA San Andreas/MTA/coreconfig.xml" '''(Also remember to create a copy, if you don't want to lose your edited MTA configuration)'''

==== Crash when connecting ====

Sometimes the audio-server makes problems (could be related to pulseaudio),

in this case you've to go to WineConfig and choose the tab Audio,

then deselect "ALSA" and select "EsoundD". Save the settings and restart MTA.

Getting MTA:SA to work with wine

2011-01-25T20:19:26Z

Tjong Tjong: /* Installing MTA:SA */

=== Installing MTA:SA ===

In order to install MTA:SA you will need the latest Wine version available to be able to install and run it.

'''Be sure you use Wine version 1.3 ([http://tinyurl.com/installWine1-3 Click on this link to check and install if needed] (Ubuntu-only)) '''

Once you installed MTA:SA you might need some missing fonts, this is not always the case,

but if the game doesn't start consider installing them.

==== Required fonts ====
These are the required fonts:

[http://projets.developpez.com/repositories/entry/vforum-php/data/fonts/verdana.ttf?format=raw&rev=1 verdana]

[http://www.bikeparadise.cz/jpgraph/ttf/tahoma.ttf tahoma]

[http://www.bikeparadise.cz/jpgraph/ttf/tahomabd.ttf tahomabd]

Simply copy the fonts to the 'Fonts' directory in the Windows directory inside your Wine directory.

=== Bugfixes ===

==== If MTA is not starting ====

If MTA doesn't start and you've already copied all the fonts needed,
you can try the following possible fixes:
* Try to start MTA:SA in a virtual desktop Go to WineConfig, choose the tab "Graphics" and select "Emulate a virtual desktop".

* Try to delete your gta_sa.set file which is located in the "GTA San Andreas User Files"-folder which can be found in your home directory. '''(Remember to create a copy, if you're playing San Andreas in singleplayer)'''

* Try to delete your MTA config file which is: "MTA San Andreas/MTA/coreconfig.xml" '''(Also remember to create a copy, if you don't want to lose your edited MTA configuration)'''

==== Crash when connecting ====

Sometimes the audio-server makes problems (could be related to pulseaudio),

in this case you've to go to WineConfig and choose the tab Audio,

then deselect "ALSA" and select "EsoundD". Save the settings and restart MTA.

Getting MTA:SA to work with wine

2011-01-25T19:56:48Z

Tjong Tjong:

=== Installing MTA:SA ===

In order to install MTA:SA you will need the latest Wine version available to be able to install and run it.

'''Be sure you use Wine version 1.3 ([http://tinyurl.com/installWine1-3 Click on this link to check and install if needed]) '''

Once you installed MTA:SA you might need some missing fonts, this is not always the case,

but if the game doesn't start consider installing them.

==== Required fonts ====
These are the required fonts:

[http://projets.developpez.com/repositories/entry/vforum-php/data/fonts/verdana.ttf?format=raw&rev=1 verdana]

[http://www.bikeparadise.cz/jpgraph/ttf/tahoma.ttf tahoma]

[http://www.bikeparadise.cz/jpgraph/ttf/tahomabd.ttf tahomabd]

Simply copy the fonts to the 'Fonts' directory in the Windows directory inside your Wine directory.

=== Bugfixes ===

==== If MTA is not starting ====

If MTA doesn't start and you've already copied all the fonts needed,
you can try the following possible fixes:
* Try to start MTA:SA in a virtual desktop Go to WineConfig, choose the tab "Graphics" and select "Emulate a virtual desktop".

* Try to delete your gta_sa.set file which is located in the "GTA San Andreas User Files"-folder which can be found in your home directory. '''(Remember to create a copy, if you're playing San Andreas in singleplayer)'''

* Try to delete your MTA config file which is: "MTA San Andreas/MTA/coreconfig.xml" '''(Also remember to create a copy, if you don't want to lose your edited MTA configuration)'''

==== Crash when connecting ====

Sometimes the audio-server makes problems (could be related to pulseaudio),

in this case you've to go to WineConfig and choose the tab Audio,

then deselect "ALSA" and select "EsoundD". Save the settings and restart MTA.

Slothman/Slothbot

2010-12-28T18:27:20Z

Tjong Tjong: /* spawnBot */

This is a resource designed to allow scripts or gamemodes to insert a ped into the game that roughly simulates combat with a real player. gamemodes can implement the bots as opponents to actual players or as teammates.

=Features=
'''Teamplay:'''
The bot is capable of identifying friend from foe

'''Map Navigation:'''
When the bot is placed in a map that has suitable pathways marked out (see below on how to do that) the bot will navigate the map, seeking out enemies. Without pathways, a bot can still think for itself, but wont move around as profficiently.

'''Aggressiveness:'''
Bots will attack any ped, player or bot thats not on it's team.

'''Cooperation:'''
Bots can automatically team up with teammates (either player or bot) by meeting up with them and sticking together

'''Advanced movement:'''
If theres obstacles blocking a bot's path, the bot will attempt to get around or over it instead of just walking into a wall for eternity

'''Multiple modes of playing:'''
*"hunting" - travel pathways untill finding an enemy or teammate
*"waiting" - stand still untill an enemy of teammate comes into view
*"guarding" - the bot will attack any enemy that comes within sight, but not move from its spawn position
*"following" - the bot will follow a player or bot while attacking enemies
*"chasing" - the bot will attack an anemy bot or player

'''Gamemode/Script integration:'''
This script provides several functions and events to allow other resources to see and control what the bot's are doing, and even take control of certain behaviour.

'''EDF for map path creation:'''
Integrated into the map editor, map designers can easily place paths for bots to follow along in their maps. this greatly increased the bots ability to simulate true playing.

=Server Events=

==onBotFindEnemy==
This triggers when a bot locates an enemy, This event can be cancelled to prevent the bot from chasing players

<big>'''Parameters'''</big>
<syntaxhighlight lang="lua">
element enemy
</syntaxhighlight>
*'''enemy''': The Player or Ped the bot has spotted
<big>'''Source'''</big>

The [[event system#Event source|source]] of this event is the Bot that has found an enemy

==onBotWasted==
This triggers when a bot is killed.

<big>'''Parameters'''</big>
<syntaxhighlight lang="lua">
element attacker, float weapon, float bodypart
</syntaxhighlight>
*'''attacker''': The Element that killed the bot
*'''weapon''': The weapon id used to kill the bot
*'''bodypart''': The bodypart id that was hit to kill the bot
<big>'''Source'''</big>

The [[event system#Event source|source]] of this event is the Bot that died

==onBotSpawned==
This triggers when a bot is spawned.

<big>'''Source'''</big>
The [[event system#Event source|source]] of this event is the Bot that spawned

==onBotFollow==
This triggers when a bot starts following a teammate

<big>'''Parameters'''</big>
<syntaxhighlight lang="lua">
element leader
</syntaxhighlight>
*'''leader''': The Player or Ped the bot has started following
<big>'''Source'''</big>

The [[event system#Event source|source]] of this event is the Bot that starts following a teammate

=Server Functions=
All of these funtions will have to be used through the [[call]] function, otherwise they won't work

==spawnBot==
This function spawns a bot ingame, will return the bot element, or false if there was a problem.

<big>'''Syntax'''</big>
<syntaxhighlight lang="lua">
element spawnBot ( float x, float y, float z, int rotation = 0, [ int skinID = 0, int interior = 0, int dimension = 0, team theTeam = nil, int weapon = 0, string theMode = "hunting", element theModesubject = nil ] )
</syntaxhighlight>

<big>'''Required Arguments'''</big>
*'''x:''' The x co-ordinate to spawn the bot at
*'''y:''' The y co-ordinate to spawn the bot at
*'''z:''' The z co-ordinate to spawn the bot at
*'''rotation:''' Rotation of the bot on spawn

<big>'''Optional Arguments'''</big>
*'''skinID:''' Bots skin on spawn
*'''interior:''' Interior the bot will spawn into
*'''dimension:''' The ID of the [[dimension]] that the bot should be in
*'''theTeam:''' The team the bot will join
*'''weapon:''' The weapon the ped will carry
*'''theMode:''' The action the bot will be performing when spawned (see "modes of playing" above)
*'''theModeSubject:''' If theMode is "chasing" or "following" this arg is needed to tell the bot what opponent to chase or teammate to follow

==setBotHunt==
makes the bot travel pathways untill finding an enemy or teammate

<big>'''Syntax'''</big>
<syntaxhighlight lang="lua">
bool setBotHunt ( element theBot )
</syntaxhighlight>

<big>'''Required Arguments'''</big>
*'''theBot:''' The bot you want to hunt

==setBotWait==
makes the bot stand still untill an enemy of teammate comes into view

<big>'''Syntax'''</big>
<syntaxhighlight lang="lua">
bool setBotWait ( element theBot )
</syntaxhighlight>

<big>'''Required Arguments'''</big>
*'''theBot:''' The bot you want to wait

==setBotChase==
makes the bot attack an anemy bot or player

<big>'''Syntax'''</big>
<syntaxhighlight lang="lua">
bool setBotChase ( element theBot, element theTarget )
</syntaxhighlight>

<big>'''Required Arguments'''</big>
*'''theBot:''' The bot that you want to do the chasing
*'''theTarget:''' The bot or player you want to be chased

==setBotFollow==
makes the bot follow a teammate bot or player

<big>'''Syntax'''</big>
<syntaxhighlight lang="lua">
bool setBotFollow( element theBot, element theTarget )
</syntaxhighlight>

<big>'''Required Arguments'''</big>
*'''theBot:''' The bot that you want to do the following
*'''theTarget:''' The bot or player you want to be followed

==setBotGuard==
makes the bot move to the specific coords and stay there while attacking any enemies

<big>'''Syntax'''</big>
<syntaxhighlight lang="lua">
bool setBotGuard( element theBot, float x, float y, float z, [ bool priority = false ] )
</syntaxhighlight>

<big>'''Required Arguments'''</big>
*'''theBot:''' The bot you want to do the guarding
*'''x:''' The X coords you want the bot to guard
*'''y:''' The Y coords you want the bot to guard
*'''z:''' The Z coords you want the bot to guard

<big>'''Optional Arguments'''</big>
*'''priority:''' Set to true only if you want the bot to only shoot once it has reached the location to guard

==getBotTeam==
returns the Team the bot is on, false if no team

<big>'''Syntax'''</big>
<syntaxhighlight lang="lua">
string getBotTeam ( element theBot)
</syntaxhighlight>

<big>'''Required Arguments'''</big>
*'''theBot:''' The bot you want to check the team of

==setBotTeam==
changes the bot's team and loyalties

<big>'''Syntax'''</big>
<syntaxhighlight lang="lua">
bool setBotTeam ( element theBot, team theTeam )
</syntaxhighlight>

<big>'''Required Arguments'''</big>
*'''theBot:''' The bot you want to change the team of
*'''theTeam:''' The team the bot should join

==getBotAttackEnabled==
returns true if the bot is allowed to attack, false otherwise

<big>'''Syntax'''</big>
<syntaxhighlight lang="lua">
bool getBotAttackEnabled( element theBot)
</syntaxhighlight>

<big>'''Required Arguments'''</big>
*'''theBot:''' The bot you want to check if it can atack

==setBotAttackEnabled==
allow or disallow the bot to attack (press fire)

<big>'''Syntax'''</big>
<syntaxhighlight lang="lua">
bool setBotAttackEnabled( element theBot, bool enabled)
</syntaxhighlight>

<big>'''Required Arguments'''</big>
*'''theBot:''' The bot you want to set if it can atack
*'''enabled:''' set to false to remove the bots ability to attack, true to allow it

==getBotMode==
returns the mode the bot is in ("chasing", "waiting", "guarding", "hunting", "following") or if the bot is chasing or following, it will return the mode and the target

<big>'''Syntax'''</big>
<syntaxhighlight lang="lua">
string getBotMode( element theBot)
</syntaxhighlight>

<big>'''Required Arguments'''</big>
*'''theBot:''' The bot you want to check the status of

==isPedBot==
returns true if the ped is a bot, false otherwise

<big>'''Syntax'''</big>
<syntaxhighlight lang="lua">
bool ispedbot( element thePed)
</syntaxhighlight>

<big>'''Required Arguments'''</big>
*'''thePed:''' The ped you want to check if its a bot

==setBotWeapon==
sets the bot's weapon id (ammo is always infinite)

<big>'''Syntax'''</big>
<syntaxhighlight lang="lua">
bool setBotWeapon( element theBot, float weapon)
</syntaxhighlight>

<big>'''Required Arguments'''</big>
*'''theBot:''' The bot you want to set the weapon of
*'''weapon:''' the weapon id you want to give the bot

=Credits=
*'''Slothman:''' Bot creator, main scripter
*'''Gamesnert:''' EDF creator, scripting, testing
*'''Dragon:''' Gamemode creator, testing, scripting help
*'''EvGeniz:''' early testing, mapping
'''Thanks to Everyone else who made suggestions, tested the script, helped when i was stuck, etc'''