Skip to content

How to import and export

A player brings their magus over from another saga, or you'd rather type forty books into a spreadsheet than one by one. Here's how to move records between sagas, bring books and spells in from CSV files, and keep your saga safe.

Exporting a covenant, laboratory or character

  1. Open the record. Open the page of the covenant, laboratory or character you want to move.
  2. Open Export. Open its Manage chapter and click Export.
  3. Check the File. It starts in the exports folder of your save folder, named after the record.
  4. Take the rest of a covenant. For a covenant, tick With its laboratories and characters to take them too.
  5. Export. Choose Export. A character with a portrait goes as a zip, .amm.zip, holding the file and the portrait.

What goes with the record, and what stays behind, is in Exporting.

Bringing a record's changes back from another computer

  1. Export it there. Export the record on the computer where it was changed, and copy the file to this one.
  2. Open it here. Open its page here, and its Manage chapter.
  3. Choose the file. Choose Update from a File, then the file.
  4. Update. Read what would change, then choose Update.

The record keeps its place in the saga. See Updating a record from a file.

Importing a record into another saga

  1. Open the saga. Open the saga that should receive the record, on its page.
  2. Open Import. Open its Saga Management chapter and click Import. The Import Data list opens.
  3. Choose the kind. Choose Characters, Covenants or Laboratories, matching what the file holds.
  4. Choose the file. Pick it in the Open window, which starts in the exports folder.
  5. Import. Read the preview, which lists what will be added, the links kept and the links dropped, and choose Import.

Nothing here is overwritten. How names, links and a missing covenant are matched is in Importing an exported record. A link that's dropped can be set again on the sheet.

A saga-made spell is matched to one here with the same name, Technique, Form and level. A House Rule is matched by name, type and tier, and a saga Ability by name, against the catalog's and the saga's. Anything not matched is added.

Importing books from a CSV file

  1. Make the file. Make a CSV file with a header row. The columns are listed under What can be imported, and name and type are needed.
  2. Import books with no owner. In the saga page's Saga Management chapter, click Import, then choose Books. They land in the Armarium, unassigned, where a new covenant can buy from them on its Creation Worksheet.
  3. Give them an owner later. Open the Armarium from the saga page's Compendium. Use Give on a book, or Change Owner for several at once.
  4. Or import into a library. To put books straight into a covenant's library, open the covenant's page and click Import on its Library.
  5. Choose the file. Pick it in the Open window, which starts in the folder the app was started from.
  6. Import. Read the preview, which lists the books found and any rows skipped with the reason, and choose Import.

The app comes with one such file, data/book_packages/ArM5_books_by_ability.csv. It holds the ArM5 Books by Ability index (Lachie Hayes, 2009), 286 books in 46 codices, with each one's specialty, date and source in its description. Four have a Level or Quality still to be set ("var"), highlighted until you give them their numbers.

Importing spells from a CSV file

  1. Open Import Spells. On the saga's page, click Import in its Saga Management chapter, then choose Spells. The Import Spells helper opens and lists the columns it reads. name, technique and form are needed.
  2. Start from an example. If you have no file yet, tick Save an example CSV instead and choose Choose CSV File. It writes spells_example.csv, with two example spells, to the folder the app was started from. Edit it in a spreadsheet, save it as CSV, and start the import again.
  3. Choose the file. Choose Choose CSV File and pick it.
  4. Import. Read the preview and choose Import.

The spells become the saga's own, and you can edit them on Spells.

When a name is already taken

When an imported book or spell has the name of one already in the saga (spell names compared in any case), the app asks about each one, as What can be imported says. Skip leaves it out, and Duplicate adds it anyway. Skip All and Duplicate All give the same answer for the rest of that import.

Keeping backups

Each saga is one file, the saga's id followed by .json, in the sagas folder of your save folder. To keep it somewhere else, use Change Save Folder on the saga picker. The app saves every change as you make it.

  • Before each season. Before a season or downtime run is applied, the app copies the saga to sagas/backups and keeps the last five, named as How to restore a saga from a backup shows. Undo Last Season uses them (see Undoing a mistake).
  • Anything older. That's the only backup the app keeps, so copy the saga's file yourself from time to time.
  • One record. To keep a single character, laboratory or covenant safe before a big change, export it as above.
  • A damaged file. Every saga file, export and pack is checked as it's read. A field holding the wrong kind of thing, from a file edited by hand or damaged, is named, and the saga isn't opened or changed. Copy a backup over its file to go back to before the damage.

See also: Import Data, Import Spells, The Armarium, Library, House Rules, The saga, Advancing a season