DayZ:Workbench Script Debugging - Revision history

Lou Montana: Some wiki formatting

2023-04-24T23:24:57Z

Some wiki formatting

← Older revision		Revision as of 01:24, 25 April 2023
Line 185:		Line 185:
	</syntaxhighlight>		</syntaxhighlight>

	~~[[Category:DayZ:~~ Tutorials~~\|Workbench]]~~
			{{GameCategory\|dayz\|Tutorials}}

ImpulZ: /* Loading Mods */

2023-01-26T08:38:24Z

Loading Mods

← Older revision		Revision as of 10:38, 26 January 2023
Line 42:		Line 42:

	<syntaxhighlight lang="batch">		<syntaxhighlight lang="batch">
	start /D "WorkbenchInstallationFolder" workbenchApp.exe "-mod=P:\~~Mods\@~~FirstMod"		start /D "WorkbenchInstallationFolder" workbenchApp.exe "-mod=P:\FirstMod"
	</syntaxhighlight>		</syntaxhighlight>

	Additional mods can be added by being delimited by a semi-colon. For example: ''-mod=P:\~~Mods\@~~FirstMod;P:\~~Mods\@~~SecondMod''.		Additional mods can be added by being delimited by a semi-colon. For example: ''-mod=P:\FirstMod;P:\SecondMod''.

	== Connecting Workbench to DayZ ==		== Connecting Workbench to DayZ ==

Jacob Mango: Put more emphasis on a proper structure

2021-12-23T14:44:50Z

Put more emphasis on a proper structure

Show changes

Pr9inichek: Add some

2021-07-21T20:10:38Z

Add some <br>

Pr9inichek: add a some \n

2021-07-21T19:56:25Z

add a some \n

← Older revision		Revision as of 21:56, 21 July 2021
Line 13:		Line 13:


	Note: For script debugging, only the script.pbo file needs to be extracted, containing the scripts\ folder. This will allow you to debug the running script. It is recommended to extract everything as '''Workbench''' has additional tools that can help you with modding.		Note: For script debugging, only the script.pbo file needs to be extracted, containing the scripts\ folder.
			This will allow you to debug the running script.
			It is recommended to extract everything as '''Workbench''' has additional tools that can help you with modding.

	== Workbench Setup ==		== Workbench Setup ==

	Launch the Workbench from Dayz Tools\Bin\Workbench\workbenchApp.exe or using the tool launcher. From the top menu, navigate to "'''Workbench → Options'''" and point the '''Source Data directory''' to where you have your data extracted, ideally just P:\		Launch the Workbench from Dayz Tools\Bin\Workbench\workbenchApp.exe or using the tool launcher.
			From the top menu, navigate to "'''Workbench → Options'''" and point the '''Source Data directory''' to where you have your data extracted, ideally just P:\


Line 33:		Line 36:
	== Connecting Workbench to DayZ ==		== Connecting Workbench to DayZ ==

	The '''DayZDiag_x64.exe''' is able to act as a client or as a server (with the addition of the -server command line parameter). It takes all the other parameters like the base executable.		The '''DayZDiag_x64.exe''' is able to act as a client or as a server (with the addition of the -server command line parameter).
			It takes all the other parameters like the base executable.

	With workbench running, open the '''Script Editor''' module.		With workbench running, open the '''Script Editor''' module.
Line 63:		Line 67:
	== Script Breakpoints ==		== Script Breakpoints ==

	You can pause the script execution when it reaches a certain line in the script by inserting a '''Breakpoint''' - locate the line you are interested in and then by pressing '''F9''' a red dot should appear to the left, indicating the execution will stop once it reaches that line. If a yellow exclamation mark in a red circle appears instead, it means that that line of code is never really executed and the script will not stop there.		You can pause the script execution when it reaches a certain line in the script by inserting a '''Breakpoint''' - locate the line you are interested in and then by pressing '''F9''' a red dot should appear to the left, indicating the execution will stop once it reaches that line.
			If a yellow exclamation mark in a red circle appears instead, it means that that line of code is never really executed and the script will not stop there.


Line 97:		Line 102:


	If done correctly, after opening the Script Editor you should see all your .c mod files in the '''Script Editor Resource Browser''', in the root of the module that you are modding. So for example if you are modding the Mission module using class missionScriptModule in your config.cpp, all your scripts should appear directly under Mission(scripts/5_Mission) in the '''Script Editor'''. You should also be able to find them using the search functions of the script editor.		If done correctly, after opening the Script Editor you should see all your .c mod files in the '''Script Editor Resource Browser''', in the root of the module that you are modding.
			So for example if you are modding the Mission module using class missionScriptModule in your config.cpp, all your scripts should appear directly under Mission(scripts/5_Mission) in the '''Script Editor'''. You should also be able to find them using the search functions of the script editor.

	Note: You can still use your own folder structure/custom folders inside the script module path in whatever way you want, since the script does not care where the files are placed beside them being in a correct script module. With the above example, placing the scripts in a ''scripts/5_Mission/ModdedScripts'' might help with a visibility while sorting in workbench.		Note: You can still use your own folder structure/custom folders inside the script module path in whatever way you want, since the script does not care where the files are placed beside them being in a correct script module.
			With the above example, placing the scripts in a ''scripts/5_Mission/ModdedScripts'' might help with a visibility while sorting in workbench.


Line 111:		Line 118:


	Make sure that your packed mod folder has '''identical''' data as your unpacked mod folder loaded into workbench. If they are not the same, breakpoints might not work at all. For debugging with unpacked data, see Filepatching below.		Make sure that your packed mod folder has '''identical''' data as your unpacked mod folder loaded into workbench.
			If they are not the same, breakpoints might not work at all.
			For debugging with unpacked data, see Filepatching below.
	If you are debugging in a multiplayer environment ('''DayZDiag_x64.exe''' with -server launch parameter), you may need to change some of the following settings in '''serverDZ.cfg'''		If you are debugging in a multiplayer environment ('''DayZDiag_x64.exe''' with -server launch parameter), you may need to change some of the following settings in '''serverDZ.cfg'''

Line 123:		Line 132:
	== Filepatching ==		== Filepatching ==

	Filepatching allows you to work with unpacked data, saving you the need to repack your pbo every time you make a change. It works by loading your packed mod in a standard fashion while at the same time using '''-filePatching''' launch parameter and having unpacked data present in your steam DayZ folder. If such data is found, the existing data from the packed mod will be patched by the unpacked data.		Filepatching allows you to work with unpacked data, saving you the need to repack your pbo every time you make a change.
			It works by loading your packed mod in a standard fashion while at the same time using '''-filePatching''' launch parameter and having unpacked data present in your steam DayZ folder.
			If such data is found, the existing data from the packed mod will be patched by the unpacked data.


	Requirements:		Requirements:
	* You need to pack your unpacked data at least once - this '''packed version''' will be used when launching the game with '''-mod=Mod''' parameter. If you add/remove additional files, you will have to repack the pbo as well		* You need to pack your unpacked data at least once - this '''packed version''' will be used when launching the game with '''-mod=Mod''' parameter.
			If you add/remove additional files, you will have to repack the pbo as well
	* Your folder with unpacked data needs to be present in your steam DayZ root folder ( ''path\Steam\steamapps\common\DayZ'' )		* Your folder with unpacked data needs to be present in your steam DayZ root folder ( ''path\Steam\steamapps\common\DayZ'' )
	* Structure of the unpacked folder has to be the same as the packed pbo, including the prefix - If your pbo named MyMod is in ''P:\Mods\MyMod\...'' and is built with Mods\MyMod prefix then your unpacked data have to be present in ''path\DayZ\Mods\MyMod\...'' as well		* Structure of the unpacked folder has to be the same as the packed pbo, including the prefix - If your pbo named MyMod is in ''P:\Mods\MyMod\...'' and is built with Mods\MyMod prefix then your unpacked data have to be present in ''path\DayZ\Mods\MyMod\...'' as well
Line 138:		Line 150:


	'''FileSystem''' allows you to specify path where workbench looks for data which is needed for browsing files and creating ScriptModulePaths. This is the source data directory which you are setting in workbench options, so path to your P: is not necessary if you have set it there instead.		'''FileSystem''' allows you to specify path where workbench looks for data which is needed for browsing files and creating ScriptModulePaths.
			This is the source data directory which you are setting in workbench options, so path to your P: is not necessary if you have set it there instead.


Line 179:		Line 192:


	'''ScriptModules''' are paths which are required for script editor functionalities. They are '''automatically set''' when you launch '''Workbench''' with a ''-mod=YourUnpackedMod'' parameter, only set these if you require a custom setup		'''ScriptModules''' are paths which are required for script editor functionalities.
			They are '''automatically set''' when you launch '''Workbench''' with a ''-mod=YourUnpackedMod'' parameter, only set these if you require a custom setup

	<syntaxhighlight lang="c++">		<syntaxhighlight lang="c++">

Lou Montana: Text replacement - " (={2,})([^ = ])(.)([^ = ])(={2,}) " to " $1 $2$3$4 $5 "

2021-01-31T18:27:31Z

Text replacement - " (={2,})([^ = ])(.*)([^ = ])(={2,}) * " to " $1 $2$3$4 $5 "

← Older revision		Revision as of 20:27, 31 January 2021
Line 3:		Line 3:
	Using the diagnostic version of the game executable ('''DayZDiag_x64.exe'''), it is possible to connect Workbench tool to a running instance of the game client/server and break and debug it's execution.		Using the diagnostic version of the game executable ('''DayZDiag_x64.exe'''), it is possible to connect Workbench tool to a running instance of the game client/server and break and debug it's execution.

	==File Setup==		== File Setup ==

	You will require official '''DayZ Tools''' where the '''Workbench''' tool is located and a way to unpack PBOs, using either the '''WorkDrive''' to unpack all the PBOs to your P:\ drive (recommended) or manually extract the script .pbo files (located inside your steam folder, by default C:\Program Files (x86)\Steam\steamapps\common\DayZ\dta\) using the '''BankRev''' tool.		You will require official '''DayZ Tools''' where the '''Workbench''' tool is located and a way to unpack PBOs, using either the '''WorkDrive''' to unpack all the PBOs to your P:\ drive (recommended) or manually extract the script .pbo files (located inside your steam folder, by default C:\Program Files (x86)\Steam\steamapps\common\DayZ\dta\) using the '''BankRev''' tool.
Line 15:		Line 15:
	Note: For script debugging, only the script.pbo file needs to be extracted, containing the scripts\ folder. This will allow you to debug the running script. It is recommended to extract everything as '''Workbench''' has additional tools that can help you with modding.		Note: For script debugging, only the script.pbo file needs to be extracted, containing the scripts\ folder. This will allow you to debug the running script. It is recommended to extract everything as '''Workbench''' has additional tools that can help you with modding.

	==Workbench Setup==		== Workbench Setup ==

	Launch the Workbench from Dayz Tools\Bin\Workbench\workbenchApp.exe or using the tool launcher. From the top menu, navigate to "'''Workbench → Options'''" and point the '''Source Data directory''' to where you have your data extracted, ideally just P:\		Launch the Workbench from Dayz Tools\Bin\Workbench\workbenchApp.exe or using the tool launcher. From the top menu, navigate to "'''Workbench → Options'''" and point the '''Source Data directory''' to where you have your data extracted, ideally just P:\
Line 31:		Line 31:
	[[Image:wb_rsc_browser.png]]		[[Image:wb_rsc_browser.png]]

	==Connecting Workbench to DayZ==		== Connecting Workbench to DayZ ==

	The '''DayZDiag_x64.exe''' is able to act as a client or as a server (with the addition of the -server command line parameter). It takes all the other parameters like the base executable.		The '''DayZDiag_x64.exe''' is able to act as a client or as a server (with the addition of the -server command line parameter). It takes all the other parameters like the base executable.
Line 61:		Line 61:
	Note: If you only want to see the console output, then extracting and loading PBOs is not needed, '''Script Editor''' should connect to the diagnostic executable without them, but then only the console output is available.		Note: If you only want to see the console output, then extracting and loading PBOs is not needed, '''Script Editor''' should connect to the diagnostic executable without them, but then only the console output is available.

	==Script Breakpoints==		== Script Breakpoints ==

	You can pause the script execution when it reaches a certain line in the script by inserting a '''Breakpoint''' - locate the line you are interested in and then by pressing '''F9''' a red dot should appear to the left, indicating the execution will stop once it reaches that line. If a yellow exclamation mark in a red circle appears instead, it means that that line of code is never really executed and the script will not stop there.		You can pause the script execution when it reaches a certain line in the script by inserting a '''Breakpoint''' - locate the line you are interested in and then by pressing '''F9''' a red dot should appear to the left, indicating the execution will stop once it reaches that line. If a yellow exclamation mark in a red circle appears instead, it means that that line of code is never really executed and the script will not stop there.
Line 83:		Line 83:
	Note: You can also add and remove '''Breakpoints''' by left clicking where the red dots appear. Right clicking adds a blue '''Bookmark''' - these don't have any inherent function except marking script in interesting places so you can then easily navigate to them.		Note: You can also add and remove '''Breakpoints''' by left clicking where the red dots appear. Right clicking adds a blue '''Bookmark''' - these don't have any inherent function except marking script in interesting places so you can then easily navigate to them.

	==Debugging Modded Scripts==		== Debugging Modded Scripts ==

	You need to load your modded scripts into '''Workbench''' if you want to debug them.		You need to load your modded scripts into '''Workbench''' if you want to debug them.
Line 133:		Line 133:
	* If in multiplayer environment ('''DayZDiag_x64.exe''' with -server launch parameter), you will need to have '''allowFilePatching = 1;''' setting in '''serverDZ.cfg'''		* If in multiplayer environment ('''DayZDiag_x64.exe''' with -server launch parameter), you will need to have '''allowFilePatching = 1;''' setting in '''serverDZ.cfg'''

	==Advanced Configuration==		== Advanced Configuration ==

	Additional configuration options are possible using the '''dayz.gproj''' file in the Workbench directory		Additional configuration options are possible using the '''dayz.gproj''' file in the Workbench directory

R3vo: category

2021-01-17T14:02:42Z

Thurstonn: Fixed spelling mistakes with DayZDiag_x64.exe

2019-06-18T15:50:16Z

Fixed spelling mistakes with DayZDiag_x64.exe

← Older revision		Revision as of 17:50, 18 June 2019
Line 4:		Line 4:


	Using the diagnostic version of the game executable ('''~~DayZDiax_x64~~.exe'''), it is possible to connect Workbench tool to a running instance of the game client/server and break and debug it's execution.		Using the diagnostic version of the game executable ('''DayZDiag_x64.exe'''), it is possible to connect Workbench tool to a running instance of the game client/server and break and debug it's execution.

	==File Setup==		==File Setup==
Line 36:		Line 36:
	==Connecting Workbench to DayZ==		==Connecting Workbench to DayZ==

	The '''~~DayZDiax_x64~~.exe''' is able to act as a client or as a server (with the addition of the -server command line parameter). It takes all the other parameters like the base executable.		The '''DayZDiag_x64.exe''' is able to act as a client or as a server (with the addition of the -server command line parameter). It takes all the other parameters like the base executable.

	With workbench running, open the '''Script Editor''' module.		With workbench running, open the '''Script Editor''' module.
Line 108:		Line 108:


	You will also need to have your packed mod properly loaded in the game, which means launching the '''~~DayZDiax_x64~~.exe''' with		You will also need to have your packed mod properly loaded in the game, which means launching the '''DayZDiag_x64.exe''' with


Line 115:		Line 115:

	Make sure that your packed mod folder has '''identical''' data as your unpacked mod folder loaded into workbench. If they are not the same, breakpoints might not work at all. For debugging with unpacked data, see Filepatching below.		Make sure that your packed mod folder has '''identical''' data as your unpacked mod folder loaded into workbench. If they are not the same, breakpoints might not work at all. For debugging with unpacked data, see Filepatching below.
	If you are debugging in a multiplayer environment ('''~~DayZDiax_x64~~.exe''' with -server launch parameter), you may need to change some of the following settings in '''serverDZ.cfg'''		If you are debugging in a multiplayer environment ('''DayZDiag_x64.exe''' with -server launch parameter), you may need to change some of the following settings in '''serverDZ.cfg'''


Line 133:		Line 133:
	* Your folder with unpacked data needs to be present in your steam DayZ root folder ( ''path\Steam\steamapps\common\DayZ'' )		* Your folder with unpacked data needs to be present in your steam DayZ root folder ( ''path\Steam\steamapps\common\DayZ'' )
	* Structure of the unpacked folder has to be the same as the packed pbo, including the prefix - If your pbo named MyMod is in ''P:\Mods\MyMod\...'' and is built with Mods\MyMod prefix then your unpacked data have to be present in ''path\DayZ\Mods\MyMod\...'' as well		* Structure of the unpacked folder has to be the same as the packed pbo, including the prefix - If your pbo named MyMod is in ''P:\Mods\MyMod\...'' and is built with Mods\MyMod prefix then your unpacked data have to be present in ''path\DayZ\Mods\MyMod\...'' as well
	* Your '''~~DayZDiax_x64~~.exe''' has to be launched with -filePatching (both client and server)		* Your '''DayZDiag_x64.exe''' has to be launched with -filePatching (both client and server)
	* If in multiplayer environment ('''~~DayZDiax_x64~~.exe''' with -server launch parameter), you will need to have '''allowFilePatching = 1;''' setting in '''serverDZ.cfg'''		* If in multiplayer environment ('''DayZDiag_x64.exe''' with -server launch parameter), you will need to have '''allowFilePatching = 1;''' setting in '''serverDZ.cfg'''

	==Advanced Configuration==		==Advanced Configuration==

RVn: /* Advanced Configuration */

2019-06-18T15:22:28Z

Advanced Configuration

← Older revision		Revision as of 17:22, 18 June 2019
Line 141:		Line 141:


	'''FileSystem''' allows you to specify path where workbench looks for data. This is the source data directory which you are setting in workbench options, so path to your P: is not necessary if you have set it there instead.		'''FileSystem''' allows you to specify path where workbench looks for data which is needed for browsing files and creating ScriptModulePaths. This is the source data directory which you are setting in workbench options, so path to your P: is not necessary if you have set it there instead.


			Be aware of prefixes! When launching Workbench with '''-mod=YourUnpackedMod''' parameter to set the '''ScriptModulePaths''' automatically, FileSystemPath is used as part of the final path.
			This means that if your mod folder is located in

			''P:\OtherMods\MyMod''

			and it's ScriptModulePath in '''config.cpp''' is

			''MyMod/scripts/etc''

			then your file system has to point to

			''P:\OtherMods''

			'''OR''' the path in config.cpp has to be updated to

			''OtherMods/MyMod/scripts/etc''

			in order to create correct full path(FileSystemPath+ScriptModulePath) which will work in '''Script Editor'''.

	<syntaxhighlight lang="c++">		<syntaxhighlight lang="c++">
Line 154:		Line 173:
	Name "Mods folder"		Name "Mods folder"
	Directory "P:\OtherMods"		Directory "P:\OtherMods"
	}
	~~FileSystemPathClass { // Custom Dir for the One True Mod~~
	~~Name "Mods folder"~~
	~~Directory "P:\BestMod"~~
	}		}
	FileSystemPathClass { // Game dir		FileSystemPathClass { // Game dir
Line 167:		Line 182:


	'''ScriptModules''' are paths which are required for script editor functionalities. They are '''automatically set''' when you launch '''Workbench''' with a ''-mod=~~YourMod~~'' parameter, only set these if you require a custom setup		'''ScriptModules''' are paths which are required for script editor functionalities. They are '''automatically set''' when you launch '''Workbench''' with a ''-mod=YourUnpackedMod'' parameter, only set these if you require a custom setup

	<syntaxhighlight lang="c++">		<syntaxhighlight lang="c++">

RVn: /* Filepatching */

2019-06-17T15:04:50Z

Filepatching

← Older revision		Revision as of 17:04, 17 June 2019
Line 125:		Line 125:

	== Filepatching ==		== Filepatching ==

			Filepatching allows you to work with unpacked data, saving you the need to repack your pbo every time you make a change. It works by loading your packed mod in a standard fashion while at the same time using '''-filePatching''' launch parameter and having unpacked data present in your steam DayZ folder. If such data is found, the existing data from the packed mod will be patched by the unpacked data.


			Requirements:
			* You need to pack your unpacked data at least once - this '''packed version''' will be used when launching the game with '''-mod=Mod''' parameter. If you add/remove additional files, you will have to repack the pbo as well
			* Your folder with unpacked data needs to be present in your steam DayZ root folder ( ''path\Steam\steamapps\common\DayZ'' )
			* Structure of the unpacked folder has to be the same as the packed pbo, including the prefix - If your pbo named MyMod is in ''P:\Mods\MyMod\...'' and is built with Mods\MyMod prefix then your unpacked data have to be present in ''path\DayZ\Mods\MyMod\...'' as well
			* Your '''DayZDiax_x64.exe''' has to be launched with -filePatching (both client and server)
			* If in multiplayer environment ('''DayZDiax_x64.exe''' with -server launch parameter), you will need to have '''allowFilePatching = 1;''' setting in '''serverDZ.cfg'''

	==Advanced Configuration==		==Advanced Configuration==

← Older revision		Revision as of 16:02, 17 January 2021
Line 1:		Line 1:
	~~[[Category:DayZ:Tutorials\|Workbench]]~~

	__TOC__		__TOC__


	Using the diagnostic version of the game executable ('''DayZDiag_x64.exe'''), it is possible to connect Workbench tool to a running instance of the game client/server and break and debug it's execution.		Using the diagnostic version of the game executable ('''DayZDiag_x64.exe'''), it is possible to connect Workbench tool to a running instance of the game client/server and break and debug it's execution.
Line 231:		Line 228:
	}		}
	</syntaxhighlight>		</syntaxhighlight>

			[[Category:DayZ: Tutorials\|Workbench]]

← Older revision		Revision as of 22:10, 21 July 2021
Line 14:		Line 14:

	Note: For script debugging, only the script.pbo file needs to be extracted, containing the scripts\ folder.		Note: For script debugging, only the script.pbo file needs to be extracted, containing the scripts\ folder.
	This will allow you to debug the running script.		<br>This will allow you to debug the running script.
	It is recommended to extract everything as '''Workbench''' has additional tools that can help you with modding.		<br>It is recommended to extract everything as '''Workbench''' has additional tools that can help you with modding.

	== Workbench Setup ==		== Workbench Setup ==

	Launch the Workbench from Dayz Tools\Bin\Workbench\workbenchApp.exe or using the tool launcher.		Launch the Workbench from Dayz Tools\Bin\Workbench\workbenchApp.exe or using the tool launcher.
	From the top menu, navigate to "'''Workbench → Options'''" and point the '''Source Data directory''' to where you have your data extracted, ideally just P:\		<br>From the top menu, navigate to "'''Workbench → Options'''" and point the '''Source Data directory''' to where you have your data extracted, ideally just P:\


Line 37:		Line 37:

	The '''DayZDiag_x64.exe''' is able to act as a client or as a server (with the addition of the -server command line parameter).		The '''DayZDiag_x64.exe''' is able to act as a client or as a server (with the addition of the -server command line parameter).
	It takes all the other parameters like the base executable.		<br>It takes all the other parameters like the base executable.

	With workbench running, open the '''Script Editor''' module.		<br>With workbench running, open the '''Script Editor''' module.


Line 68:		Line 68:

	You can pause the script execution when it reaches a certain line in the script by inserting a '''Breakpoint''' - locate the line you are interested in and then by pressing '''F9''' a red dot should appear to the left, indicating the execution will stop once it reaches that line.		You can pause the script execution when it reaches a certain line in the script by inserting a '''Breakpoint''' - locate the line you are interested in and then by pressing '''F9''' a red dot should appear to the left, indicating the execution will stop once it reaches that line.
	If a yellow exclamation mark in a red circle appears instead, it means that that line of code is never really executed and the script will not stop there.		<br>If a yellow exclamation mark in a red circle appears instead, it means that that line of code is never really executed and the script will not stop there.


Line 103:		Line 103:

	If done correctly, after opening the Script Editor you should see all your .c mod files in the '''Script Editor Resource Browser''', in the root of the module that you are modding.		If done correctly, after opening the Script Editor you should see all your .c mod files in the '''Script Editor Resource Browser''', in the root of the module that you are modding.
	So for example if you are modding the Mission module using class missionScriptModule in your config.cpp, all your scripts should appear directly under Mission(scripts/5_Mission) in the '''Script Editor'''. You should also be able to find them using the search functions of the script editor.		<br>So for example if you are modding the Mission module using class missionScriptModule in your config.cpp, all your scripts should appear directly under Mission(scripts/5_Mission) in the '''Script Editor'''. You should also be able to find them using the search functions of the script editor.

	Note: You can still use your own folder structure/custom folders inside the script module path in whatever way you want, since the script does not care where the files are placed beside them being in a correct script module.		Note: You can still use your own folder structure/custom folders inside the script module path in whatever way you want, since the script does not care where the files are placed beside them being in a correct script module.
	With the above example, placing the scripts in a ''scripts/5_Mission/ModdedScripts'' might help with a visibility while sorting in workbench.		<br>With the above example, placing the scripts in a ''scripts/5_Mission/ModdedScripts'' might help with a visibility while sorting in workbench.


Line 119:		Line 119:

	Make sure that your packed mod folder has '''identical''' data as your unpacked mod folder loaded into workbench.		Make sure that your packed mod folder has '''identical''' data as your unpacked mod folder loaded into workbench.
	If they are not the same, breakpoints might not work at all.		<br>If they are not the same, breakpoints might not work at all.
	For debugging with unpacked data, see Filepatching below.		<br>For debugging with unpacked data, see Filepatching below.
	If you are debugging in a multiplayer environment ('''DayZDiag_x64.exe''' with -server launch parameter), you may need to change some of the following settings in '''serverDZ.cfg'''		<br>If you are debugging in a multiplayer environment ('''DayZDiag_x64.exe''' with -server launch parameter), you may need to change some of the following settings in '''serverDZ.cfg'''


Line 133:		Line 133:

	Filepatching allows you to work with unpacked data, saving you the need to repack your pbo every time you make a change.		Filepatching allows you to work with unpacked data, saving you the need to repack your pbo every time you make a change.
	It works by loading your packed mod in a standard fashion while at the same time using '''-filePatching''' launch parameter and having unpacked data present in your steam DayZ folder.		<br>It works by loading your packed mod in a standard fashion while at the same time using '''-filePatching''' launch parameter and having unpacked data present in your steam DayZ folder.
	If such data is found, the existing data from the packed mod will be patched by the unpacked data.		<br>If such data is found, the existing data from the packed mod will be patched by the unpacked data.


Line 151:		Line 151:

	'''FileSystem''' allows you to specify path where workbench looks for data which is needed for browsing files and creating ScriptModulePaths.		'''FileSystem''' allows you to specify path where workbench looks for data which is needed for browsing files and creating ScriptModulePaths.
	This is the source data directory which you are setting in workbench options, so path to your P: is not necessary if you have set it there instead.		<br>This is the source data directory which you are setting in workbench options, so path to your P: is not necessary if you have set it there instead.


	Be aware of prefixes! When launching Workbench with '''-mod=YourUnpackedMod''' parameter to set the '''ScriptModulePaths''' automatically, FileSystemPath is used as part of the final path.		Be aware of prefixes! When launching Workbench with '''-mod=YourUnpackedMod''' parameter to set the '''ScriptModulePaths''' automatically, FileSystemPath is used as part of the final path.
	This means that if your mod folder is located in		<br>This means that if your mod folder is located in

	''P:\OtherMods\MyMod''		''P:\OtherMods\MyMod''