2DA - Revision history

Lynamy: /* Users of Open Office */ Google docs no longer does .xls (only .xlsx)

2013-08-02T18:15:46Z

‎Users of Open Office: Google docs no longer does .xls (only .xlsx)

Proleric1: /* Excel file formatting */

2011-01-18T07:48:15Z

‎Excel file formatting

Sunjammer: Applied Languages template

2010-10-26T12:28:10Z

Applied Languages template

Kelamor: Add links for other language

2010-10-25T00:39:06Z

Add links for other language

Sunjammer: /* Guidelines */ fixed links so they are pointing to "2da types" not "dascript types"

2010-03-27T00:54:20Z

‎Guidelines: fixed links so they are pointing to "2da types" not "dascript types"

Proleric1: /* See Also */

2010-03-21T10:29:54Z

‎See Also

Proleric1: /* Reserved ID Ranges and overriding existing rows */

2010-03-05T14:16:12Z

‎Reserved ID Ranges and overriding existing rows

Proleric1: /* Adding Strings */

2010-03-05T13:50:09Z

‎Adding Strings

Craig Graff: /* Users of Open Office */

2010-03-03T03:43:46Z

‎Users of Open Office

FollowTheGourd: Score one for Google Docs. Mentioning a specific case of FLOAT32 trunction as Falloutboy mentioned a while ago.

2010-02-16T05:15:33Z

Score one for Google Docs. Mentioning a specific case of FLOAT32 trunction as Falloutboy mentioned a while ago.

@@ Line 151: / Line 151: @@
 == Users of Open Office ==
-* Users of Open Office may find that no .gda file is created when they use ExcelProcessor.exe - one workaround is to copy a worksheet from an existing .xls file (such as placeable_types from placeables.xls), process the file, then remove the extraneous .gda file (e.g. placeable_types.gda). Alternately, upload your .xls file to Google Docs and then download the file as Excel format, then process the file with ExcelProcessor.exe.
+* Users of Open Office may find that no .gda file is created when they use ExcelProcessor.exe - one workaround is to copy a worksheet from an existing .xls file (such as placeable_types from placeables.xls), process the file, then remove the extraneous .gda file (e.g. placeable_types.gda).
 * When editing existing xls files, it also works to leave the format as standard while saving the file. Open Office asks to change the file to its own spreatsheet format when saving a format other then its own, don't change the format and it should work. [Edit- And yet it doesn't seem to.]
 == Adding Strings ==

@@ Line 12: / Line 12: @@
 == Excel file formatting ==
-The source files for 2DAs are Microsoft Excel worksheets. This allows a wide variety of sophisticated techniques to be used to generate the values of the 2DA fields, such as macros and formulas. It also makes editing much easier since the columns can be annotated and formatted in helpful ways, and multiple related worksheets can be grouped into one file. Before they can be used by the toolset or the game, 2DAs must be converted from Excel files into a more efficient form. Processed 2DAs are stored in files with the .[[GDA]] extension.
+The source files for 2DAs are Microsoft Excel worksheets. This allows a wide variety of sophisticated techniques to be used to generate the values of the 2DA fields, such as macros and formulas. It also makes editing much easier since the columns can be annotated and formatted in helpful ways, and multiple related worksheets can be grouped into one file.
 ''See: [[compiling 2DAs]]'' - for several methods of how to perform this conversion, and where to put 2DAs.

← Older revision		Revision as of 12:28, 26 October 2010
Line 1:		Line 1:
−	~~<includeonly>{{K-langs:{{{enname\|}}}}}</includeonly><noinclude>{{K-langs:H:f 2DA}}~~
−	*Перевод: Kelamor / [mailto:kelamor@inbox.ru Почта] / [[User:Kelamor\|Переводы]]
−	~~----------------~~
−
−
	Many of the properties of objects in the toolset make reference to 2DAs (two-dimensional arrays). These are read-only arrays containing various data used by scripting and the game engine. Each 2DA is simply an organized collection of strings and numbers. The specific function of each 2DA depends on how it is used by other systems in the game.		Many of the properties of objects in the toolset make reference to 2DAs (two-dimensional arrays). These are read-only arrays containing various data used by scripting and the game engine. Each 2DA is simply an organized collection of strings and numbers. The specific function of each 2DA depends on how it is used by other systems in the game.

Line 195:		Line 190:

	[[Category:2DAs]]		[[Category:2DAs]]
		+	{{Languages}}

← Older revision		Revision as of 00:39, 25 October 2010
Line 1:		Line 1:
		+	<includeonly>{{K-langs:{{{enname\|}}}}}</includeonly><noinclude>{{K-langs:H:f 2DA}}
		+	*Перевод: Kelamor / [mailto:kelamor@inbox.ru Почта] / [[User:Kelamor\|Переводы]]
		+	----------------
		+
		+
	Many of the properties of objects in the toolset make reference to 2DAs (two-dimensional arrays). These are read-only arrays containing various data used by scripting and the game engine. Each 2DA is simply an organized collection of strings and numbers. The specific function of each 2DA depends on how it is used by other systems in the game.		Many of the properties of objects in the toolset make reference to 2DAs (two-dimensional arrays). These are read-only arrays containing various data used by scripting and the game engine. Each 2DA is simply an organized collection of strings and numbers. The specific function of each 2DA depends on how it is used by other systems in the game.

@@ Line 73: / Line 73: @@
 *A blank row or column will determine the dimension of the spreadsheet in that direction. Everything past that point is ignored by the binarizer.
 *Column names are case sensitive. This is because of the CRC32 algorithm used to generate the hash key. Changing the case of a column name after it is in use will break the game. White space before and after a column name will be removed before hashing.
-*Row 2 will be a "types" row. Each is a single word: [[int]], [[string]] (single chars as well), [[resource]], [[float]] or [[bool]]. A special type "[[comment]]" can be used to exclude a column from export.
+*Row 2 will be a "types" row. Each is a single word: [[int (2da type)|int]], [[string (2da type)|string]] (single chars as well), [[resource (2da type)|resource]], [[float (2da type)|float]] or [[bool (2da type)|bool]]. A special type "[[comment (2da type)|comment]]" can be used to exclude a column from export.
 *Any column with string data that refers to files should have a type of "resource" and not "string". This is because the "resource" type is used to determine dependencies for the 2DA file.
 *'bool' type may be one of: a zero or non-zero number, Yes or No (case insensitive), or words beginning with T or F (such as True! and False!). NOTE: You cannot use TRUE and FALSE because Excel converts those to a special keyword the binarizer can't parse properly at this time. '''Note:''' the scripting language doesn't have a function for retrieving boolean values from a 2DA, and the behavior of Get2DAInt when retrieving a boolean is untested. It is probably safer to just use an integer for scripting purposes.

← Older revision		Revision as of 10:29, 21 March 2010
Line 178:		Line 178:

	The previous Version stated: ''Take that StringID and add 16777216 to the number.'' this appears to be wrong and is likely a holdover from NWN.		The previous Version stated: ''Take that StringID and add 16777216 to the number.'' this appears to be wrong and is likely a holdover from NWN.
		+
		+	== Using a custom 2DA in the toolset ==
		+
		+	Some 2DA tables are used by the toolset itself - for example, appearances for creatures and rewards for plots.
		+
		+	Once a custom GDA is in the export folder for your module, the next time the toolset is started, it will use your custom table.

	== See Also ==		== See Also ==

← Older revision		Revision as of 14:16, 5 March 2010
Line 130:		Line 130:

	To help ensure compatibility between authors' custom content, you should make sure that the ranges you choose don't conflict with ones already in use: [[2DA_ranges_in_use]].		To help ensure compatibility between authors' custom content, you should make sure that the ranges you choose don't conflict with ones already in use: [[2DA_ranges_in_use]].
		+
		+	To ensure that the M2DA suffix is unique, you might like to register and use a code for your module - see [[Prefixes in use]].

	''See: [[compiling 2DAs#Afterwards\|compiling 2DAs]]'' - for Information on where to place M2DA files to achieve the desired effect.		''See: [[compiling 2DAs#Afterwards\|compiling 2DAs]]'' - for Information on where to place M2DA files to achieve the desired effect.

← Older revision		Revision as of 13:50, 5 March 2010
Line 176:		Line 176:

	The previous Version stated: ''Take that StringID and add 16777216 to the number.'' this appears to be wrong and is likely a holdover from NWN.		The previous Version stated: ''Take that StringID and add 16777216 to the number.'' this appears to be wrong and is likely a holdover from NWN.
		+
		+	== See Also ==
		+
		+	*[[Compatibility]]

	[[Category:2DAs]]		[[Category:2DAs]]