RLS fails if server has never been launched #7
Description
If a user installs RustDedicated and then attempts to run it up via RLS without having done so manually, RLS fails on startup with the following error:
ERROR: Unhandled exception: Server identity path does not exist: C:\Games\rustserver\server\server1
While using RLS to actually install RustDedicated (and optionally Oxide) is not currently a targeted use case (but will be captured in another issue as a possible enhancement), we probably do want to support using RLS for a first-time run.
Notes:
- Just creating the directory seems to be enough for RLS - it doesn't have to actually contain anything?
- RustDedicated creates the directory on launch, and effectively owns the files inside
Options (from most to least safe):
- Force the user to create the directory?
- Allow only if RLS also has no cache file?
- Always allow, but log a warning?
Need to inspect RLS' code to see what it needs in there to support server launch. If the answer is nothing, then RLS should probably not audit until it actually needs to use the directory.
Off the top of my head, it's possible that only wipe processing actually needs to know about this folder tree. If this is the case, then we could just log a warning and then defer checking until a wipe is triggered, at which point we'd log another warning or error and abort that specific activity.