anchor.diff:  
    CurrentPlayer =~ Blue|Green|Red (checks if the Blue, Green or Red player is the current player)
   
  -_*Using Properties: Game Piece Properties*_
  -
   You can also negate regular expressions by using !~ instead of ~=.
   
  -*Comparing a Property to Another Property*
  +=== Comparing a Property to Another Property
   
   On occasion, you may need to compare the value of one Property to the value of another. In this case, surround the name of the Property on the right side of the operator with $-signs (such as $PieceName$) to indicate that the Property with that name should be checked for its value. (Do not use $-signs in the left side of the expression. The left side of the expression is always treated as the name of a Property.) Examples:
   
  
positive.code: 
  Properties do nothing by themselves. They need to be evaluated by other VASSAL functions or components. Properties can be used as selection criteria for certain pieces, to track game quantities or game events, and for many other purposes.
  
  _*Types of Properties*_
  
  Properties come in two types: system Properties, and custom Properties.
  
  * Many VASSAL components, such Game Pieces, Decks, Maps, Boards, Dice Rollers, and Turn Counters, already have Properties defined for them. These are called _System Properties_. System Properties for components are listed in the component descriptions in later sections.
  * In addition, you can create and define _custom_ Properties for Game Pieces, Map Windows, Zones, and the module itself. Examples of custom Properties include Global Properties, Dynamic Property Traits, and Marker Traits. Information on using component Properties, Traits, or Global Properties will be found in their descriptions in this Guide.
  
  _*Property Names*_
  
  *System Property Names:* The names of System Properties are already defined for module components. For example, all Game Pieces have a system Property named CurrentMap, the value of which is the name the Map where the Game Piece is currently located. System Properties cannot be renamed. System properties for module components are defined in this guide in the sections describing those components.
  
  
negative.code: 
  If Bill clicked a Dice button named 2d6, and the result was 5, the message displayed in the Chat Window would be: _**2d6 =_ _5***<Bill>._
  
  *Constructing a Message Format*
  
  In a Message Format, any word surrounded by $-signs represents a variable, the value of which will be determined when the message is generated during play. When constructing a Message Format for a component, click the *Insert* drop-down menu for a list of available variables for the Message Format. Selecting one of the variables from the menu will insert it at the current cursor position.
  
  