OnClientDebugMessage - Revision history

Myonlake at 11:22, 11 April 2021

2021-04-11T11:22:35Z

← Older revision		Revision as of 11:22, 11 April 2021
Line 22:		Line 22:
	*'''line''': The line in file '''file''' where the debug message was outputted		*'''line''': The line in file '''file''' where the debug message was outputted
	**'''Note:''' May return [[nil]] when the source could not be found		**'''Note:''' May return [[nil]] when the source could not be found
	{{New feature/item\|3.~~0160~~\|1.6\|11412\|		{{New feature/item\|3.0158\|1.5.7\|11412\|
	*'''r''': Amount of red color (0-255)		*'''r''': Amount of red color (0-255)
	*'''g''': Amount of green color (0-255)		*'''g''': Amount of green color (0-255)

Myonlake at 11:22, 11 April 2021

2021-04-11T11:22:22Z

← Older revision		Revision as of 11:22, 11 April 2021
Line 6:		Line 6:

	==Parameters==		==Parameters==
	~~<syntaxhighlight lang="lua">~~
	~~string message, int level, string file, int line~~
	~~</syntaxhighlight>~~
	{{New feature/item\|3.0158\|1.5.7\|11412\|		{{New feature/item\|3.0158\|1.5.7\|11412\|
	<syntaxhighlight lang="lua">		<syntaxhighlight lang="lua">

Myonlake at 11:22, 11 April 2021

2021-04-11T11:22:07Z

← Older revision		Revision as of 11:22, 11 April 2021
Line 9:		Line 9:
	string message, int level, string file, int line		string message, int level, string file, int line
	</syntaxhighlight>		</syntaxhighlight>
	{{New feature/item\|3.~~0160~~\|1.6\|11412\|		{{New feature/item\|3.0158\|1.5.7\|11412\|
	<syntaxhighlight lang="lua">		<syntaxhighlight lang="lua">
	string message, int level, string file, int line, int r, int g, int b		string message, int level, string file, int line, int r, int g, int b

Srslyyyy: Improve examples.

2021-02-27T15:52:17Z

Improve examples.

← Older revision		Revision as of 15:52, 27 February 2021
Line 35:		Line 35:

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


	This example tells players that they missed a debug message, if they don't have debugscript enabled.		This example tells players that they missed a debug message, if they don't have debugscript enabled.
	<syntaxhighlight lang="lua">		<syntaxhighlight lang="lua">
	function newDebug() ~~-- Since we don't need any of the parameters, we can optimize the code and exclude them~~		function newDebug()
	if not isDebugViewActive() then -- If their debug view is not active		if not isDebugViewActive() then -- If their debug view is not active
	outputChatBox("* You just missed a debug message. Use the \'/debugscript\' command to view it.",255,0,0) -- Output to them that they missed a debug message		outputChatBox("* You just missed a debug message. Use the \'/debugscript\' command to view it.", 255, 0, 0) -- Output to them that they missed a debug message
	end		end
	end		end
	addEventHandler("onClientDebugMessage",root,newDebug) -- When we get a new client debug message, call the newDebug function		addEventHandler("onClientDebugMessage", root, newDebug) -- When we get a new client debug message, call the newDebug function
	</syntaxhighlight>		</syntaxhighlight>

Botder at 21:22, 9 October 2018

2018-10-09T21:22:05Z

← Older revision		Revision as of 21:22, 9 October 2018
Line 2:		Line 2:
	{{Client event}}		{{Client 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.		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.

			'''Note:''' To prevent infinite loops, debug messages that occur inside the function that handles this event won't trigger this event, so you won't be able to rely on debug info to fix faulty code that is inside this function. Since build [https://buildinfo.mtasa.com/index.php?Revision=14683 r14683] debug messages from [[outputDebugString]] and [[iprint]] will show up.

	==Parameters==		==Parameters==

Qaisjp: fix typo

2017-08-17T18:59:03Z

fix typo

← Older revision		Revision as of 18:59, 17 August 2017
Line 7:		Line 7:
	string message, int level, string file, int line		string message, int level, string file, int line
	</syntaxhighlight>		</syntaxhighlight>


	{{New feature/item\|3.0160\|1.6\|11412\|		{{New feature/item\|3.0160\|1.6\|11412\|
	<syntaxhighlight lang="lua">		<syntaxhighlight lang="lua">

Qaisjp: fix new feature/item

2017-08-17T18:58:55Z

fix new feature/item

← Older revision		Revision as of 18:58, 17 August 2017
Line 8:		Line 8:
	</syntaxhighlight>		</syntaxhighlight>

	{{New feature/item\|3.~~0154~~\|1.~~5.4~~\|11412\|
			{{New feature/item\|3.0160\|1.6\|11412\|
	<syntaxhighlight lang="lua">		<syntaxhighlight lang="lua">
	string message, int level, string file, int line, int r, int g, int b		string message, int level, string file, int line, int r, int g, int b
Line 24:		Line 25:
	*'''line''': The line in file '''file''' where the debug message was outputted		*'''line''': The line in file '''file''' where the debug message was outputted
	**'''Note:''' May return [[nil]] when the source could not be found		**'''Note:''' May return [[nil]] when the source could not be found
	{{New ~~items~~\|5.~~0154~~\|1.~~5.4-9.~~11412\|		{{New feature/item\|3.0160\|1.6\|11412\|
	*'''r''': Amount of red color (0-255)		*'''r''': Amount of red color (0-255)
	*'''g''': Amount of green color (0-255)		*'''g''': Amount of green color (0-255)

Qaisjp: Fix new feature/item template

2017-08-17T18:55:48Z

Fix new feature/item template

← Older revision		Revision as of 18:55, 17 August 2017
Line 8:		Line 8:
	</syntaxhighlight>		</syntaxhighlight>

	{{New ~~items~~\|5.0154\|1.5.4~~-9.~~11412\|		{{New feature/item\|3.0154\|1.5.4\|11412\|
	<syntaxhighlight lang="lua">		<syntaxhighlight lang="lua">
	string message, int level, string file, int line, int r, int g, int b		string message, int level, string file, int line, int r, int g, int b

Necktrox: Added RGB params

2017-06-02T16:05:35Z

Added RGB params

← Older revision		Revision as of 16:05, 2 June 2017
Line 7:		Line 7:
	string message, int level, string file, int line		string message, int level, string file, int line
	</syntaxhighlight>		</syntaxhighlight>

			{{New items\|5.0154\|1.5.4-9.11412\|
			<syntaxhighlight lang="lua">
			string message, int level, string file, int line, int r, int g, int b
			</syntaxhighlight>
			}}

	*'''message''': The message which was outputted in the server console, without details like file, line etc		*'''message''': The message which was outputted in the server console, without details like file, line etc
Line 18:		Line 24:
	*'''line''': The line in file '''file''' where the debug message was outputted		*'''line''': The line in file '''file''' where the debug message was outputted
	**'''Note:''' May return [[nil]] when the source could not be found		**'''Note:''' May return [[nil]] when the source could not be found
			{{New items\|5.0154\|1.5.4-9.11412\|
			*'''r''': Amount of red color (0-255)
			*'''g''': Amount of green color (0-255)
			*'''b''': Amount of blue color (0-255)
			}}

	==Source==		==Source==

Callum Dawson: Added an example.

2011-08-26T22:13:49Z

Added an example.

← Older revision		Revision as of 22:13, 26 August 2011
Line 22:		Line 22:
	The [[event system#Event source\|source]] of this event is the [[root element]].		The [[event system#Event source\|source]] of this event is the [[root element]].

	==~~Example~~==		==Examples==
	This (easy) example outputs the debug message in the console, so you don't need to open debugscript 3 :D		This (easy) example outputs the debug message in the console, so you don't need to open debugscript 3 :D
	<syntaxhighlight lang="lua">		<syntaxhighlight lang="lua">
Line 29:		Line 29:
	outputConsole (message,getLocalPlayer())		outputConsole (message,getLocalPlayer())
	end)		end)
			</syntaxhighlight>


			This example tells players that they missed a debug message, if they don't have debugscript enabled.
			<syntaxhighlight lang="lua">
			function newDebug() -- Since we don't need any of the parameters, we can optimize the code and exclude them
			if not isDebugViewActive() then -- If their debug view is not active
			outputChatBox("* You just missed a debug message. Use the \'/debugscript\' command to view it.",255,0,0) -- Output to them that they missed a debug message
			end
			end
			addEventHandler("onClientDebugMessage",root,newDebug) -- When we get a new client debug message, call the newDebug function
	</syntaxhighlight>		</syntaxhighlight>

Line 36:		Line 47:
	===Client event functions===		===Client event functions===
	{{Client_event_functions}}		{{Client_event_functions}}

	~~[[Category:Needs_Example]]~~