Debugging - Revision history

BlueMountains at 16:26, 8 October 2020

2020-10-08T16:26:33Z

← Older revision		Revision as of 16:26, 8 October 2020
Line 46:		Line 46:
	[[File:ClientConsole.PNG\|900px]]		[[File:ClientConsole.PNG\|900px]]

	=== Debugging ~~CEF~~ ===		=== Debugging WebUIs ===
	In game version 1.0.3, a feature was introduced to debug WebUIs. Inspect your Onset UI in Google Chrome. Start Onset with the '''-dev''' flag and connect to '''localhost:9222''' in Chrome. You can specify a different port to Onset like this: '''-cefdebug=1337'''. You can use '''alert("")''' in your Javascript code to test it. The errors in your Javascript code can also be found in '''%AppData%\..\Local\Onset\Saved\Logs\cef3.log'''.		In game version 1.0.3, a feature was introduced to debug WebUIs. Inspect your Onset UI in Google Chrome. Start Onset with the '''-dev''' flag and connect to '''localhost:9222''' in Chrome. You can specify a different port to Onset like this: '''-cefdebug=1337'''. You can use '''alert("")''' in your Javascript code to test it. The errors in your Javascript code can also be found in '''%AppData%\..\Local\Onset\Saved\Logs\cef3.log'''.

BlueMountains at 09:48, 7 October 2020

2020-10-07T09:48:48Z

@@ Line 29: / Line 29: @@
 end
 </syntaxhighlight>
 === Debugging CEF ===

BlueMountains at 19:29, 8 September 2020

2020-09-08T19:29:25Z

← Older revision		Revision as of 19:29, 8 September 2020
Line 1:		Line 1:
	== Debugging your own code ==		== Debugging your own code ==
	This ~~is a quick newbie~~ guide ~~to what debugging is and~~ how to ~~do it.~~		This guide will teach you on how to debug your Lua code and WebUIs.

	~~Debugging is the process of adding messages into~~ your code to provide insight of the script's process or working. The debugging helps us to find out where the issue occurs, which can help us where exactly our issue is present or is coming from. The errors in the code can be a huge problem as they can skip the code or crash the server where they occcur.

	<div class="noprint" style="float:right;">		<div class="noprint" style="float:right;">
	[[File:clientOption.png\|Steam Client Options]]		[[File:clientOption.png\|Steam Client Options]]
	</div>		</div>

			Debugging is the process of adding messages into your code to provide insight of the script's process or working. The debugging helps us to find out where the issue occurs, which can help us where exactly our issue is present or is coming from. The errors in the code can be a huge problem as they can skip the code or crash the server where they occur.

	This process is based on few different techniques, the first one is to add (print) messages, which can help you which part of the code gets run and what values you are getting.		This process is based on few different techniques, the first one is to add (print) messages, which can help you which part of the code gets run and what values you are getting.

	The second technique is to add this piece of code in your server side script, and as for the client you can run the game with '''-dev''' launch argument to run the game in development mode, which prints client side script errors in the chat if you have this piece of code in your script* and also you can find the errors in your '''%appdata%\..\Local\Onset\Saved\Logs''' folder.		The second technique is to add this piece of code in your server side script, and as for the client you can run the game with '''-dev''' launch argument to run the game in development mode, which prints client side script errors in the chat if you have this piece of code in your script* and also you can find the errors in your '''%appdata%\..\Local\Onset\Saved\Logs''' folder.

	In game version 1.0.3, Talos introduced a new method to debug web UIs. Inspect your Onset UI in Google Chrome. Start Onset with the '''-dev''' flag and connect to '''localhost:9222''' in Chrome. You can specify a different port to Onset like this: '''-cefdebug=1337'''. You can use '''alert("")''' in your JS code to test it. The errors in your JS code can also be found in '''%AppData%\..\Local\Onset\Saved\Logs\cef3.log'''.

	Code*:		Code*:
Line 32:		Line 30:
	</syntaxhighlight>		</syntaxhighlight>

			=== Debugging CEF ===
			In game version 1.0.3, a feature was introduced to debug WebUIs. Inspect your Onset UI in Google Chrome. Start Onset with the '''-dev''' flag and connect to '''localhost:9222''' in Chrome. You can specify a different port to Onset like this: '''-cefdebug=1337'''. You can use '''alert("")''' in your Javascript code to test it. The errors in your Javascript code can also be found in '''%AppData%\..\Local\Onset\Saved\Logs\cef3.log'''.

			[[File:cefdebug.png\|1000px]]

	== Debugging server crashes ==		== Debugging server crashes ==

BlueMountains at 18:07, 18 August 2020

2020-08-18T18:07:49Z

← Older revision		Revision as of 18:07, 18 August 2020
Line 42:		Line 42:
	If the key ''LocalDumps'' does not exist then create it. Inside of the ''LocalDumps'' key create another one named ''OnsetServer.exe''.		If the key ''LocalDumps'' does not exist then create it. Inside of the ''LocalDumps'' key create another one named ''OnsetServer.exe''.
	Now right click on the right side and create a new value with the name ''DumpType'' and set data = 2		Now right click on the right side and create a new value with the name ''DumpType'' and set data = 2
	The .dmp crash dump files will be in the folder <pre>%LOCALAPPDATA%\CrashDumps</pre>.		The .dmp crash dump files will be in the folder: <pre>%LOCALAPPDATA%\CrashDumps</pre>.
	[[File:WERregistry.PNG]]		[[File:WERregistry.PNG]]

	=== Linux ===		=== Linux ===
	Before launching your Onset Server execute the following command in a terminal.		Before launching your Onset Server, execute the following command in a terminal.
	<pre>ulimit -c unlimited</pre>		<pre>ulimit -c unlimited</pre>
	Core crash dump files should appear in the same folder as your server executable with the name "core" in it.		Core crash dump files should appear in the same folder as your server executable with the name "core" in it.

BlueMountains at 18:03, 18 August 2020

2020-08-18T18:03:55Z

← Older revision		Revision as of 18:03, 18 August 2020
Line 1:		Line 1:
	==~~=Test=~~==		== Debugging your own code ==
	This is a quick newbie guide to what debugging is and how to do it.		This is a quick newbie guide to what debugging is and how to do it.

BlueMountains at 18:03, 18 August 2020

2020-08-18T18:03:17Z

← Older revision		Revision as of 18:03, 18 August 2020
Line 1:		Line 1:
			===Test===
	This is a quick newbie guide to what debugging is and how to do it.		This is a quick newbie guide to what debugging is and how to do it.

BlueMountains at 18:02, 18 August 2020

2020-08-18T18:02:43Z

← Older revision		Revision as of 18:02, 18 August 2020
Line 30:		Line 30:
	end		end
	</syntaxhighlight>		</syntaxhighlight>


			== Debugging server crashes ==
			In case your Onset server crashes and you have no idea why, you can enable crash dumps that contain useful information about the crash.
			The crash dump files should be sent to the developer of the game who can then take a closer look at them.

			=== Windows ===
			In the registry (regedit.exe) go to the following location:
			<pre>HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\Windows Error Reporting\LocalDumps</pre>
			If the key ''LocalDumps'' does not exist then create it. Inside of the ''LocalDumps'' key create another one named ''OnsetServer.exe''.
			Now right click on the right side and create a new value with the name ''DumpType'' and set data = 2
			The .dmp crash dump files will be in the folder <pre>%LOCALAPPDATA%\CrashDumps</pre>.
			[[File:WERregistry.PNG]]

			=== Linux ===
			Before launching your Onset Server execute the following command in a terminal.
			<pre>ulimit -c unlimited</pre>
			Core crash dump files should appear in the same folder as your server executable with the name "core" in it.

28days at 10:19, 20 January 2020

2020-01-20T10:19:36Z

← Older revision		Revision as of 10:19, 20 January 2020
Line 11:		Line 11:
	The second technique is to add this piece of code in your server side script, and as for the client you can run the game with '''-dev''' launch argument to run the game in development mode, which prints client side script errors in the chat if you have this piece of code in your script* and also you can find the errors in your '''%appdata%\..\Local\Onset\Saved\Logs''' folder.		The second technique is to add this piece of code in your server side script, and as for the client you can run the game with '''-dev''' launch argument to run the game in development mode, which prints client side script errors in the chat if you have this piece of code in your script* and also you can find the errors in your '''%appdata%\..\Local\Onset\Saved\Logs''' folder.

	In game version 1.0.3, Talos introduced a new method to debug web UIs. Inspect your Onset UI in Google Chrome. Start Onset with the '''-dev''' flag and connect to '''localhost:9222''' in Chrome. You can specify a different port to Onset like this: '''-cefdebug=1337'''. You can use '''alert("")''' in your JS code to test it.		In game version 1.0.3, Talos introduced a new method to debug web UIs. Inspect your Onset UI in Google Chrome. Start Onset with the '''-dev''' flag and connect to '''localhost:9222''' in Chrome. You can specify a different port to Onset like this: '''-cefdebug=1337'''. You can use '''alert("")''' in your JS code to test it. The errors in your JS code can also be found in '''%AppData%\..\Local\Onset\Saved\Logs\cef3.log'''.

	Code*:		Code*:

28days: Updated and finalized changes

2020-01-20T10:17:23Z

Updated and finalized changes

← Older revision		Revision as of 10:17, 20 January 2020
Line 11:		Line 11:
	The second technique is to add this piece of code in your server side script, and as for the client you can run the game with '''-dev''' launch argument to run the game in development mode, which prints client side script errors in the chat if you have this piece of code in your script* and also you can find the errors in your '''%appdata%\..\Local\Onset\Saved\Logs''' folder.		The second technique is to add this piece of code in your server side script, and as for the client you can run the game with '''-dev''' launch argument to run the game in development mode, which prints client side script errors in the chat if you have this piece of code in your script* and also you can find the errors in your '''%appdata%\..\Local\Onset\Saved\Logs''' folder.

	In game version 1.0.3, Talos introduced a new method to debug web UIs. Inspect your Onset UI in Google Chrome. Start Onset with the '''-dev''' flag and connect to '''localhost:9222''' in Chrome. You can specify a different port to Onset like this: '''-cefdebug=1337''' You can use '''alert("")''' in your JS code to test ~~whether your code works not~~.		In game version 1.0.3, Talos introduced a new method to debug web UIs. Inspect your Onset UI in Google Chrome. Start Onset with the '''-dev''' flag and connect to '''localhost:9222''' in Chrome. You can specify a different port to Onset like this: '''-cefdebug=1337'''. You can use '''alert("")''' in your JS code to test it.

	Code*:		Code*:

28days at 10:16, 20 January 2020

2020-01-20T10:16:04Z

← Older revision		Revision as of 10:16, 20 January 2020
Line 11:		Line 11:
	The second technique is to add this piece of code in your server side script, and as for the client you can run the game with '''-dev''' launch argument to run the game in development mode, which prints client side script errors in the chat if you have this piece of code in your script* and also you can find the errors in your '''%appdata%\..\Local\Onset\Saved\Logs''' folder.		The second technique is to add this piece of code in your server side script, and as for the client you can run the game with '''-dev''' launch argument to run the game in development mode, which prints client side script errors in the chat if you have this piece of code in your script* and also you can find the errors in your '''%appdata%\..\Local\Onset\Saved\Logs''' folder.

	~~Please note that you can~~ '''~~not~~''' ~~debug your web UIs with this method,~~ and ~~has~~ to ~~be done externally!~~ You can use '''alert("")''' in your JS code to test whether your code works not.		In game version 1.0.3, Talos introduced a new method to debug web UIs. Inspect your Onset UI in Google Chrome. Start Onset with the '''-dev''' flag and connect to '''localhost:9222''' in Chrome. You can specify a different port to Onset like this: '''-cefdebug=1337''' You can use '''alert("")''' in your JS code to test whether your code works not.

	Code*:		Code*: