OnChatMessage: Difference between revisions
Jump to navigation
Jump to search
m (updated needs checkin) |
No edit summary |
||
Line 1: | Line 1: | ||
{{Server event}} | {{Server event}} | ||
{{Needs_Checking|thePlayer | {{Needs_Checking|thePlayer arguement from a say command returns userdata but is not an element, teamsay and me worked however.}} | ||
__NOTOC__ | __NOTOC__ | ||
{{New feature|3.0120|1.2| | {{New feature|3.0120|1.2| |
Revision as of 20:13, 1 October 2011
This article needs checking. | |
Reason(s): thePlayer arguement from a say command returns userdata but is not an element, teamsay and me worked however. |
Available only in MTA SA 1.2 and onwards This event is triggered when a player uses say, teamsay, me successfully. Or when any message is sent to a player using outputChatBox.
Parameters
string theMessage, element thePlayer
- theMessage: The text that was output to the chatbox
- thePlayer: The player who triggered the event (needs checking)
Source
The source of this event is the root element.
Example
This example outputs all chat messages to debug view.
[lua] function onChatMessageHandler(theMessage, thePlayer) outputDebugString(theMessage) end addEventHandler("onChatMessage", root, onChatMessageHandler)
See Also
Server events
Event functions
- addEvent
- addEventHandler
- cancelEvent
- cancelLatentEvent
- getEventHandlers
- getLatentEventHandles
- getLatentEventStatus
- removeEventHandler
- triggerEvent
- wasEventCancelled