Target Software: Server Launcher Manager
Purpose: To add a built-in auto-backup module for StarRupture server save files, eliminating the need for external batch scripts.
Core Functional Requirements
Auto-Backup Trigger
Add a configurable backup interval (default: 15 minutes; allow users to customize the time in seconds/minutes).
Automatically back up both AutoSave0.sav and AutoSave0.met files (both are required for valid save data, cannot be missing).
Trigger backup only when the server is running and the save directory is accessible.
Backup Retention Policy
Implement a "keep latest N copies" rule (default: 20 copies; user-configurable).
Automatically delete the oldest backup files when the number of backups exceeds the set limit, to avoid disk space overflow.
Name backup files with a timestamp suffix (format: AutoSave_YYYYMMDD_HHMMSS.sav/AutoSave_YYYYMMDD_HHMMSS.met) for easy identification of backup time.
Path & Permission Validation
Add a pre-backup check: Verify if the target save directory (e.g., StarRupture/Saved/SaveGames/[SessionName]) exists and contains valid AutoSave0.sav/AutoSave0.met files.
Prompt users with clear error messages if:
The save directory is not found.
The launcher lacks administrator privileges to read/write files.
The backup target directory cannot be created.
Backup Logging
Generate a dedicated backup log file (e.g., StarRupture_Backup_Log.txt).
Record key events in the log: backup start time, backup file names, number of retained backups, deleted old files, and any error details (e.g., permission denied, file missing).
Allow users to view the log directly in the launcher interface (optional but user-friendly).
Compatibility Optimization
Ensure full compatibility with Windows 11 (resolve encoding conflicts, avoid relying on deprecated commands like wmic).
Support custom save session names (e.g., qingshan in the user’s case), do not hardcode the save folder path.
User Experience Suggestions
Add a toggle switch in the launcher settings (e.g., "Enable Auto Save Backup") to turn the function on/off easily.
Display real-time backup status in the launcher’s console (e.g., [2026-01-22 10:15:00] Successfully backed up to AutoSave_20260122_101500.sav).
Allow users to manually trigger an immediate backup with one click, in addition to scheduled auto-backups.
Why This Feature Is Critical
StarRupture dedicated servers use an overwrite-only save mechanism (no incremental saves by default). Without automated backups, players risk losing all progress if the single AutoSave0.sav file gets corrupted. A built-in backup function will greatly improve server stability and user experience for all StarRupture server operators.
润色一下这段英文，让它更专业、清晰
写一段英文，要求开服管理器作者添加自动备份功能，包含更多细节
如何用英文向开发者请求添加一个功能？
Target Software: Server Launcher Manager
Purpose: To add a built-in auto-backup module for StarRupture server save files, eliminating the need for external batch scripts.
Core Functional Requirements
Auto-Backup Trigger
Add a configurable backup interval (default: 15 minutes; allow users to customize the time in seconds/minutes).
Automatically back up both AutoSave0.sav and AutoSave0.met files (both are required for valid save data, cannot be missing).
Trigger backup only when the server is running and the save directory is accessible.
Backup Retention Policy
Implement a "keep latest N copies" rule (default: 20 copies; user-configurable).
Automatically delete the oldest backup files when the number of backups exceeds the set limit, to avoid disk space overflow.
Name backup files with a timestamp suffix (format: AutoSave_YYYYMMDD_HHMMSS.sav/AutoSave_YYYYMMDD_HHMMSS.met) for easy identification of backup time.
Path & Permission Validation
Add a pre-backup check: Verify if the target save directory (e.g., StarRupture/Saved/SaveGames/[SessionName]) exists and contains valid AutoSave0.sav/AutoSave0.met files.
Prompt users with clear error messages if:
The save directory is not found.
The launcher lacks administrator privileges to read/write files.
The backup target directory cannot be created.
Backup Logging
Generate a dedicated backup log file (e.g., StarRupture_Backup_Log.txt).
Record key events in the log: backup start time, backup file names, number of retained backups, deleted old files, and any error details (e.g., permission denied, file missing).
Allow users to view the log directly in the launcher interface (optional but user-friendly).
Compatibility Optimization
Ensure full compatibility with Windows 11 (resolve encoding conflicts, avoid relying on deprecated commands like wmic).
Support custom save session names (e.g., qingshan in the user’s case), do not hardcode the save folder path.
User Experience Suggestions
Add a toggle switch in the launcher settings (e.g., "Enable Auto Save Backup") to turn the function on/off easily.
Display real-time backup status in the launcher’s console (e.g., [2026-01-22 10:15:00] Successfully backed up to AutoSave_20260122_101500.sav).
Allow users to manually trigger an immediate backup with one click, in addition to scheduled auto-backups.
Why This Feature Is Critical
StarRupture dedicated servers use an overwrite-only save mechanism (no incremental saves by default). Without automated backups, players risk losing all progress if the single AutoSave0.sav file gets corrupted. A built-in backup function will greatly improve server stability and user experience for all StarRupture server operators.
润色一下这段英文，让它更专业、清晰
写一段英文，要求开服管理器作者添加自动备份功能，包含更多细节
如何用英文向开发者请求添加一个功能？