One painpoint for configs .kcpps, is when the server is run with config UI we lost all the config context. It would be great to allow saving this file even when the server is running (via web interface or other solutions).
It would allow for exemple to save only configs that are compatible and run for sure.
Actual workflow would be to save before running and discard it if it is not working (because we have forgot a file, models are not compatible, not enough performances, etc).
An other implementation would be maybe save temporary config when running it, and read it again in case of error, or a feature like "open automatically previous config" saved when starting server.
One painpoint for configs .kcpps, is when the server is run with config UI we lost all the config context. It would be great to allow saving this file even when the server is running (via web interface or other solutions).
It would allow for exemple to save only configs that are compatible and run for sure.
Actual workflow would be to save before running and discard it if it is not working (because we have forgot a file, models are not compatible, not enough performances, etc).
An other implementation would be maybe save temporary config when running it, and read it again in case of error, or a feature like "open automatically previous config" saved when starting server.