Since v5 it is possible to prevent files being overwritten, that nice. :)
But as example for my use case I would like to update server.properties with each modpack update, to set a new resourcepack version too.
Currently as far I understand the current implementation it is not possible to allow for that.
Example lockedpaths.txt, how a new implemention could be used:
!server.properties
!ops.json
Also if there are no files existing (nothing can be overwritten), it should use the default provided files form the modpack.
Mostly applicable to the first server start (e.g. default world/configs).
Since v5 it is possible to prevent files being overwritten, that nice. :)
But as example for my use case I would like to update server.properties with each modpack update, to set a new resourcepack version too.
Currently as far I understand the current implementation it is not possible to allow for that.
Example
lockedpaths.txt, how a new implemention could be used:Also if there are no files existing (nothing can be overwritten), it should use the default provided files form the modpack.
Mostly applicable to the first server start (e.g. default world/configs).