anchor.diff:  
   Some modifications, such as new board graphics, sound files, or changes to Prototype Definitions, may not be immediately reflected in the VASSAL Player. As well, the names of some components, such as Game Piece Palette tabs, Charts, and Irregular Grid Regions, may be truncated after you create them. This truncation is merely cosmetic. Any of these additions will require you to re-start the Editor in order for them to be displayed correctly in the VASSAL Player.
   
  -_*The Module Editor: Module Basic Settings*_
   
   As a result, a good habit is to save your work, close, and then re-launch your module after you have made any major changes, particularly after adding or editing graphics files. Click *Save* , and then close the Configuration Window. In the Module Manager, right-click your module and pick *Edit Module* to re-load the module in the Module Editor. Any changes you have made to graphics or components should be fully functional after a restart.
   
   _In some instances, you may edit a module but, frustratingly, the changes wonʼt show up even after you refresh the view._
  -
  -_This can occur in games that load a Pre-Defined Setup at game start--changes to a module will not be reflected in a Pre-_
  -
  -_Defined Setup. See page 110 for more information._
  -
  -_*Default Module Nodes*_
  +_This can occur in games that load a Pre-Defined Setup at game start--changes to a module will not be reflected in a Predefined Setup. See page 110 for more information._
  +
  +=== Default Module Nodes
   
   By default, a new module includes the following nodes. Not all of these nodes need be used in a given module.
   
  
positive.code: . In the dialog, enter values for *Game Name, Version Number* and *Description*.
  . Click *Ok*.
  
  _*The Module Editor: Module Basic Settings*_
  
  _*Suggested Module Filename Convention*_
  
  When saving, choose a filename for the module. A suggested filename convention is <game name>_<version number>.vmod.
  
  
negative.code: * *Save, Save As:* Duplicates the items of the same names on the menubar *File* menu. As with any other application, save your work often.
  * *Help:* Click *Help* to display the VASSAL HTML help.
  
  image:_images/image13.png[image,width=348,height=324]Menu Bar
  
  *The Configuration Window*
  
  Most of the effort of module creation is performed in the Configuration window. Any instructions given here refer to using the Configuration Window to create or configure module components.
  
  The Configuration window browser displays the moduleʼs components as _nodes_, in a hierarchical tree view.
  
  Each node displays a folder icon. Node types appear in brackets *[ ]*. The component name precedes the node type. For example, a node labeled *Japanese Units [Game Piece* *Palette]* would indicate a Game Piece Palette component named _Japanese Units._
  
  Click the arrow next to each folder icon to toggle the expanded folder view and view the various sub -components of the folder. Click the arrow again to contract the node.
  
  You can perform any the following operations on components by right clicking on the component node and selecting the operation from the menu.
  
  image:_images/image13.png[image,width=348,height=324]
  
  *The Module Editor, showing the Configuration Window, Menu Bar, and default nodes for a new module.*
  
  * *Properties:* Enables you to choose the settings for the selected component. For components that have already been created, you can access the *Properties* dialog by double-clicking on the selected component.
  * *Translate:* Enables you to set translations for the component into a language of your choice. VASSAL is not localized; you must supply the translations for a given module component. See _Translations_ on page 104 for more information.
  