Settings, object assignments and individual style recipes have different export scopes. Preserve scene/prefab identities alongside metadata when sharing an entire project.
Choose the export category#
| Action | Includes |
|---|---|
| Export style | One selected reusable style/draft in preset JSON. |
| Import style | New custom style with an available name, retaining existing factory/custom identities. |
| Export settings | Global options, role profiles, ten Quick colors, imported icon payloads, bookmarks and custom presets. |
| Export assignments | Project object/prefab style records; references are project-specific. |
| Import configuration | Settings or Assignments JSON, validated before Merge/Replace. |
For a complete backup, export Settings and Assignments separately. A preset file does not include the private image library; include Settings when a recipe depends on imported icons.
Merge, replace and recovery#
Files identify category/version and are validated before mutation. Imports record Undo, capture pre-import state and restore snapshots on failure. Unresolved references are reported and retained for recovery.
| Operation | Effect |
|---|---|
| Merge settings | Apply incoming option/profile values; combine bookmarks/icons; update matching preset IDs while retaining unrelated custom presets. |
| Replace settings | Replace global settings/custom presets. Object assignments are separate. |
| Merge assignments | Update matching object IDs/add incoming records, retaining other assignments. |
| Replace assignments | Replace assignment records without changing settings/custom presets. |
| Automatic backup | Write both categories as timestamped JSON under ProjectSettings/ERAGANX.HOP.Backups/. |
| Icon ID conflict | Merge rejects one ID with different image payloads. Use an intentional Replace or import images separately. |
| Missing references | Report unresolved scenes/assets/icons; assignments need matching GUIDs/local IDs. |
- Export current Settings and Assignments, then choose the desired configuration file.
- Read the category-specific Merge/Replace dialog. Merge still applies incoming global option values.
- Inspect status, missing references, styled rows, icons, presets and bookmarks.
- Use Undo or the matching pre-import backup when recovery is needed. Keep a current copy before manual recovery.
Single preset JSON is limited to 64 KB. Configuration input is limited to 24 MB, with up to 2,000 custom presets or 100,000 assignment records, depending on category.
Persistent project files#
| Data | Location or identity |
|---|---|
| Style database | ProjectSettings/ERAGANX.HierarchyOrganizerPro.asset: assignments and custom presets. |
| Options database | ProjectSettings/ERAGANX.HierarchyOrganizerPro.Options.asset: options, profiles, icons and scene references. |
| Database backup | .bak recovery copy; imports also create JSON backups in ERAGANX.HOP.Backups. |
| Saved scene/prefab references | Asset GUIDs and local object IDs; retain matching .meta files. |
| Unsaved scenes | Temporary assignments until durable saved identities are available. |
| Moving / Save As | Live objects can promote/migrate styles as identities change; unresolved records are retained. |
Keep relevant ProjectSettings files, scenes/prefabs and .meta files together in version control. Resolve metadata conflicts deliberately. Back up both categories before package updates; factory definitions do not overwrite user presets.
Transfer to another project#
- Import the Editor package; export/import Settings for recipes and icon payloads.
- Transfer scene/prefab assets with matching GUIDs/local identities before importing Assignments.
- Read missing-reference reports. Recreated objects with similar names and new identities require new assignments.
- Open scenes, inspect rows and save project data.
Enable Styling can hide presentation without deleting records. Keep exports/metadata before removing the extension if you plan to restore it.