Currently when a value is changed in the messages.yml file (note changed, not a new node added), the user will receive improper formatting for the command output as the saveDefaultConfig() method only looks for missing values, not changed ones.

A system to update the existing values would be an ideal solution to this problem, rather than forcing the user to remove the existing file.

Proposed solutions:

1. Check the current version and see what changes needed applying. Care would need to be taken if a version is skipped (a version stepping update solution would need to be used).

2. Wipe the messages.yml each time the server is run. This defeats the purpose of having such a file, however.

3. Internalize the messages.yml in the jar. This allows more advanced users to still edit the file if they really wish to do so. This is preferential to removing the file altogether.

The third option has since been implemented.