Closed joshwenke closed 5 months ago
Here is an example of our current workaround for when server.properties removes the server-name variable. It is super messy and very frustrating.
Thank you for sharing.
I propose we add a new file called bungee.yml. I was advised not to place this option in settings.yml for networks wanting to symlink their settings between multiple servers would end up in a server name duplicates. What do you think?
This is a great idea! Many other plugins have a dedicated bungee config file, and this allows us to pull our standard settings.yml from a single location in Git, and the server configs from their own respective locations. When the servers are dynamically generated, this will make it easy from a server management perspective.
Done!
Summary
For every other Bungee plugin out there, they provide a config.yml option to set the server's name. You can tell the plugin what the name of your servers are via a normal configuration file. ChatControl makes you edit your server.properties.
What would happen if we didn't implement this feature? Why not having this feature is a problem?
ChatControl's implementation of requiring edits to the server.properties is unsustainable for us.
We love the plugin otherwise, but this inconvenience and inconsistency with the recognized standard of Bungee plugins (a .yml config value) is frustrating and will lower our 5 star review down to 3 or 4. Please fix this!