Multi Theft Auto: Wiki - User contributions [en]

CreateColPolygon

2008-12-30T14:20:30Z

BrophY:

__NOTOC__
{{Server client function}}
This function creates a collision polygon. See [http://en.wikipedia.org/wiki/Polygon Wikipedia] for a definition of a polygon. The first set of X Y of this shape is not part of the colshape bounds, so can set anywhere in the game world, however for performance, place it somewhere within the polygon. It should be noted this shape is '''2D'''. There should be at least 3 bound points set.

==Syntax==
<syntaxhighlight lang="lua">
colshape createColPolygon ( float fX, float fY, float fX1, float fY1, float fX2, float fY2, float fX3, float fY3, ... )
</syntaxhighlight>

===Required Arguments===
*'''fX:''' The X position of the collision polygon's dummy point
*'''fY:''' The Y position of the collision polygon's dummy point
*'''fX1:''' The 1st X position of the collision polygon's bound point
*'''fY1:''' The 1st Y position of the collision polygon's bound point
*'''fX2:''' The 2nd X position of the collision polygon's bound point
*'''fY2:''' The 2nd Y position of the collision polygon's bound point
*'''fX3:''' The 3rd X position of the collision polygon's bound point
*'''fY3:''' The 3rd Y position of the collision polygon's bound point
*'''...''' From the 3rd position you can have as many points as you require to create the colshape.

===Returns===
Returns a [[colshape]] element if successful, ''false'' if invalid arguments were passed to the function.

==Example==
<section name="Server" class="server" show="true">
<syntaxhighlight lang="lua">--To Do.</syntaxhighlight>
</section>
<section name="Client" class="client" show="true">
<syntaxhighlight lang="lua">--To Do.</syntaxhighlight>
</section>

==See Also==
{{Collision shape functions}}

Template:Collision shape functions

2008-12-29T18:10:10Z

BrophY:

*[[createColCircle]]

*[[createColCuboid]]

*[[createColSphere]]

*[[createColRectangle]]

*[[createColTube]]

*[[createColPolygon]]

CreateColPolygon

2008-12-29T18:08:35Z

BrophY:

__NOTOC__
{{Server client function}}
This function creates a collision polygon. See [http://en.wikipedia.org/wiki/Polygon Wikipedia] for a definition of a polygon. The first set of X Y of this shape is not part of the colshape bounds, so can set anywhere in the game world, however for performance, place it somewhere within the polygon. It should be noted this shape is '''2D'''. There should be at least 3 bound points set.

==Syntax==
<syntaxhighlight lang="lua">
colshape createColPolygon ( float fX, float fY, float fX1, float fX2, float fX3, ... )
</syntaxhighlight>

===Required Arguments===
*'''fX:''' The X position of the collision polygon's dummy point
*'''fY:''' The Y position of the collision polygon's dummy point
*'''fX1:''' The 1st position of the collision polygon's bound point
*'''fX2:''' The 2st position of the collision polygon's bound point
*'''fX3:''' The 3st position of the collision polygon's bound point
*'''...''' From the 3rd position you can have as many points as you require to create the colshape.

===Returns===
Returns a [[colshape]] element if successful, ''false'' if invalid arguments were passed to the function.

==Example==
<section name="Server" class="server" show="true">
<syntaxhighlight lang="lua">--To Do.</syntaxhighlight>
</section>
<section name="Client" class="client" show="true">
<syntaxhighlight lang="lua">--To Do.</syntaxhighlight>
</section>

==See Also==
{{Collision shape functions}}

CreateColPolygon

2008-12-29T18:07:56Z

BrophY:

__NOTOC__
{{Server client function}}
This function creates a collision polygon. See [http://en.wikipedia.org/wiki/Polygon Wikipedia] for a definition of a polygon. The first set of X Y of this shape is not part of the colshape bounds, so can set anywhere in the game world, however for performance, place it somewhere within the polygon. It should be noted this shape is '''2D'''. There should be at least 3 bound points set.

==Syntax==
<syntaxhighlight lang="lua">
colshape createColPolygon ( float fX, float fY, float fX1, float fX2, float fX3, ... )
</syntaxhighlight>

===Required Arguments===
*'''fX:''' The X position of the collision polygon's dummy point
*'''fY:''' The Y position of the collision polygon's dummy point
*'''fX1:''' The 1st position of the collision polygon's bound point
*'''fX2:''' The 2st position of the collision polygon's bound point
*'''fX3:''' The 3st position of the collision polygon's bound point
*'''...''' From the 3rd position you can have as many points as you require to create the colshape.

===Returns===
Returns a [[colshape]] element if successful, ''false'' if invalid arguments were passed to the function.

==Example==
<section name="Server" class="server" show="true">
<syntaxhighlight lang="lua" lang="lua">--To Do.</syntaxhighlight>
</section>
<section name="Client" class="client" show="true">
<syntaxhighlight lang="lua" lang="lua">--To Do.</syntaxhighlight>
</section>

==See Also==
{{Collision shape functions}}

CreateColPolygon

2008-12-29T18:06:30Z

BrophY:

__NOTOC__
{{Server client function}}
This function creates a collision polygon. See [http://en.wikipedia.org/wiki/Polygon Wikipedia] for a definition of a polygon. The first set of X Y of this shape is not part of the colshape bounds, so can set anywhere in the game world, however for performance, place it somewhere within the polygon. It should be noted this shape is '''2D'''. There should be at least 3 bound points set.

==Syntax==
<syntaxhighlight lang="lua">
colshape createColPolygon ( float fX, float fY, float fX1, float fX2, float fX3, ... )
</syntaxhighlight>

===Required Arguments===
*'''fX:''' The X position of the collision polygon's dummy point
*'''fY:''' The Y position of the collision polygon's dummy point
*'''fX1:''' The 1st position of the collision polygon's bound point
*'''fX2:''' The 2st position of the collision polygon's bound point
*'''fX3:''' The 3st position of the collision polygon's bound point
*'''...''' From the 3rd position you can have as many points as you require to create the colshape.

===Returns===
Returns a [[colshape]] element if successful, ''false'' if invalid arguments were passed to the function.

==Example==
<section name="Server" class="server" show="true">
To Do.
</section>

==See Also==
{{Collision shape functions}}

CreateColPolygon

2008-12-29T18:05:42Z

BrophY: New page: __NOTOC__ {{Server client function}} This function creates a collision polygon. See [http://en.wikipedia.org/wiki/Polygon Wikipedia] for a definition of a polygon. The first set of X Y of...

CreateColCuboid

2008-12-29T18:05:18Z

BrophY: Edited wrong page

__NOTOC__
{{Server client function}}
This function creates a collision cuboid. This is a shape that has a position, width, depth and height. See [http://en.wikipedia.org/wiki/Cuboid Wikipedia] for a definition of a cuboid. The XYZ of the col starts at the southwest bottom corner of the shape.

==Syntax==
<syntaxhighlight lang="lua">
colshape createColCuboid ( float fX, float fY, float fZ, float fWidth, float fDepth, float fHeight )
</syntaxhighlight>

===Required Arguments===
*'''fX:''' The X position of the collision cuboid's western side
*'''fY:''' The Y position of the collision cuboid's southern side
*'''fZ:''' The Z position of the collision cuboid's lowest side
*'''fWidth:''' The collision cuboid's width
*'''fDepth:''' The collision cuboid's depth
*'''fHeight:''' The collision cuboid's height

===Returns===
Returns a [[colshape]] element if successful, ''false'' if invalid arguments were passed to the function.

==Example==
<section name="Server" class="server" show="true">
This example displays a chat message when a player enters the colshape and allows the colshape to be created using a console function ''set_zone''.
<syntaxhighlight lang="lua">
theZone = false

function shapeHit ( thePlayer )
outputChatBox ( getClientName ( thePlayer ) .. " is in the zone!" ) -- display a message in everyone's chat box
end

function setZone ( playerSource, commandName, fX, fY, fZ )
if ( fZ and fY and fX ) then -- check we've got all 3 args we need
local tempCol = createColCuboid ( fX, fY, fZ, 10.0, 10.0, 10.0 ) -- create a col
if ( tempCol == false ) then -- did the col get created successfully?
outputConsole ( "Syntax is: set_zone <X> <Y> <Z>" ) -- inform the user what the valid syntax is
else
if ( theZone ~= false ) then -- did we already have a zone?
destroyElement ( theZone ) -- if so, destroy it
else
addEventHandler ( "onColShapeHit", theZone, shapeHit ) -- add a handler for the onColShapeHit event
end
theZone = tempCol -- store the new zone we've made
outputChatBox ( "Zone has moved!" ) -- and tell everyone
end
end
end
addCommandHandler ( "set_zone", setZone ) -- add a console function called set_zone that will trigger the function setZone
</syntaxhighlight>
</section>

==See Also==
{{Collision shape functions}}

CreateColCuboid

2008-12-29T18:04:08Z

BrophY:

CreateColCuboid

2008-12-29T18:04:00Z

BrophY:

CreateColCuboid

2008-12-29T18:03:37Z

BrophY:

OnClientGUIClick

2008-09-21T11:32:01Z

BrophY: Undo revision 17712 by BrophY (Talk) Oops, wrong page

{{Client event}}
__NOTOC__
{{Needs Checking|''middle'' button does not trigger this event.--[[User:50pence|50pence]] 12:19, 19 May 2008 (CDT)}}
This event is fired when the user clicks a GUI element.

==Parameters==
<syntaxhighlight lang="lua">
string button, string state, int absoluteX, int absoluteY
</syntaxhighlight>
*'''button:''' the name of the mouse button that the GUI element was clicked with, can be ''left'', ''right'', or ''middle''.
*'''state:''' the state of the mouse button, will be ''down'' if the mouse button was pushed, or ''up'' if it was released.
*'''absoluteX:''' the X position of the mouse cursor, in pixels, measured from the left side of the screen.
*'''absoluteY:''' the Y position of the mouse cursor, in pixels, measured from the top of the screen.

==Source==
The [[event system#Event source|source]] of this event is the GUI element that was clicked.

==Example==
This example creates an edit box alongside an "Output!" button. When the button is clicked with the left mouse button, it will output the message in the edit box into the Chat Box.
<syntaxhighlight lang="lua">
-- when client's resource start, create the gui
function initGUI( )
--create our button
btnOutput = guiCreateButton( 0.7, 0.1, 0.2, 0.1, "Output!", true )

--Create an edit box and define it as "editBox".
editBox = guiCreateEdit( 0.3, 0.1, 0.4, 0.1, "Type your message here!", true )
guiEditSetMaxLength ( editBox, 128 ) --the max chatbox length is 128, so force this
end
addEventHandler( "onClientResourceStart", getResourceRootElement( getThisResource( ) ), initGUI )

--setup our function to output the message to the chatbox
function outputEditBox (button)
if button == "left" then
local text = guiGetText ( editBox )--get the text from the edit box
outputChatBox ( text ) --output that text
end
end
--and attach our button to the outputEditBox function
addEventHandler ( "onClientGUIClick", btnOutput, outputEditBox, false )
</syntaxhighlight>

==See Also==
===GUI events===
{{GUI_events}}
===Client event functions===
{{Client_event_functions}}

OnClientGUIClick

2008-09-21T11:30:26Z

BrophY: button hasnt been a 'string' for a long time, changed to element

{{Client event}}
__NOTOC__
{{Needs Checking|''middle'' button does not trigger this event.--[[User:50pence|50pence]] 12:19, 19 May 2008 (CDT)}}
This event is fired when the user clicks a GUI element.

==Parameters==
<syntaxhighlight lang="lua">
element button, string state, int absoluteX, int absoluteY
</syntaxhighlight>
*'''button:''' the name of the mouse button that the GUI element was clicked with, can be ''left'', ''right'', or ''middle''.
*'''state:''' the state of the mouse button, will be ''down'' if the mouse button was pushed, or ''up'' if it was released.
*'''absoluteX:''' the X position of the mouse cursor, in pixels, measured from the left side of the screen.
*'''absoluteY:''' the Y position of the mouse cursor, in pixels, measured from the top of the screen.

==Source==
The [[event system#Event source|source]] of this event is the GUI element that was clicked.

==Example==
This example creates an edit box alongside an "Output!" button. When the button is clicked with the left mouse button, it will output the message in the edit box into the Chat Box.
<syntaxhighlight lang="lua">
-- when client's resource start, create the gui
function initGUI( )
--create our button
btnOutput = guiCreateButton( 0.7, 0.1, 0.2, 0.1, "Output!", true )

--Create an edit box and define it as "editBox".
editBox = guiCreateEdit( 0.3, 0.1, 0.4, 0.1, "Type your message here!", true )
guiEditSetMaxLength ( editBox, 128 ) --the max chatbox length is 128, so force this
end
addEventHandler( "onClientResourceStart", getResourceRootElement( getThisResource( ) ), initGUI )

--setup our function to output the message to the chatbox
function outputEditBox (button)
if button == "left" then
local text = guiGetText ( editBox )--get the text from the edit box
outputChatBox ( text ) --output that text
end
end
--and attach our button to the outputEditBox function
addEventHandler ( "onClientGUIClick", btnOutput, outputEditBox, false )
</syntaxhighlight>

==See Also==
===GUI events===
{{GUI_events}}
===Client event functions===
{{Client_event_functions}}

Dictionary

2008-04-22T10:35:51Z

BrophY: New page: Over the years MTA's community has come across some new terms and words. They are most often used in IRC and on the forums but some are also featered in the game. What follows is an alphab...

Over the years MTA's community has come across some new terms and words. They are most often used in IRC and on the forums but some are also featered in the game. What follows is an alphabetical list.
<hr /><br />

* Bitchpack (verb)
Use of the lack of enter vehicle animation in MTA 0.x in order to get unlimited players into a
vehicle

* Johnline (being a ..) (noun)
acting immature, using a lot of sexual related insults hoping to make you look cool/mature.

* MAD_BOY (noun)
When something is refered to as old or outdated

* Ransom
GTANet's resident bastard operator from hell

* RIFK
A common typographical error of "rofl", has also come to be known as an acronym
for "rolling in fucking kitchens." Though first pioneered in #mta by Jani, it is most
frequently used by BrophY and Johnline

* Robpol86 (verb)/(noun)
-Consistent use of mushrooms in order to grow and the ability to jump incredibly high
-Also a mythical creature with a mustache of supernatural size and ability

* YOIV
-Your Opinion Is Void (aka "pulling a Luke")
-Used to discribe a situation where an admin uses his powers to force his own opinion onto
a person or a group of people.

User:BrophY

2007-07-09T08:53:12Z

BrophY:

IJs and ChrML fear BrophY
<br /><br />
[[Image:BatChild.jpg]]

User:IJs

2007-07-04T07:22:14Z

BrophY:

'''IJs'''

----

I work on various parts of MTA and the Blue platform, including the GUI, POSIX compatibility and the modifications. Also founder of the MTA project (on Feb 9, 2003).

Self-taught programmer mainly experienced in C/C++, Basic, Java, PHP, (X)HTML, Perl, ASM. Started with batches and EXE's on MS-DOS. Worked on various projects on different hardware platforms including x86's, mobile phones, C64 and Amiga's. Also experienced in various scripting languages, OpenGL programming, reverse engineering, hardware modifications, sound engineering, composing music, mapping, graphics design, maintaining linux servers, Counter-Strike and OS research.

[http://i128.photobucket.com/albums/p175/the_chosen_one1/Care-Room.jpg]

I'm also scared of BrophY, but dont tell him that!

Template:Announce functions

2007-07-03T10:37:38Z

BrophY:

*[[setGameType]]

*[[setMapName]]

*[[getRuleValue]]

*[[setRuleValue]]

*[[removeRuleValue]]

RemoveRuleValue

2007-07-03T10:34:49Z

BrophY:

__NOTOC__
This function removes a set rule value that can be viewed by server browsers.

==Syntax==
<syntaxhighlight lang="lua">
bool removeRuleValue ( string key )
</syntaxhighlight>

===Required Arguments===
*'''key:''' The name of the rule you wish to remove

===Returns===
Returns ''true'' if the rule value was removed, ''false'' if it failed.

==Example==
This example shows how you could set a rule that shows that your script is running on the server.
<syntaxhighlight lang="lua">
removeRuleValue ( "myScriptRunning" )
</syntaxhighlight>

==See Also==
{{ASE_functions}}

User:BrophY

2007-06-04T15:20:56Z

BrophY:

'''Capture the Vehicle'''
<br /><br />
Also thanks to Talidan, Dragon, Ransom :)
<br /><br />
Tasks to be Completed:
<br /><br />
* <strike>SpawnScreen</strike> --[[User:BrophY|BrophY]] 05:01, 6 April 2007 (CDT)
* <strike>SpawnPoints</strike> --[[User:BrophY|BrophY]] 05:01, 6 April 2007 (CDT)
* <strike>Teams and Weapons</strike> --[[User:BrophY|BrophY]] 05:01, 6 April 2007 (CDT)
* <strike>Capture Markers</strike> --[[User:BrophY|BrophY]] 05:01, 6 April 2007 (CDT)
* <strike>Move everything XML side (in .map)</strike> --[[User:BrophY|BrophY]] 10:20, 4 June 2007 (CDT)
* <strike>Capture Vehicle Placements ( Random Locations )</strike> --[[User:BrophY|BrophY]] 05:01, 6 April 2007 (CDT)
* <strike>Scoreboard</strike> ''Include/Use Scoreboard Resource'' --[[User:BrophY|BrophY]] 08:35, 12 May 2007 (CDT)
* <strike>Normal Vehicle Placements</strike> --[[User:BrophY|BrophY]] 08:35, 12 May 2007 (CDT)
* Any Necessary Pickups
* <strike>Remove Debug stuff such as Invincible 'Vehicle'</strike> --[[User:BrophY|BrophY]] 11:24, 25 May 2007 (CDT)
* <strike>Convert Rounds to carry on straight off the bat</strike> --[[User:BrophY|BrophY]] 11:24, 25 May 2007 (CDT)
<br />
----
<br />
IJs and ChrML fear BrophY
<br /><br />
[[Image:BatChild.jpg]]

User:BrophY

2007-05-25T16:24:30Z

BrophY:

'''Capture the Vehicle'''
<br /><br />
Also thanks to Talidan, Dragon, Ransom :)
<br /><br />
Tasks to be Completed:
<br /><br />
* <strike>SpawnScreen</strike> --[[User:BrophY|BrophY]] 05:01, 6 April 2007 (CDT)
* <strike>SpawnPoints</strike> --[[User:BrophY|BrophY]] 05:01, 6 April 2007 (CDT)
* <strike>Teams and Weapons</strike> --[[User:BrophY|BrophY]] 05:01, 6 April 2007 (CDT)
* <strike>Capture Markers</strike> --[[User:BrophY|BrophY]] 05:01, 6 April 2007 (CDT)
* <strike>Capture Vehicle Placements ( Random Locations )</strike> --[[User:BrophY|BrophY]] 05:01, 6 April 2007 (CDT)
* <strike>Scoreboard</strike> ''Include/Use Scoreboard Resource'' --[[User:BrophY|BrophY]] 08:35, 12 May 2007 (CDT)
* <strike>Normal Vehicle Placements</strike> --[[User:BrophY|BrophY]] 08:35, 12 May 2007 (CDT)
* Any Necessary Pickups
* <strike>Remove Debug stuff such as Invincible 'Vehicle'</strike> --[[User:BrophY|BrophY]] 11:24, 25 May 2007 (CDT)
* <strike>Convert Rounds to carry on straight off the bat</strike> --[[User:BrophY|BrophY]] 11:24, 25 May 2007 (CDT)
<br />
----
<br />
IJs and ChrML fear BrophY
<br /><br />
[[Image:BatChild.jpg]]

User:BrophY

2007-05-25T16:14:57Z

BrophY:

'''Capture the Vehicle'''
<br /><br />
Also thanks to Talidan, Dragon, Ransom :)
<br /><br />
Tasks to be Completed:
<br /><br />
* <strike>SpawnScreen</strike> --[[User:BrophY|BrophY]] 05:01, 6 April 2007 (CDT)
* <strike>SpawnPoints</strike> --[[User:BrophY|BrophY]] 05:01, 6 April 2007 (CDT)
* <strike>Teams and Weapons</strike> --[[User:BrophY|BrophY]] 05:01, 6 April 2007 (CDT)
* <strike>Capture Markers</strike> --[[User:BrophY|BrophY]] 05:01, 6 April 2007 (CDT)
* <strike>Capture Vehicle Placements ( Random Locations )</strike> --[[User:BrophY|BrophY]] 05:01, 6 April 2007 (CDT)
* <strike>Scoreboard</strike> ''Include/Use Scoreboard Resource'' --[[User:BrophY|BrophY]] 08:35, 12 May 2007 (CDT)
* <strike>Normal Vehicle Placements</strike> --[[User:BrophY|BrophY]] 08:35, 12 May 2007 (CDT)
* Any Necessary Pickups
* Remove Debug stuff such as Invincible 'Vehicle'
* Convert Rounds to carry on straight off the bat
<br />
----
<br />
IJs and ChrML fear BrophY
<br /><br />
[[Image:BatChild.jpg]]

GetGameSpeed

2007-05-12T13:45:58Z

BrophY:

__NOTOC__
==Description==
This function get the current game speed value

==Syntax==
<syntaxhighlight lang="lua">getGameSpeed ()</syntaxhighlight>

==Example==
<syntaxhighlight lang="lua">addCommandHandler ( "gamespeed", "gamespeedvalue" )
function gamespeedvalue ()
local speed = getGameSpeed ()
outputChatbox ( "Gamespeed is currently set to " ..speed.. "" )
end</syntaxhighlight>

==See Also==
{{World functions}}

GetGameSpeed

2007-05-12T13:45:40Z

BrophY:

__NOTOC__
==Description==
This function get the current game speed value

==Syntax==
<syntaxhighlight lang="lua">getGameSpeed ()</syntaxhighlight>

==Example==
<syntaxhighlight lang="lua">addCommandHandler ( "gamespeed", "gamespeedvalue" )
function getgamespeedvalue ()
local speed = getGameSpeed ()
outputChatbox ( "Gamespeed is currently set to " ..speed.. "" )
end</syntaxhighlight>

==See Also==
{{World functions}}

SetGameSpeed

2007-05-12T13:43:29Z

BrophY:

__NOTOC__
==Description==
This function sets the game speed to the given value

==Syntax==
<syntaxhighlight lang="lua">setGameSpeed ( int value )</syntaxhighlight>

===Required Arguments===
*'''value''': The int value of the gamespeed (Range 0 - 10)

==Example==
<syntaxhighlight lang="lua">addCommandHandler ( "setgamespeed", "gamespeedfunction")
function gamespeedfunction ( player, command, value )
setGameSpeed ( tonumber ( value ) )
end</syntaxhighlight>

==See Also==
{{World functions}}

User:BrophY

2007-05-12T13:35:32Z

BrophY:

'''Capture the Vehicle'''
<br /><br />
Also thanks to Talidan, Dragon, Ransom :)
<br /><br />
Tasks to be Completed:
<br /><br />
* <strike>SpawnScreen</strike> --[[User:BrophY|BrophY]] 05:01, 6 April 2007 (CDT)
* <strike>SpawnPoints</strike> --[[User:BrophY|BrophY]] 05:01, 6 April 2007 (CDT)
* <strike>Teams and Weapons</strike> --[[User:BrophY|BrophY]] 05:01, 6 April 2007 (CDT)
* <strike>Capture Markers</strike> --[[User:BrophY|BrophY]] 05:01, 6 April 2007 (CDT)
* <strike>Capture Vehicle Placements ( Random Locations )</strike> --[[User:BrophY|BrophY]] 05:01, 6 April 2007 (CDT)
* <strike>Scoreboard</strike> ''Include/Use Scoreboard Resource'' --[[User:BrophY|BrophY]] 08:35, 12 May 2007 (CDT)
* <strike>Normal Vehicle Placements</strike> --[[User:BrophY|BrophY]] 08:35, 12 May 2007 (CDT)
* Any Necessary Pickups
<br />
----
<br />
IJs and ChrML fear BrophY
<br /><br />
[[Image:BatChild.jpg]]

SetCameraMode

2007-05-07T11:03:23Z

BrophY:

__NOTOC__
<h2 style="margin:0; background:#990000; font-size:120%; font-weight:bold; border:1px solid #a3bfb1; text-align:left; color:#fff; padding:0.2em 0.4em;">Please remember to set players camera mode back to "player" on resource unload, or you will encounter the invisible player 'bug' if players camera is still set to fixed</h2>

This function allows you to change a player's camera mode to either "player" or "fixed".

==Syntax==
<syntaxhighlight lang="lua">
bool setCameraMode ( player thePlayer, string mode )
</syntaxhighlight>

===Required Arguments===
*'''thePlayer:''' The player whose camera you wish to modify.
*'''mode:''' The mode to be set. It has the following possible values:
** '''"player":''' Sets the camera to follow a player.
** '''"fixed":''' Fixes the camera in a set position/rotation.

===Returns===
Returns a [[bool]] with a value of ''true'' if the function was successful, ''false'' otherwise.

==Example==

==See Also==
{{Camera functions}}

[[Category:Incomplete]]

SetCameraMode

2007-05-07T11:02:45Z

BrophY: /* Syntax */

__NOTOC__
<h2 style="margin:0; background:#990000; font-size:120%; font-weight:bold; border:1px solid #a3bfb1; text-align:left; color:#fff; padding:0.2em 0.4em;">Please remember to set players camera mode back to "player" on resource unload, or you will encounter the invisible player 'bug'</h2>

This function allows you to change a player's camera mode to either "player" or "fixed".

==Syntax==
<syntaxhighlight lang="lua">
bool setCameraMode ( player thePlayer, string mode )
</syntaxhighlight>

===Required Arguments===
*'''thePlayer:''' The player whose camera you wish to modify.
*'''mode:''' The mode to be set. It has the following possible values:
** '''"player":''' Sets the camera to follow a player.
** '''"fixed":''' Fixes the camera in a set position/rotation.

===Returns===
Returns a [[bool]] with a value of ''true'' if the function was successful, ''false'' otherwise.

==Example==

==See Also==
{{Camera functions}}

[[Category:Incomplete]]

SetCameraMode

2007-05-07T11:01:29Z

BrophY:

__NOTOC__
<h2 style="margin:0; background:#cef2e0; font-size:120%; font-weight:bold; border:1px solid #a3bfb1; text-align:left; color:#000; padding:0.2em 0.4em;">Please remember to set camera mode back to player on resource unload, or you will encounter the invisible player 'bug', just set a loop for onResoureUnload</h2>

This function allows you to change a player's camera mode to either "player" or "fixed".

==Syntax==
<syntaxhighlight lang="lua">
bool setCameraMode ( player thePlayer, string mode )
</syntaxhighlight>

===Required Arguments===
*'''thePlayer:''' The player whose camera you wish to modify.
*'''mode:''' The mode to be set. It has the following possible values:
** '''"player":''' Sets the camera to follow a player.
** '''"fixed":''' Fixes the camera in a set position/rotation.

===Returns===
Returns a [[bool]] with a value of ''true'' if the function was successful, ''false'' otherwise.

==Example==

==See Also==
{{Camera functions}}

[[Category:Incomplete]]

SetCameraMode

2007-05-07T11:01:14Z

BrophY:

__NOTOC__
<h2 style="margin:0; background:#cef2e0; font-size:120%; font-weight:bold; border:1px solid #a3bfb1; text-align:left; color:#000; padding:0.2em 0.4em;">Please remember to set camera mode back to player on resource unload, or you will encounter the invisible player 'bug', just set a loop for onResoureUnload</h2>

This function allows you to change a player's camera mode to either "player" or "fixed".
==Syntax==
<syntaxhighlight lang="lua">
bool setCameraMode ( player thePlayer, string mode )
</syntaxhighlight>

===Required Arguments===
*'''thePlayer:''' The player whose camera you wish to modify.
*'''mode:''' The mode to be set. It has the following possible values:
** '''"player":''' Sets the camera to follow a player.
** '''"fixed":''' Fixes the camera in a set position/rotation.

===Returns===
Returns a [[bool]] with a value of ''true'' if the function was successful, ''false'' otherwise.

==Example==

==See Also==
{{Camera functions}}

[[Category:Incomplete]]

File:Mtalogo.png

2007-04-14T12:23:26Z

BrophY:

User:BrophY

2007-04-06T19:10:59Z

BrophY:

'''Capture the Vehicle'''
<br /><br />
Also thanks to Talidan and Dragon :)
<br /><br />
Tasks to be Completed:
<br /><br />
* <strike>SpawnScreen</strike> --[[User:BrophY|BrophY]] 05:01, 6 April 2007 (CDT)
* <strike>SpawnPoints</strike> --[[User:BrophY|BrophY]] 05:01, 6 April 2007 (CDT)
* <strike>Teams and Weapons</strike> --[[User:BrophY|BrophY]] 05:01, 6 April 2007 (CDT)
* <strike>Capture Markers</strike> --[[User:BrophY|BrophY]] 05:01, 6 April 2007 (CDT)
* <strike>Capture Vehicle Placements ( Random Locations )</strike> --[[User:BrophY|BrophY]] 05:01, 6 April 2007 (CDT)
* Scoreboard ( Probably a onscreen text based one, until we get a working on with team support ? )
* Normal Vehicle Placements
* Any Necessary Pickups
<br />
----
<br />
IJs and ChrML fear BrophY
<br /><br />
[[Image:BatChild.jpg]]

User:BrophY

2007-04-06T11:36:49Z

BrophY:

'''Capture the Vehicle'''
<br /><br />
Also thanks to Talidan and Dragon :)
<br /><br />
Tasks to be Completed:
<br /><br />
* <strike>SpawnScreen</strike> --[[User:BrophY|BrophY]] 05:01, 6 April 2007 (CDT)
* <strike>SpawnPoints</strike> --[[User:BrophY|BrophY]] 05:01, 6 April 2007 (CDT)
* <strike>Teams and Weapons</strike> --[[User:BrophY|BrophY]] 05:01, 6 April 2007 (CDT)
* <strike>Capture Markers</strike> --[[User:BrophY|BrophY]] 05:01, 6 April 2007 (CDT)
* <strike>Capture Vehicle Placements ( Random Locations )</strike> --[[User:BrophY|BrophY]] 05:01, 6 April 2007 (CDT)
* Scoreboard ( Probably a onscreen text based one, until we get a working on with team support ? )
* Normal Vehicle Placements
* Any Necessary Pickups
* Move stuff such as spawnpoints to .map XML
<br />
----
<br />
IJs and ChrML fear BrophY
<br /><br />
[[Image:BatChild.jpg]]

User:BrophY

2007-04-06T10:10:28Z

BrophY:

'''Capture the Vehicle'''
<br /><br />
Also thanks to Talidan and Dragon :)
<br /><br />
Tasks to be Completed:
<br /><br />
* <strike>SpawnScreen</strike> --[[User:BrophY|BrophY]] 05:01, 6 April 2007 (CDT)
* <strike>SpawnPoints</strike> --[[User:BrophY|BrophY]] 05:01, 6 April 2007 (CDT)
* <strike>Teams and Weapons</strike> --[[User:BrophY|BrophY]] 05:01, 6 April 2007 (CDT)
* <strike>Capture Markers</strike> --[[User:BrophY|BrophY]] 05:01, 6 April 2007 (CDT)
* <strike>Capture Vehicle Placements ( Random Locations )</strike> --[[User:BrophY|BrophY]] 05:01, 6 April 2007 (CDT)
* Scoreboard ( Proberly a onscreen text based one, until we get a working on with team support ? )
* Normal Vehicle Placements
* Any Necessary Pickups
* Move stuff such as spawnpoints to .map XML
<br />
----
<br />
IJs and ChrML fear BrophY
<br /><br />
[[Image:BatChild.jpg]]

User:BrophY

2007-04-06T10:01:47Z

BrophY:

'''Capture the Vehicle'''
<br /><br />
Also thanks to Talidan and Dragon :)
<br /><br />
Tasks to be Completed:
<br /><br />
* <strike>SpawnScreen</strike> --[[User:BrophY|BrophY]] 05:01, 6 April 2007 (CDT)
* <strike>SpawnPoints</strike> --[[User:BrophY|BrophY]] 05:01, 6 April 2007 (CDT)
* <strike>Teams and Weapons</strike> --[[User:BrophY|BrophY]] 05:01, 6 April 2007 (CDT)
* <strike>Capture Markers</strike> --[[User:BrophY|BrophY]] 05:01, 6 April 2007 (CDT)
* <strike>Capture Vehicle Placements ( Random Locations )</strike> --[[User:BrophY|BrophY]] 05:01, 6 April 2007 (CDT)
* Normal Vehicle Placements
* Any Necessary Pickups
* Move stuff such as spawnpoints to .map XML
<br />
----
<br />
IJs and ChrML fear BrophY
<br /><br />
[[Image:BatChild.jpg]]

User:BrophY

2007-04-06T10:00:42Z

BrophY:

'''Capture the Vehicle'''
<br /><br />
Also thanks to Talidan and Dragon :)
<br /><br />
Tasks to be Completed:
<br /><br />
* <strike>SpawnScreen</strike> --[[User:BrophY|BrophY]] 04:58, 6 April 2007 (CDT)
* <strike>SpawnPoints</strike> --[[User:BrophY|BrophY]] 04:58, 6 April 2007 (CDT)
* <strike>Teams and Weapons</strike> --[[User:BrophY|BrophY]] 04:58, 6 April 2007 (CDT)
* <strike>Capture Markers</strike> --[[User:BrophY|BrophY]] 04:58, 6 April 2007 (CDT)
* <strike>Capture Vehicle Placements ( Random Locations )</strike> --[[User:BrophY|BrophY]] 04:58, 6 April 2007 (CDT)
* Normal Vehicle Placements
* Any Necessary Pickups
* Move stuff such as spawnpoints to .map XML
<br />
----
<br />
IJs and ChrML fear BrophY
<br /><br />
[[Image:BatChild.jpg]]

User:BrophY

2007-04-06T09:59:44Z

BrophY:

'''Capture the Vehicle'''
<br />
Tasks to be Completed:
<br />
Also thanks to Talidan and Dragon :)
<br />
* <strike>SpawnScreen</strike> --[[User:BrophY|BrophY]] 04:58, 6 April 2007 (CDT)
* <strike>SpawnPoints</strike> --[[User:BrophY|BrophY]] 04:58, 6 April 2007 (CDT)
* <strike>Teams and Weapons</strike> --[[User:BrophY|BrophY]] 04:58, 6 April 2007 (CDT)
* <strike>Capture Markers</strike> --[[User:BrophY|BrophY]] 04:58, 6 April 2007 (CDT)
* <strike>Capture Vehicle Placements ( Random Locations )</strike> --[[User:BrophY|BrophY]] 04:58, 6 April 2007 (CDT)
* Normal Vehicle Placements
* Any Necessary Pickups
* Move stuff such as spawnpoints to .map XML
<br />
----
<br />
IJs and ChrML fear BrophY

[[Image:BatChild.jpg]]

User:BrophY

2007-04-06T09:58:38Z

BrophY:

'''BrophY'''
----

'''Capture the Vehicle'''

Tasks to be Completed:

Also thanks to Talidan and Dragon :)

* <strike>SpawnScreen</strike> --[[User:BrophY|BrophY]] 04:58, 6 April 2007 (CDT)
* <strike>SpawnPoints</strike> --[[User:BrophY|BrophY]] 04:58, 6 April 2007 (CDT)
* <strike>Teams and Weapons</strike> --[[User:BrophY|BrophY]] 04:58, 6 April 2007 (CDT)
* <strike>Capture Markers<strike> --[[User:BrophY|BrophY]] 04:58, 6 April 2007 (CDT)
* <strike>Capture Vehicle Placements ( Random Locations )</strike> --[[User:BrophY|BrophY]] 04:58, 6 April 2007 (CDT)
* Normal Vehicle Placements
* Any Necessary Pickups
* Move stuff such as spawnpoints to .map XML

----

IJs and ChrML fear BrophY

[[Image:BatChild.jpg]]

Advanced Topics

2007-03-24T16:16:50Z

BrophY:

This page explains some advanced things you can do with scripts, this page should probably be changed later, depending how useful it is.

==Custom element types==
One of the most powerful areas of MTA scripting is custom element types. These types can be defined in map files and their functionality implemented by scripts. In this example, we're going to look at a custom ''flag'' element, such as you would use in a ''capture-the-flag'' game-mode, though this same method could be used for many different things.

First of all you need to decide what format you want the element to be defined in, we're going to use the following:
<syntaxhighlight lang="lua">[pua,N]
<flag id="redFlag" name="red team flag" posX="1210.0" posY="-2241.34" posZ="18.4332" />
</syntaxhighlight>

Now you can define the flag element in the map file.

Next, you can write some code to handle your flag element. First of all, lets add an event that happens when you pick it up, called ''onFlagPickup''. We should do this in an external script file, lets call this ''capture-the-flag.lua''. At the top of the file (outside any functions), define the event:

<syntaxhighlight lang="lua">
addEvent ( "onFlagPickup", "player" )
</syntaxhighlight>

Easy enough! We've added an event that will have a parameter called ''player''. We'll use this to say which player picked up the flag. Next, we have a choice. Either we can add an event handler to the root of the map, and capture every flag pickup event, or we can add it to the individual flag. Its easiest if we use the root of the map, so lets do this here:

<syntaxhighlight lang="lua">
mapRoot = getRootElement ( )
addEventHandler ( "onFlagPickup", mapRoot, "flagPickup" )
</syntaxhighlight>

This says that we want to direct all ''onFlagPickup'' events to our function called ''flagPickup'', that we're about to define on the following line:

<syntaxhighlight lang="lua">
function flagPickup ( player )
flagName = getElementData ( source, "name" )
playerName = getPlayerName ( player )
outputChatBox ( playerName .. " picked up the flag " .. flagName )
end
</syntaxhighlight>

The final part of the puzzle is to make it so that the event is triggered at the correct time. To do this, we'll need to create a timer that will be used to check if a player is trying to pick up the flag. Put the following code below your previous [[addEventHandler]] call:

<syntaxhighlight lang="lua">
setTimer ( "flagCheckPulse", 1000 )
</syntaxhighlight>

This will make our soon-to-be-defined function ''flagCheckPulse'' be called every second. Now we'll define this function:

<syntaxhighlight lang="lua">
function flagCheckPulse ( )
local flags = getElementsByType ( "flag" )
local players = getElementsByType ( "player" )
local flagPositionX, flagPositionY, flagPositionZ
for flagKey,flagValue in flags do
flagX = getElementData ( flagValue, "posX" )
flagY = getElementData ( flagValue, "posY" )
flagZ = getElementData ( flagValue, "posZ" )
for playerKey,playerValue in players do
playerX, playerY, playerZ = getEntityPosition ( playerValue )
distance = getDistanceBetweenPoints3D ( flagX, flagY, flagZ, playerX, playerY, playerZ )
if ( distance < 1) then
triggerEvent ( "onFlagPickup", flagValue, playerValue )
end
end
end
setTimer ( "flagCheckPulse", 1000 )
end
</syntaxhighlight>

And thats it!

Note: Although this should work, its not tested. Some things could be improved if better support was provided by us, for example, theres no getPlayerByIndex, no getElementCount(type), an onPlayerPulse event would be useful. This currently only works for one flag, as theres I'm not sure how to find how many flags getElementByType ( "flag" ) returned.

Next: representing the flag in the world - spawning an object at the flags position.

Advanced Topics

2007-03-24T16:16:26Z

BrophY:

This page explains some advanced things you can do with scripts, this page should probably be changed later, depending how useful it is.

==Custom element types==
One of the most powerful areas of MTA scripting is custom element types. These types can be defined in map files and their functionality implemented by scripts. In this example, we're going to look at a custom ''flag'' element, such as you would use in a ''capture-the-flag'' game-mode, though this same method could be used for many different things.

First of all you need to decide what format you want the element to be defined in, we're going to use the following:
<syntaxhighlight lang="lua">[xml,N]
<flag id="redFlag" name="red team flag" posX="1210.0" posY="-2241.34" posZ="18.4332" />
</syntaxhighlight>

Now you can define the flag element in the map file.

Next, you can write some code to handle your flag element. First of all, lets add an event that happens when you pick it up, called ''onFlagPickup''. We should do this in an external script file, lets call this ''capture-the-flag.lua''. At the top of the file (outside any functions), define the event:

<syntaxhighlight lang="lua">
addEvent ( "onFlagPickup", "player" )
</syntaxhighlight>

Easy enough! We've added an event that will have a parameter called ''player''. We'll use this to say which player picked up the flag. Next, we have a choice. Either we can add an event handler to the root of the map, and capture every flag pickup event, or we can add it to the individual flag. Its easiest if we use the root of the map, so lets do this here:

<syntaxhighlight lang="lua">
mapRoot = getRootElement ( )
addEventHandler ( "onFlagPickup", mapRoot, "flagPickup" )
</syntaxhighlight>

This says that we want to direct all ''onFlagPickup'' events to our function called ''flagPickup'', that we're about to define on the following line:

<syntaxhighlight lang="lua">
function flagPickup ( player )
flagName = getElementData ( source, "name" )
playerName = getPlayerName ( player )
outputChatBox ( playerName .. " picked up the flag " .. flagName )
end
</syntaxhighlight>

The final part of the puzzle is to make it so that the event is triggered at the correct time. To do this, we'll need to create a timer that will be used to check if a player is trying to pick up the flag. Put the following code below your previous [[addEventHandler]] call:

<syntaxhighlight lang="lua">
setTimer ( "flagCheckPulse", 1000 )
</syntaxhighlight>

This will make our soon-to-be-defined function ''flagCheckPulse'' be called every second. Now we'll define this function:

<syntaxhighlight lang="lua">
function flagCheckPulse ( )
local flags = getElementsByType ( "flag" )
local players = getElementsByType ( "player" )
local flagPositionX, flagPositionY, flagPositionZ
for flagKey,flagValue in flags do
flagX = getElementData ( flagValue, "posX" )
flagY = getElementData ( flagValue, "posY" )
flagZ = getElementData ( flagValue, "posZ" )
for playerKey,playerValue in players do
playerX, playerY, playerZ = getEntityPosition ( playerValue )
distance = getDistanceBetweenPoints3D ( flagX, flagY, flagZ, playerX, playerY, playerZ )
if ( distance < 1) then
triggerEvent ( "onFlagPickup", flagValue, playerValue )
end
end
end
setTimer ( "flagCheckPulse", 1000 )
end
</syntaxhighlight>

And thats it!

Note: Although this should work, its not tested. Some things could be improved if better support was provided by us, for example, theres no getPlayerByIndex, no getElementCount(type), an onPlayerPulse event would be useful. This currently only works for one flag, as theres I'm not sure how to find how many flags getElementByType ( "flag" ) returned.

Next: representing the flag in the world - spawning an object at the flags position.

CreateExplosion

2007-03-21T10:33:46Z

BrophY: /* Example */

__NOTOC__
Creates an explosion of a certain type at a specified point in the world.

==Syntax==
<syntaxhighlight lang="lua">createExplosion ( float x, float y, float z, int type, [ player creator ] )</syntaxhighlight>

===Required Arguments===
*'''x:''' A float value that specifies the X coordinate where the object is spawned at in the [[world]]
*'''y:''' A float value that specifies the Y coordinate where the object is spawned at in the world
*'''z:''' A float value that specifies the Z coordinate where the object is spawned at in the world
*'''type:''' A integer specifying the explosion type. Valid types are:
{{Explosions}}

===Optional Arguments===
*'''creator:''' The explosion's simulated creator, responsible for it.

==Example==
This code will create an explosion at the player's position when they spawn.
<syntaxhighlight lang="lua">root = getRootElement ()
addEventHandler ( "onPlayerSpawn", root, "onPlayerSpawn" )
function onPlayerSpawn ( spawnpoint )
createExplosion ( getElementPosition ( source ), 6, source )
end</syntaxhighlight>

==See Also==
{{Explosion functions}}

CreateExplosion

2007-03-21T10:33:26Z

BrophY: /* Example */

GetGravity

2007-03-13T11:02:17Z

BrophY:

__NOTOC__
==Description==
This function returns the current gravity level

==Syntax==
<syntaxhighlight lang="lua">getGravity ()</syntaxhighlight>

==Example==
<syntaxhighlight lang="lua">addCommandHandler ( "gravity", "gravlevel" )
function gravlevel ()
local gravity = getGravity ( )
outputConsole ( "The Gravity is currently set to " ..gravity )
end</syntaxhighlight>

==See Also==
{{World functions}}

SetGravity

2007-03-13T10:59:38Z

BrophY: /* Example */

__NOTOC__
==Description==
This function sets the servers gravity level

==Syntax==
<syntaxhighlight lang="lua">setGravity ( float level )</syntaxhighlight>

===Required Arguments===
*'''level''': The level of gravity ( default is <b>0.008</b> )

==Example==
<syntaxhighlight lang="lua">addCommandHandler ( "setgravity", "grav" )
function grav ( source, command, gravid )
setGravity ( gravid )
end</syntaxhighlight>

==See Also==
{{World functions}}

SetGravity

2007-03-13T10:59:14Z

BrophY:

SetPlayerFightingStyle

2007-03-05T20:29:27Z

BrophY:

__NOTOC__
Sets a player's fighting style

ILL PUT LIST HERE IN A BIT

values from 4-16

==Syntax==
<syntaxhighlight lang="lua">setPlayerFightingStyle ( player, int style ) </syntaxhighlight>

===Required Arguments===
*'''Player:''' Tells the function to give the fighting style to a player
*'''Style:''' A whole integer specifying the style of fighting you want to give to the player

==Example==
This example sets the player's fighting style to the desired style when he types "style" folldowed by a number from 4 to 16 in console.
<syntaxhighlight lang="lua">addCommandHandler ( "style", "style" ) -- add a command handler for setcash
function style ( player, command, id ) --when the style function is called
setPlayerFightingStyle ( player, id ) --set players fighting style
end</syntaxhighlight>

==See Also==
{{Player functions}}

User:BrophY

2007-02-02T17:06:34Z

BrophY:

'''BrophY'''
----
IJs and ChrML fear BrophY

[[Image:BatChild.jpg]]

Server Scripting Events

2007-01-26T11:59:10Z

BrophY:

{{Critical_Update|This entire section is undergoing a function-use change. It no longer lists functions designed to handle events, but instead should list all the events themselves, and the arguments they supply, along with information regarding the use of addEventHandler, and instructions detailing how to insert event handlers into the XML code.|[[User:Vandalite|Vandalite]]}}

This is a list of scripting events that currently exist. More will come soon.

===Server Events===
void [[onClientLogin]] ( [[account]] previous_account, [[account]] current_account, bool auto-login )

void [[onClientLogout]] ( [[account]] previous_account, [[account]] current_account )

void [[onColShapeHit]] ( [[player]] player, bool matchingDimension )

void [[onColShapeLeave]] ( [[player]] player, bool matchingDimension )

void [[onConsole]] ( string message )

void [[onElementDataChange]] ( string name )

void [[onElementColShapeHit]] ( [[colshape]] hitcolshape, bool matchingDimension )

void [[onElementColShapeLeave]] ( [[colshape]] leftcolshape, bool matchingDimension )

void [[onElementClicked]] ( string button, string state, [[player]] clicker, float posX, float posY, float posZ )

void [[onMarkerHit]] ( [[player]] hitplayer, bool matchingDimension )

void [[onPlayerChat]] ( string message, bool teamchat )

void [[onPlayerDamage]] ( [[player]] attacker, int attackerweapon, int bodypart, float loss )

void [[onPlayerJoin]] ()

void [[onPlayerQuit]] ( string reason )

void [[onPlayerSpawn]] ( [[spawnpoint]] spawnpoint, team )

void [[onPlayerWasted]] ( int ammo, [[player]] killer, int killerweapon, int bodypart )

void [[onPlayerTarget]] ( [[element]] targetedElement )

void [[onPlayerEnterVehicle]] ( [[vehicle]] vehicle, int seat, [[player]] jacked )

void [[onPlayerExitVehicle]] ( [[vehicle]] vehicle, int seat, [[player]] jacker )

void [[onPlayerWeaponSwitch]] ( int previousWeaponID, int currentWeaponID )

void [[onPlayerTask]] ( string priority, int type, string name )

void [[onPlayerMarkerHit]] ( [[marker]] hitmarker, bool matchingDimension )

void [[onPlayerPickupHit]] ( [[pickup]] hitpickup, bool matchingDimension )

void [[onPlayerPickupUse]] ( [[pickup]] usedpickup )

void [[onPickupSpawn]] ()

void [[onPickupHit]] ( [[player]] player, bool matchingDimension )

void [[onPickupUse]] ( [[player]] player )

void [[onPlayerClick]] ( string button, string state, [[element]] clickedElement, float posX, float posY, float posZ )

void [[onResourceStart]] ( string name )

void [[onResourceStop]] ()

void [[onSpawnpointUse]] ( [[player]] player )

void [[onTrailerAttach]] ( [[vehicle]] towedBy )

void [[onTrailerDetach]] ( [[vehicle]] towedBy )

void [[onVehicleDamage]] ( float loss )

void [[onVehicleRespawn]] ( bool explosion )

void [[onVehicleStartEnter]] ( [[player]] player, int seat, [[player]] jacked )

void [[onVehicleStartExit]] ( [[player]] player, int seat, [[player]] jacker )

void [[onVehicleEnter]] ( [[player]] player, int seat, [[player]] jacked )

void [[onVehicleExit]] ( [[player]] player, int seat, [[player]] jacker )

void [[onVehicleExplode]] ()

===Client Events===
void [[onClientMapLoad]] ( string name )

void [[onClientMapUnload]] ( void )

void [[onClientWeaponFire]] ( int weapon, int ammo, int ammoInClip, float hitX, float hitY, float hitZ, [[element]] hitElement )

<div style="border: 3px solid green;padding:5px">WARNING: These events will change their names to onClientGUI... in the near future</div>
bool [[guiWindowEventOnKeyDown]] ( [[element]] theElement, callback )

bool [[guiWindowEventOnClose]] ( [[element]] theElement, callback )

bool [[guiEditEventOnChanged]] ( [[element]] theElement, callback )

bool [[guiEditEventOnAccepted]] ( [[element]] theElement, callback )

OnResourceStop

2007-01-26T11:58:17Z

BrophY:

[[Category:Incomplete Event]]
This event is triggered when the resource is changed or unloaded.

==Example==
This example displays a message in the textbox when the resource is changed / unloaded

<syntaxhighlight lang="lua">

addEventHandler ( "onResourceStop", root, "onResourceStop" )
function onResourceStop ( )
outputChatBox ( "Script Unloaded!", root, 255, 255, 255 )
end

</syntaxhighlight>

OnResourceUnload

2007-01-26T11:57:38Z

BrophY:

This function doesnt exist, its [[onResourceStop]]

OnResourceLoad

2007-01-26T11:56:51Z

BrophY:

This function doesnt exist, its [[onResourceStart]]

OnResourceLoad

2007-01-26T11:55:33Z

BrophY: