Script - Revision history

Sunjammer: Fixing link

2012-03-26T21:09:36Z

Fixing link

Sunjammer: /* Local variables - data repositories for individual objects */ fixing link

2012-02-18T02:22:38Z

‎Local variables - data repositories for individual objects: fixing link

Sunjammer: /* Scripting overview - basic syntax */

2012-02-18T02:21:26Z

‎Scripting overview - basic syntax

Sunjammer: Fixing link

2011-08-08T12:51:54Z

Fixing link

Sunjammer: Fixing links

2011-08-02T23:57:54Z

Fixing links

Sunjammer: /* Events - driving practically everything */ Fixing links

2011-08-02T23:55:44Z

‎Events - driving practically everything: Fixing links

Sunjammer: /* Scripting overview - basic syntax */ Fixing link again!

2011-08-02T22:44:43Z

‎Scripting overview - basic syntax: Fixing link again!

Sunjammer: /* Scripting overview - basic syntax */ Updating link

2011-08-02T22:30:46Z

‎Scripting overview - basic syntax: Updating link

Sunjammer: /* Scripting overview - basic syntax */ Temporary fix to include lexicon categories

2011-08-01T20:45:18Z

‎Scripting overview - basic syntax: Temporary fix to include lexicon categories

Kelamor: Add languages template

2010-11-01T02:27:26Z

Add languages template

@@ Line 15: / Line 15: @@
 : ''See [[:Category:Keywords|Scripting keywords]]''
 : ''See [[:Category:Constants|Scripting constants]]''
-: ''See [[:Category:Script functions|Scripting functions]]''
+: ''See [[:Category:Functions|Scripting functions]]''
 == [[Event keyword|Event]] - driving practically everything ==

@@ Line 65: / Line 65: @@
 Local variables must be pre-defined in a variable [[2DA]] before they can be read or set using these functions. Dragon Age doesn't support the dynamic in-game allocation of new local variables.
-An alternative to local variables can be found in the unlimited variable storage project[http://social.bioware.com/project/1787/]. With a single include file and a simple function call in your module script, you can have unlimited variable and array storage with no need to declare anything in a 2da.
+An alternative to local variables can be found in the [http://social.bioware.com/project/1787/ unlimited variable storage project]. With a single include file and a simple function call in your module script, you can have unlimited variable and array storage with no need to declare anything in a 2da.
 :''See main article: [[Local variable]]s''

@@ Line 10: / Line 10: @@
 == [[Scripting overview]] - basic syntax ==
-The DA scripting language is very similar to C in terms of syntax. Files can be included into other files, with files containing libraries of functions designated by a "_h" suffix. (eg. wrappers_h)
+The Dragon Age scripting language is an evolution of '''nwscript''' which was used in '''Neverwinter Night Toolset'''. It is similar to '''C''' in terms of syntax but is much smaller and easier to learn. Scripts can be executable (i.e. they contain a '''StartingConditional''' or '''main''' function) or they can be libraries (often called "include files") which can be included into other scripts. In the Dragon Age Toolset include files usually have an "_h" suffix. (e.g. [[wrappers_h]]).
 : ''See [[Scripting overview]]''

@@ Line 51: / Line 51: @@
 == [[Treasure system]] ==
-The treasure possessed by most creatures and containers is randomly generated by the game's core scripts using a system that selects from appropriate treasure types (for example, wild animals should rarely possess steel armor in their inventories, and Darkspawn are unlikely to be carrying fine porcelain vases) and auto-scales it to be reasonably useful or valuable at the character's level. Manipulating the treasure system can involve both [[local variable]]s and [[event (type)|event]]s.
+The treasure possessed by most creatures and containers is randomly generated by the game's core scripts using a system that selects from appropriate treasure types (for example, wild animals should rarely possess steel armor in their inventories, and Darkspawn are unlikely to be carrying fine porcelain vases) and auto-scales it to be reasonably useful or valuable at the character's level. Manipulating the treasure system can involve both [[local variable]]s and [[Event keyword|event]]s.
 To put a specific treasure item in a specific creature's [[inventory]], you'll have to create a new creature template for that creature. Inventory cannot be directly defined for particular objects already placed in an [[area]].

@@ Line 17: / Line 17: @@
 : ''See [[:Category:Script functions|Scripting functions]]''
-== Events - driving practically everything ==
+== [[Event keyword|Event]] - driving practically everything ==
 Dragon Age has an [[Event keyword|event]]-driven scripting model, with event objects being passed to scripts containing different parameters depending on the event's type. A large portion of script-writing for a standard adventure is going to involve dealing with events. Common examples include:
@@ Line 30: / Line 30: @@
 :''See [[Event keyword|Event]] for more details.''
-== [[Effect (dascript type)|Effect]]s and [[Ability|Abilities]] - how to make things affect other things ==
+== [[Effect keyword|Effect]]s and [[Ability|Abilities]] - how to make things affect other things ==
-[[Effect (dascript type)|Effect]]s are a bundle of modifiers that are applied to an object or creature. Every effect has a type set on it that determines how it affects the object it is applied to. They also have a number of parameters on them, which vary based on the type, that change the specific behaviour. When the effect is removed (usually because the duration on the effect expires) the modifier is removed. These modifiers can be rule or stat based or more complicated visual and game effects.
+[[Effect keyword|Effect]]s are a bundle of modifiers that are applied to an object or creature. Every effect has a type set on it that determines how it affects the object it is applied to. They also have a number of parameters on them, which vary based on the type, that change the specific behaviour. When the effect is removed (usually because the duration on the effect expires) the modifier is removed. These modifiers can be rule or stat based or more complicated visual and game effects.
 They can be assigned different duration types which affect how they're applied and removed:

@@ Line 13: / Line 13: @@
 : ''See [[Scripting overview]]''
-: ''See [[:Category:DAScript_types|Scripting types]]''
+: ''See [[:Category:Scripting keywords|Scripting keywords]]''
 : ''See [[:Category:Constants|Scripting constants]]''
-: ''See [[:Category:Script_functions|Scripting functions]]''
+: ''See [[:Category:Script functions|Scripting functions]]''
 == [[Event (dascript type)|Event]]s - driving practically everything ==

← Older revision		Revision as of 02:27, 1 November 2010
Line 66:		Line 66:
	:''See main article: [[Local variable]]s''		:''See main article: [[Local variable]]s''

		+	{{Languages}}
	[[Category:Scripts]]		[[Category:Scripts]]