Output and exchange

Exchanging lists

A list leaves the application as a file and comes back in as a file: to keep a copy, for a second device or from another tool.

Exporting as a file

Open the list, choose Export and, under As a file, one of two formats:

  • Export JSON writes the whole list in New Recruit's JSON format. The application reads this file back in on import, on this device or another.
  • Export roster file (.ros) writes the list in BattleScribe's roster format, in every edition.
The layer “Export”, scrolled down: under “As a file” the buttons “Export JSON” and “Export roster file (.ros)”, below them “For Tabletop Simulator” with “Send to YellowScribe”.
  1. “Export JSON”: the list in New Recruit's JSON format.
  2. “Export roster file (.ros)”: the list in BattleScribe's roster format.
  3. “Send to YellowScribe” sends the list to a third-party service, see its own chapter.

Both files stay on your device until you pass them on yourself. The list as text for tournament software or a chat is covered in Text export, sending it to YellowScribe in Sending to YellowScribe.

Importing a list

  1. At the top of the army lists, choose the edition the list comes from.
  2. At the bottom, choose Import JSON and the file.
  3. The application creates the list and opens it.
Area A of the main view: the army lists of the 11th Edition, at the bottom the buttons “New list” and “Import JSON”.
  1. “Import JSON” reads a list in from a file.
  • What comes in: a JSON file from New Recruit or from this application. A roster file (.ros, .rosz) or a text cannot be imported.
  • A copy: The imported list is a new list with a name of its own, “… (Imported)”. You can edit it like any built list. The file does not carry the accent colour: the copy starts with the default tone, and you choose another in the list settings.
  • Edition: The list belongs to the edition chosen when you import, not to the one in the file.
  • Free version: An import counts as a new list. Once the limit is reached, no further list can be imported; the locked button in its place leads to unlocking in the options.

If the file cannot be read, the application says it could not be read as an army list; the details are in the log.

Between devices

There is no automatic synchronisation, and the application needs no account. This is how a list gets onto another device:

  1. On the first device: open the list, Export, Export JSON.
  2. Bring the file to the second device, by whatever way suits you.
  3. On the second device: choose the same edition and Import JSON.

The edition's catalogue has to be on the second device, see More catalogues later.

Switching from New Recruit or BattleScribe

Existing lists from New Recruit come across as JSON: export them as JSON there and import them here. For lists from BattleScribe there is no direct way, because the application does not read roster files.

The terms in the files go by these names in the application:

Terms from New Recruit and BattleScribe and their names in the application
In the file In the application
RosterArmy list
ForceForce: the built force of the list and its child forces
SelectionRow of the list, such as a unit or an option
CatalogueCatalogue of a faction
Game SystemGame system; within it you choose the edition

What is different:

  • Areas and layers: lists, catalogue, army list and datasheet stand side by side; tasks such as the unit detail lie over them as a layer, see A tour of the interface.
  • A list belongs to its edition: you see only the lists of the chosen edition.
  • An import is a copy: the file stays as it was; what changes is the new list.
  • Your lists live on the device: no account, no cloud. They leave it only when you pass them on yourself or send them to YellowScribe, see the privacy statement. Once the catalogue is downloaded, you keep working without a network.

As of version 1.4.0