Introductory tutorial - Revision history

Sunjammer: Fixing image

2011-08-10T22:19:10Z

Fixing image

Sunjammer: Removed misleading link

2011-06-11T12:08:43Z

Removed misleading link

Sunjammer: Fixing link

2011-06-11T12:05:02Z

Fixing link

Proleric1: /* Palette */

2010-03-01T17:10:34Z

‎Palette

Eshme at 16:58, 12 January 2010

2010-01-12T16:58:23Z

Eshme at 21:59, 11 January 2010

2010-01-11T21:59:15Z

Eshme at 21:42, 11 January 2010

2010-01-11T21:42:23Z

Eshme at 21:41, 11 January 2010

2010-01-11T21:41:35Z

Illyism at 12:10, 25 November 2009

2009-11-25T12:10:46Z

Illyism at 09:58, 25 November 2009

2009-11-25T09:58:27Z

@@ Line 71: / Line 71: @@
 The properties can be grouped by category (in this case General, Actions, Audio and Map), with each group being collapsible by clicking on the &#8863; symbol. They can also be set to a simple alphabetical list of all properties. The name of the property is listed in the left-hand column and the value of the property is in the right-hand column.
-Some properties actually consist of more than just a single simple value. The "Variables" property is one such; in this example you can see that when it's selected a button with an ellipsis ([[Image:ellipsis.png]]) appears, and when you click on the ellipsis button a specialized editing window appears for that property.
+Some properties actually consist of more than just a single simple value. The "Variables" property is one such; in this example you can see that when it's selected a button with an ellipsis ([[Image:ellipsis.png|link=]]) appears, and when you click on the ellipsis button a specialized editing window appears for that property.
 When a property cannot be edited at the current time, for whatever reason, this is indicated by greying out both the name and the value. In this example the "Resource Name" property cannot be changed.

@@ Line 7: / Line 7: @@
 !! A very little bit on DB administration and builder-to-builder here !!
-The main exceptions to this are [[Art Resources]] such as the [[model]] files that define how a creature looks or the area layout files that define a landscape or dungeon. These are not stored directly in the database, though of course many resources in the database will make reference to them. They are instead stored as ordinary [[List of file types|files]] in your [[ERF|filesystem]]. We have not included many art tools in the current build of the end user toolset.
+The main exceptions to this are [[Art Resources]] such as the [[model]] files that define how a creature looks or the area layout files that define a landscape or dungeon. These are not stored directly in the database, though of course many resources in the database will make reference to them. They are instead stored as ordinary [[List of file types|files]] in your file system. We have not included many art tools in the current build of the end user toolset.
 Resources created in the toolset must be exported before the game can make use of them. Exporting converts a resource into the binary file formats used by the game itself, and places the files into the "override" directory where the game looks for new content.

@@ Line 7: / Line 7: @@
 !! A very little bit on DB administration and builder-to-builder here !!
-The main exceptions to this are [[Art Resources]] such as the [[model]] files that define how a creature looks or the area layout files that define a landscape or dungeon. These are not stored directly in the database, though of course many resources in the database will make reference to them. They are instead stored as ordinary [[File types|files]] in your [[ERF|filesystem]]. We have not included many art tools in the current build of the end user toolset.
+The main exceptions to this are [[Art Resources]] such as the [[model]] files that define how a creature looks or the area layout files that define a landscape or dungeon. These are not stored directly in the database, though of course many resources in the database will make reference to them. They are instead stored as ordinary [[List of file types|files]] in your [[ERF|filesystem]]. We have not included many art tools in the current build of the end user toolset.
 Resources created in the toolset must be exported before the game can make use of them. Exporting converts a resource into the binary file formats used by the game itself, and places the files into the "override" directory where the game looks for new content.

@@ Line 40: / Line 40: @@
 The palette has a set of icons across the top that allows you to select which type of resource is to be displayed, as well as an [[Image:IconAll.png]] icon that shows all resources. There's a filter text field that allows you to filter based on a partial string; only resources whose names include the string entered here will be displayed.
-It's also possible to create folders in the palette view to group resources. The folders here are purely for the benefit of the human builder and have no other function within the toolset itself; when the game makes reference to a resource it doesn't need to know what folder it's in. Resource names must therefore be unique, you can't have two different resources with the same name in different palette folders. It's a good idea to use a resource [[Naming conventions|naming convention]] that includes a prefix of some sort to distinguish your resources from others. For example, a three-letter abbreviation of the name of your module.
+It's also possible to create folders in the palette view to group resources. The folders here are purely for the benefit of the human builder and have no other function within the toolset itself; when the game makes reference to a resource it doesn't need to know what folder it's in. Resource names must therefore be unique, you can't have two different resources with the same name in different palette folders. It's a good idea to use a resource [[Naming conventions|naming convention]] that includes a prefix of some sort to distinguish your resources from others. For example, a three-letter abbreviation of the name of your module - see [[Prefixes in use]].
 [[Image:palette with arrows.png]]

@@ Line 7: / Line 7: @@
 !! A very little bit on DB administration and builder-to-builder here !!
-The main exceptions to this are [[Art Resources]] such as the [[model]] files that define how a creature looks or the area layout files that define a landscape or dungeon. These are not stored directly in the database, though of course many resources in the database will make reference to them. They are instead stored as ordinary files in your filesystem. We have not included many art tools in the current build of the end user toolset.
+The main exceptions to this are [[Art Resources]] such as the [[model]] files that define how a creature looks or the area layout files that define a landscape or dungeon. These are not stored directly in the database, though of course many resources in the database will make reference to them. They are instead stored as ordinary [[File types|files]] in your [[ERF|filesystem]]. We have not included many art tools in the current build of the end user toolset.
 Resources created in the toolset must be exported before the game can make use of them. Exporting converts a resource into the binary file formats used by the game itself, and places the files into the "override" directory where the game looks for new content.

@@ Line 5: / Line 5: @@
 The raw data you'll be working with in the toolset is for the most part stored in a database.
-'''A very little bit on DB administration and builder-to-builder here'''
+!! A very little bit on DB administration and builder-to-builder here !!
 The main exceptions to this are art resources such as the model files that define how a creature looks or the area layout files that define a landscape or dungeon. These are not stored directly in the database, though of course many resources in the database will make reference to them. They are instead stored as ordinary files in your filesystem. We have not included many art tools in the current build of the end user toolset.