You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Describe the bug
It appears that the plugin does not function at all, changing the config.yml yields 0 change to the MOTD.
To Reproduce
1.18 server
Installed plugin
Changed randommotd to some funny quotes
did /serverlist randommotd
the motd lines are still default even after restart
after restart the config.yml is reset to be completely default
Expected behavior
The plugin to actually work and use the random motds put in the config.yml? also to not rewrite the config.yml every single restart
Config
It's literally resetting to the default config.yml
Versions (please complete the following information):
Spigot 1.18.1
ServerlistMOTD I assume latest
ProtocolLib Also latest
I just installed all of this stuff, and never usually have this problem
Additional context
The text was updated successfully, but these errors were encountered:
Hey, thanks for reporting. I know of multiple instances where the current version is working as expected. Can you please attach your changed config.yml (which resets) here, as instructed during creation of this report? (maybe via pastebin) YAML files can be very tricky sometimes. :) Otherwise, I have no way to reproduce your problem.
Describe the bug
It appears that the plugin does not function at all, changing the config.yml yields 0 change to the MOTD.
To Reproduce
1.18 server
Installed plugin
Changed randommotd to some funny quotes
did /serverlist randommotd
the motd lines are still default even after restart
after restart the config.yml is reset to be completely default
Expected behavior
The plugin to actually work and use the random motds put in the config.yml? also to not rewrite the config.yml every single restart
Config
It's literally resetting to the default config.yml
Versions (please complete the following information):
I just installed all of this stuff, and never usually have this problem
Additional context
The text was updated successfully, but these errors were encountered: