Hey, was planning to run this adventure but I was wondering, is the lcp file only supposed to contain one system or is it supposed to have NPC data too?
Hello! The LCP only contains a single piece of custom exotic gear, correct. This module does not include any new NPC data; it simply references NPC material from the paid version of the Lancer Core Book. I intentionally do not include any prebuilt NPCs to avoid running afoul of the Lancer Third Party License. If CompCon changes how it stores its exported NPC data in the future, it may then be possible to safely include prebuilt NPC encounters. For now, this module will require a prospective GM to build the NPCs and encounters themselves. Thank you for understanding!
Thanks for the adventure, love the layout and the vibes, has fantastic production.
I do have a few questions, if you don't mind though: When the players get their mechs at the beginning, there isn't really a guidance for what that looks like. Are they designing their own LL0 mechs as normal (Access to all normal options) or is it intended to be limited in some way due to being in this mining camp? I had assumed the players might need to be using the Printer in the Supply Depot to make "reserves" in the form of weapons for the mechs they'll be piloting, but that might be wrong?
The second question is more of a suggestion related to the Reserves, in the section of the adventure where it mentioned gaining reserves, I feel like it would have been nice to give a curated list of suggested gains, rather than just the open concept of Reserves (pg 51). I am going to work out more specifics as to what they might be getting by earning reserves, because I don't think players will be making too much use of an Orbital Drop, or CORE Battery.
Hello, glad the adventure resonates with you! To answer your questions:
For acquiring mechs, the intent is that the players design their mechs ahead of time as part of character creation. Then, when they print their mechs in-fiction, they’re simply the same mechs as the players designed. Whether this is because the characters customized the mechs themselves or because the UIB print codes are just perfectly tailored for them is up to the table.
A curated list of reserves could be useful! When I ran a playtest of the adventure, I cherry-picked reserves from the Lancer Core Book that seemed to fit the moment of the narrative. So, I simply didn’t pick reserves that didn’t make much sense in-fiction (like Orbital Drop as-written, though it could maybe be refluffed). I’ll keep a suggested list in mind for a future revision; for the time being, my best recommendation is to pick what feels right in the moment.
Thank you for taking the time to comment, and I hope you and your table enjoy the adventure!
There's a bit of an issue -- in the intro, the doctor will let any PC take the drill, but then the combat "Grit Those Teeth" relies on the drill being in the enemy's custody and not safe in one of the mech cockpits. Knowing PCs, if they have the drill on hand, they're going to ask why they can't just leave the doctor to his fate and deploy it in another location. Surely the doctor should hold onto it "for safekeeping" while the PCs are out doing all this dangerous could-be-captured-or-killed stuff.
Thank you for the feedback! I mostly didn’t want to have to press the issue if the PCs wanted to hold onto the drill. The primary in-universe reasoning I had was that the dig site would be the safest place to deploy the drill. Dmitri’s capture is primarily intended to motivate the PCs to fight in the dig site, but if the PCs want to deploy the drill elsewhere, I see no reason to stop them other than “this is the map and combat I prepared”. Combat 2 should likely happen regardless, for the reasons outlined in the sidebar “Elevator, Going Up”.
I may make adjustments to this in a future version, to make it clear to a GM that they can allow alternative deployment locations or simply solidifying an in-universe reason for why the drill needs deployed in the dig site (or even just explicitly have Dmitri hold onto it for the reasons you stated). Thank you again for the feedback; I’ll take note of it for future revisions!
← Return to Lancer module
Comments
Log in with itch.io to leave a comment.
Hey, was planning to run this adventure but I was wondering, is the lcp file only supposed to contain one system or is it supposed to have NPC data too?
Hello! The LCP only contains a single piece of custom exotic gear, correct. This module does not include any new NPC data; it simply references NPC material from the paid version of the Lancer Core Book. I intentionally do not include any prebuilt NPCs to avoid running afoul of the Lancer Third Party License. If CompCon changes how it stores its exported NPC data in the future, it may then be possible to safely include prebuilt NPC encounters. For now, this module will require a prospective GM to build the NPCs and encounters themselves. Thank you for understanding!
Ok, thanks for responding, I just didn't know if a link was broken or something!
Thanks for the adventure, love the layout and the vibes, has fantastic production.
I do have a few questions, if you don't mind though: When the players get their mechs at the beginning, there isn't really a guidance for what that looks like. Are they designing their own LL0 mechs as normal (Access to all normal options) or is it intended to be limited in some way due to being in this mining camp? I had assumed the players might need to be using the Printer in the Supply Depot to make "reserves" in the form of weapons for the mechs they'll be piloting, but that might be wrong?
The second question is more of a suggestion related to the Reserves, in the section of the adventure where it mentioned gaining reserves, I feel like it would have been nice to give a curated list of suggested gains, rather than just the open concept of Reserves (pg 51). I am going to work out more specifics as to what they might be getting by earning reserves, because I don't think players will be making too much use of an Orbital Drop, or CORE Battery.
Hello, glad the adventure resonates with you! To answer your questions:
For acquiring mechs, the intent is that the players design their mechs ahead of time as part of character creation. Then, when they print their mechs in-fiction, they’re simply the same mechs as the players designed. Whether this is because the characters customized the mechs themselves or because the UIB print codes are just perfectly tailored for them is up to the table.
A curated list of reserves could be useful! When I ran a playtest of the adventure, I cherry-picked reserves from the Lancer Core Book that seemed to fit the moment of the narrative. So, I simply didn’t pick reserves that didn’t make much sense in-fiction (like Orbital Drop as-written, though it could maybe be refluffed). I’ll keep a suggested list in mind for a future revision; for the time being, my best recommendation is to pick what feels right in the moment.
Thank you for taking the time to comment, and I hope you and your table enjoy the adventure!
There's a bit of an issue -- in the intro, the doctor will let any PC take the drill, but then the combat "Grit Those Teeth" relies on the drill being in the enemy's custody and not safe in one of the mech cockpits.
Knowing PCs, if they have the drill on hand, they're going to ask why they can't just leave the doctor to his fate and deploy it in another location. Surely the doctor should hold onto it "for safekeeping" while the PCs are out doing all this dangerous could-be-captured-or-killed stuff.
Thank you for the feedback! I mostly didn’t want to have to press the issue if the PCs wanted to hold onto the drill. The primary in-universe reasoning I had was that the dig site would be the safest place to deploy the drill. Dmitri’s capture is primarily intended to motivate the PCs to fight in the dig site, but if the PCs want to deploy the drill elsewhere, I see no reason to stop them other than “this is the map and combat I prepared”. Combat 2 should likely happen regardless, for the reasons outlined in the sidebar “Elevator, Going Up”.
I may make adjustments to this in a future version, to make it clear to a GM that they can allow alternative deployment locations or simply solidifying an in-universe reason for why the drill needs deployed in the dig site (or even just explicitly have Dmitri hold onto it for the reasons you stated). Thank you again for the feedback; I’ll take note of it for future revisions!
Purchased! Awesome definitely going to run this.
Thank you! I hope you and your table enjoy it!
This is a fantastic idea and i'm immediately buying this when I have money again.