Resource palette - Revision history

Sunjammer: Tweaking table

2012-02-15T09:01:04Z

Tweaking table

Sunjammer: Added checked in icon and bullet

2012-02-14T22:24:13Z

Added checked in icon and bullet

Sunjammer: Fixing images

2012-02-14T21:42:53Z

Fixing images

BryanDerksen at 22:37, 2 February 2010

2010-02-02T22:37:25Z

BryanDerksen: expand on the locked resource icon

2010-02-02T22:37:02Z

expand on the locked resource icon

BryanDerksen: icons

2010-02-02T22:33:32Z

icons

BryanDerksen: reorganizing. Moving the more detailed list of resource types to resource list, making this more palette-specific

2010-02-02T20:58:24Z

reorganizing. Moving the more detailed list of resource types to resource list, making this more palette-specific

Eshme: /* Global Resource properties */

2010-01-31T00:25:52Z

‎Global Resource properties

Eshme: removed wrong info. Tis could get replaced with something cleaner later

2010-01-31T00:22:53Z

removed wrong info. Tis could get replaced with something cleaner later

Eshme at 00:18, 31 January 2010

2010-01-31T00:18:47Z

@@ Line 5: / Line 5: @@
 {|
 |- align="left"
-! Icon
+! width="10%" | Icon
-! width="33%" | Resource type
+! width="30%" | Resource type
-! Icon
+! width="10%" | Icon
-! width="33%" | Resource type
+! width="40%" | Resource type
 |-
 |[[Image:IconArea.png|link=Area]] || [[Area]] || [[Image:IconPlaceable.png|link=Placeable]] || [[Placeable]]

@@ Line 37: / Line 37: @@
 The checkout status of a resource is indicated by the icon next to its resource name:
-*[[File:IconResourceCheckedOutToYou.png|link=]] - Resource is checked out to you
+{|
-*[[File:IconResourceCheckedOutToSomeoneElse.png|link=]] - Resource is checked out to someone else
+|-
-*[[File:IconOtherModuleResource.png|link=]] - Resource belongs to a different module (inherited)
+| align=right | [[File:Checked in resource icon.png|link=]]
-*[[File:IconCoreResource.png|link=]] - Resource belongs to core resources
+| Resource is checked in
-*[[File:IconLockedResource.png|link=]] - Resource is locked in database (this should not normally occur; no locked resources are shipped with the toolset. If you see locked resources you will need to unlock them in the [[database]] via an administrative interface before you can edit them. The toolset does not have the ability to lock or unlock resources itself.)
+|-
 == Object templates vs. object instances ==

@@ Line 37: / Line 37: @@
 The checkout status of a resource is indicated by the icon next to its resource name:
-*[[File:IconResourceCheckedOutToYou.png]] - Resource is checked out to you
+*[[File:IconResourceCheckedOutToYou.png|link=]] - Resource is checked out to you
-*[[File:IconResourceCheckedOutToSomeoneElse.png]] - Resource is checked out to someone else
+*[[File:IconResourceCheckedOutToSomeoneElse.png|link=]] - Resource is checked out to someone else
-*[[File:IconOtherModuleResource.png]] - Resource belongs to a different module (inherited)
+*[[File:IconOtherModuleResource.png|link=]] - Resource belongs to a different module (inherited)
-*[[File:IconCoreResource.png]] - Resource belongs to core resources
+*[[File:IconCoreResource.png|link=]] - Resource belongs to core resources
-*[[File:IconLockedResource.png]] - Resource is locked in database (this should not normally occur; no locked resources are shipped with the toolset. If you see locked resources you will need to unlock them in the [[database]] via an administrative interface before you can edit them. The toolset does not have the ability to lock or unlock resources itself.)
+*[[File:IconLockedResource.png|link=]] - Resource is locked in database (this should not normally occur; no locked resources are shipped with the toolset. If you see locked resources you will need to unlock them in the [[database]] via an administrative interface before you can edit them. The toolset does not have the ability to lock or unlock resources itself.)
 == Object templates vs. object instances ==

@@ Line 41: / Line 41: @@
 *[[File:IconOtherModuleResource.png]] - Resource belongs to a different module (inherited)
 *[[File:IconCoreResource.png]] - Resource belongs to core resources
-*[[File:IconLockedResource.png]] - Resource is locked in database (this should not normally occur; no locked resources are shipped with the toolset. If you see locked resources you will need to unlock them in the [[database]] via an administrative interface before you can edit them.)
+*[[File:IconLockedResource.png]] - Resource is locked in database (this should not normally occur; no locked resources are shipped with the toolset. If you see locked resources you will need to unlock them in the [[database]] via an administrative interface before you can edit them. The toolset does not have the ability to lock or unlock resources itself.)
 == Object templates vs. object instances ==

@@ Line 41: / Line 41: @@
 *[[File:IconOtherModuleResource.png]] - Resource belongs to a different module (inherited)
 *[[File:IconCoreResource.png]] - Resource belongs to core resources
-*[[File:IconLockedResource.png]] - Resource is locked in database (this should not normally occur)
+*[[File:IconLockedResource.png]] - Resource is locked in database (this should not normally occur; no locked resources are shipped with the toolset. If you see locked resources you will need to unlock them in the [[database]] via an administrative interface before you can edit them.)
 == Object templates vs. object instances ==

← Older revision		Revision as of 22:33, 2 February 2010
Line 34:		Line 34:

	A resource's checkout status is indicated by a small icon next to the resource's name. See [[checking in and checking out resources]] for information on how Dragon Age's database manages multiple editors working simultaneously on the same database. You will need to know how to check out and check in resources for certain tasks even when working on your own.		A resource's checkout status is indicated by a small icon next to the resource's name. See [[checking in and checking out resources]] for information on how Dragon Age's database manages multiple editors working simultaneously on the same database. You will need to know how to check out and check in resources for certain tasks even when working on your own.
		+
		+	The checkout status of a resource is indicated by the icon next to its resource name:
		+
		+	*[[File:IconResourceCheckedOutToYou.png]] - Resource is checked out to you
		+	*[[File:IconResourceCheckedOutToSomeoneElse.png]] - Resource is checked out to someone else
		+	*[[File:IconOtherModuleResource.png]] - Resource belongs to a different module (inherited)
		+	*[[File:IconCoreResource.png]] - Resource belongs to core resources
		+	*[[File:IconLockedResource.png]] - Resource is locked in database (this should not normally occur)

	== Object templates vs. object instances ==		== Object templates vs. object instances ==

@@ Line 1: / Line 1: @@
 {{Resource palette}}
-The following classes of resource are available in the palette window.
+The resource palette is the main navigational interface in the toolset for finding and opening designer resources for editing. At the top of the resource palette is a set of icons that allow the palette to be quickly sorted by type:
-*[[Image:IconArea.png]] [[Area]]s - An area represents a level in the game.  It has a visible model associated with it, as well as a walk-mesh (for hit-finding) and walk-grid (for path-finding).
+{|
-**[[Waypoint]]s are simple objects for marking points within an area for reference purposes.
+|- align="left"
-*[[Image:IconAreaList.png]] [[Area list]]s - An area list a grouping of area objects made in the toolset.  These areas are considered to be a block and will always be loaded together.  The player will be able to wander between these areas without requiring a major area transition, at least until they try to move to another area list.
+! Icon
-*[[Image:IconCharacter.png]] [[Character]]s - this resource is for coordinating voice-over and localization efforts, and is not used directly by game code.
+! width="33%" | Resource type
-*[[Image:IconConversation.png]] [[Conversation]]s - collections of questions, answers, statements, and other interactive activities laid out in a tree structure.
+! Icon
-**[[Conversation plots and scripting]] discusses how plots and scripts can interact with conversations.
+! width="33%" | Resource type
-**[[Conversation cinematics and animation]] discusses how to direct the visual performance of your virtual actors.
+|-
-*[[Image:IconCreature.png]] [[Creature]]s - Creature objects are used to represent the player's characters and every other living creature in the game.  Creatures can run actions or scripts, move, cast spells, use talents or skills and engage in combat.
+|[[Image:IconArea.png|link=Area]] || [[Area]] || [[Image:IconPlaceable.png|link=Placeable]] || [[Placeable]]
-**[[Morph]]s are highly customizable heads that can be used to create an enormous diversity of unique character appearances. They are not listed in the resource palette, to create new ones go to the File menu and select "Morph" from the "New" submenu. This will bring up the morph creator tool.
+|-
-**[[Creature group]]s are used when determining who is hostile to whom.
+|[[Image:IconAreaList.png|link=Area list]] || [[Area list]] || [[Image:IconPlot.png|link=Plot]] || [[Plot]]
-**[[Ambient behaviour]] determines how the creature behaves when not doing anything else in particular.
+|-
-*[[Image:IconCutscene.png]] [[Cutscene]]s - A cutscene is a pre-determined cinematic sequence played back using the game engine.
+|[[Image:IconCharacter.png|link=Character]] || [[Character]] || [[Image:IconScript.png|link=Script]] || [[Script]]
-** [[cutscene object]]s
+|-
-** [[cutscene action]]s
+|[[Image:IconConversation.png|link=Conversation]] || [[Conversation]] || [[Image:IconClientScript.png|link=Client script]] || [[Client script]]
-** [[cutscene effect]]s
+|-
-** [[curve editor]]
+|[[Image:IconCreature.png|link=Creature]] || [[Creature]] || [[Image:IconStage.png|link=Stage]] || [[Stage]]
-*[[Image:IconItem.png]] [[Item]]s - items that can be taken into inventory, and are often equippable by characters or otherwise usable within the game.
+|-
-*[[Image:IconMap.png]] [[Map]]s - images of maps with location pins whose location and appearance can be scripted.
+|[[Image:IconCutscene.png|link=Cutscene]] || [[Cutscene]] || [[Image:IconTrigger.png|link=Trigger]] || [[Trigger]]
-*[[Image:IconMerchant.png]] [[Merchant]]s - where the player can buy and sell items. Often linked to a creature.
+|-
-*[[Image:IconPlaceable.png]] [[Placeable]]s - items that can't be taken into inventory. They can serve a wide variety of roles such as decoration, obstruction, or container, and the player can interact with them in various ways.
+|[[Image:IconItem.png|link=Item]] || [[Item]] || [[Image:IconSound.png|link=Sound]] || [[Sound]]
-** [[Door]]s are a type of placeable but are complex enough to warrant special treatment.
+|-
-** [[Trap system]] - placeables are used as triggers for traps.
+|[[Image:IconMap.png|link=Map]] || [[Map]] || [[Image:IconModel.png|link=Model Placement]] || [[Model Placement|Model]]
-*[[Image:IconPlot.png]] [[Plot]]s -  The plot manager maintains a list of variables that are important to the storyline. They are stored with the party and serve as a gameplay history.  Each creature will also maintain a plot table of local variables that can be accessed through scripting. These can be used to keep track of player progress through quests and control journal entries.
+|-
-*[[Image:IconScript.png]] [[Script]]s - Scripting is used whenever the designers need control over the game's behaviour. The syntax for DA scripts is very similar to the C programming language.
+|[[Image:IconMerchant.png|link=Merchant]] || [[Merchant]] || [[Image:IconAll.png|link=Designer Resources]] || All designer resources
-*[[Image:IconClientScript.png]] [[Client script]]s - The client side scripting language is meant to be used for automated testing.  It's similar to the server scripting, except that it's designed to simulate client input.
+|}
-*[[Image:IconStage.png]] [[Stage]]s - a form of cinematic cutscene that's applied during a conversation to control character and camera placement.
-*[[Image:IconTrigger.png]] [[Trigger]]s - A trigger is an invisible polygonal area painted on the floor in the toolset.  This game object will receive events whenever a creature enters or exits it.  They are most commonly used for plot scripting in an area.
+The "sound" and "model" filters will show sound and model resources, which are not themselves designer resources but which are commonly used when working with areas and level layouts and so are also included in this interface.
-*[[Image:IconSound.png]] [[Sound]]s - audible sounds that can be generated by objects or scripts. These cannot be edited within the designer toolset; the [[FMOD]] utility is used for this.
-*[[Image:IconModel.png]] [[Model Placement|Models]] - the basic physical appearance used by physical objects. These cannot be edited within the designer toolset, though see [[morph]]s for altering the appearance of character heads.
 Creating new resources is done by selecting "New" from the File menu, or from the right-click dropdown menu on the resource palette.
-See [[checking in and checking out resources]] for information on how Dragon Age's database manages multiple editors working simultaneously on the same database. You will need to know how to check out and check in resources for certain tasks even when working on your own.
+A resource's checkout status is indicated by a small icon next to the resource's name. See [[checking in and checking out resources]] for information on how Dragon Age's database manages multiple editors working simultaneously on the same database. You will need to know how to check out and check in resources for certain tasks even when working on your own.
 == Object templates vs. object instances ==

← Older revision		Revision as of 00:25, 31 January 2010
Line 55:		Line 55:
	If the other resources are core then you are fine. But if you created a creature in single player and then places it into area 1 then moved area 1 from single player to a new module then the creature will not show up anymore unless you either move the creature to the new module as well or else move the creature to core.		If the other resources are core then you are fine. But if you created a creature in single player and then places it into area 1 then moved area 1 from single player to a new module then the creature will not show up anymore unless you either move the creature to the new module as well or else move the creature to core.

−	~~== Global Resource properties ==~~
−
−	Every such resource has the same set of generic properties that can be viewed by right-clicking on it in the palette window and selecting "properties". The general tab of the resulting popup window shows the following properties that can be modified:
−
−	* Resource name - This is the Resource Name. It must be unique across the entire database (not just the current module) and lower case. When the resource is created this name is also set as its tag. Oddly, the tag must be in lower case also. To edit the resource name, or any of the resource properties you must first save the resource, check it in, then right click on the name and select Properties. Once done be sure to right click on the resource name once more and select Refresh, this will update all the instances in the module with the new changes.
−	* Folder - This setting will move the new Resource into a specific Folder of the Resource palette. This is only for navigational aid.
−	* Module - Sets the environment of the Module, as either "Game Core Resource" or Module, where Module should equal the Owner Module. Exported Resources will be put into either the Core or Module directory of the Owner Module. The Game will treat Game Core Resources as available to other Modules, while setting Module makes a Resource only available within that Module. Other settings are irrelevant and treated as if setting the Owner Module.
−	* Owner module - Sets the Module which shall inherit the Resource. The exported Resource is put into that Modules directory, and the Game will treat that Resource as only available when the Module is activated. Default should always be the custom Module you are working on. Other settings can cause potential problems.
−	* State - A flag that can be set to NONE, Written, Edited, Pre-localization, Localization, Voice over, Voice over ready. {{undocumented}}
−
−	~~The "references" tab lists all of the other resources that this resource contains references to, and the "referenced by" tab lists all of the other resources that contain references to this one.~~
−
−	~~[[Image:Resource properties.png\|center\|330px]]~~

	[[Category:Designer resources]]		[[Category:Designer resources]]

@@ Line 40: / Line 40: @@
 See [[checking in and checking out resources]] for information on how Dragon Age's database manages multiple editors working simultaneously on the same database. You will need to know how to check out and check in resources for certain tasks even when working on your own.
 == Object templates vs. object instances ==
@@ Line 74: / Line 58: @@
 If the other resources are core then you are fine. But if you created a creature in single player and then places it into area 1 then moved area 1 from single player to a new module then the creature will not show up anymore unless you either move the creature to the new module as well or else move the creature to core.
 [[Category:Designer resources]]