Migrating From Lancer v0.1.x - Eranziel/foundryvtt-lancer GitHub Wiki

Migrating Your Lancer World From v0.1.x

:rotating_light: PSA: ALWAYS BACKUP YOUR FOUNDRY DATA BEFORE UPDATING ANYTHING :rotating_light:

The Lancer system has undergone a huge overhaul since the 0.1.x versions, including changing nearly all of the data model. As such, there is a lot to migrate! We have done our best to write migration code to handle as much as possible, but with a change this big it simply isn't possible to fully migrate everything. Read on for the details!

Things That Won't Be Migrated

  • Some world-level Items (those in the Items tab of the sidebar) will not be migrated. If you need them, you will need to create a new item and fill in the details. (They are not automatically deleted so that you can see which ones there are and export their data if you so desire. You should delete them once you no longer need them.)
    • Pilot Items - pilot armor, pilot weapons, pilot gear, skills, talents, core bonuses, licenses.
    • Mech-related Items - frames, weapons, systems.
  • Customizations to pilot/mech items may be lost.
  • Unlinked pilot tokens in scenes. (NPC and deployable tokens will be migrated; see the note about NPC stats below.)
  • Compendiums which were not automatically generated by the v0.1.x system.

Changes to NPC Stats

Lancer v1.0+ has moved to a model of automatically calculating NPC stats, similar to how Comp/Con does. This means that changes to NPC stats need to be made by editing the NPC's Class item or adding NPC Feature items with the appropriate bonuses (for example, the Reinforced feature from the Veteran template to add +1 structure/stress). This means that some of your NPC's stats may have changed from what they were in v0.1.x.

Migrating Pilots

Before pilots can be migrated, you need to import all of the LCPs that your pilots require. You must use current, up-to-date LCPs compatible with Comp/Con. You may also want to move each pilot into their own folder, especially if you have multiple pilots with the same type of deployable. Doing so will also help keep track of which mechs belong to which pilots.

Once all needed LCPs are imported, click the "Start Migrating Pilots" button on the migration window to start migrating all of your pilots. If you close the migration window while working on your LCPs, you can migrate your pilots individually by right clicking on them in the Actors sidebar and clicking "Migrate Pilot".

Troubleshooting

  • If you are unable to add tokens to a new combat encounter after migrating, click the gear icon on the combat tracker and change the tracked resource. After doing so, you should be able to add tokens to encounters again.