User:Sunjammer/Item upgrades (draft) - Revision history

Sunjammer: /* Material Types */

2009-11-15T20:57:24Z

‎Material Types

Sunjammer: /* Material Types */

2009-11-15T20:57:12Z

‎Material Types

Sunjammer: /* Material Progression */

2009-11-08T20:19:28Z

‎Material Progression

Sunjammer: /* Runes */

2009-11-08T20:18:42Z

‎Runes

Sunjammer: /* Runes */

2009-11-08T20:18:14Z

‎Runes

Sunjammer: /* Runes */

2009-11-08T20:17:13Z

‎Runes

Sunjammer: /* Runes */

2009-11-08T20:14:53Z

‎Runes

Sunjammer: /* Material Progression */

2009-11-08T20:14:01Z

‎Material Progression

Sunjammer: /* Materials */

2009-11-08T20:13:52Z

‎Materials

Sunjammer: /* Material Types */

2009-11-08T20:13:35Z

‎Material Types

@@ Line 71: / Line 71: @@
 I estimate there are about 66 valid material types (and several other old and presumably invalid ones).
-In scripting the material type can be obtained using [[GetMaterialType]]] and modified using [[SetMaterialType]] however there are no examples in resources in the current version of the toolset to confirm this. I believe that the missing MATERIAL_TYPE constants referred to in the help for [[SetMaterialType]] would, if they existed, point to the valid rows in this file.
+In scripting the material type can be obtained using [[GetMaterialType]] and modified using [[SetMaterialType]] however there are no examples in resources in the current version of the toolset to confirm this. I believe that the missing MATERIAL_TYPE constants referred to in the help for [[SetMaterialType]] would, if they existed, point to the valid rows in this file.
 In the toolset the only noticeable effect of changing the material type is a change of colours however doing so can also change the actual base Material which could have unintended in-game effects.

@@ Line 71: / Line 71: @@
 I estimate there are about 66 valid material types (and several other old and presumably invalid ones).
-In scripting the material type can be obtained using GetMaterialType and modified using SetMaterialType however there are no examples in resources in the current version of the toolset to confirm this. I believe that the missing MATERIAL_TYPE constants referred to in the help for SetMaterialType would, if they existed, point to the valid rows in this file.
+In scripting the material type can be obtained using [[GetMaterialType]]] and modified using [[SetMaterialType]] however there are no examples in resources in the current version of the toolset to confirm this. I believe that the missing MATERIAL_TYPE constants referred to in the help for [[SetMaterialType]] would, if they existed, point to the valid rows in this file.
 In the toolset the only noticeable effect of changing the material type is a change of colours however doing so can also change the actual base Material which could have unintended in-game effects.

@@ Line 112: / Line 112: @@
 Material Progression appears to be used the Treasure System for auto-scaling armour, shield and weapons for loot (as seen in [[sys_tressure_h.nss]]) however it could also be used as the basis for any item upgrade system.
-It is important to note that an item's MaterialProgression property can only be set at design time (i.e. in the toolset) for while there is a GetItemMaterialProgression there is no corresponding SetItemMaterialProgression. Moreover the name is slightly misleading, as the property and function actually set and return the item's material type progression.
+It is important to note that an item's '''MaterialProgression''' property can only be set at design time (i.e. in the toolset) for while there is a [[GetItemMaterialProgression]] there is no corresponding '''SetItemMaterialProgression'''. Moreover the name is slightly misleading, as the property and function actually set and return the item's material type progression.
 The MaterialProgression list in the toolset is populate using the Label column in [[TS_Material.2da]] (contained in [[TS_System.xls]]):
@@ Line 133: / Line 133: @@
      Material15    int        6
-The Material# columns are populated with references to material types from [[materialtypes.2da]]. It is presumably important to ensure that the progression is logical i.e. an armour progression only uses armour material types and that they ascend in line with the underlying base material.
+The '''Material#''' columns are populated with references to material types from [[materialtypes.2da]]. It is presumably important to ensure that the progression is logical i.e. an armour progression only uses armour material types and that they ascend in line with the underlying base material.
 The formula for determining which of these should be used by the auto-scaling system is basically (the player's level / 3) + a small random element. The player's level is essentially capped at 45 for this system.

@@ Line 147: / Line 147: @@
 Item's using the default '''Variables''' 2da file ([[var_item.2da]]) have a [[ITEM_RUNE_ENABLED]] local variable (default 0), which presumably allows an item to be excluded from the runes system regardless of its base material. The switch is randomly set in the [[ScaleStoreItems]] function in [[core_h.nss]] but no other references to it have been found in the Toolset Beta resources.
-From the description of the [[GetItemProperties]] and [[GetItemPropertyPower]] functions it appears a rune's Item Properties (and possibly OnHit Effect) are included with those of the item they are installed in. The rune items are known as sub items and can accessed using the GetItemSubItems function.
+From the description of the [[GetItemProperties]] and [[GetItemPropertyPower]] functions it appears a rune's Item Properties (and possibly OnHit Effect) are included with those of the item they are installed in. The rune items are known as sub items and can accessed using the [[GetItemSubItems]] function.
 There is a special Upgrade GUI which presumably allows the PC to install to or uninstall from an item. It can be displayed using the [[OpenItemUpgradeGUI]] function however there does not appear to be any way to set the item's sub items (i.e. install or uninstall runes) via scripting.

@@ Line 147: / Line 147: @@
 Item's using the default '''Variables''' 2da file ([[var_item.2da]]) have a [[ITEM_RUNE_ENABLED]] local variable (default 0), which presumably allows an item to be excluded from the runes system regardless of its base material. The switch is randomly set in the [[ScaleStoreItems]] function in [[core_h.nss]] but no other references to it have been found in the Toolset Beta resources.
-From the description of the [[GetItemProperites]] and [[GetItemPropertyPower]] functions it appears a rune's Item Properties (and possibly OnHit Effect) are included with those of the item they are installed in. The rune items are known as sub items and can accessed using the GetItemSubItems function.
+From the description of the [[GetItemProperties]] and [[GetItemPropertyPower]] functions it appears a rune's Item Properties (and possibly OnHit Effect) are included with those of the item they are installed in. The rune items are known as sub items and can accessed using the GetItemSubItems function.
 There is a special Upgrade GUI which presumably allows the PC to install to or uninstall from an item. It can be displayed using the [[OpenItemUpgradeGUI]] function however there does not appear to be any way to set the item's sub items (i.e. install or uninstall runes) via scripting.

@@ Line 139: / Line 139: @@
 === Runes ===
-Runes are a special type of item that can be installed, and subsequently uninstalled, from another item thereby granting additional benefits to that item. There are currently two types of rune defined in BITM_base.2da (contained in BITM_base.xls): one for weapons (including a mage's staff) and one for armour (including a shields).
+Runes are a special type of item that can be installed, and subsequently uninstalled, from another item thereby granting additional benefits to that item. There are currently two types of rune defined in [[BITM_base.2da]] (contained in [[BITM_base.xls]]): one for weapons (including a mage's staff) and one for armour (including a shields).
-Currently runes can only be installed in a weapon or armour however as this appears to be controlled through the RuneSlots column in BITM_base.2da it may be possible to simply create new types of runes that could be applied to other item types. The value entered into the RuneSlots column is based on the inventory slots constants and calculated in exactly the same way as discussed in the Item Sets section (above).
+Currently runes can only be installed in a weapon or armour however as this appears to be controlled through the '''RuneSlots''' column in [[BITM_base.2da]] it may be possible to simply create new types of runes that could be applied to other item types. The value entered into the '''RuneSlots''' column is based on the inventory slots constants and calculated in exactly the same way as discussed in the Item Sets section (above).
-The number of runes that can be installed on an item is determined by the quality of the material used to construct it and range from 0 to 3 runes accordingly. The number of runes is for a material is defined in materialrules.2da (above).
+The number of runes that can be installed on an item is determined by the quality of the material used to construct it and range from 0 to 3 runes accordingly. The number of runes is for a material is defined in [[materialrules.2da]] (above).
-Item's using the default Variables 2da file (var_item.2da) have a ITEM_RUNE_ENABLED local variable (default 0), which presumably allows an item to be excluded from the runes system regardless of its base material. The switch is randomly set in the ScaleStoreItems function in core_h.nss but no other references to it have been found in the Toolset Beta resources.
+Item's using the default '''Variables''' 2da file ([[var_item.2da]]) have a [[ITEM_RUNE_ENABLED]] local variable (default 0), which presumably allows an item to be excluded from the runes system regardless of its base material. The switch is randomly set in the [[ScaleStoreItems]] function in [[core_h.nss]] but no other references to it have been found in the Toolset Beta resources.
-From the description of the GetItemProperites and GetItemPropertyPower functions it appears a rune's Item Properties (and possibly OnHit Effect) are included with those of the item they are installed in. The rune items are known as sub items and can accessed using the GetItemSubItems function.
+From the description of the [[GetItemProperites]] and [[GetItemPropertyPower]] functions it appears a rune's Item Properties (and possibly OnHit Effect) are included with those of the item they are installed in. The rune items are known as sub items and can accessed using the GetItemSubItems function.
-There is a special Upgrade GUI which presumably allows the PC to install to or uninstall from an item. It can be displayed using the OpenItemUpgradeGUI function however there does not appear to be any way to set the item's sub items (i.e. install or uninstall runes) via scripting.
+There is a special Upgrade GUI which presumably allows the PC to install to or uninstall from an item. It can be displayed using the [[OpenItemUpgradeGUI]] function however there does not appear to be any way to set the item's sub items (i.e. install or uninstall runes) via scripting.
 === Item Properties & OnHit Properties ===

← Older revision		Revision as of 20:14, 8 November 2009
Line 136:		Line 136:

	The formula for determining which of these should be used by the auto-scaling system is basically (the player's level / 3) + a small random element. The player's level is essentially capped at 45 for this system.		The formula for determining which of these should be used by the auto-scaling system is basically (the player's level / 3) + a small random element. The player's level is essentially capped at 45 for this system.
		+
		+	=== Runes ===
		+
		+	Runes are a special type of item that can be installed, and subsequently uninstalled, from another item thereby granting additional benefits to that item. There are currently two types of rune defined in BITM_base.2da (contained in BITM_base.xls): one for weapons (including a mage's staff) and one for armour (including a shields).
		+
		+	Currently runes can only be installed in a weapon or armour however as this appears to be controlled through the RuneSlots column in BITM_base.2da it may be possible to simply create new types of runes that could be applied to other item types. The value entered into the RuneSlots column is based on the inventory slots constants and calculated in exactly the same way as discussed in the Item Sets section (above).
		+
		+	The number of runes that can be installed on an item is determined by the quality of the material used to construct it and range from 0 to 3 runes accordingly. The number of runes is for a material is defined in materialrules.2da (above).
		+
		+	Item's using the default Variables 2da file (var_item.2da) have a ITEM_RUNE_ENABLED local variable (default 0), which presumably allows an item to be excluded from the runes system regardless of its base material. The switch is randomly set in the ScaleStoreItems function in core_h.nss but no other references to it have been found in the Toolset Beta resources.
		+
		+	From the description of the GetItemProperites and GetItemPropertyPower functions it appears a rune's Item Properties (and possibly OnHit Effect) are included with those of the item they are installed in. The rune items are known as sub items and can accessed using the GetItemSubItems function.
		+
		+	There is a special Upgrade GUI which presumably allows the PC to install to or uninstall from an item. It can be displayed using the OpenItemUpgradeGUI function however there does not appear to be any way to set the item's sub items (i.e. install or uninstall runes) via scripting.

	=== Item Properties & OnHit Properties ===		=== Item Properties & OnHit Properties ===

@@ Line 108: / Line 108: @@
 It does not appear to be possible to set the material directly through scripting with the functions that are currently available.
-=== Material Progression ===
+==== Material Progression ====
 Material Progression appears to be used the Treasure System for auto-scaling armour, shield and weapons for loot (as seen in [[sys_tressure_h.nss]]) however it could also be used as the basis for any item upgrade system.

@@ Line 75: / Line 75: @@
 In the toolset the only noticeable effect of changing the material type is a change of colours however doing so can also change the actual base Material which could have unintended in-game effects.
-=== Materials ===
+==== Materials ====
 As mentioned above each Material Type has a base Material that determines the in-game effectiveness of that item. As the quality of the material increases it does more damage, offer better protection, improve the chance of critical hits, etc. This data is contained in [[materialrules.2da]]:

@@ Line 57: / Line 57: @@
 The MaterialType list is populated using the Label column in [[materialtypes.2da]] (contained in [[materialtypes.xls]]). The MaterialProgression list is populated using the Label column in [[TS_Material.2da]] (contained in [[TS_System.xls]]).
-=== Material Types ===
+==== Material Types ====
 It appears that the [[materialtypes.2da]] actually consists of two sets of data: the current material types data and the an old, confused version of material rules data.