>.... [22:15:45 WARN]: [GhostScavengerHunt] Could not save messages.yml to plugins/GhostScavengerHunt/messages.yml because messages.yml already exists.

>....�=>.... [22:12:43 INFO]: [GhostScavengerHunt] Disabling GhostScavengerHunt v2.1.0-SNAPSHOT
>.... [22:12:45 INFO]: [GhostScavengerHunt] Enabling GhostScavengerHunt v2.1.0-SNAPSHOT
>.... [22:12:45 WARN]: [GhostScavengerHunt] Could not save messages.yml to plugins/GhostScavengerHunt/messages.yml because messages.yml already exists.

On our Server we get this line on start each time
the head plugin does not work before we reloaded it
but on reloading we also get this crazzy meassage about the message.yml

after reloading once the plugin works fine

Hi, I'm setting up the plugin for a small Christmas event.

There are things that I do not understand and they are:

-Because when you find a head, it tells you that you already found that head?
It is not enough with: You found a ghost! (x / x)?
Photo
-Another thing, that I really do not know, if it's my problem?

When you find a head that you already found, the message multiplies:
You already found this ghost!
You already found this ghost!
Photo

Thank you in advance for the development of the plugin

Can you add a config option to disable the ghost flying away and instead just mark the ghost as found.

On server startup, this is outputted to the console:

[Server thread/WARN]: [GhostScavengerHunt] Could not save messages.yml to plugins/GhostScavengerHunt/messages.yml because messages.yml already exists.

It looks like the plugin is trying to create the messages.yml file every time the server starts up.

I'm using v2.2.3-FIX

Hey bro
I have a question, will you update the plugin for version 1.13, will you need some change or will it be so "small" the plugin will not need any change and can be used comfortably?

I await an answer, thanks