Add server launch parameters to avoid unnecessary data storage
When I need to run multiple servers with different worlds, whitelists, ban lists, etc. I am required to have separate directories for each one. Many of these server directories share server code, files, and the jar files themselves that are identical to their counterparts in separate directories, with the only (hacky and still storage-gluttonous) solution being to store the identical files in a single directory and have the others store links to the real file.
That can become an issue if a person or company wished to host a large quantity of servers, all that storage could be used more efficiently! That's why I propose that parameters for starting the server jar be implemented to either set data (such as the IP or MOTD) to a separate value than what's stored in the configuration file, or (the better solution is) to add parameters that change the file-paths for worlds, whitelists, ban lists, and configuration files for individual server instances.
This would better improve storage efficiency for server administrators who wish to run multiple servers, and would allow for custom file paths to organize the unique data of specific servers.
I hope you consider my proposed addition.
Please sign in to leave a comment.