Presets
A preset is one plain JSON file holding any of: rule sets, character profiles, palettes, styles, kit annotations and project settings. Use presets to share a setup between projects or teammates, or to back it up. Assets refer to each other by name inside the file, and every part is optional.
Open Tools > All In One Prefab Builder > Presets (Export, Import)...
Export #
- What: Everything ticked below: tick rule sets, character profiles, palettes, styles, kit annotations and settings. The active rule set and palette are remembered.
- What: Only the kit …, only that kit's settings and annotations. (Also on the Add Pack wizard's last page and in a kit's actions.)
Kit annotations are the kit's settings and each piece's measurements and annotations. The pack's files are not in the preset: the project you import into needs the same pack.
Import #
Choose a file. A preview lists one line per asset: Create, Update (merge) or Replace, with details. Untick anything you don't want, then click Import.
- Merge: adds what's new; for what exists (same name), the file's values win and anything the file doesn't mention is kept. Lists inside a rule set are merged by id (categories, closure types, fill types), palettes by colour name.
- Replace: what exists with the same name becomes exactly what's in the file. For a kit, annotations the file doesn't have are cleared back to the scanner's guesses.
Kit pieces are matched by GUID (the same pack imported the same way has the same GUIDs), else by their path inside the pack, else by a unique name. A kit that doesn't exist yet is created from the pieces that are in this project; if none are, its line says so and is skipped.
The file #
<name>.wbpreset.json, readable and editable in any text editor. format and formatVersion identify it; a file
from a newer version of the Prefab Builder is refused with a message rather than half-imported.