V10 FAQ (Archived)
Check out the new Migration Page for information about migrating your Lancer world from v0.1.x.
Check out PilotNET's pins in #lancer-vtt, it has a bunch of random guides.
Check out the Recommended Modules page.
We recommend Encounter Library for a non-Lancer guide to Foundry if you want to learn about everything it can do.
Check out Eravel's Lancer Foundry Guide, which has a lot of detailed advice and how-to's.
My recommendation: Just make a throwaway world, open it up, and start messing around. We tried to make it as intuitive to use as possible so you should be able to figure out the Lancer-specific stuff. You can always got to PilotNET with any questions you may have!
See the GIF here, or check out the brief guide here.
Use the Hex Size Support module. After installing, make sure it's enabled for your world:
Then see this GIF for hex setup and token assignment.
More details can be found on the HSS page.
There are several great modules for that that do slightly different things:
- Multilevel Tokens
- Levels
- Roof and Overhead Tiles (NOTE: Roof and Overhead Tiles is deprecated after Foundry version 0.7.10, and should not be used with versions newer than that, or it will cause errors.)
When you create a new world and log in to it for the first time, the system will prompt you to install the latest core Lancer data. This will create compendiums that contain all player-facing data from the core rulebook, such as core frames, systems, and weapons. All non-core Lancer data, including core NPCs, data from The Long Rim, and data from No Room For A Wallflower, must be added to the system manually by importing the associated LCP files within the Lancer Compendium Manager, which is found in the Compendium tab of your world, directly below Create Compendium:
Probably worth checking out the Foundry Knowledge Base.