Reloading the configuration without restarting the server is a feature i'd really like to implement. However there are some open issues i haven't settled yet. For example what should i do if the new configuration has less channels ? Should i preserve the channels, drop the players or move them to another channel ?
Just changing the settings of a channel is easier, this can be done by a /set command, the point here is to define a clear and simple syntax, there are many parameters. There is still an issue though, the configuration file is read only, so the changes will not be persisted on shutdown.
I'm not really pleased with the current configuration system, it's quite efficient for a read only use but it's not convenient for writting.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
if possible i would like the server to be a ble to refresh the setting from the chat command is the user is admin.
Also.. if we can store winlist on the server!
Yes this will be included in the upcoming 0.1.2 release.
Reloading the configuration without restarting the server is a feature i'd really like to implement. However there are some open issues i haven't settled yet. For example what should i do if the new configuration has less channels ? Should i preserve the channels, drop the players or move them to another channel ?
Just changing the settings of a channel is easier, this can be done by a /set command, the point here is to define a clear and simple syntax, there are many parameters. There is still an issue though, the configuration file is read only, so the changes will not be persisted on shutdown.
I'm not really pleased with the current configuration system, it's quite efficient for a read only use but it's not convenient for writting.
> what should i do if the new configuration has less channels ?
I think i have the right solution to this issue : the exceeding channels are turned into non persistent channels.