Preferences & migration
Keep public client settings separate from local library profiles and dashboard account data.
Three kinds of state#
| State | Where it belongs |
|---|---|
| Public Hub preferences | Executor-local files for the existing client, where file APIs are available. |
| Dashboard account data | Authenticated backend profile, account links, history and stored telemetry. |
| Local UI Library profiles | Separate namespaced configurations in the unpublished UI integration. |
These are not interchangeable backups. The UI configuration manager documents named profiles and its Session fallback. It does not describe the older public Hub’s file format.
Public client migration#
The current client uses AroynHub/ for settings and assets. When new preferences are missing, it can read AroynStagingTest/SeedAutoBuy or SeedAutoBuy preferences. The documented dashboard-key migration reads AroynStagingTest/web_config.json.
Pet feeding preferences#
Enable state, hunger thresholds and maximum fruit value use the existing client preference file. Feeding starts off on a fresh configuration. Check saved settings before allowing consumption, especially when moving between client versions.
Configuration in the local new interface#
The local Phase 6A integration uses a game-specific configuration namespace and preserves compatible preferences without overwriting old files. It restores automation controls safely rather than starting workers merely because a profile was loaded. This interface remains unpublished.