We’re building an internal launcher that lets artists check out a central Flame project, work locally, then check it back in. Media is already available through shared storage/LucidLink; we’re trying to automate project transfer without opening Flame’s GUI.
The GUI’s Restore Project dialog lets us choose:
- Project Home
- Setups Directory
- Media Cache location
However, we haven’t found equivalent destination options in flame_archive, or an external API that performs a complete project restore with these settings.
In our Flame 2027.1 tests, we supplied local defaults through DL_SYSCONFIG_FILE and confirmed they were loaded. Whole-project CLI restore:
- Honored the new Project Home.
- Placed setups inside that home, ignoring the separate setups default.
- Reused the archive’s original media-cache location, ignoring the local cache default.
That last point is the main problem: restoring a project locally still requires access to its old cache location. If that location is unavailable or unwritable, the restore can fail before we have a chance to relocate anything.
We tested relocating the cache and setups afterward and could verify the new paths through Wiretap. But this requires extra steps and doesn’t solve the initial dependency on the old cache location.
The Python project_init_restore hook exposes destination overrides for the GUI dialog, but we haven’t found a way to use those overrides for an unattended, external restore.
Is there a supported headless method we’ve missed? If not, could flame_archive expose the same three destination options as the GUI—or could an API accept them when restoring a complete project?
Ideally, restoring to a new location should not need to access or create directories at the original media-cache location, particularly for an archive that contains no media.