Currently, entries which are missing in messages.yml, but are needed by the plugin (which can happen when updating to newer versions), the plugin sets the message to null which is not the desired behavior.
A hard coded default set of messages should be created or the defaults from the JAR resources should be used instead and written to the actual messages.yml file.
Currently, entries which are missing in messages.yml, but are needed by the plugin (which can happen when updating to newer versions), the plugin sets the message to null which is not the desired behavior.
A hard coded default set of messages should be created or the defaults from the JAR resources should be used instead and written to the actual messages.yml file.