The list of players who can bypass a world's border is currently stored in WorldBorder's singular config.yml file. I suggest moving that list into a separate file so that the rest of the config can be managed separately with a tool like Ansible.
For context, the network I work on uses Ansible to generate and push config files to several servers, but the list of players who can bypass the world border is managed with WorldBorder's in-game commands. Separating the list of players from the config would allow the config file (which doesn't change very often) to be managed by Ansible while continuing to manage the bypass list in-game.
AppleDash
commented
8 years ago
The list of players who can bypass a world's border is currently stored in WorldBorder's singular
config.ymlfile. I suggest moving that list into a separate file so that the rest of the config can be managed separately with a tool like Ansible.For context, the network I work on uses Ansible to generate and push config files to several servers, but the list of players who can bypass the world border is managed with WorldBorder's in-game commands. Separating the list of players from the config would allow the config file (which doesn't change very often) to be managed by Ansible while continuing to manage the bypass list in-game.