The migrator is out of date as it does not adequately deal with the new module system, the new config layout, etc.

• Update the migrator to be able to get from to the last supported version's config to the current dev build's config
• Update the migrator to be able to handle knarvik configs (within the context of the three modules + sgDynmap)
• Implement a /sg parity command that automatically installs stargate-customizations, stargate-mechanics, stargate-integrations, and stargate-dynmap. Only register this command if the migrator has detected a knarvik configuration.
• Update the migrator to add a console nag message about something to the effect of:

You are upgrading from a fork with non-standard features!
Compatibility modules are required if you used any of the following features:
[V gates, type-specific sign colouring, dynmap integration, command-based editing]

To automatically install all required modules, type /sg parity
For more information, visit sgrewritten.org/stargaterevived.

Known migrator problems:

• Relocated gatefiles are not properly moved.
• Pre-legacy gatefiles are not currently implemented.

NOTE: The most recent TMS identified a load of issues with the existing migrator.
Drakia, Knarvik, and Alpha configs no longer load; this will need to be fixed before the next beta.

For the /sg parity command, from what network address' will those files be?

Also do we need another translatable message for that?

Also a permission node

And how long should this command last / be possible to initiate? Should it be possible even if I restart the server, in that case it's going to need another variable to be stored in the database.