itch.io

And here it is! After a year and a half of hard work in secret I'm finally able to launch this project for the world!

A few things:

First I don't consider this the 'final' final version of the product. If it does well I plan to get actual professional art made for the book instead of the kooky stuff I threw together in paint and one generous contribution from a friend of mine (who provided the art for the IVAN. Go check out Zedrin's work it's cool I promise).

Second, If during play you find issues either with LCP files or misses in the editing process I absolutely want to know! Feel free to start a threat on it here and I'll see about addressing issues as they come up. 272 pages is a lot of book to cover, not to mention supplementary material, and I've got a lot of work to do going forward.

Third, This book has one partial dependency other than the Lancer Core Rulebook. Maximum Threat is another book that I published a few years ago and some of its content is used in this book. Don't worry I've included the relevant parts in the PDF for the full book, but if you don't own the LCP a complimentary copy of the full LCP is included in this book. This means that this book is complete, and needs no other outside LCP or third party content to run.

Fourth, this is a long campaign. Given a group of five players and a weekly cadence of sessions you can expect a full run through of the campaign to take about a year. Granted, you are free to change whatever you want about the structure of your campaign. Remember this is a framework for a campaign, not a novel. Ultimately the experience you bring for your players will be unique to your table. Add, subtract, do whatever you want. Nothing is canon, everything is canon.

Finally, if you have made a purchase of this work, thank you, from the bottom of my heart. I hope this book serves you well and provides a fun experience for you and your players. Good luck, and godspeed.

Thank you for the feedback! While the supplement itself is basically set in stone at this point, there is nothing stopping you from workshopping one yourself! Part of the joy of this is the ability to homebrew, and if you think of a neat thing to add, by all means add it.

Hey! Glad to hear that you're getting some use out of it. I realized in post that is basically what would happen to the Super if it's alone against 5 characters. I wanted the turn structure to work similar to an Eidolon from Wallflower.  A workaround is to give your PCs some grunts to fight alongside to increase the headcount at the start of combat and just quickly kill them off before they become a problem. Or just don't run it that way. You're the GM, you have final say.

Turn calculation is done at the very start of combat before those drones could be deployed. So unless you have RPV characters from somewhere else helping your party the drones that come with the Hydra would not count versus that total. The drone that deploys with the Hydra would technically be a hostile character, but that drone also doesn't take its own turns so GM Fiat for whether you want that to count or not.

I've gone ahead and added the table of contents as a free file, feel free to peruse

Rules for Hijacking NPCs
6 On-Foot pilot talents for PCs.
- Saboteur specializes in hijacking NPCs
- Command specializes in battlefield survival
- Operative sneaky force multiplier
- Field Medic can bring Pilots back from the brink
- Marksman increases damage dealt as a pilot
- Techie allows tech actions on foot

18 new NPCS that fill a number of archetypes I feel were missing or just seemed like cool ideas to me. Among my favorites:

- Ramshackle - an 'every class but worse' mech that keeps your players guessing
- Puppeteer - Drone based controller

 9 New Templates that expand the kinds of characters you might encounter including:
- Revenant - Zombie-like mechs that keep on coming
- Colosssus - Template for oversizing units and adding gozilla-like flavor abilities
-  Buddy - Template for representing to related NPCs (like bonded for players)
- Super - A more durable Ultra with guaranteed stress and structure

5 Sitreps
A collection of randomized tables
Example combats for testing out the new NPCs
LANSIM - a combat focused simulation
Point Skirmish - a more wargame focused take on lancer for NPC vs NPC.

Hey thanks for reaching out. Unfortunately yes, it has no effect in COMP/CON. That kind of addition would require coding on the website's side which is far beyond the scope of the supplement. Sorry about that, you'll have to track it pen and paper style.

This supplement only contains rules for players to take over control of NPC mechs on the battlefield. Specifically it covers: Taking initial control, what you are allowed to do with it, what you can do with it after combat, etc. Keep in mind, you can always introduce NPC-like things as exotic gear for your players to use on their mechs. They do not necessarily need to be part of the licensing system to be used, certain downtime actions even allow players to create their own systems after a fashion.

Glad you like it. Best of luck!

I see Unknown Npc System listed there, my guess is that somehow the json text of that particular weapon was corrupted. Should be fairly obvious once you look at the JSON file itself.

Did you delete the old NPC and lcp data from previous installs of the LCP in owlbear before installing the new one? (it could be the case that they do not cleanly overwrite each other.)

A few things to try: 

Try updating the lcp file in Comp Con, and then deleting the old NPC, before regenerating your JSON for use in owlbear.

Try making sure that the lcp file in Comp Con and Owlbear are the same version. (Delete the one in OwlBear first, and then import the newer lcp file [warning: I can't speak to whether this will automatically delete your old NPCs or if that may break them]  )

Try deleting the old NPC in Compcon . In some cases Compcon will simply save old configurations instead of checking their systems against its lcp counterpart if the NPC already exists (hence why you can rename things). Once you recreate the NPC, export a new JSON, delete the old NPC from Owlbear and import using the newly minted JSON.

I recognize this is a lot of trouble to go to just to fix one NPC. Personally I'm of the camp of living with the silliness and running off Compcon (that is my preferred way to run).

Alright, so this is what I get after importing with an NPC Json pulled from compcon. As you can see, the flak cannon is in there, as well as the other traits relevant to the NPC. This was from an NPC uploaded using the Export function on CompCon which will generate a JSON file for you to import.

I am also assuming you are using witchdice which is what this sheet is based off of

Ok, so this LCP was not tested for Owlbear, I am not sure what differences might exist between the parser for that program versus compcon. So this will be something that I'll have to look into. Thank you for bringing it to my attention!

Hey, thank you for the bug report! I'll get a patch out today, so keep an eye out for it.

Taking a look at it, let me download the LCP and make sure it was patched correctly, because I'm seeing it on my local copy in comp/con correctly. What platform are you using?

You move freely, but systems that rely on you sitting still are not going to function as you are counted as moving.

Changed my life