SetPlayerScriptDebugLevel: Difference between revisions

From Multi Theft Auto: Wiki
Jump to navigation Jump to search
m (fix typo)
No edit summary
 
(3 intermediate revisions by 3 users not shown)
Line 2: Line 2:
{{Server function}}
{{Server function}}
<!-- Describe in plain english what this function does. Don't go into details, just give an overview -->
<!-- Describe in plain english what this function does. Don't go into details, just give an overview -->
{{New feature/item|3.0158|1.5.7|19626|
This will set player's debug level, equivalent to [[Debugging|debugscript <level>]].
This will set player's debug level, equivalent to [[Debugging|debugscript <level>]].
 
}}
==Syntax==  
==Syntax==  
<!-- NOTE: don't use 'special' names for variable names, e.g. you shouldn't be writing things like 'player player, vehicle vehicle', instead write something like 'player thePlayer, vehicle vehicleToGetInto'. This is less confusing and prevents the syntax highlighting being odd -->
<!-- NOTE: don't use 'special' names for variable names, e.g. you shouldn't be writing things like 'player player, vehicle vehicle', instead write something like 'player thePlayer, vehicle vehicleToGetInto'. This is less confusing and prevents the syntax highlighting being odd -->
Line 9: Line 10:
bool setPlayerScriptDebugLevel ( player thePlayer, int level )
bool setPlayerScriptDebugLevel ( player thePlayer, int level )
</syntaxhighlight>  
</syntaxhighlight>  
{{OOP||[[player]]:setScriptDebugLevel|scriptDebugLevel}}
{{OOP||[[player]]:setScriptDebugLevel|scriptDebugLevel|getPlayerScriptDebugLevel}}
===Required Arguments===  
===Required Arguments===  
<!-- List each argument one per line. This should be the argument's name as in the argument list above, NOT the argument's data type -->
<!-- List each argument one per line. This should be the argument's name as in the argument list above, NOT the argument's data type -->
Line 23: Line 24:
This code will set joining players debug level to (3), (It is no recommended to use it in production, specially if you have sensitive data in your logs).
This code will set joining players debug level to (3), (It is no recommended to use it in production, specially if you have sensitive data in your logs).
<syntaxhighlight lang="lua">
<syntaxhighlight lang="lua">
addEventHandler('onPlayerJoin', root, function()
function setPlayerDebug (player)
     setPlayerScriptDebugLevel(source, 3)
     setPlayerScriptDebugLevel(player, 3)
end)
    outputChatBox("You set debug script level to 3", player)
end  
addCommandHandler("setdebug", setPlayerDebug)  
</syntaxhighlight>
</syntaxhighlight>
</section>
</section>
==Requirements==
{{Requirements|1.5.7-9.19626|n/a|}}


==See Also==
==See Also==
<!-- Change FunctionArea to the area that this function is in on the main function list page, e.g. Server, Player, Vehicle etc -->
<!-- Change FunctionArea to the area that this function is in on the main function list page, e.g. Server, Player, Vehicle etc -->
{{Player_functions}}
{{Player_functions}}

Latest revision as of 14:15, 25 October 2020

This will set player's debug level, equivalent to debugscript <level>.

Syntax

bool setPlayerScriptDebugLevel ( player thePlayer, int level )

OOP Syntax Help! I don't understand this!

Method: player:setScriptDebugLevel(...)
Variable: .scriptDebugLevel
Counterpart: getPlayerScriptDebugLevel


Required Arguments

  • thePlayer: The player whose debug level you wish to change
  • level: 0: close debug console, 1: only errors, 2: errors and warnings, 3: errors, warnings and info messages

Returns

Returns true if successful, false otherwise.

Example

Click to collapse [-]
Server

This code will set joining players debug level to (3), (It is no recommended to use it in production, specially if you have sensitive data in your logs).

function setPlayerDebug (player)
    setPlayerScriptDebugLevel(player, 3)
    outputChatBox("You set debug script level to 3", player)
end 
addCommandHandler("setdebug", setPlayerDebug) 

Requirements

Minimum server version 1.5.7-9.19626
Minimum client version n/a

Note: Using this feature requires the resource to have the above minimum version declared in the meta.xml <min_mta_version> section. e.g. <min_mta_version server="1.5.7-9.19626" />

See Also