To enable this function you modify the '[general]' stanza as follows:

[general]

MergeNodeLists       = true

The '[MergeNodeLists]' stanza instructs MUTIL to find the latest nodelists available in your Mystic system and merges them together in the mystic data folder.

For each message network your BBS carries you can define a 'nodefile' statement for it. These should be stated one message network per line. The value should contain the full path and the base filename of the nodelist

Here's an example.

[MergeNodeLists]

nodefile=c:\mystic\files\fdn\fdn_node\nodelist
nodefile=c:\mystic\files\fsx\fsx_node\fsxnet
nodefile=c:\mystic\files\agn\agn_node\agoranet

In the example above Mystic will search in c:\mystic\files\fdn\fdn_node and select the latest nodelist.### nodelist. This comparison is first done by checking the day extension. If the extension is archived (.z12, etc) it will be unarchived before comparison.

After decompressing, the 3-digit day extensions are compared, selecting the highest number. It will also compare the years of the file dates, and select the newest option. So if you have nodelist.025 dated 2013 and also nodelist.320 dated 2012, nodelist.025 will be selected.

The same process is then be repeated for fsxnet.### nodelist and then again for the agoranet.### nodelist. Once all of the defined 'nodefiles' are processed, they will be merged together and copied in to Mystic's DATA folder so it can be used for nodelist lookups by a logged in BBS user.

If no nodelists are found, Mystic will not overwrite the current nodelist. Comments are stripped while merging to lower filesize and increase search performance.

The use of this stanza is recommended as part of a nightly or weekly maintenance process that can be set up and and run by the Mystic BBS Event Editor.