Formula Parser Equip Vars Demo - Revision history

Tom Parker at 02:04, 25 January 2018

2018-01-25T02:04:57Z

Show changes

Tom Parker: /* WARNING: THIS IS DEPRECATED */

2018-01-23T23:52:49Z

‎WARNING: THIS IS DEPRECATED

Tom Parker at 04:02, 21 January 2018

2018-01-21T04:02:26Z

Tom Parker at 03:47, 16 August 2015

2015-08-16T03:47:40Z

Tom Parker at 03:29, 10 August 2015

2015-08-10T03:29:19Z

Tom Parker: /* VARTYPEDEF */

2015-08-10T03:24:59Z

‎VARTYPEDEF

Tom Parker: /* New Data Control File Tokens */

2015-08-10T03:24:48Z

‎New Data Control File Tokens

Tom Parker: /* New Game Mode MISC Info File Token */

2015-08-10T03:22:17Z

‎New Game Mode MISC Info File Token

Tom Parker: /* Legal Types */

2015-08-09T21:30:33Z

‎Legal Types

Tom Parker: /* An Example */

2014-07-05T19:29:42Z

‎An Example

← Older revision		Revision as of 23:52, 23 January 2018
Line 4:		Line 4:

	=WARNING: THIS IS DEPRECATED=		=WARNING: THIS IS DEPRECATED=
		+	=Deprecated=

	It is saved for archival purposes at the moment (it still has a few useful tidbits the code folks don't want to retype from scratch)		It is saved for archival purposes at the moment (it still has a few useful tidbits the code folks don't want to retype from scratch)

@@ Line 2: / Line 2: @@
    | __TOC__
    |}
 =Description=

@@ Line 53: / Line 53: @@
   NAMESPACEDEF:x|y
-  x is a legal data format (currently NUMBER, GRIDPOINT)
+  x is a legal data format (currently NUMBER, STRING, ORDEREDPAIR)
   y is a name for the data type ("traditional variables" should be defined as "VAR", other items are up to the data team)
@@ Line 65: / Line 65: @@
 The following tokens are REQUIRED in the game mode to set the default value of a variable type:
   DEFAULTVARIABLEVALUE:NUMBER|0
-  DEFAULTVARIABLEVALUE:GRIDPOINT|0,0
+  DEFAULTVARIABLEVALUE:ORDEREDPAIR|0,0
 The Syntax is:
@@ Line 131: / Line 131: @@
 The following tokens are REQUIRED in data control file:
   NAMESPACEDEF:NUMBER|VAR
-  NAMESPACEDEF:GRIDPOINT|AREA
+  NAMESPACEDEF:ORDEREDPAIR|AREA
 ==Variable File==
@@ Line 339: / Line 339: @@
 Once the second argument is used in a TYPE entry, then it can be used in other data, including LOCAL and GLOBAL in the variable file and MODIFY in other LST files.  Items are referred to by the second argument, NOT the underlying type.  So the following would be reasonable data:
-  NAMESPACEDEF:GRIDPOINT|AREA
+  NAMESPACEDEF:ORDEREDPAIR|AREA
   AREA|Face (note that since GLOBAL is implied, this is equal to GLOBAL:AREA|Face)
   MODIFY:AREA=Face|SET|10,10

@@ Line 89: / Line 89: @@
   x is a legal variable scope
-  y is a variable type (see VARTYPEDEF)
+  y is a variable type (see NAMESPACEDEF)
   z is the variable name
@@ Line 130: / Line 130: @@
 The following tokens are REQUIRED in data control file:
-  VARTYPEDEF:NUMBER|VAR
+  NAMESPACEDEF:NUMBER|VAR
-  VARTYPEDEF:POINT|AREA
+  NAMESPACEDEF:GRIDPOINT|AREA
 ==Variable File==
@@ Line 329: / Line 329: @@
 Therefore:
-  VARTYPEDEF:NUMBER|VAR
+  NAMESPACEDEF:NUMBER|VAR
 Defines an internal "variable type" of "VAR" that holds numbers.
 This is done because we may want something like:
-  VARTYPEDEF:NUMBER|MOVEMENT
+  NAMESPACEDEF:NUMBER|MOVEMENT
 This allows us to have multiple, non-conflicting types of numbers in the data.
 Once the second argument is used in a TYPE entry, then it can be used in other data, including LOCAL and GLOBAL in the variable file and MODIFY in other LST files.  Items are referred to by the second argument, NOT the underlying type.  So the following would be reasonable data:
-  VARTYPEDEF:POINT|AREA
+  NAMESPACEDEF:GRIDPOINT|AREA
   AREA|Face (note that since GLOBAL is implied, this is equal to GLOBAL:AREA|Face)
   MODIFY:AREA=Face|SET|10,10

@@ Line 47: / Line 47: @@
 =New Data Control File Tokens=
-==VARTYPEDEF==
+==NAMESPACEDEF==
 NAMESPACEDEF: is a token for the Data Control File defined by the DATACONTROL: PCC token

@@ Line 49: / Line 49: @@
 ==VARTYPEDEF==
-VARTYPEDEF: is a token for the Data Control File defined by the DATACONTROL: PCC token
+NAMESPACEDEF: is a token for the Data Control File defined by the DATACONTROL: PCC token
-  VARTYPEDEF:x|y
+  NAMESPACEDEF:x|y
   x is a legal data format (currently NUMBER, GRIDPOINT)
@@ Line 59: / Line 59: @@
 * x will have a lot more legal values going forward (STRING, etc. - many of those that are legal on QUALIFY today)
-Note that a y value MUST have a VARTYPEDEF in the Data Control file for it to be legal in the "y" slot of LOCAL in the Variable File.
+Note that a y value MUST have a NAMESPACEDEF in the Data Control file for it to be legal in the "y" slot of LOCAL in the Variable File.
 =New Global Modifier Tokens=

@@ Line 18: / Line 18: @@
 * Is not intended to cover unreasonably high numbers
 * There is at least one UI problem, in that the UI doesn't realize that the PRExxx status of an EqMod can dynamically changes when another EqMod is added.  The EqMod in question has to be selected to turn red.
 =New Campaign File Tokens=

@@ Line 198: / Line 198: @@
 ===ADD===
-ADD takes a Numeric Argument.  Must be a legal Integer or Double, no calculations are allowed.
+ADD takes a Numeric Argument.
 The 'natural' priority is 3.
@@ Line 204: / Line 206: @@
 ===MULTIPLY===
-MULTIPLY takes a Numeric Argument.  Must be a legal Integer or Double, no calculations are allowed.
+MULTIPLY takes a Numeric Argument.
 The 'natural' priority is 2.
@@ Line 210: / Line 214: @@
 ===MAX===
-MAX takes a Numeric Argument.  Must be a legal Integer or Double, no calculations are allowed.
+MAX takes a Numeric Argument.
 This sets an upper bound on the value (a maximum that the value can be)
@@ Line 218: / Line 224: @@
 ===MIN===
-MIN takes a Numeric Argument.  Must be a legal Integer or Double, no calculations are allowed.
+MIN takes a Numeric Argument.
 This sets a lower bound on the value (a minimum that the value can be)
@@ Line 226: / Line 234: @@
 ===SET===
-SET takes a Numeric Argument.  Must be a legal Integer or Double, no calculations are allowed.
+SET takes a Numeric Argument.
 This sets the value (any previous value is overwritten/ignored)
@@ Line 232: / Line 242: @@
 The 'natural' priority is 0.
-===SOLVE===
+If you have a value that was previously modified from the default (or you want to enable that based on using a higher PRIORITY= then you should use the value() function to capture the existing value.  Thus the following are equivalent:
   MODIFY:Foo|ADD|4
   MODIFY:Foo|SOLVE|value()+4
-(Note that the ADD is preferred because it is smaller in memory and faster to process, but more complex calculations will obviously require SOLVE)
+Note that the ADD is preferred because it is smaller in memory and faster to process, but more complex calculations will obviously require SOLVE
 =ModifyOther Token=

@@ Line 276: / Line 276: @@
 And in GlobalModifiers
-MODIFYOTHER:EQUIPMENT.PART|ALL|CritRange|SOLVE|value()+EqCritRange
+ MODIFYOTHER:EQUIPMENT.PART|ALL|CritRange|SOLVE|value()+EqCritRange
 Note: