Debugging: Difference between revisions
(Created page with "This is a quick newbie guide to what debugging is and how to do it. Debugging is the process of adding messages into your code to provide insight of the script's process or w...") |
No edit summary |
||
| Line 2: | Line 2: | ||
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. | 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. | ||
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 rely on server or client side errors, you can run the game with '''-dev''' launch argument to run the game in dev mode, which prints client side script errors in the chat, and also you can find the errors in your '''%appdata%/local/Onset/Logs/''' folder. | |||
Revision as of 15:10, 18 December 2019
This is a quick newbie guide to what debugging is and how to do it.
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.
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 rely on server or client side errors, you can run the game with -dev launch argument to run the game in dev mode, which prints client side script errors in the chat, and also you can find the errors in your %appdata%/local/Onset/Logs/ folder.
