FAQ Sharing Pilots
- Navigate to the Pilot Roster. Click on the "Gear" icon for the pilot of which you want a statblock.
- Click on "Generate Statblock".
- You can optionally include the pilot's mech, create a compact & mech-focused statblock, or add emojis from the Pilot NET Discord.
- When satisfied, select the contents of the statblock and copy them to your clipboard (ctrl+C or right click -> Copy).
GIF Example from NordicNinja on Pilot NET:
If you and another user each have a COMP/CON account, you can share read-only copy of a pilot with that user that tracks your updates as you save them to the cloud.
- Create and log into a COMP/CON account if you haven’t already.
- Enter Pilot Management for the Pilot you wish to share.
- In the navbar at the bottom of the screen, there should be a
{…}icon to the right of the navbar’s divider. Click this icon. NOTE: If you can’t see the icon, try whitelistingcompcon.appin your Adblocker or similar browser extensions. The space should still be clickable even if the icon is invisible.
- If this pilot does not yet have a code, click “generate code”. Wait for the code to be generated.
- Once the 6-digit code is generated, copy it and send it to your desired recipients. This code will last for 90 days, after which the code will need to be extended or regenerated to continue use.
- Navigate to the Pilot Roster.
- At the bottom of the roster, click the Import Pilot button.
- Select “Import From Code”, then enter the share code you received and click Search.
- You will have an option to either import the Pilot as an editable copy tied to your account, or as read-only remote Pilot tied to the original owner’s account (which will track the owner’s changes to the Pilot). NOTE: At this time, remote Pilots are only saved LOCALLY and are NOT stored on the cloud. If you use COMP/CON on a different browser or reset your local data, you will need to reimport the remote Pilots.
COMP/CON supports exporting and importing data files for a given pilot. This method of sharing does NOT require a COMP/CON account.
- Navigate to the Pilot Roster. Click on the "Gear" icon for the pilot you wish to export.
- Click on "Export Pilot."
- Click on "EXPORT PILOT DATA FILE" to save a
.jsonfile named after the pilot's callsign.
- Navigate to the Pilot Roster. At the bottom of the roster, click "IMPORT PILOT".
- Select “Import From File”, then click the paperclip icon.
- Select the file you wish to import. NOTE: Only valid pilot
.jsonfiles will be accepted. - Click the "IMPORT" button that displays after the upload.
NOTE: If you already have a pilot with the same unique ID as the pilot you are importing, you will be prompted to instead create a copy of that pilot.
Roll20 does not support imports from COMP/CON at this time. For more information, check the #lancer-vtt channel on the Pilot NET Discord.
Please refer to the Lancer for FoundryVTT Wiki for any questions you may have about sharing pilots to FoundryVTT.
If you are still using the old version of COMP/CON (v2.2.38), follow these steps:
- Double check that both you and your GM are using the same LCP versions for any content your pilot uses.
- Have both yourself and your GM create and log into a COMP/CON account.
- Navigate to the Pilot Roster in List view. Ensure your pilots are saved to the cloud by clicking the Cloud Save icon in the top navbar.
- Click the “Options” gear for the pilot you want to share, and select “COMP/CON Vault Record”.
- Copy the pilot code and share it with your GM.
- Have your GM “Add New Pilot” and select “Vault Import”. Have them paste your Vault Code into the prompt and import.
- Verify that the pilot on your GM’s side has a Checked Cloud icon, indicating that the pilot belongs to another user.
With the Vault system, your GM pulls your pilot’s saved changes from the cloud whenever they sync their COMP/CON app. If there are discrepancies, make sure that you saved your changes to the vault before your GM syncs!