GetPlayerScriptDebugLevel - Revision history

Fernando187: Remove obsolete Requirements section

2024-11-07T17:18:24Z

Remove obsolete Requirements section

← Older revision		Revision as of 17:18, 7 November 2024
Line 45:		Line 45:
	addCommandHandler ( "showdebug", showdebug )		addCommandHandler ( "showdebug", showdebug )
	</syntaxhighlight>		</syntaxhighlight>

	~~==Requirements==~~
	~~{{Requirements\|1.5.7-9.19626\|1.6.0-9.22592\|}}~~

	==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 -->
	{{Shared_player_functions}}		{{Shared_player_functions}}

Nico834: Add new oop syntax

2024-07-15T20:56:57Z

Add new oop syntax

← Older revision		Revision as of 20:56, 15 July 2024
Line 28:		Line 28:
	int getPlayerScriptDebugLevel()		int getPlayerScriptDebugLevel()
	</syntaxhighlight>		</syntaxhighlight>
	{{OOP\|\|[[player]]:getScriptDebugLevel\|~~debugLevel~~}}		{{OOP\|\|[[player]]:getScriptDebugLevel\|scriptDebugLevel}}

	===Returns===		===Returns===

Nico834: Add shared function area & beta header

2024-06-30T10:00:46Z

Add shared function area & beta header

← Older revision		Revision as of 10:00, 30 June 2024
Line 4:		Line 4:
	{{New feature/item\|3.0158\|1.5.7\|19626\|		{{New feature/item\|3.0158\|1.5.7\|19626\|
	This will allow you to retrieve the player current debug script level.		This will allow you to retrieve the player current debug script level.
			}}
			{{New feature/item\|3.0161\|1.6.0\|22592\|
			This function has a client-sided variant, which can only retrieve the local player's script debug level.
	}}		}}
	==Syntax==		==Syntax==
Line 48:		Line 51:
	==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~~}}		{{Shared_player_functions}}

Nico834: Add client-sided variant of this function

2024-06-30T09:51:14Z

Add client-sided variant of this function

← Older revision		Revision as of 09:51, 30 June 2024
Line 1:		Line 1:
	__NOTOC__		__NOTOC__
	{{~~Server~~ function}}		{{Shared 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\|		{{New feature/item\|3.0158\|1.5.7\|19626\|
Line 7:		Line 7:
	==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 -->
			<section name="Server" class="server" show="true">
	<syntaxhighlight lang="lua">		<syntaxhighlight lang="lua">
	int getPlayerScriptDebugLevel( player thePlayer )		int getPlayerScriptDebugLevel( player thePlayer )
Line 18:		Line 19:
	<!-- Make this descriptive. Explain what cases will return false. If you're unsure, add a tag to it so we can check -->		<!-- Make this descriptive. Explain what cases will return false. If you're unsure, add a tag to it so we can check -->
	Returns an ''int'' with the player debug script level, ''false'' if the player is invalid.		Returns an ''int'' with the player debug script level, ''false'' if the player is invalid.
			</section>

			<section name="Client" class="client" show="true">
			<syntaxhighlight lang="lua">
			int getPlayerScriptDebugLevel()
			</syntaxhighlight>
			{{OOP\|\|[[player]]:getScriptDebugLevel\|debugLevel}}

			===Returns===
			<!-- Make this descriptive. Explain what cases will return false. If you're unsure, add a tag to it so we can check -->
			Returns an ''int'' with the local player's debug script level.
			</section>
	==Example==		==Example==
	<!-- Explain what the example is in a single sentance -->		<!-- Explain what the example is in a single sentance -->
Line 32:		Line 44:

	==Requirements==		==Requirements==
	{{Requirements\|1.5.7-9.19626\|~~n/a~~\|}}		{{Requirements\|1.5.7-9.19626\|1.6.0-9.22592\|}}

	==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}}

StrixG at 14:15, 25 October 2020

2020-10-25T14:15:21Z

← Older revision		Revision as of 14:15, 25 October 2020
Line 32:		Line 32:

	==Requirements==		==Requirements==
	{{Requirements\|1.5.7-9.19626\|\|}}		{{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}}

StrixG at 14:14, 25 October 2020

2020-10-25T14:14:15Z

← Older revision		Revision as of 14:14, 25 October 2020
Line 10:		Line 10:
	int getPlayerScriptDebugLevel( player thePlayer )		int getPlayerScriptDebugLevel( player thePlayer )
	</syntaxhighlight>		</syntaxhighlight>
	{{OOP\|\|[[player]]:getScriptDebugLevel\|scriptDebugLevel}}		{{OOP\|\|[[player]]:getScriptDebugLevel\|scriptDebugLevel\|setPlayerScriptDebugLevel}}
	===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 -->

StrixG at 14:13, 25 October 2020

2020-10-25T14:13:52Z

← Older revision		Revision as of 14:13, 25 October 2020
Line 30:		Line 30:
	addCommandHandler ( "showdebug", showdebug )		addCommandHandler ( "showdebug", showdebug )
	</syntaxhighlight>		</syntaxhighlight>

			==Requirements==
			{{Requirements\|1.5.7-9.19626\|\|}}

	==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}}

Qaisjp: ver

2020-05-20T10:36:12Z

ver

← Older revision		Revision as of 10:36, 20 May 2020
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 allow you to retrieve the player current debug script level.		This will allow you to retrieve the player current debug script 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 -->

Vadya963: /* Example */

2020-01-25T18:45:38Z

Example

← Older revision		Revision as of 18:45, 25 January 2020
Line 21:		Line 21:
	<!-- Explain what the example is in a single sentance -->		<!-- Explain what the example is in a single sentance -->
	<!-- Add the code below, an emphasis should be on making it clear, not optimized. You could provide two versions if you wish, one clear and well commented, the other optimized -->		<!-- Add the code below, an emphasis should be on making it clear, not optimized. You could provide two versions if you wish, one clear and well commented, the other optimized -->
	~~This will show your~~ debug ~~script~~ level ~~on your screen~~.		Displays a message in the chat what is the player's debug level.
	<syntaxhighlight lang="lua">		<syntaxhighlight lang="lua">
	~~addEventHandler~~(~~'onClientRender', root, function~~()		function showdebug (player)
	~~dxDrawText~~("Debug ~~Script~~ Level: "..~~getPlayerScriptDebugLevel(localPlayer), 10, 10~~)		local level = getPlayerScriptDebugLevel( player )
	end)		outputChatBox( "Your Script Debug Level: " .. level )
			end
			addCommandHandler ( "showdebug", showdebug )
	</syntaxhighlight>		</syntaxhighlight>

Vadya963: /* Syntax */

2020-01-23T13:36:17Z

Syntax

← Older revision		Revision as of 13:36, 23 January 2020
Line 7:		Line 7:
	<!-- 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 -->
	<syntaxhighlight lang="lua">		<syntaxhighlight lang="lua">
	~~string~~ getPlayerScriptDebugLevel( player thePlayer )		int getPlayerScriptDebugLevel( player thePlayer )
	</syntaxhighlight>		</syntaxhighlight>
	{{OOP\|\|[[player]]:getScriptDebugLevel\|scriptDebugLevel}}		{{OOP\|\|[[player]]:getScriptDebugLevel\|scriptDebugLevel}}