Multi Theft Auto: Wiki - User contributions [en]

Talk:SetPedAnimation

2012-09-04T20:10:28Z

Jasper Wiljijwelwetenhea: /* Lol at example 2 */ new section

Why is there only the ''one'' ped argument actually needed? An argument specyfing if it should start or cancel would be more useful imo [[User:1337MaVe|1337MaVe]] 07:32, 9 August 2009 (UTC)

== Lol at example 2 ==

Why would you setElementData when the camera renders client-side? This is retarded.

GetGaragePosition

2011-01-15T16:17:24Z

Jasper Wiljijwelwetenhea: Example edited

__NOTOC__
{{client function}}
This function outputs X, Y and Z position of given garage.

==Syntax==
<syntaxhighlight lang="lua">
float, float, float getGaragePosition ( int garageID )
</syntaxhighlight>

===Required Arguments===
*'''garageID:''' The [[Garage|garage ID]] that represents the garage door that is being checked.

===Returns===
Returns three ''float''s indicating the position of the garage, ''x'', ''y'' and ''z'' respectively.

==Example==
<section name="Client" class="client" show="true">
This element has to create a blip at the nearest garage and removes it in 10 seconds.
<syntaxhighlight lang="lua">
function getNearestGarageFromElement (element)
nearestID = -1
nearestDistance = 999999999999
local ex,ey,ez = getElementPosition (element)
for i=0,49 do
local x,y,z = getGaragePosition (i)
if (getDistanceBetweenPoints3D (ex,ey,ez,x,y,z) < nearestDistance) then
nearestID = i
nearestDistance = getDistanceBetweenPoints3D (ex,ey,ez,x,y,z)
end
end
local _nearestID = nearestID
nearestID = nil
return _nearestID
end

addCommandHandler ("findgarage",
function(command)
local garageID = getNearestGarageFromElement (getLocalPlayer())
if (garageID ~= -1) then
local x,y,z = getGaragePosition (garageID)
local garageBlip = createBlip (x,y,z,41)
setTimer (
function (garageBlip)
destroyElement (garageBlip)
end
,10000,1,garageBlip)
end
end)
</syntaxhighlight>
</section>

==See Also==
{{Client world functions}}
[[Category:Needs_More_Examples]]

Dictionary

2011-01-09T21:09:01Z

Jasper Wiljijwelwetenhea:

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
The act of being cheered by JasperNL=D

* 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
-<s>Being cheered by JasperNL=D</s>

* 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.

BindKey

2011-01-09T21:08:13Z

Jasper Wiljijwelwetenhea: /* Example */

{{Server client function}}
__NOTOC__
Binds a player's key to a handler function or command, which will be called when the key is pressed.

==Syntax==
<section name="Server - Syntax 1" class="server" show="true">
<syntaxhighlight lang="lua">bindKey ( player thePlayer, string key, string keyState, function handlerFunction, [ var arguments, ... ] )</syntaxhighlight>

===Required Arguments===
*'''thePlayer:''' The player you wish to bind the key of.
*'''key:''' The key or control you wish to bind to the command. See [[key names]] for a list of possible keys and [[control names]] for a list of possible controls.
*'''keyState:''' A string that has one of the following values:
**'''"up":''' If the bound key should trigger the function when the key is released
**'''"down":''' If the bound key should trigger the function when the key is pressed
**'''"both":''' If the bound key should trigger the function when the key is pressed or released
*'''handlerFunction:''' The function that will be triggered when the player's key is pressed. This function should have the form:
:<syntaxhighlight lang="lua">function functionName ( player keyPresser, string key, string keyState, [ var arguments, ... ] )</syntaxhighlight>
:The values passed to this function are:
:*'''keyPresser:''' The player who pressed the key
:*'''key:''' The key that was pressed
:*'''keyState:''' The state of the key that was pressed, ''down'' if it was pressed, ''up'' if it was released.
:*'''arguments''' The optional arguments you specified when calling [[bindKey]] (see below).
</section>

{{New feature|3|1.0|
<section name="Server - Syntax 2" class="server" show="true">
This alternative syntax allows you to bind a key with a command. This will also allow users to customize the control in their Settings menu. Use in conjunction with [[addCommandHandler]] to add handler functions to the keybind.

<syntaxhighlight lang="lua">bindKey ( player thePlayer, string key, string keyState, string commandName, string arguments )</syntaxhighlight>

===Required Arguments===
*'''thePlayer:''' The player you wish to bind the key of.
*'''key:''' The key or control you wish to bind to the command. See [[key names]] for a list of possible keys.
*'''keyState:''' A string that has one of the following values:
**'''"up":''' If the bound key should trigger the function when the key is released
**'''"down":''' If the bound key should trigger the function when the key is pressed
**'''"both":''' If the bound key should trigger the function when the key is pressed or released
*'''commandName:''' The name of the command that the key should be binded to.
*'''arguments''' Space delimited arguments that are entered as if one was typing the command.
</section>
}}

<section name="Client - Syntax 1" class="client" show="true">
<syntaxhighlight lang="lua">bindKey ( string key, string keyState, function handlerFunction, [ var arguments, ... ] ) </syntaxhighlight>

===Required Arguments===
*'''key:''' The key or control you wish to bind to the command. See [[key names]] for a list of possible keys and [[control names]] for a list of possible controls.
*'''keyState:''' A string that has one of the following values:
**'''"up":''' If the bound key should trigger the function when the key is released
**'''"down":''' If the bound key should trigger the function when the key is pressed
**'''"both":''' If the bound key should trigger the function when the key is pressed or released

*'''handlerFunction:''' The function that will be triggered when the player's key is pressed. This function should have the form:
:<syntaxhighlight lang="lua">function functionName ( string key, string keyState, [ var arguments, ... ] )</syntaxhighlight>
:The values passed to this function are:
:*'''key:''' The key that was pressed
:*'''keyState:''' The state of the key that was pressed, ''down'' if it was pressed, ''up'' if it was released.
:*'''arguments''' The optional arguments you specified when calling [[bindKey]] (see below).
</section>

{{New feature|3|1.0|
<section name="Client - Syntax 2" class="client" show="true">
This alternative syntax allows you to bind a key with a command. This will also allow users to customize the control in their Settings menu. Use in conjunction with [[addCommandHandler]] to add handler functions to the keybind.

<syntaxhighlight lang="lua">bindKey ( string key, string keyState, string commandName, string arguments )</syntaxhighlight>

===Required Arguments===
*'''key:''' The key or control you wish to bind to the command. See [[key names]] for a list of possible keys.
*'''keyState:''' A string that has one of the following values:
**'''"up":''' If the bound key should trigger the function when the key is released
**'''"down":''' If the bound key should trigger the function when the key is pressed
**'''"both":''' If the bound key should trigger the function when the key is pressed or released
*'''commandName:''' The name of the command that the key should be binded to.
*'''arguments''' Space delimited arguments that are entered as if one was typing the command.
</section>
}}

===Optional Arguments===
{{OptionalArg}}
*'''arguments:''' Any arguments you may want to pass to the function when the key is pressed by the user. Any number of arguments of can be specified, each being passed to the designated function. You may not pass functions.

==Example==
Example 1
<section name="Server" class="server" show="true">
This example will bind a player's 'F1' key and 'fire' control to 1 input function.
<syntaxhighlight lang="lua">
function funcInput ( player, key, keyState )
local state = "let go of"
if ( keyState == "down" ) then
state = "pressed"
end
outputChatBox ( getPlayerName ( player) .. " " .. state .. " the " .. key .. " key!" )
end

function bindTheKeys ( player, commandName )
bindKey ( player, "F1", "down", funcInput ) -- bind the player's F1 down key
bindKey ( player, "F1", "up", funcInput ) -- bind the player's F1 up key
bindKey ( player, "fire", "both", funcInput ) -- bind the player's fire down and up control
end
addCommandHandler ( "bindme", bindTheKeys )
</syntaxhighlight>
</section>

Example 2
<section name="Client" class="client" show="true">
This example will bind a player's 'F1' key and 'fire' control to 1 input function, clientside.
<syntaxhighlight lang="lua">
function funcInput ( key, keyState )
local state = "let go of"
if ( keyState == "down" ) then
state = "pressed"
end
outputChatBox ( "You " .. state .. " the " .. key .. " key!" )
end

function bindTheKeys ()
bindKey ( "F1", "down", funcInput ) -- bind the player's F1 down key
bindKey ( "F1", "up", funcInput ) -- bind the player's F1 up key
bindKey ( "fire", "both", funcInput ) -- bind the player's fire down and up control
end
addCommandHandler ( "bindme", bindTheKeys )
</syntaxhighlight>
</section>

<section name="Server" class="server" show="true">
This example says how cool <s>Robpol86</s> Ransom is if players wants to move.
<syntaxhighlight lang="lua">
function fanFunction()
bindKey (source,"forwards","down",
function(player,key,state)
outputChatBox (getPlayerName (player) .. "#FFFF00 thinks Ransom is cool.",getRootElement(),255,255,0,true)
end
)
end
addEventHandler ("onPlayerLogin",getRootElement(),fanFunction)
</syntaxhighlight>
</section>

==See Also==
{{Input functions}}

Dictionary

2011-01-09T20:25:36Z

Jasper Wiljijwelwetenhea:

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
-Being cheered by JasperNL=D

* 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.

OnClientDebugMessage

2011-01-09T11:19:41Z

Jasper Wiljijwelwetenhea: /* Example */

__NOTOC__
{{Server event}}
This event is triggered when client-side debug messages (for instance errors or warnings) would appear in the debug window. This event doesn't require the debug window to be enabled to trigger, however.

==Parameters==
<syntaxhighlight lang="lua">
string message, int level, string file, int line
</syntaxhighlight>

*'''message''': The message which was outputted in the server console, without details like file, line etc
*'''level''': The type of debug message which was outputted
**'''0:''' "Custom" message
**'''1:''' Error message
**'''2:''' Warning message
**'''3:''' Information message
*'''file''': The file from which the debug message was outputted
**'''Note:''' May return [[nil]] when the source could not be found
*'''line''': The line in file '''file''' where the debug message was outputted
**'''Note:''' May return [[nil]] when the source could not be found

==Source==
The [[event system#Event source|source]] of this event is the [[root element]].

==Example==
This (easy) example outputs the debug message in the console, so you don't need to open debugscript 3 :D
<syntaxhighlight lang="lua">
addEventHandler ("onClientDebugMessage",getRootElement(),
function(message,level,file,line)
outputConsole (message,getLocalPlayer())
end)
</syntaxhighlight>

==See Also==
===Other client events===
{{Client_other_events}}
===Client event functions===
{{Client_event_functions}}

[[Category:Needs_Example]]

GetGaragePosition

2011-01-09T11:15:30Z

Jasper Wiljijwelwetenhea: Example.

__NOTOC__
{{client function}}
This function outputs X, Y and Z position of given garage.

==Syntax==
<syntaxhighlight lang="lua">
float, float, float getGaragePosition ( int garageID )
</syntaxhighlight>

===Required Arguments===
*'''garageID:''' The [[Garage|garage ID]] that represents the garage door that is being checked.

===Returns===
Returns three ''float''s indicating the position of the garage, ''x'', ''y'' and ''z'' respectively.

==Example==
<section name="Client" class="client" show="true">
This element has to create a blip at the nearest garage and removes it in 10 seconds. (untested)
<syntaxhighlight lang="lua">
function getNearestGarageFromElement (element)
local nearestID = -1
local nearestDistance = 999999999999
local ex,ey,ez = getElementPosition (element)
for i=0,49 do
local x,y,z = getGaragePosition (i)
if (getDistanceBetweenPoints3D (ex,ey,ez,x,y,z) < nearestDistance) then
local nearestID = i
end
end
return nearestID
end

addCommandHandler ("findgarage",
function(command)
local garageID = getNearestGarageFromElement (getLocalPlayer())
if (garageID ~= -1) then
local x,y,z = getGaragePosition (garageID)
local garageBlip = createBlip (x,y,z,41)
setTimer (
function (garageBlip)
destroyElement (garageBlip)
end
,10000,1,garageBlip)
end
end)
</syntaxhighlight>
</section>

==See Also==
{{Client world functions}}
[[Category:Needs_More_Examples]]

HasObjectPermissionTo

2011-01-09T11:05:44Z

Jasper Wiljijwelwetenhea: /* Example */

__NOTOC__
{{Server function}}
This function returns whether or not the given object has access to perform the given action.

Scripts frequently wish to limit access to features to particular users. The naïve way to do this would be to check if the player who is attempting to perform an action is in a particular group (usually the Admin group). The main issue with doing this is that the Admin group is not guaranteed to exist. It also doesn't give the server admin any flexibility. He might want to allow his 'moderators' access to the function you're limiting access to, or he may want it disabled entirely.

This is where using the ACL properly comes in, and luckily this is very easy. It all comes down to using this function. This, somewhat confusingly named function lets you check if an ACL object (a player or a resource) has a particular ACL right. In this case, we just care about players.

So, first of all, think of a name for your 'right'. Let's say we want a private area only certain people can go in, we'll call our right accessPrivateArea. Then, all you need to do is add one 'if' statement to your code:
<syntaxhighlight lang="lua">if hasObjectPermissionTo ( player, "resource.YourResourceName.accessPrivateArea", false ) then
-- Whatever you want to happen if they're allowed in
else
-- Whatever you want to happen if they aren't
end
</syntaxhighlight>

Notice that we've named the ''right'' using ''resource.YourResourceName.accessPrivateArea'' - this is just for neatness, so that the admin knows what resource the right belongs to. It's strongly advised you follow this convention. The ''false'' argument specifies the 'defaultPermission', false indicating that if the user hasn't had the right allowed or dissallowed (i.e. the admin hasn't added it to the config), that it should default to being not allowed.

The only downside of using this method is that the admin has to modify his config. The upsides are that the admin has much more control and your script will work for any server, however the admin has configured it.

==Syntax==
<syntaxhighlight lang="lua">
bool hasObjectPermissionTo ( string / element theObject, string theAction [, bool defaultPermission = true ] )
</syntaxhighlight>

===Required Arguments===
*'''theObject:''' The object to test if has permission to. This can be a client element (ie. a player), a resource or a string in the form "user.<name>" or "resource.<name>".
*'''theAction:''' The action to test if the given object has access to. Ie. "function.kickPlayer".

===Optional Arguments===
{{OptionalArg}}
*'''defaultPermission:''' The default permission if none is specified in either of the groups the given object is a member of. If this is left to true, the given object will have permissions to perform the action unless the opposite is explicitly specified in the [[ACL]]. If false, the action will be denied by default unless explicitly approved by the [[Access Control List]].

===Returns===
Returns ''true'' if the given object has permission to perform the given action, ''false'' otherwise. Returns ''nil'' if the function failed because of bad arguments.

==Example==
This example kicks a player if the user using it has access to the kickPlayer function.
<syntaxhighlight lang="lua">
-- Ban command
function onKickCommandHandler ( playerSource, commandName, playerToKick, stringReason )
-- Does the calling user have permission to kick the player? Default
-- to false for safety reasons. We do this so any user can't use us to
-- kick players.
if ( hasObjectPermissionTo ( playerSource, "function.kickPlayer", false ) ) then

-- Do we have permission to kick the player? We do this so we can fail
-- nicely if this resource doesn't have access to call that function.
if ( hasObjectPermissionTo ( getThisResource (), "function.kickPlayer", true ) ) then
-- Kick him
kickPlayer ( playerToKick, playerSource, stringReason )
else
-- Resource doesn't have any permissions, sorry
outputChatBox ( "kick: The admin resource is not able to kick players. Please give this resource access to 'function.kickPlayer' in the ACL to use this function.", playerSource )
end
else
-- User doesn't have any permissions
outputChatBox ( "kick: You don't have permissions to use this command.", playerSource )
end
end
addCommandHandler ( "kick", onKickCommandHandler )
</syntaxhighlight>

This function checks if a player is admin
<syntaxhighlight lang="lua">
function isAdmin (player)
if (hasObjectPermissionTo (player,"command.aexec",false)) then
return true
else
return false
end
end

</syntaxhighlight>

==See Also==

{{ACL_functions}}

Talk:Element/Ped

2011-01-09T11:03:27Z

Jasper Wiljijwelwetenhea:

Not that this is a forum but, I've been trying to use the function createPed and it keeps returning an error about a nil value.
If anyone has any information about this particular function please add it in here thanks.

== createPed() is a DP3 function ==

If you check [[CreatePed]] page, it clearly says "From version DP3 onwards". --[[User:Ryden|Ryden]] 12:13, 19 August 2008 (CEST)

No dimension thing? --[[User:Jasper Wiljijwelwetenhea|JasperNL=D]] 11:03, 9 January 2011 (UTC)

BindKey

2011-01-08T10:58:51Z

Jasper Wiljijwelwetenhea: /* Example */

{{Server client function}}
__NOTOC__
Binds a player's key to a handler function or command, which will be called when the key is pressed.

==Syntax==
<section name="Server - Syntax 1" class="server" show="true">
<syntaxhighlight lang="lua">bindKey ( player thePlayer, string key, string keyState, function handlerFunction, [ var arguments, ... ] )</syntaxhighlight>

===Required Arguments===
*'''thePlayer:''' The player you wish to bind the key of.
*'''key:''' The key or control you wish to bind to the command. See [[key names]] for a list of possible keys and [[control names]] for a list of possible controls.
*'''keyState:''' A string that has one of the following values:
**'''"up":''' If the bound key should trigger the function when the key is released
**'''"down":''' If the bound key should trigger the function when the key is pressed
**'''"both":''' If the bound key should trigger the function when the key is pressed or released
*'''handlerFunction:''' The function that will be triggered when the player's key is pressed. This function should have the form:
:<syntaxhighlight lang="lua">function functionName ( player keyPresser, string key, string keyState, [ var arguments, ... ] )</syntaxhighlight>
:The values passed to this function are:
:*'''keyPresser:''' The player who pressed the key
:*'''key:''' The key that was pressed
:*'''keyState:''' The state of the key that was pressed, ''down'' if it was pressed, ''up'' if it was released.
:*'''arguments''' The optional arguments you specified when calling [[bindKey]] (see below).
</section>

{{New feature|3|1.0|
<section name="Server - Syntax 2" class="server" show="true">
This alternative syntax allows you to bind a key with a command. This will also allow users to customize the control in their Settings menu. Use in conjunction with [[addCommandHandler]] to add handler functions to the keybind.

<syntaxhighlight lang="lua">bindKey ( player thePlayer, string key, string keyState, string commandName, string arguments )</syntaxhighlight>

===Required Arguments===
*'''thePlayer:''' The player you wish to bind the key of.
*'''key:''' The key or control you wish to bind to the command. See [[key names]] for a list of possible keys.
*'''keyState:''' A string that has one of the following values:
**'''"up":''' If the bound key should trigger the function when the key is released
**'''"down":''' If the bound key should trigger the function when the key is pressed
**'''"both":''' If the bound key should trigger the function when the key is pressed or released
*'''commandName:''' The name of the command that the key should be binded to.
*'''arguments''' Space delimited arguments that are entered as if one was typing the command.
</section>
}}

<section name="Client - Syntax 1" class="client" show="true">
<syntaxhighlight lang="lua">bindKey ( string key, string keyState, function handlerFunction, [ var arguments, ... ] ) </syntaxhighlight>

===Required Arguments===
*'''key:''' The key or control you wish to bind to the command. See [[key names]] for a list of possible keys and [[control names]] for a list of possible controls.
*'''keyState:''' A string that has one of the following values:
**'''"up":''' If the bound key should trigger the function when the key is released
**'''"down":''' If the bound key should trigger the function when the key is pressed
**'''"both":''' If the bound key should trigger the function when the key is pressed or released

*'''handlerFunction:''' The function that will be triggered when the player's key is pressed. This function should have the form:
:<syntaxhighlight lang="lua">function functionName ( string key, string keyState, [ var arguments, ... ] )</syntaxhighlight>
:The values passed to this function are:
:*'''key:''' The key that was pressed
:*'''keyState:''' The state of the key that was pressed, ''down'' if it was pressed, ''up'' if it was released.
:*'''arguments''' The optional arguments you specified when calling [[bindKey]] (see below).
</section>

{{New feature|3|1.0|
<section name="Client - Syntax 2" class="client" show="true">
This alternative syntax allows you to bind a key with a command. This will also allow users to customize the control in their Settings menu. Use in conjunction with [[addCommandHandler]] to add handler functions to the keybind.

<syntaxhighlight lang="lua">bindKey ( string key, string keyState, string commandName, string arguments )</syntaxhighlight>

===Required Arguments===
*'''key:''' The key or control you wish to bind to the command. See [[key names]] for a list of possible keys.
*'''keyState:''' A string that has one of the following values:
**'''"up":''' If the bound key should trigger the function when the key is released
**'''"down":''' If the bound key should trigger the function when the key is pressed
**'''"both":''' If the bound key should trigger the function when the key is pressed or released
*'''commandName:''' The name of the command that the key should be binded to.
*'''arguments''' Space delimited arguments that are entered as if one was typing the command.
</section>
}}

===Optional Arguments===
{{OptionalArg}}
*'''arguments:''' Any arguments you may want to pass to the function when the key is pressed by the user. Any number of arguments of can be specified, each being passed to the designated function. You may not pass functions.

==Example==
Example 1
<section name="Server" class="server" show="true">
This example will bind a player's 'F1' key and 'fire' control to 1 input function.
<syntaxhighlight lang="lua">
function funcInput ( player, key, keyState )
local state = "let go of"
if ( keyState == "down" ) then
state = "pressed"
end
outputChatBox ( getPlayerName ( player) .. " " .. state .. " the " .. key .. " key!" )
end

function bindTheKeys ( player, commandName )
bindKey ( player, "F1", "down", funcInput ) -- bind the player's F1 down key
bindKey ( player, "F1", "up", funcInput ) -- bind the player's F1 up key
bindKey ( player, "fire", "both", funcInput ) -- bind the player's fire down and up control
end
addCommandHandler ( "bindme", bindTheKeys )
</syntaxhighlight>
</section>

Example 2
<section name="Client" class="client" show="true">
This example will bind a player's 'F1' key and 'fire' control to 1 input function, clientside.
<syntaxhighlight lang="lua">
function funcInput ( key, keyState )
local state = "let go of"
if ( keyState == "down" ) then
state = "pressed"
end
outputChatBox ( "You " .. state .. " the " .. key .. " key!" )
end

function bindTheKeys ()
bindKey ( "F1", "down", funcInput ) -- bind the player's F1 down key
bindKey ( "F1", "up", funcInput ) -- bind the player's F1 up key
bindKey ( "fire", "both", funcInput ) -- bind the player's fire down and up control
end
addCommandHandler ( "bindme", bindTheKeys )
</syntaxhighlight>
</section>

<section name="Server" class="server" show="true">
This example says how cool Robpol86 is if players wants to move.
<syntaxhighlight lang="lua">
function fanFunction()
bindKey (source,"forwards","down",
function(player,key,state)
outputChatBox (getPlayerName (player) .. "#FFFF00 thinks Robpol86 is cool.",getRootElement(),255,255,0,true)
end
)
end
addEventHandler ("onPlayerLogin",getRootElement(),fanFunction)
</syntaxhighlight>
</section>

==See Also==
{{Input functions}}