Data Cleanup Projects - Revision history

Tom Parker at 01:39, 29 June 2010

2010-06-29T01:39:54Z

Tom Parker at 01:37, 29 June 2010

2010-06-29T01:37:59Z

Tom Parker at 01:23, 29 June 2010

2010-06-29T01:23:37Z

Tom Parker: Created page with '{| align="right" | TOC |} =Wield Category= ==Special Value: WeaponProf LST HANDS Token== Currently, the HANDS: token in WeaponProf LST files takes a special value: 1IF…'

2010-06-29T01:14:41Z

Created page with '{| align="right" | __TOC__ |} =Wield Category= ==Special Value: WeaponProf LST HANDS Token== Currently, the HANDS: token in WeaponProf LST files takes a special value: 1IF…'

New page

{| align="right"
| __TOC__
|}

=Wield Category=

==Special Value: WeaponProf LST HANDS Token==

Currently, the HANDS: token in WeaponProf LST files takes a special value: 1IFLARGERTHANWEAPON

This special value is no longer required and we should find ways to remove it from other game systems (other than SRD and RSRD where it is no longer present)

This will require defining the appropriate replacement, as well as doing a conversion

==Replacement==

==Conversion==

@@ Line 40: / Line 40: @@
 The current WieldCategory tokens are "old style" tokens that do not have a LoadContext or unparse present.  We should update these to "new style" tokens
 ==Complete Rebuild of Wield Category model==
 The Wield Category model today involves a significant amount of redundant information.  Both the UP and DOWN tokens are redundant across the different WieldCategory items, and that would seem to allow mistakes.  Should think about a method of having a single list of items (or only one way to define PREVIOUS/NEXT in the Wield Category family of objects)

← Older revision		Revision as of 01:37, 29 June 2010
Line 40:		Line 40:

	The current WieldCategory tokens are "old style" tokens that do not have a LoadContext or unparse present. We should update these to "new style" tokens		The current WieldCategory tokens are "old style" tokens that do not have a LoadContext or unparse present. We should update these to "new style" tokens
		+
		+	==Complete Rebuild of Wield Category model==
		+
		+	The Wield Category model today involves a significant amount of redundant information. Both the UP and DOWN tokens are redundant across the different WieldCategory items, and that would seem to allow mistakes. Should think about a method of having a single list of items (or only one way to define PREVIOUS/NEXT in the Wield Category family of objects)

@@ Line 13: / Line 13: @@
 This will require defining the appropriate replacement, as well as doing a conversion
-==Replacement==
+===Replacement===
-==Conversion==
+Currently, there are some default values of Wield Category that exist if no other values are defined in the Game Mode.  These defaults should always be built on data load, rather than waiting for them to be accessed.  These values are currently in WieldCategory.findByName() as of SVN 12324

Data Cleanup Projects - Revision history

Tom Parker at 01:39, 29 June 2010

Tom Parker at 01:37, 29 June 2010

Tom Parker at 01:23, 29 June 2010

Tom Parker: Created page with '{| align="right" | __TOC__ |} =Wield Category= ==Special Value: WeaponProf LST HANDS Token== Currently, the HANDS: token in WeaponProf LST files takes a special value: 1IF…'

Tom Parker: Created page with '{| align="right" | TOC |} =Wield Category= ==Special Value: WeaponProf LST HANDS Token== Currently, the HANDS: token in WeaponProf LST files takes a special value: 1IF…'