Currently, when record_on_startup is enabled and a recording reaches max_length, the recording stops and is saved (with save_on_stop: true), but a new recording does not automatically start afterward. I tested this with max_length: 60 and confirmed the recording just ends without a new one beginning.
For servers that stay online for long periods (many hours/days), this means recording effectively stops entirely after the first max_length period unless someone manually runs /replay start again.
Would it be possible to add an option (e.g. something like restart_on_max_length: true) that automatically starts a new recording right after the previous one is stopped/saved due to hitting max_length? That would make it possible to keep continuous recording running indefinitely without needing manual intervention. Would really appreciate it if this could be considered!
Currently, when
record_on_startupis enabled and a recording reachesmax_length, the recording stops and is saved (withsave_on_stop: true), but a new recording does not automatically start afterward. I tested this withmax_length: 60and confirmed the recording just ends without a new one beginning.For servers that stay online for long periods (many hours/days), this means recording effectively stops entirely after the first
max_lengthperiod unless someone manually runs/replay startagain.Would it be possible to add an option (e.g. something like
restart_on_max_length: true) that automatically starts a new recording right after the previous one is stopped/saved due to hittingmax_length? That would make it possible to keep continuous recording running indefinitely without needing manual intervention. Would really appreciate it if this could be considered!