Hibakeresés - Revision history

StrixG: Undo revision 50683 by StrixG (talk)

2017-04-15T16:40:32Z

Undo revision 50683 by StrixG (talk)

← Older revision		Revision as of 16:40, 15 April 2017
Line 1:		Line 1:
	~~A szkriptekben gyakran előfordulnak kisebb nagyobb problémák, amelyeket nem veszünk észre!Ez a leírás segít abban hogy gyorsan megtaláld őket!~~		When scripting you will often come across problems that are not immediately apparent. This page tries to point out some basic strategies to locate the error.

	==~~Hibakereső konzol~~==		==Debug console==
	Az MTA ~~tartalmaz beépített hibakereső konzolt!Hasznos mivel ha elgépelünk valamit és nem vesszük észre ő segítségünkre lehet~~.~~Ahhoz hogy tudjuk aktiválni ezt a jogusultságot Adminisztrátor rangot kell viselnünk{~~ACL}.~~Ha ez rendben van akkor a "~~debugscript ~~x" parancsal tudjuk változtatni a visszajelzési szintet!~~		MTA features a built-in debug console that shows debug messages output from MTA functions or from scripts. Keeping it mind that you should have administrator access (unless you modify the ACL to change this), you can open the debug console by typing ''debugscript x'' in the console, where ''x'' is the debug level:
			* '''1:''' only errors
			* '''2:''' errors and warnings
			* '''3:''' errors, warnings and info messages
			By typing ''debugscript 3'' all messages are visible. Level 3 and level 2 are recommended for most occasions. You should have ''debugscript'' enabled whenever you are testing your scripts as it will help you easily detect and solve typos and other issues.

	~~----~~		===Example===
	~~Lehetőségek:~~		This example code has two errors:
	* '''1:''' Csak a '''Hibákat''' jelzi
	* '''2:''' A '''hibákat''' és a '''Figyelmeztetéseket''' is jelzi
	* '''3:''' A '''hibákat''' és a '''Figyelmeztetéseket''' is jelzi illetve az '''Információkat''' amelyeket elrejtünk a szkriptekben!
	~~Ha begépeljük a "debugscript 3" parancsot akkor a fent leírt paramétereket fogja megmutatni.Ez a legcélszerűbb funkció, sokkal egyszerűbb vele a fejlesztés~~

	===~~Példa~~===
	~~Ebben a kódban elrejtettünk két darab hibát~~:
	<syntaxhighlight lang="lua">		<syntaxhighlight lang="lua">
	function ~~Koszones~~(message, player)		function SayHello(message, player)
	if (getPlayerName(player) == "~~Józsika~~")		if (getPlayerName(player) == "Fedor")
	outputChatbox("~~Szia Józsika~~")		outputChatbox("Hello Fedor")
	end		end
	end		end
	addEventHandler("onChatMessage", root, ~~Koszones~~)		addEventHandler("onChatMessage", root, SayHello)
	</syntaxhighlight>		</syntaxhighlight>
	~~Ha ezt a kódot lefuttatjuk akkor ezt a hibaüzenetet fogjuk kapni~~:		When the script this piece of code is in is tried to be loaded, debugscript will output something similiar to this:
	:{{Debug info\|Loading script failed: myResource\script.lua:2: 'then' expected near ´outputChatbox'}}~~[Ezt nem fordítom le]~~		:{{Debug info\|Loading script failed: myResource\script.lua:2: 'then' expected near ´outputChatbox'}}
	This means the script could not be parsed because there was a syntax error. It shows the script path relative to the resource directory so you can identify to script where the error originated from. After the filename it shows a colon and a number, this number presents the line number - this is so you can find out where in your script the error is - it is very helpful for large scripts. After that is the error message, which varies depending on the error made. Looking at the error message, we can easily determine that the error originated from the resource '''myResource''' and line two of the script file '''script.lua'''. The error message is very clear, we forgot the "then"! We can easily fix that!		This means the script could not be parsed because there was a syntax error. It shows the script path relative to the resource directory so you can identify to script where the error originated from. After the filename it shows a colon and a number, this number presents the line number - this is so you can find out where in your script the error is - it is very helpful for large scripts. After that is the error message, which varies depending on the error made. Looking at the error message, we can easily determine that the error originated from the resource '''myResource''' and line two of the script file '''script.lua'''. The error message is very clear, we forgot the "then"! We can easily fix that!
	<syntaxhighlight lang="lua">		<syntaxhighlight lang="lua">

StrixG: Undo revision 50682 by StrixG (talk)

2017-04-15T16:39:35Z

Undo revision 50682 by StrixG (talk)

← Older revision		Revision as of 16:39, 15 April 2017
Line 1:		Line 1:
	~~When scripting you will often come across problems that are not immediately apparent. This page tries to point out some basic strategies to locate the error.~~		A szkriptekben gyakran előfordulnak kisebb nagyobb problémák, amelyeket nem veszünk észre!Ez a leírás segít abban hogy gyorsan megtaláld őket!

	==~~Debug console~~==		==Hibakereső konzol==
	MTA ~~features~~ a ~~built-in debug console that shows debug messages output from MTA functions or from scripts~~. ~~Keeping it mind that you should have administrator access (unless you modify the ACL to change this), you can open the debug console by typing ''~~debugscript x'' in the console, where ''x'' is the debug level:		Az MTA tartalmaz beépített hibakereső konzolt!Hasznos mivel ha elgépelünk valamit és nem vesszük észre ő segítségünkre lehet.Ahhoz hogy tudjuk aktiválni ezt a jogusultságot Adminisztrátor rangot kell viselnünk{ACL}.Ha ez rendben van akkor a "debugscript x" parancsal tudjuk változtatni a visszajelzési szintet!
	* '''1:''' only errors
	* '''2:''' errors and warnings
	* '''3:''' errors, warnings and info messages
	By typing ''debugscript 3'' all messages are visible. Level 3 and level 2 are recommended for most occasions. You should have ''debugscript'' enabled whenever you are testing your scripts as it will help you easily detect and solve typos and other issues.

	===~~Example~~===		----
	~~This example code has two errors~~:		Lehetőségek:
			* '''1:''' Csak a '''Hibákat''' jelzi
			* '''2:''' A '''hibákat''' és a '''Figyelmeztetéseket''' is jelzi
			* '''3:''' A '''hibákat''' és a '''Figyelmeztetéseket''' is jelzi illetve az '''Információkat''' amelyeket elrejtünk a szkriptekben!
			Ha begépeljük a "debugscript 3" parancsot akkor a fent leírt paramétereket fogja megmutatni.Ez a legcélszerűbb funkció, sokkal egyszerűbb vele a fejlesztés

			===Példa===
			Ebben a kódban elrejtettünk két darab hibát:
	<syntaxhighlight lang="lua">		<syntaxhighlight lang="lua">
	function ~~SayHello~~(message, player)		function Koszones(message, player)
	if (getPlayerName(player) == "~~Fedor~~")		if (getPlayerName(player) == "Józsika")
	outputChatbox("~~Hello Fedor~~")		outputChatbox("Szia Józsika")
	end		end
	end		end
	addEventHandler("onChatMessage", root, ~~SayHello~~)		addEventHandler("onChatMessage", root, Koszones)
	</syntaxhighlight>		</syntaxhighlight>
	~~When the script this piece of code is in is tried to be loaded, debugscript will output something similiar to this~~:		Ha ezt a kódot lefuttatjuk akkor ezt a hibaüzenetet fogjuk kapni:
	:{{Debug info\|Loading script failed: myResource\script.lua:2: 'then' expected near ´outputChatbox'}}		:{{Debug info\|Loading script failed: myResource\script.lua:2: 'then' expected near ´outputChatbox'}}[Ezt nem fordítom le]
	This means the script could not be parsed because there was a syntax error. It shows the script path relative to the resource directory so you can identify to script where the error originated from. After the filename it shows a colon and a number, this number presents the line number - this is so you can find out where in your script the error is - it is very helpful for large scripts. After that is the error message, which varies depending on the error made. Looking at the error message, we can easily determine that the error originated from the resource '''myResource''' and line two of the script file '''script.lua'''. The error message is very clear, we forgot the "then"! We can easily fix that!		This means the script could not be parsed because there was a syntax error. It shows the script path relative to the resource directory so you can identify to script where the error originated from. After the filename it shows a colon and a number, this number presents the line number - this is so you can find out where in your script the error is - it is very helpful for large scripts. After that is the error message, which varies depending on the error made. Looking at the error message, we can easily determine that the error originated from the resource '''myResource''' and line two of the script file '''script.lua'''. The error message is very clear, we forgot the "then"! We can easily fix that!
	<syntaxhighlight lang="lua">		<syntaxhighlight lang="lua">

StrixG: Undo revision 50677 by Kevin (talk)

2017-04-15T16:39:30Z

Undo revision 50677 by Kevin (talk)

← Older revision		Revision as of 16:39, 15 April 2017
Line 1:		Line 1:
	~~A szkriptekben gyakran előfordulnak kisebb nagyobb problémák, amelyeket nem veszünk észre!Ez a leírás segít abban hogy gyorsan megtaláld őket!~~		When scripting you will often come across problems that are not immediately apparent. This page tries to point out some basic strategies to locate the error.

	==~~Hibakereső konzol~~==		==Debug console==
	Az MTA ~~tartalmaz beépített hibakereső konzolt!Hasznos mivel ha elgépelünk valamit és nem vesszük észre ő segítségünkre lehet~~.~~Ahhoz hogy tudjuk aktiválni ezt a jogusultságot Adminisztrátor rangot kell viselnünk{~~ACL}.~~Ha ez rendben van akkor a "~~debugscript ~~x" parancsal tudjuk változtatni a visszajelzési szintet!~~		MTA features a built-in debug console that shows debug messages output from MTA functions or from scripts. Keeping it mind that you should have administrator access (unless you modify the ACL to change this), you can open the debug console by typing ''debugscript x'' in the console, where ''x'' is the debug level:
			* '''1:''' only errors
			* '''2:''' errors and warnings
			* '''3:''' errors, warnings and info messages
			By typing ''debugscript 3'' all messages are visible. Level 3 and level 2 are recommended for most occasions. You should have ''debugscript'' enabled whenever you are testing your scripts as it will help you easily detect and solve typos and other issues.

	~~----~~		===Example===
	~~Lehetőségek:~~		This example code has two errors:
	* '''1:''' Csak a '''Hibákat''' jelzi
	* '''2:''' A '''hibákat''' és a '''Figyelmeztetéseket''' is jelzi
	* '''3:''' A '''hibákat''' és a '''Figyelmeztetéseket''' is jelzi illetve az '''Információkat''' amelyeket elrejtünk a szkriptekben!
	~~Ha begépeljük a "debugscript 3" parancsot akkor a fent leírt paramétereket fogja megmutatni.Ez a legcélszerűbb funkció, sokkal egyszerűbb vele a fejlesztés~~

	===~~Példa~~===
	~~Ebben a kódban elrejtettünk két darab hibát~~:
	<syntaxhighlight lang="lua">		<syntaxhighlight lang="lua">
	function ~~Koszones~~(message, player)		function SayHello(message, player)
	if (getPlayerName(player) == "~~Józsika~~")		if (getPlayerName(player) == "Fedor")
	outputChatbox("~~Szia Józsika~~")		outputChatbox("Hello Fedor")
	end		end
	end		end
	addEventHandler("onChatMessage", root, ~~Koszones~~)		addEventHandler("onChatMessage", root, SayHello)
	</syntaxhighlight>		</syntaxhighlight>
	~~Ha ezt a kódot lefuttatjuk akkor ezt a hibaüzenetet fogjuk kapni~~:		When the script this piece of code is in is tried to be loaded, debugscript will output something similiar to this:
	:{{Debug info\|Loading script failed: myResource\script.lua:2: 'then' expected near ´outputChatbox'}}~~[Ezt nem fordítom le]~~		:{{Debug info\|Loading script failed: myResource\script.lua:2: 'then' expected near ´outputChatbox'}}
	This means the script could not be parsed because there was a syntax error. It shows the script path relative to the resource directory so you can identify to script where the error originated from. After the filename it shows a colon and a number, this number presents the line number - this is so you can find out where in your script the error is - it is very helpful for large scripts. After that is the error message, which varies depending on the error made. Looking at the error message, we can easily determine that the error originated from the resource '''myResource''' and line two of the script file '''script.lua'''. The error message is very clear, we forgot the "then"! We can easily fix that!		This means the script could not be parsed because there was a syntax error. It shows the script path relative to the resource directory so you can identify to script where the error originated from. After the filename it shows a colon and a number, this number presents the line number - this is so you can find out where in your script the error is - it is very helpful for large scripts. After that is the error message, which varies depending on the error made. Looking at the error message, we can easily determine that the error originated from the resource '''myResource''' and line two of the script file '''script.lua'''. The error message is very clear, we forgot the "then"! We can easily fix that!
	<syntaxhighlight lang="lua">		<syntaxhighlight lang="lua">

Kevin at 14:20, 15 April 2017

2017-04-15T14:20:04Z

← Older revision		Revision as of 14:20, 15 April 2017
Line 1:		Line 1:
	~~When scripting you will often come across problems that are not immediately apparent. This page tries to point out some basic strategies to locate the error.~~		A szkriptekben gyakran előfordulnak kisebb nagyobb problémák, amelyeket nem veszünk észre!Ez a leírás segít abban hogy gyorsan megtaláld őket!

	==~~Debug console~~==		==Hibakereső konzol==
	MTA ~~features~~ a ~~built-in debug console that shows debug messages output from MTA functions or from scripts~~. ~~Keeping it mind that you should have administrator access (unless you modify the ACL to change this), you can open the debug console by typing ''~~debugscript x'' in the console, where ''x'' is the debug level:		Az MTA tartalmaz beépített hibakereső konzolt!Hasznos mivel ha elgépelünk valamit és nem vesszük észre ő segítségünkre lehet.Ahhoz hogy tudjuk aktiválni ezt a jogusultságot Adminisztrátor rangot kell viselnünk{ACL}.Ha ez rendben van akkor a "debugscript x" parancsal tudjuk változtatni a visszajelzési szintet!
	* '''1:''' only errors
	* '''2:''' errors and warnings
	* '''3:''' errors, warnings and info messages
	By typing ''debugscript 3'' all messages are visible. Level 3 and level 2 are recommended for most occasions. You should have ''debugscript'' enabled whenever you are testing your scripts as it will help you easily detect and solve typos and other issues.

	===~~Example~~===		----
	~~This example code has two errors~~:		Lehetőségek:
			* '''1:''' Csak a '''Hibákat''' jelzi
			* '''2:''' A '''hibákat''' és a '''Figyelmeztetéseket''' is jelzi
			* '''3:''' A '''hibákat''' és a '''Figyelmeztetéseket''' is jelzi illetve az '''Információkat''' amelyeket elrejtünk a szkriptekben!
			Ha begépeljük a "debugscript 3" parancsot akkor a fent leírt paramétereket fogja megmutatni.Ez a legcélszerűbb funkció, sokkal egyszerűbb vele a fejlesztés

			===Példa===
			Ebben a kódban elrejtettünk két darab hibát:
	<syntaxhighlight lang="lua">		<syntaxhighlight lang="lua">
	function ~~SayHello~~(message, player)		function Koszones(message, player)
	if (getPlayerName(player) == "~~Fedor~~")		if (getPlayerName(player) == "Józsika")
	outputChatbox("~~Hello Fedor~~")		outputChatbox("Szia Józsika")
	end		end
	end		end
	addEventHandler("onChatMessage", root, ~~SayHello~~)		addEventHandler("onChatMessage", root, Koszones)
	</syntaxhighlight>		</syntaxhighlight>
	~~When the script this piece of code is in is tried to be loaded, debugscript will output something similiar to this~~:		Ha ezt a kódot lefuttatjuk akkor ezt a hibaüzenetet fogjuk kapni:
	:{{Debug info\|Loading script failed: myResource\script.lua:2: 'then' expected near ´outputChatbox'}}		:{{Debug info\|Loading script failed: myResource\script.lua:2: 'then' expected near ´outputChatbox'}}[Ezt nem fordítom le]
	This means the script could not be parsed because there was a syntax error. It shows the script path relative to the resource directory so you can identify to script where the error originated from. After the filename it shows a colon and a number, this number presents the line number - this is so you can find out where in your script the error is - it is very helpful for large scripts. After that is the error message, which varies depending on the error made. Looking at the error message, we can easily determine that the error originated from the resource '''myResource''' and line two of the script file '''script.lua'''. The error message is very clear, we forgot the "then"! We can easily fix that!		This means the script could not be parsed because there was a syntax error. It shows the script path relative to the resource directory so you can identify to script where the error originated from. After the filename it shows a colon and a number, this number presents the line number - this is so you can find out where in your script the error is - it is very helpful for large scripts. After that is the error message, which varies depending on the error made. Looking at the error message, we can easily determine that the error originated from the resource '''myResource''' and line two of the script file '''script.lua'''. The error message is very clear, we forgot the "then"! We can easily fix that!
	<syntaxhighlight lang="lua">		<syntaxhighlight lang="lua">

Kevin: Kevin moved page Debugging to Hibakeresés

2017-04-15T13:59:47Z

Kevin moved page Debugging to Hibakeresés

← Older revision

Revision as of 13:59, 15 April 2017

Thisdp at 14:37, 16 February 2017

2017-02-16T14:37:34Z

← Older revision		Revision as of 14:37, 16 February 2017
Line 311:		Line 311:
	[[Category:Scripting Concepts]]		[[Category:Scripting Concepts]]
	[[ru:Debugging]]		[[ru:Debugging]]
			[[zh-cn:脚本调试教程]]
	[[Category:Tutorials]]		[[Category:Tutorials]]

Thisdp: Undo revision 50459 by Skyvzla (talk)

2017-02-14T13:23:55Z

Undo revision 50459 by Skyvzla (talk)

← Older revision		Revision as of 13:23, 14 February 2017
Line 1:		Line 1:
	~~在编写脚本时，你会经常遇到脚本编写完成后不能执行或显示的问题。在本页面中我们通过一些方法定位脚本中的错误位置。~~		When scripting you will often come across problems that are not immediately apparent. This page tries to point out some basic strategies to locate the error.

	==~~控制台调试~~==		==Debug console==
	MTA features a built-in debug console that shows debug messages output from MTA functions or from scripts. Keeping it mind that you should have administrator access (unless you modify the ACL to change this), you can open the debug console by typing ''debugscript x'' in the console, where ''x'' is the debug level:		MTA features a built-in debug console that shows debug messages output from MTA functions or from scripts. Keeping it mind that you should have administrator access (unless you modify the ACL to change this), you can open the debug console by typing ''debugscript x'' in the console, where ''x'' is the debug level:
	* '''1:''' only errors		* '''1:''' only errors
Line 8:		Line 8:
	By typing ''debugscript 3'' all messages are visible. Level 3 and level 2 are recommended for most occasions. You should have ''debugscript'' enabled whenever you are testing your scripts as it will help you easily detect and solve typos and other issues.		By typing ''debugscript 3'' all messages are visible. Level 3 and level 2 are recommended for most occasions. You should have ''debugscript'' enabled whenever you are testing your scripts as it will help you easily detect and solve typos and other issues.

	===例===		===Example===
	~~下面这串代码有两处错误。~~		This example code has two errors:
	<syntaxhighlight lang="lua">		<syntaxhighlight lang="lua">
	function SayHello(message, player)		function SayHello(message, player)

Skyvzla at 12:49, 14 February 2017

2017-02-14T12:49:45Z

← Older revision		Revision as of 12:49, 14 February 2017
Line 1:		Line 1:
	~~When scripting you will often come across problems that are not immediately apparent. This page tries to point out some basic strategies to locate the error.~~		在编写脚本时，你会经常遇到脚本编写完成后不能执行或显示的问题。在本页面中我们通过一些方法定位脚本中的错误位置。

	==~~Debug console~~==		==控制台调试==
	MTA features a built-in debug console that shows debug messages output from MTA functions or from scripts. Keeping it mind that you should have administrator access (unless you modify the ACL to change this), you can open the debug console by typing ''debugscript x'' in the console, where ''x'' is the debug level:		MTA features a built-in debug console that shows debug messages output from MTA functions or from scripts. Keeping it mind that you should have administrator access (unless you modify the ACL to change this), you can open the debug console by typing ''debugscript x'' in the console, where ''x'' is the debug level:
	* '''1:''' only errors		* '''1:''' only errors
Line 8:		Line 8:
	By typing ''debugscript 3'' all messages are visible. Level 3 and level 2 are recommended for most occasions. You should have ''debugscript'' enabled whenever you are testing your scripts as it will help you easily detect and solve typos and other issues.		By typing ''debugscript 3'' all messages are visible. Level 3 and level 2 are recommended for most occasions. You should have ''debugscript'' enabled whenever you are testing your scripts as it will help you easily detect and solve typos and other issues.

	===~~Example~~===		===例===
	~~This example code has two errors:~~		下面这串代码有两处错误。
	<syntaxhighlight lang="lua">		<syntaxhighlight lang="lua">
	function SayHello(message, player)		function SayHello(message, player)

JHXP: Reverted edits by Marcin778 (talk) to last revision by AlexTMjugador

2017-01-01T18:43:54Z

Reverted edits by Marcin778 (talk) to last revision by AlexTMjugador

Show changes

Marcin778 at 18:10, 1 January 2017

2017-01-01T18:10:41Z

Show changes