122 added support for the `saves` cli argument, however it may be more appropriate for this to be variadic and support changing this at runtime. If `saves` were implemented as a cvar, I could leverage the existing cvar code which provides file path suggesters to autocomplete the saves path.

c20978bdca115434bf778e40e18fcd3f67b95762 and 3e9b01bf02c6fbe938d5070f4d4e4acf4c3d8b9d added home and saves commands which will either need to be deprecated and removed or modified to work with any change made by this issue (should I decide to support a command syntax like saves C:\path\to\saves) -- I think a cvar impl may be easier.

collinsmith / riiablo

Support for changing `saves` path at runtime #123

122 added support for the `saves` cli argument, however it may be more appropriate for this to be variadic and support changing this at runtime. If `saves` were implemented as a cvar, I could leverage the existing cvar code which provides file path suggesters to autocomplete the saves path.

collinsmith / riiablo

Support for changing `saves` path at runtime #123

122 added support for the saves cli argument, however it may be more appropriate for this to be variadic and support changing this at runtime. If saves were implemented as a cvar, I could leverage the existing cvar code which provides file path suggesters to autocomplete the saves path.

122 added support for the `saves` cli argument, however it may be more appropriate for this to be variadic and support changing this at runtime. If `saves` were implemented as a cvar, I could leverage the existing cvar code which provides file path suggesters to autocomplete the saves path.