DetonatePlayerSatchels: Difference between revisions
Jump to navigation
Jump to search
(deleted Disabled template because this function never exist) |
m (fixed blank space) |
||
| Line 1: | Line 1: | ||
{{Server function}} | |||
{{Delete|It seems this page was created in confusion.}} | {{Delete|It seems this page was created in confusion.}} | ||
This function detonates the thrown satchels of a player, as if they had fired the detonator. | This function detonates the thrown satchels of a player, as if they had fired the detonator. | ||
__NOTOC__ | |||
==Syntax== | ==Syntax== | ||
<syntaxhighlight lang="lua"> | <syntaxhighlight lang="lua"> | ||
Revision as of 17:21, 1 March 2014
|
This page is marked for deletion. |
Reason: It seems this page was created in confusion. Actions: Delete (Administrators) - Discuss - What links here - Category
|
This function detonates the thrown satchels of a player, as if they had fired the detonator.
Syntax
bool detonatePlayerSatchels( player thePlayer )
Required Arguments
- thePlayer: the player that should have their thrown satchels detonated.
Returns
Returns true if a valid player element was passed, false otherwise.
Example
This example will allow players to detonate their thrown satchels via the command /detonate
function cmdDetonateSatchels(plr)
detonatePlayerSatchels(plr)
end
addCommandHandler("detonate", cmdDetonateSatchels)
Requirements
This template will be deleted.
See Also
- getPlayerTeam
- getPlayerBlurLevel
- setPlayerBlurLevel
- getPlayerSerial
- forcePlayerMap
- getPlayerScriptDebugLevel
- getPlayerFromName
- getPlayerMoney
- getPlayerName
- getPlayerNametagColor
- getPlayerNametagText
- getPlayerPing
- getPlayerWantedLevel
- givePlayerMoney
- isPlayerMapForced
- isPlayerNametagShowing
- setPlayerHudComponentVisible
- setPlayerMoney
- setPlayerNametagColor
- setPlayerNametagShowing
- setPlayerNametagText
- takePlayerMoney
- countPlayersInTeam
- getPlayersInTeam
- isVoiceEnabled
- setControlState
- getControlState