-
Notifications
You must be signed in to change notification settings - Fork 2
/
Field Guide to Field Guides.tex
1266 lines (1061 loc) · 62.8 KB
/
Field Guide to Field Guides.tex
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
193
194
195
196
197
198
199
200
201
202
203
204
205
206
207
208
209
210
211
212
213
214
215
216
217
218
219
220
221
222
223
224
225
226
227
228
229
230
231
232
233
234
235
236
237
238
239
240
241
242
243
244
245
246
247
248
249
250
251
252
253
254
255
256
257
258
259
260
261
262
263
264
265
266
267
268
269
270
271
272
273
274
275
276
277
278
279
280
281
282
283
284
285
286
287
288
289
290
291
292
293
294
295
296
297
298
299
300
301
302
303
304
305
306
307
308
309
310
311
312
313
314
315
316
317
318
319
320
321
322
323
324
325
326
327
328
329
330
331
332
333
334
335
336
337
338
339
340
341
342
343
344
345
346
347
348
349
350
351
352
353
354
355
356
357
358
359
360
361
362
363
364
365
366
367
368
369
370
371
372
373
374
375
376
377
378
379
380
381
382
383
384
385
386
387
388
389
390
391
392
393
394
395
396
397
398
399
400
401
402
403
404
405
406
407
408
409
410
411
412
413
414
415
416
417
418
419
420
421
422
423
424
425
426
427
428
429
430
431
432
433
434
435
436
437
438
439
440
441
442
443
444
445
446
447
448
449
450
451
452
453
454
455
456
457
458
459
460
461
462
463
464
465
466
467
468
469
470
471
472
473
474
475
476
477
478
479
480
481
482
483
484
485
486
487
488
489
490
491
492
493
494
495
496
497
498
499
500
501
502
503
504
505
506
507
508
509
510
511
512
513
514
515
516
517
518
519
520
521
522
523
524
525
526
527
528
529
530
531
532
533
534
535
536
537
538
539
540
541
542
543
544
545
546
547
548
549
550
551
552
553
554
555
556
557
558
559
560
561
562
563
564
565
566
567
568
569
570
571
572
573
574
575
576
577
578
579
580
581
582
583
584
585
586
587
588
589
590
591
592
593
594
595
596
597
598
599
600
601
602
603
604
605
606
607
608
609
610
611
612
613
614
615
616
617
618
619
620
621
622
623
624
625
626
627
628
629
630
631
632
633
634
635
636
637
638
639
640
641
642
643
644
645
646
647
648
649
650
651
652
653
654
655
656
657
658
659
660
661
662
663
664
665
666
667
668
669
670
671
672
673
674
675
676
677
678
679
680
681
682
683
684
685
686
687
688
689
690
691
692
693
694
695
696
697
698
699
700
701
702
703
704
705
706
707
708
709
710
711
712
713
714
715
716
717
718
719
720
721
722
723
724
725
726
727
728
729
730
731
732
733
734
735
736
737
738
739
740
741
742
743
744
745
746
747
748
749
750
751
752
753
754
755
756
757
758
759
760
761
762
763
764
765
766
767
768
769
770
771
772
773
774
775
776
777
778
779
780
781
782
783
784
785
786
787
788
789
790
791
792
793
794
795
796
797
798
799
800
801
802
803
804
805
806
807
808
809
810
811
812
813
814
815
816
817
818
819
820
821
822
823
824
825
826
827
828
829
830
831
832
833
834
835
836
837
838
839
840
841
842
843
844
845
846
847
848
849
850
851
852
853
854
855
856
857
858
859
860
861
862
863
864
865
866
867
868
869
870
871
872
873
874
875
876
877
878
879
880
881
882
883
884
885
886
887
888
889
890
891
892
893
894
895
896
897
898
899
900
901
902
903
904
905
906
907
908
909
910
911
912
913
914
915
916
917
918
919
920
921
922
923
924
925
926
927
928
929
930
931
932
933
934
935
936
937
938
939
940
941
942
943
944
945
946
947
948
949
950
951
952
953
954
955
956
957
958
959
960
961
962
963
964
965
966
967
968
969
970
971
972
973
974
975
976
977
978
979
980
981
982
983
984
985
986
987
988
989
990
991
992
993
994
995
996
997
998
999
1000
\documentclass[twoside,headings,letterpaper,twocolumn]{article}
\usepackage{FieldGuide}
\usepackage{listings}
\usepackage{lipsum}
\usepackage{adjustbox}
\usepackage{shadowtext}
\usepackage{contour}
\lstset{frame=tb,
language=[LaTeX]TeX,
aboveskip=3mm,
belowskip=0mm,
breaklines=true,
showstringspaces=false,
columns=flexible,
basicstyle={\small\ttfamily\raggedright},
numbers=none,
numberstyle=\tiny\color{black},
keywordstyle=\color{blue},
commentstyle=\color{orange},
stringstyle=\color{magenta},
tabsize=4
}
% Set path for images
\graphicspath{{./images}} % or multiple paths \graphicspath{{./images}{../../mystuff/Lancer/images}}
% Use this command to make the table of contents ALL UPPERCASE instead of exactly what you typed.
\renewcommand{\sectioncase}[2]{\FillLine{\MakeUppercase{#1}}{#2}}
% Use this command to start at SECTION 0 like the core book does.
\setcounter{section}{-1}
\title{Field Guide to Lancer Field Guides}
\author{Tetragramm}
\listfiles
\begin{document}
\frontmatter
\maketitle
\clearpage
\tableofcontents
\mainmatter
\section{INTRODUCTION TO THE FIELD GUIDE}
\subsection{FIRST QUESTIONS}
\subsubsection{A Template}
This document is produced using, and describes how to use, the Lancer Field Guide package for \LaTeX{}. It makes it (relatively) simple to create a document in the format of the official Lancer content.
It's important to know that \LaTeX{} is a text markup language that gets compiled to PDF files. It's very like a programming language. However, this package (the FieldGuide.sty file), hides as much of the complexity as possible so all you have to do is type in text, numbers, and image names.
\subsubsection{Why LaTeX?}
First of all, \LaTeX{} is free, both in the money sense, and in the information sense. You can download it on pretty much any computer and use it.
It's also capable of doing amazing things when formatting text. You'll see some of that below. To be truthful, I'm not a \LaTeX{} expert. I hope this template will be useful to you and help you make better Lancer content, without worrying about graphic design.
\subsubsection{First Steps}
There are two ways of using \LaTeX{}: Building it yourself or using a service that wants you to pay them. If you don't mind the second, go to \href{https://overleaf.com}{\color{blue}\underline{Overleaf}} and upload every file and folder into a new project. It should compile and give you your pdf.
For everyone else, install \LaTeX{}. Go to: \href{https://tug.org/texlive/}{\color{blue}\underline{TeX Live}}, download, and install it. It's going to take a while (no, seriously, get a book or go do something else for a bit), because there are a lot of useful packages it will download in tiny pieces.
Next, open up \href{https://www.overleaf.com/learn}{\color{blue}\underline{Overleaf}} and check it out. This website is a very good source on basic \LaTeX{}, and is very good to have open as you work.
Now, open Main.tex in your favorite text editor (or Overleaf's editor). VSCode is a popular, free choice, because it has extensions for \LaTeX{} that let you compile on save, intellisense, custom keyboard shortcuts, and things like that. But any text editor works, from notepad to vim to emacs.
It is import to note that \LaTeX{} uses a multi-pass compilation system. Typically, documents built with this template require three compilation runs. See \textcolor{blue}{Compile.py} for an example call that can be easily modified to work with your document.
Common symptoms that indicate another compile is needed are log messages about "Package color Error: Argument not in range", and the triangles in the corners moving into the middle of the page. Don't Panic! Just run the compile again, and it should work. Overleaf is nice enough to run it the correct number of times automatically for you (so far as I've seen).
\subsubsection{About the Template}
The template is in two parts. Most important is the file FieldGuide.sty, which defines a lot of useful commands, symbols, and formatting. Second is the file Main.tex, which sets up the skeleton that you will be filling out.
Here is the full text of Main.tex, and we'll use this to explain what it does, then we'll get into FieldGuide.sty.
\begin{lstlisting}
\documentclass[twoside,headings,letterpaper,twocolumn]{article}
\usepackage{FieldGuide}
% Set path for images
\graphicspath{{./images}} % or multiple paths \graphicspath{{./images}{../../mystuff/Lancer/images}}
% Use this command to make the table of contents ALL UPPERCASE instead of exactly what you typed.
\renewcommand{\sectioncase}[2]{ \FillLine{\MakeUppercase{#1}}{#2}}
% Use this command to start at SECTION 0 like the core book does.
\setcounter{section}{-1}
\title{Your Title Here}
\author{Your Name Here}
\begin{document}
\frontmatter
\maketitle
\clearpage
\tableofcontents
\mainmatter
\end{document}
\end{lstlisting}
First is the preamble, everything before \verb|\begin{document}|. The first line you shouldn't mess with, as it defines the basic format of the book. The usepackage command includes the FieldGuide.sty file, and you can also use it to import other \LaTeX{} packages. Next in the preamble are three settings.
\begin{itemize}
\item The graphicspath defines where it looks for images. So if you've already got all the images in a specific folder, define it here.
\item The renewcommand option exists to make the table of contents all uppercase. Whenever you define a section, subsection, or subsubsection, the name you type in gets used everywhere, but this makes it appear uppercase in the contents. If you turn it off, it will just be however you typed it. Either way works, just be consistent.
\item The setcounter option makes the first Section number into 0, like the core Lancer book does. If you want to start at one, just comment it out.
\end{itemize}
After \verb|\begin{document}|, there is the content of the document, which you will be modifying. The frontmatter command starts the roman numeral page numbering, and sets the style, while the maketitle command inserts the title page using the title and author set in the preamble. You may add additional text below the maketitle command to show other text, acknowledgements, ect.
One thing you may want to do is add a full-page cover. If you do, add a fullpageimage command, referencing your cover (see \hyperref[Images]{Adding Images}).
The tableofcontents command inserts the table of contents. The mainmatter command switches to arabic page numbers and indicates you're ready to go by filling in empty space until the next left page.
After that, it's all yours. Next is what you put on all these wonderful blank pages.
\subsection{USEFUL AND CUSTOM COMMANDS}
\paragraph{Basic Formatting}
The basic text formatting commands are \textbf{bold} (\verb|\textbf{bold}|), \textit{italic} (\verb|\textit{italic}|), and \KeyWord{KeyWords} (\verb|\KeyWord{KeyWords}|). The last is defined by the FieldGuide template, and sets the text in small caps (plus a bit of spacing adjustment). Keyword is what is used for all of the, well, key words like \KeyWord{Stunned}, \KeyWord{Engaged}, ect.
\subsubsection{Sections}
You will be wanting to divide and sub-divide your Field Guide to keep things organized. This too is simple. The largest division is the section, like \hyperref[INTRODUCTION TO THE FIELD GUIDE]{\textcolor{blue}{INTRODUCTION TO THE FIELD GUIDE}}. These are created by typing \verb|\section{SECTION NAME}|. You can also add images to the pages by doing \verb|\section[left-image][right-image]{SECTION NAME}|. The section command forces the book to the next left page, occupies the facing pages, and everything after is on the next page.
A subsection starts on a left page and places a banner across the top of the page, like \hyperref[USEFUL AND CUSTOM COMMANDS]{\textcolor{blue}{USEFUL AND CUSTOM COMMANDS}}. You create it by, drumroll please... \verb|\subsection{SUBSECTION NAME}|. An alternative version \verb|\subsection*| is allowed to start on either left or right pages. A subsubsection, like \hyperref[Sections]{\textcolor{blue}{Sections}} is created by \verb|\subsubsection{SubSubSection Name}|, with the starred version \verb|\subsubsection*| being excluded from the table of contents. Useful for repetitive things like Encounter SITREPs. Lastly, a named paragraph, like \hyperref[Damage Symbols]{\textcolor{blue}{Damage Symbols}}, is created with \verb|\paragraph{Title}|.
\textcolor{red}{\Large WARNING!} The text of the sections needs to be plain-text. No \LaTeX{} macros, no spacing, nothing that uses the \verb|\| and so forth. There's probably a way to make it safe for you to do that, but I haven't figured it out.
\subsubsection{Lancer Symbols}
Lancer has a great deal of custom symbols, contained in a custom font, which is automatically included.
\paragraph{Damage Symbols}
\begin{NiceTabular}{|cl|cl|}[hlines]
\CodeBefore\rowcolors{0}{white}{tablegrey}\Body
\CCKinetic & \verb|\CCKinetic{}| & \CCEnergy & \verb|\CCEnergy{}| \\
\CCExplosive & \verb|\CCExplosive{}| & \CCBurn & \verb|\CCBurn{}| \\
\CCHeat & \verb|\CCHeat{}| & \CCVariable & \verb|\CCVariable{}| \\
\end{NiceTabular}
\paragraph{Mech Size Symbols}
\begin{NiceTabular}{|cl|cl|}[hlines]
\CodeBefore\rowcolors{0}{white}{tablegrey}\Body
\CCSizeOne & \verb|\CCSizeOne{}| & \CCSizeTwo & \verb|\CCSizeTwo{}| \\
\CCSizeThree & \verb|\CCSizeThree{}| & \CCSizeFour & \verb|\CCSizeFour{}| \\
\CCSizeHalf & \verb|\CCSizeHalf{}| & \CCSquad & \verb|\CCSquad{}| \\
\end{NiceTabular}
\paragraph{Attack Symbols}
\begin{NiceTabular}{|cl|cl|}[hlines]
\CodeBefore\rowcolors{0}{white}{tablegrey}\Body
\CCThreat & \verb|\CCThreat{}| & \CCRange & \verb|\CCRange{}| \\
\CCLine & \verb|\CCLine{}| & \CCBlast & \verb|\CCBlast{}| \\
\CCBurst & \verb|\CCBurst{}| & \CCCone & \verb|\CCCone{}| \\
\CCMelee & \verb|\CCMelee{}| & \CCThrown & \verb|\CCThrown{}| \\
\CCAccuracy & \verb|\CCAccuracy{}| & \CCDifficulty & \verb|\CCDifficulty{}| \\
\CCGrenade & \verb|\CCGrenade{}| & \CCMine & \verb|\CCMine{}| \\
\CCDeployable & \verb|\CCDeployable{}| & \CCDrone & \verb|\CCDrone{}| \\
\end{NiceTabular}
\paragraph{Action Symbols}
\begin{NiceTabular}{|cl|cl|}[hlines]
\CodeBefore\rowcolors{0}{white}{tablegrey}\Body
\CCQuick & \verb|\CCQuick{}| & \CCFull & \verb|\CCFull{}| \\
\CCQuickTech & \verb|\CCQuickTech{}| & \CCFullTech & \verb|\CCFullTech{}| \\
\CCReaction & \verb|\CCReaction{}| & \CCProtocol & \verb|\CCProtocol{}| \\
\CCFreeAction & \verb|\CCFreeAction{}| & \CCDowntime & \verb|\CCDowntime{}| \\
\CCActivationQuick & {\footnotesize\verb|\CCActivationQuick{}|} & \CCActivationFull & {\footnotesize\verb|\CCActivationFull{}|} \\
\end{NiceTabular}
\paragraph{Status Symbols}
\begin{NiceTabular}{|cl|cl|}[hlines]
\CodeBefore\rowcolors{0}{white}{tablegrey}\Body
\CCSlowed & \verb|\CCSlowed{}| & \CCImmobilized & \verb|\CCImmobilized{}| \\
\CCShredded & \verb|\CCShredded{}| & \CCStunned & \verb|\CCStunned{}| \\
\CCLockOn & \verb|\CCLockOn{}| & \CCJammed & \verb|\CCJammed{}| \\
\CCProne & \verb|\CCProne{}| & \CCEngaged & \verb|\CCEngaged{}| \\
\CCHidden & \verb|\CCHidden{}| & \CCInvisible & \verb|\CCInvisible{}| \\
\CCDangerZone & \verb|\CCDangerZone{}| & \CCExposed & \verb|\CCExposed{}| \\
\CCDownAndOut & \verb|\CCDownAndOut{}| & \CCShutDown & \verb|\CCShutDown{}| \\
\end{NiceTabular}
\paragraph{Talent Symbols}
\begin{NiceTabular}{|cl|cl|}[hlines]
\CodeBefore\rowcolors{0}{white}{tablegrey}\Body
\CCTalent & \verb|\CCTalent{}| & \CCRankOne & \verb|\CCRankOne{}| \\
\CCRankTwo & \verb|\CCRankTwo{}| & \CCRankThree & \verb|\CCRankThree{}| \\
\CCRankCustom & \verb|\CCRankCustom{}| & \CCSquad & \verb|\CCSquad{}| \\
\end{NiceTabular}
\paragraph{NPC Symbols}
\begin{NiceTabular}{|cl|cl|}[hlines]
\CodeBefore\rowcolors{0}{white}{tablegrey}\Body
\CCNPCTemplate & \verb|\CCNPCTemplate{}| & \CCNPCFeature & \verb|\CCNPCFeature{}| \\
\CCNPCClass & \verb|\CCNPCClass{}| & \CCArtillery & \verb|\CCArtillery{}| \\
\CCBiological & \verb|\CCBiological{}| & \CCController & \verb|\CCController{}| \\
\CCDefender & \verb|\CCDefender{}| & \CCSupport & \verb|\CCSupport{}| \\
\CCStriker & \verb|\CCStriker{}| & & \\
\CCTierOne & \verb|\CCTierOne{}| & \CCTierTwo & \verb|\CCTierTwo{}| \\
\CCTierThree & \verb|\CCTierThree{}| & \CCTierCustom & \verb|\CCTierCustom{}| \\
\end{NiceTabular}
\paragraph{Active Symbols}
\begin{NiceTabular}{|cl|cl|}[hlines]
\CodeBefore\rowcolors{0}{white}{tablegrey}\Body
\CCMovement & \verb|\CCMovement{}| & \CCHex & \verb|\CCHex{}| \\
\CCStructure & \verb|\CCStructure{}| & \CCStress & \verb|\CCStress{}| \\
\CCArmor & \verb|\CCArmor{}| & \CCHP & \verb|\CCHP{}| \\
\CCHollowHex & \verb|\CCHollowHex{}| & \CCCircle & \verb|\CCCircle{}| \\
\CCRepair & \verb|\CCRepair{}| & \CCCP & \verb|\CCCP{}| \\
\CCTrait & \verb|\CCTrait{}| & \CCSystem & \verb|\CCSystem{}| \\
\CCEvasion & \verb|\CCEvasion{}| & \CCEDEF & \verb|\CCEDEF{}| \\
\CCActivation & \verb|\CCActivation{}| & \CCDeactivation & \verb|\CCDeactivation{}| \\
\CCOvercharge & \verb|\CCOvercharge{}| & \CCOvershield & \verb|\CCOvershield{}| \\
\CCSystemPoint & \verb|\CCSystemPoint{}| & \CCSensors{} & \verb|\CCSensors{}| \\
\CCRoll & \verb|\CCRoll{}| & \CCDTwenty & \verb|\CCDTwenty{}| \\
\end{NiceTabular}
\begin{figure*}[b]
\paragraph{GUI Symbols}
\begin{NiceTabular}{|cX|cX|cX|}[hlines]
\CodeBefore\rowcolors{0}{white}{tablegrey}\Body
\CCWeapon & \verb|\CCWeapon{}| & \CCWeaponProfile & \verb|\CCWeaponProfile{}| & \CCGenericItem & \verb|\CCGenericItem{}| \\
\CCGear & \verb|\CCGear{}| & \CCManufacturer & \verb|\CCManufacturer{}| & \CCLicense & \verb|\CCLicense{}| \\
\CCCoreBonus & \verb|\CCCoreBonus{}| & \CCFrame & \verb|\CCFrame{}| & \CCMechSystem & \verb|\CCMechSystem{}| \\
\CCPilotGear & \verb|\CCPilotGear{}| & \CCSkillTrigger & \verb|\CCSkillTrigger{}| & \CCBond & \verb|\CCBond{}| \\
\CCStatusAndCondition & \verb|\CCStatusAndCondition{}| & \CCEquipmentTag & \verb|\CCEquipmentTag{}| & \CCWeaponMod & \verb|\CCWeaponMod{}| \\
\CCLock & \verb|\CCLock{}| & \CCSkill & \verb|\CCSkill{}| & \CCAmmo & \verb|\CCAmmo{}| \\
\CCReserveTactical & \verb|\CCReserveTactical{}| & \CCReserveMech & \verb|\CCReserveMech{}| & \CCReserveResource & \verb|\CCReserveResource{}| \\
\CCReserveBonus & \verb|\CCReserveBonus{}| & \CCCompendium & \verb|\CCCompendium{}| & \CCContentManager & \verb|\CCContentManager{}| \\
\CCCampaign & \verb|\CCCampaign{}| & \CCEncounter & \verb|\CCEncounter{}| & \CCShip & \verb|\CCShip{}| \\
\CCVehicle & \verb|\CCVehicle{}| & \CCMarker & \verb|\CCMarker{}| & \CCNestedHexagons & \verb|\CCNestedHexagons{}| \\
\end{NiceTabular}
\end{figure*}
\paragraph{Unused Symbols}
\begin{NiceTabular}{|cl|cl|}[hlines]
\CodeBefore\rowcolors{0}{white}{tablegrey}\Body
\CCOrbit & \verb|\CCOrbit{}| & \CCOrbital & \verb|\CCOrbital{}| \\
\CCLargeBeam & \verb|\CCLargeBeam{}| & \CCBarrage & \verb|\CCBarrage{}| \\
\CCBalance & \verb|\CCBalance{}| & \CCReticule & \verb|\CCReticule{}| \\
\CCEclipse & \verb|\CCEclipse{}| & \CCBurning & \verb|\CCBurning{}| \\
\CCSpikes & \verb|\CCSpikes{}| & \CCSwordsArray & \verb|\CCSwordsArray{}| \\
\end{NiceTabular}
\subsubsection{Spacing}
The most useful tool for spacing is the \verb|\pagebreak| command. It has an optional argument ranging from 0-4 (ie: \verb|\pagebreak[2]|) that indicates how important it is to break right here. A 0 means don't break the column here, no matter what. A 4 means break right now, and is the default value, if you supply none. If you're in the second column of a page, it moves to the next page. You can also force it to go all the way to the next page with \verb|\clearpage| or to the next left page (IE: if you had a physical book) using \verb|\cleardoublepage|.
\quad For a space like the indentation of this paragraph, use the \verb|\quad| command, or \verb|\qquad| for twice the space. To add a gap that pushes text all of the way to the right, use \verb|\hfill| \hfill like so.
... Really, you want \textit{more} control? How specific do you want to get? Fine. \verb|\hspace{x}| and \verb|\vspace{x}| both add arbitrary amounts of space. x can be in several units, pt, mm, cm, in, em, and even things like \verb|0.5\baselineskip|, or half the height of a line. \LaTeX{} has a great many pre-defined lengths, so read the \href{https://www.overleaf.com/learn/LaTeX/Lengths_in_LaTeX}{\textcolor{blue}{documentation}} to find out what is available.
\paragraph{Columns}
Switching between one and two column mode is simple, use the commands \verb|\onecolumn| and \verb|\twocolumn|. Making sure you don't end up with an empty page is trickier. Each of these starts the new column mode on an empty page, or the empty page it's already on. So \verb|\onecolumn\section{blah}| ends in two column again, because the section command sets it. \verb|\section{blah}\onecolumn| and \verb|\onecolumn\subsection{blah}| work fine though, because onecolumn creates an empty page and the subsection starts at the top of the empty page.
\subsubsection{Info Boxes}
The Lancer rules have several types of fancy boxes. Most of the special box options have a color variable, and ones that Lancer uses have been pre-defined. More are available, and check out the \href{https://www.overleaf.com/learn/LaTeX/Using_colours_in_LaTeX}{\textcolor{blue}{documentation}} for instructions on how to define your own (the xcolor package).
\paragraph{COLORED BOX}
The most basic is the flat, rectangular, colored box. There are two arguments. Box color, and text. You can format the text as usual for \LaTeX{}, including spacing and setting your own text color (ie: use \verb|\textcolor{black}{Blah}| if you think it looks better.) This box is what you use when defining terms, such as on page 20 of the core book, or for Talents.
Here is where you can see the predefined colors and what they are used for, one box for each color.
\begin{lstlisting}
\lancercolorbox{lightestred}{\textbf{lightestred}}
ect, for each color
\end{lstlisting}
\lancercolorbox{lightestred}{\textbf{lightestred}}\\*
License I Header, some footers
\lancercolorbox{cherryred}{\textbf{cherryred}}\\*
Some Sidebars, some footers, some table borders (Sitrep diagrams)
\lancercolorbox{red}{\textbf{red}}\\*
General Use (Default Color)
\lancercolorbox{deepred}{\textbf{deepred}}\\*
License II Header, some footers
\lancercolorbox{darkred}{\textbf{darkred}}\\*
Read Aloud Text
\lancercolorbox{darkerred}{\textbf{darkerred}}\\*
License III Header, some Footers
\lancercolorbox{darkestred}{\textbf{darkestred}}\\*
Some Footers
\lancercolorbox{tablegrey}{\textbf{tablegrey}}\\*
Banded table backgrounds
\lancercolorbox{grey}{\textbf{grey}}\\*
Subtle text
\lancercolorbox{gearbrown}{\textbf{gearbrown}}\\*
Pilot Gear
\lancercolorbox{downtimetan}{\textbf{downtimetan}}\\*
Downtime Headers
\lancercolorbox{combatcharcoal}{\textbf{combatcharcoal}}\\*
Combat Headers
\lancercolorbox{weaponblack}{\textbf{weaponblack}}\\*
Weapon infoboxes
\lancercolorbox{protocolorange}{\textbf{protocolorange}}\\*
Protocol infoboxes
\lancercolorbox{actiongreen}{\textbf{actiongreen}}\\*
Quick Action and Full Action infoboxes
\lancercolorbox{reactionteal}{\textbf{reactionteal}}\\*
Reaction infoboxes, example text
\lancercolorbox{talentblue}{\textbf{talentblue}}\\*
Talent Headers
\lancercolorbox{techactionplum}{\textbf{techactionplum}}\\*
Tech Action infoboxes
\lancercolorbox{narrativepurple}{\textbf{narrativepurple}}\\*
Backgrounds, Mission Hooks
\paragraph{TITLED CORNER BOX}
One of the types is the one used on Page 30 of the Core book, here called the ``Titled Corner Box``. The command for it has three options: Color, Title Text, and Body Text.
\begin{lstlisting}
\titledcornerbox{red}{
\textbf{THE TITLE}
}{
This is the text inside the box.
}
\end{lstlisting}
produces the output
\titledcornerbox{red}{
\textbf{THE TITLE}
}{
This is the text inside the box.
}
\paragraph{CORNER BOX}
Another type of box is very similar to the previous, but with no title. It's used on page 66 of the Core book. The command has two options: Color, and Body Text. The color is automatically shaded towards white, so it has the same color as the body of a similar titledcornerbox.
\begin{lstlisting}
\cornerbox{red}{
This is the text inside the box.
}
\end{lstlisting}
produces the output
\cornerbox{red}{
This is the text inside the box.
}
\paragraph{MOUNT BOX}
Similar, but not quite, is a series of commands for the mount boxes used creating Lancer Frames.
\begin{lstlisting}
\MainMount\MainAuxMount\FlexMount\HeavyMount\AuxAuxMount
\end{lstlisting}
produces the output
\MainMount\MainAuxMount\FlexMount\HeavyMount\AuxAuxMount
\paragraph{INFO BOX}
And probably the most common type of box in the book, here called the ``infobox''. It is what you use to define the weapons, systems, tech attack options, and most everything else to do with a Frame. An infobox has four arguments: the color, the title, (optionally) the mechanical text, and (optionally) the flavor text. If you don't have an optional text, just leave that argument empty, like so: \verb|{}|.
\begin{lstlisting}
\infobox{weaponblack}{
\textbf{\large Weapon Name}\\
{\TechnicalText Superheavy Cannon\\
{[\CCRange{}8][1d6\CCKinetic{}]}}
}{
Mechanical text looks like so.
}{
Flavor Text looks all special like this.
}
\end{lstlisting}
\infobox{weaponblack}{
\textbf{\large Weapon Name}\\
{\TechnicalText Superheavy Cannon\\
{[\CCRange 8][1d6\CCKinetic]}}
}{
Mechanical text looks like so.
}{
Flavor Text looks all special like this.
}
\infobox{weaponblack}{
\textbf{\large Weapon Name}\\
{\TechnicalText Superheavy Cannon\\
{[\CCRange 8][1d6\CCKinetic]}}
}{
Mechanical text looks like so.
}{}
\infobox{weaponblack}{
\textbf{\large Weapon Name}\\
{\TechnicalText Superheavy Cannon\\
{[\CCRange 8][1d6\CCKinetic]}}
}{}{
Flavor Text looks all special like this.
}
\infobox{weaponblack}{
\textbf{\large Weapon Name}\\
{\TechnicalText Superheavy Cannon\\
{[\CCRange 8][1d6\CCKinetic]}}
}{}{}
You can also mark a section for special emphasis, like the Invade box from the core book on page 70.
\begin{lstlisting}
\infobox{techactionplum}{
\textbf{Invade}
}{
When you \KeyWord{Invade}, you mount a direct electronic attack against a target. To \KeyWord{Invade}, make a tech attack against a character within \KeyWord{Sensors} and line of sight.\\
On a success, your target takes \textbf{2\CCHeat{}} and you choose one of the \KeyWord{Invasion} options available to you.\\
<snip text>
\infoemphasis{
\KeyWord{Fragment Signal.} You feed false information, obscene messages, or phantom signals to your target’s computing core. They become \KeyWord{Impaired} and \KeyWord{Slowed} until the end of their next turn.
}
You can also <snip text>
}{%No Flavor Text
}
\end{lstlisting}
\infobox{techactionplum}{
\textbf{Invade}
}{
When you \KeyWord{Invade}, you mount a direct electronic
attack against a target. To \KeyWord{Invade}, make a tech attack
against a character within \KeyWord{Sensors} and line of sight.\\
On a success, your target takes \textbf{2\CCHeat} and you
choose one of the \KeyWord{Invasion} options available to you.
\KeyWord{Fragment Signal} is available to all characters, and
additional options are granted by certain systems
and equipment with the \KeyWord{Invade} tag.
\infoemphasis{
\KeyWord{Fragment Signal.} You feed false information,
obscene messages, or phantom signals to your
target’s computing core. They become \KeyWord{Impaired} and
\KeyWord{Slowed} until the end of their next turn.
}
You can also \KeyWord{Invade} willing allied characters to
create certain effects. If your target is willing and
allied, you are automatically successful, it doesn’t
count as an attack, and your target doesn’t take
any heat.
}{%No Flavor Text
}
\paragraph{Tables}
If you're making your own random roll tables, you'll need to know how to make a table. \verb|\begin{NiceTabular}| is for single column tables and \verb|\begin{NiceTabular*}| spans the entire page. The multicolumn and multirow commands let you merge cells.
\begin{NiceTabular}{|lX|}
\CodeBefore\rowcolors{0}{white}{tablegrey}\Body
\Hline
\Block[l]{1-2}{\textbf{\Large IDENTITY}\textcolor{grey}{\textbf{ROLL 1D20}}} \\
\textbf{1} & An infamous private military corporation. \\
\textbf{2} & Glory-seeking warriors. \\
\textbf{3} & Union regulars, career soldiers. \\\Hline
\end{NiceTabular}
\begin{lstlisting}
\begin{NiceTabular}{|lX|}
\CodeBefore\rowcolors{0}{white}{tablegrey}\Body
\Hline
\Block[l]{1-2}{\textbf{\Large IDENTITY}\textcolor{grey}{\textbf{ROLL 1D20}}} \\
\textbf{1} & An infamous private military corporation. \\
\textbf{2} & Glory-seeking warriors. \\
\textbf{3} & Union regulars, career soldiers. \\\Hline
\end{NiceTabular}
\end{lstlisting}
\clearpage
\subsubsection{Custom Frames}
While not strictly a box, the page for a new Lancer Frame is an important thing to automate. It is significantly more complicated than anything else, and takes up one or two pages. There are a total of 5 arguments, which will be shown separately, so commentary can be interspersed.
The first argument is the a set of key=value pairs representing Frame stats, name, and, in truth, all the things that can be described in a single value. The only two truly optional values are the Background Image and the Facing Image. Background Image is a full screen image, placed behind everything like the company logos in the core book. Facing Image is the optional image on the facing page, like the Drake in the core book. It is optional because some mechs may not have art, and you simply want to start in on the License Levels. If you don't want them, simply don't provide the argument. Also optional is the ToC Type option, which defaults to subsubsection. This is used to set what level the mech appears in the table of contents. The core book has a secton of Mechs, with each mech as a subsubsection, but if you have fewer, you may want to turn a mech into a section or a subsection.
Everything else is required. If you forget to put one of the values in, then the result will be a magenta colored box. As an example, the Speed option has been removed from the next page. If you \textit{really} want to have a blank space, fill the argument with \verb|{}| instead.
You can have dual class Frames. For example: \verb|Class=Defender\slash{}Controller|\\\verb|Class Icon={\CCDefender{}\\\CCController{}}|.
\begin{minipage}{\columnwidth}
\begin{lstlisting}
\LancerFrame[Stats]{Traits}{Mounts}{Core Power}{Flavor Text}
\LancerFrame[Manufacturer=IPS-N, Name=FAKEDRAKE, Size=2, Class=Defender, Class Icon=\CCDefender{}, Armor=3, HP=8, SP=5, Evasion=6, E-Defense=6, Heat Cap=5, Sensors=10, Tech Attack=+0, Repair Cap=5, Save Target=10, Speed=3, Background Image=IPS-N-Background, Facing Image=Drake-Facing, ToC Type = {subsubsection}]
\end{lstlisting}
\end{minipage}
The second argument is the Traits of the frame. Usually it's a set of \hyperref{TITLED CORNER BOX}{titled corner boxes} saying what the frame does. Honestly, not too complicated.
\begin{minipage}{\columnwidth}
\begin{lstlisting}
{\titledcornerbox{red}{HEAVY FRAME}{The Drake can't be pushed, pulled, knocked \KeyWord{Prone}, or knocked back by smaller characters.}
\titledcornerbox{red}{BLAST PLATING}{The Drake has \KeyWord{Resistance} to \textbf{damage}, \CCBurn{} and \CCHeat{} from \CCBlast{}, \CCBurst{}, \CCLine{}, and \CCCone{} attacks.}
\titledcornerbox{red}{SLOW}{The Drake receives \textbf{+1 \CCDifficulty{}} on \KeyWord{Agility} checks and saves.}
\titledcornerbox{red}{GUARDIAN}{Adjacent allied characters can use the Drake for \textbf{hard cover}.}
}
\end{lstlisting}
\end{minipage}
Neither is the list of mounts. Just look at the available ones \hyperref[MOUNT BOX]{HERE}.
\begin{minipage}{\columnwidth}
\begin{lstlisting}
{\MainMount\MainMount\HeavyMount}
\end{lstlisting}
\end{minipage}
Fourth, the Core System is marginally more complicated, but usually just because it has more content. Insert the typical boxes and infoboxes and such as needed to make up that content.
\begin{minipage}{\columnwidth}
\begin{lstlisting}
{\Large\textbf{FORTRESS}
\infobox{protocolorange}{
\textbf{Fortress Protocol}\\
{\TechnicalText\normalsize Active (1CP), Protocol}
}
{You deploy heavy stabilizers and your mech
becomes more like a fortified emplacement
than a vehicle. When activated, two sections of
hard cover (\textbf{\CCLine{}2, \KeyWord{Size} 1}) unfold from your
mech, drawn in any direction. These cover
sections have \KeyWord{Immunity} to all damage.
Additionally, the following effects apply while
active:
\begin{itemize}
\item You become \KeyWord{Immobilized}.
\item Snipped for size
\end{itemize}
This system can be deactivated as a \textbf{protocol}.
Otherwise, it lasts until the end of the current
scene.}{%No Flavor Text
}
}
\end{lstlisting}
\end{minipage}
Last is the Frame's flavor text. There's no example. It's just text, and if you wanted to you could put bold, boxes, or other fancy effects, go right ahead. Maybe some pretty colors?
\LancerFrame[Manufacturer=IPS-N, Name=FAKEDRAKE, Size=2,
Class=Defender, Class Icon=\CCDefender{}, Armor = 3,
HP = 8, SP = 5, Evasion = 6, E-Defense = 6,
Heat Cap = 5, Sensors = 10, Tech Attack = +0,
Repair Cap = 5, Save Target = 10,
Background Image=IPS-N-Background,
Facing Image=Drake-Facing]
{\titledcornerbox{red}{HEAVY FRAME}{The Drake can't be pushed, pulled, knocked \KeyWord{Prone}, or knocked back by smaller characters.}
\titledcornerbox{red}{BLAST PLATING}{The Drake has \KeyWord{Resistance} to \textbf{damage}, \CCBurn{} and \CCHeat{} from \CCBlast{}, \CCBurst{}, \CCLine{}, and \CCCone{} attacks.}
\titledcornerbox{red}{SLOW}{The Drake receives \textbf{+1 \CCDifficulty{}} on \KeyWord{Agility} checks and saves.}
\titledcornerbox{red}{GUARDIAN}{Adjacent allied characters can use the Drake for \textbf{hard cover}.}
}
{\MainMount\MainMount\HeavyMount}
{\Large\textbf{FORTRESS}
\infobox{protocolorange}{
\textbf{Fortress Protocol}\\
{\TechnicalText\normalsize Active (1CP), Protocol}
}
{You deploy heavy stabilizers and your mech
becomes more like a fortified emplacement
than a vehicle. When activated, two sections of
hard cover (\textbf{\CCLine{}2, \KeyWord{Size} 1}) unfold from your
mech, drawn in any direction. These cover
sections have \KeyWord{Immunity} to all damage.
Additionally, the following effects apply while
active:
\begin{itemize}
\item You become \KeyWord{Immobilized}.
\item You benefit from hard cover, even in the
open, and gain \KeyWord{Immunity} to \KeyWord{Knockback},
PRONE, and all involuntary movement.
\item When you \KeyWord{Brace}, you may take a
full action on your next turn
instead of just a quick
action.
\item Any character that
gains hard cover from
you or your cover
sections gains \KeyWord{Immunity} to
\KeyWord{Knockback},
\KeyWord{Prone}, and
all involuntary movement, and gains the
benefits of \textbf{Blast Plating}.
\end{itemize}
This system can be deactivated as a \textbf{protocol}.
Otherwise, it lasts until the end of the current
scene.}{%No Flavor Text
}
}
{The Drake, IPS-N’s first foray into military-grade mech design, is the backbone of
any proactive trade-security or anti-piracy force. Its massive, simian frame is
built around a single-cast bulkhead, sloped and reinforced to handle sustained fire
and the vagaries of vessel-proximal hardvac travel. The Drake is an imposing
chassis, its frame evoking the might of ancient armored infantry from a time when
greater numbers guaranteed victory.
The standard fleet license for the IPS-N Drake outfits each chassis with IPS-N’s
high-velocity, high–projectile fragment assault cannon for suppressing and
overwhelming targets, and a heavy kinetic–ablative shield for defense. Advanced
models feature upgraded weapons and armor including the formidable Leviathan Heavy
Assault Cannon, a high-rpm anti-materiel weapon.}
\LancerNPC[Name=FAKEASSAULT, Size=1,
Class=Striker, Class Icon=\CCStriker{},
Tier1={
Hull=+1, Systems=+1, Agility=+1, Engineering=+1,
HP=15,Evasion=8,Speed=4,Heat Cap=8,
Sensors=8,Armor=1,E-Defense=8,Size=1,
Save Target=10},
Tier2={
Hull=+2, Systems=+2, Agility=+2, Engineering=+2,
HP=18,Evasion=10,E-Defense=9,Save Target=12},
Tier3={
Hull=+3, Systems=+3, Agility=+3, Engineering=+3,
HP=21, Evasion=12,E-Defense=10,Save Target=14}]{
Assault mechs are the most common primary battle frames found throughout
the galaxy. Fitted with a heavy rifle, a sidearm, and a suite of systems that
enhance movement, targeting, and defensibility, they are straightforward,
reliable, and hardy combatants. The pilots of Assault mechs are also the
cheapest to train and outfit, but that doesn’t make them any less dangerous.
}
Unsurprisingly, the NPC command is simpler than the Frame command. It has two arguments. The second is just the flavor text at the top, same as the Frames, but the first argument has it's own quirks.
\begin{lstlisting}
\LancerNPC[Stats]{Flavor Text}
\LancerNPC[Name=FAKEASSAULT, Size=1, Class=Striker, Class Icon=\CCStriker{},
Tier1={Hull=+1, Systems=+1, Agility=+1, Engineering=+1, HP=15, Evasion=8, Speed=4, Heat Cap=8, Sensors=8, Armor=1, E-Defense=8, Size=1, Save Target=10},
Tier2={Hull=+2, Systems=+2, Agility=+2, Engineering=+2, HP=18, Evasion=10, E-Defense=9, Save Target=12},
Tier3={Hull=+3, Systems=+3, Agility=+3, Engineering=+3, HP=21, Evasion=12, E-Defense=10, Save Target=14}] {Flavor text goes here.}
\end{lstlisting}
The first few key values are the same as the LancerFrame command. The Tiers are different. At Tier 1, you need to specify all the values, or you get a magenta box. For Tiers 2 and 3, you only need to specify the values that change from Tier 1. The ToC Type command is also the same as with LancerFrame.
\clearpage
\shiptoc{Carriers}{blue}{This is where your flavor text goes. Image credit JWST. Thanks NASA!
You create this by the command shiptoc with four arguments. The title at the top of the page, the color of the first column, the flavor text under the image, and the background image.
\lstinline{\\shiptoc\{Carriers\}\{blue\}\{This is where your flavor text goes. Image credit JWST. Thanks NASA! <snip recursion>\}\{JWST-Jupiter\}}
}{JWST-Jupiter}
\LancerShip[Name=Tongass, Manufacturer=GMS, Points=4, HP=14, Defense=14, Options={2 Auxiliary, 2 Escorts}, Image=Tongass, Class=Line Carrier]
{
Contemporary doctrines recognize two distinct uses for carriers in naval combat: launching strike craft and supporting subline vessels. Subline ships, those smaller than so-called "ships of the line", typically require additional logistical support to maintain effective combat readiness. Carriers built to support squadrons of low- to mid-tonnage subline combat vessels do so not necessarily by housing them in launch bays, but by transporting them and their crews to deployment areas, then providing tactical coordination and a base for resupply and rearmament once engaged. The Tongass-class line carrier is Union's mainstay subline support vessel, and both its dorsal and ventral umbilical berths and streamlined logistics suites allow it to maintain its escorts on fire-support missions without returning to second- or third-echelon shipyards.
}
{A versatile carrier for coordinating both strike craft and subline vessels, with fleetwide command-and-control integration.}
\infobox{protocolorange}{\textbf{\large Close Support}\\{\TechnicalText Trait}}
{
Allied battlegroups in your range band may use tactics granted by this ship's \KeyWord{Escorts} as if they were under their control.
}{}
The Ship command is even simpler. With only three stats, a few pieces of text, and an image, it's the shortest of all. The ToC Type command defaults to LancerShip, which adds it to the shiptoc, but it can be overridden to instead add it to the whole book ToC. Note that the infoboxes aren't even in the command, just following it, like NPCs. The next text after the command gets inserted into the second column of the page.
\begin{lstlisting}
\LancerShip[Name=Tongass, Manufacturer=GMS, Points=4, HP=14, Defense=14, Options={2 Auxiliary, 2 Escorts}, Image=Tongass, Class=Line Carrier]
{<snip flavor text>}
\infobox{protocolorange}{\textbf{ \large Close Support}\\{\TechnicalText Trait}}
{<snip trait text>}{}
\end{lstlisting}
\subsection{IMAGES}
Adding images is somewhat complicated. \LaTeX{} is good, but it doesn't easily contour text around the contents of images the way the core book does many times. Instead, a few useful commands are provided.
First is adding an image to the bottom of the page, across both columns. The command for this is \verb|\bottomimage{imgname}|. It is important that this command be included with the text in the left column, or \LaTeX{} won't know how much space at the bottom of the page to reserve. Don't worry, it will always be pushed to the bottom of the page, even if that means moving text from after the command to before the image.
The command \verb|\topimage{imgname}| works the same way, just at the top of the page. In the mean-time, have some filler text to show how the text wraps until we describe the next image type.
\bottomimage{BottomHalf}
\lipsum[1-2]
The next type is the full column image. The command is \verb|\colimage{imgname}|, and it breaks the column (and possibly the page), fills the next, and then breaks again. It scales the image to half the page width, so make your image's aspect ratio accordingly. It also turns off page numbers, headers, and footers for the page, because they would draw over the image and look odd. It will automatically detect which column it is in and align it appropriately.
\colimage{FullCol}
The next type is the column width image. \verb|\colwidthimage{imgname}| This image is the same width as a paragraph of text, and can be positioned vertically the same as any paragraph, using vfill and the like.
\lipsum[3-7]
\vfill
\colwidthimage{BottomRight}
\pagebreak
And last, the full page image. \verb|\fullpageimage{imgname}| and \verb|\fullpageimagewframe{imgname}|. These use the entire width of the page, edge to edge, with no margins. This is what you use for full-page art. The first has no page styling, best used for solid full page images, like book covers. The second still has section names, page numbers, and edge styling, and is best for shaped images with transparent edges. Both trigger the new page commands, so you just put them where you want the break to be. You might wish to put one before \verb|\maketitle| to be the cover of the book, as an example.
\fullpageimagewframe{Intro-Last}
\newpage
The section after this is a duplication of the Lancer core book's Section 0. The purpose is to demonstrate how you would replicate a larger section, formatting and all. Obviously, at this length, the source code is not provided, so you'll need to check out the source on the github: \href{https://github.com/Tetragramm/lancer-field-guide-template}{\textcolor{blue}{HERE}}.
\vfill
\section[Intro-L][Intro-R]{GETTING STARTED}
\subsection{INTRODUCTION}
\textbf{It is 5016u, and the galaxy is home to trillions. At
the core of humanity’s territory there is a golden
age, but outside of this newly won utopia the
revolutionary project continues.}
You are a lancer, an exceptional mech pilot among
already exceptional peers, and you live in a time
where the future hangs as a spinning coin at the apex
of its toss – the fall is coming, and how the coin lands
is yet to be determined.
Far now from our humble beginnings, humanity has
spread out among and between the stars for thousands of years. We have set empty worlds and barren
moons alight with civilization, tamed asteroids and gas
giants – even built lives in the hard vacuum of space
itself. We have taken root in our arm of the Milky Way;
life – in its infinite diversity – thrives and expands.
For some, life in this time is as a river – forever moving,
with the land and time of their birth left somewhere far
behind. For most, life is spent on their home world, moon,
or station, linked to the rest of humanity via fantastic technologies, or isolated to the politics, stories, and histories
of their own lands. The trillions that make up humanity
live, for the most part, as you or I do now.
But wonders tie the galaxy together in this age.
Connecting all worlds is blinkspace – an unknowably
vast and strange plane parallel to the one in which we
live, pierced by blink gates that allow us to travel with
speed and safety. Thanks to these massive, star-
bound doors, every corner of space is open to the
daring. These portals are common wonders: thousands of ships travel through them every day seeking
trade, migration, travel, war, and myriad other aims.
Filling the lonely void is the omninet, a data-sharing
network built off the blink that connects every computer,
every server – everything – to everything else. The
omninet is much more than a way to send messages or
a means for people on far-flung worlds to read the
galaxy’s news; it overlays all human communications,
facilitating government, industry, culture, and realms
more esoteric still. Data is the new wealth, and the
omninet means that all wealth can be shared.
The form of that wealth is manna. Uniting the disparate
nations of the human diaspora outside the Core,
manna is the universal currency accepted by every
market on every planet. When a galaxy’s wealth of raw
resources are available for exploitation, a community’s
wealth comes from both its past and its potential.
The vast mass of humanity is administered by a
single sprawling government: Union, the galactic
hegemony. Luna and Mars, Mercury and Venus.
Saturn, Jupiter, Neptune, and Uranus. Phobos and
Deimos. Io, Europa, Ganymede, and Callisto. Titan
and Enceladus. These worlds strung in their orbit
around Sol are the diadem atop which Cradle rests,
the seat of Union’s power and humanity’s ancient
heart. From Cradle, Union controls the three levers
of the galaxy: the blink gates, the omninet, and
manna. Without these levers, and without Union, the
galaxy would fall into chaos.
Union is a new kind of utopia. A new state –
communal and post-capital – for a New Humanity.
Union was born from the ashes and ice of the Fall:
the collapse that felled Old Humanity, boiling Cradle
and withering her colonies entirely. Though it has
been thousands of years since Union was founded –
and thousands more since the Fall – New Humanity knows
only one truth among ten thousand
unknowns: if we are to survive, then we must come
together in solidarity and mutual aid.
Despite
Union’s
conviction
–
and
despite
its
successes so far – the sheer size of this collective
project is daunting. Union is distant to most people:
fictionalized in omninet dramas and novels; dreamed
about by children and wanderers; hailed as the
promised kingdom or damned as the pit by religions
across the galaxy. For all its authority, Union prefers to
rule from a distance. Few have ever seen one of
Union’s administrators, let alone suffered one of its
naval campaigns. For those who have never seen its
flag, Union is all but a myth; for those whose skies
have been darkened by Union’s ships, the hegemony
may have brought liberty – but it brought death first.
The galaxy remains a dangerous place outside the
Core. Rebellions, insurrections, piracy, wars – civil
and interplanetary – continue to flare and burn their
way through space, though only the most desperate
conflicts
require
Union’s
intervention.
Disputes
between Union’s subject states are common enough
that there is still a need for militaries, militias, and
mercenaries. Five major suppliers offer arms and
armor to states and entities outside the Core that
desire them. These manufacturers exist in delicate
balance
with
Union:
though
the
administrators
regulate and the suppliers comply, these two philosophies – one of post-capital utopia and the other of
permanent and wild growth – rush toward an irreconcilable end.
You are one person, alive in this time of tumult and
peace – a time of promise that was built on the sacrifice of those who came before and is threatened still
by the heirs of old adversaries. You are one whose life
is lived in the great river, where lives cross stars and
time; where one person in the right place at the right
time can divert the course of history; where the
collective action of comrades can save worlds, lives,
and better define Union’s utopian dream.
You are a mech pilot – one of the best, a lancer – and
yours is the story of this spinning coin at the apex of
its toss. At this pivotal moment in history, what will
you and your comrades do when fate, foresight, and
luck – good or bad – puts you in the right place at the
right time?
On which side will you fall?
\subsubsection{The Cavalry}
Your character in the world of Lancer is a mechanized
cavalry pilot of particular note – a lancer. Whatever
the mission, whatever the terrain, whatever the
enemy, your character is the one who is called in to
break the siege or hold the line. When the drop
klaxons sound, it’s up to them to save the day.
Your lancer hails from a world and culture of your
choice, but is human. They might come from Earth –
or Cradle, as it is now called – but to hail from Earth
in the age of Union is exceedingly rare. No, it is far
more likely that your pilot hails from somewhere in
the vastness of the human diaspora. In Lancer, it has
been millennia since we left Earth, and most of
humanity lives among the stars in our arm of the
Milky Way.
This
humanity
is
familiar
and
strange
in
equal
measure. As far as we know, the only sentient,
sapient beings in our stellar neighborhood are other
humans, but don’t take this as a limitation – there are
many roads to becoming a lancer. Your character
might be the product of significant technological and
capital investment on the part of their employers; or,
they could be a born prodigy – a wunderkind who
commands a mech with innate grace and ability,
perhaps discovered by a secretive recruiter. Your
character might be a lucky conscript – a battle-proven
draftee who managed to survive their first drop,
promoted by desperate commanders looking for a
hero. They could also be the scion of an ancient,
atemporal monarchy, destined to inherit the chassis
of their polypatriarch. Your character could be a jaded
volunteer from a Union liberator team, motivated by a
closely-guarded ember of hope for a better future; or
an anointed Loyal Wing of the Albatross; or a
facsimile of a long-dead pilot, grown in batches of
thousands; a spacer who has spent too long listening
to the deep whispers of the void.
Whatever led your character to the cockpit of their
mech, they are the sum of many parts: enhanced
through a combination of training, natural skill, battlefield
experience,
and
neural
or
physical
augmentation, a lancer is the equivalent of a knight of
old, a flying ace, or another class of elite warrior.
Lancers, many proudly declare, are a cut above
other pilots.
They aren’t entirely wrong. The recruitment, training,
and maintenance of a mech pilot demand the investment of much more time and capital than your
average soldier. To operate a mech at peak efficiency,
a pilot needs extensive physical and mental training,
or advanced (and expensive) physiological and ontological augmentations. Washout and injury rates are
high thanks to the demanding training process, but a
high bar is necessary: once a candidate attains their
final certifications and ships out to their first posting,
they face only the most dangerous missions. Mechs
aren’t sent in to keep the peace – they’re sent in when
all other options have failed. Your character, a lancer,
represents the best of this exceptional corps.
Remember, whatever their history, your pilot is ultimately human. They’re just as flawed as the rest of
us, just as perfect. Pilots are heroes and villains;
brave souls and cowards; lovers and fighters, all.
Some of them stand strong when everyone else runs,
or are the first to face danger – our best and brightest.
But they, too, break under the pressure; they fail; they
kill, even when they could have spared a life.
Pilots and lancers are from all walks of life. Every
station, criminal history, and economic class is
represented in their ranks.
\subsection{PLAYING LANCER}
Your character in \textit{Lancer} is, first and foremost, a pilot – a
dynamic, larger than life presence on and off the battle‐
field who inspires and terrifies in equal measure – but
your character also has a second component: your
mech. Though you can define their identities separately,
pilot and mech are two parts of the same whole.
The first section of this book talks you through
\nameref{BUILDING PILOTS AND MECHS}.
The second section, \nameref{MISSIONS, UPTIME AND DOWNTIME}, is about narrative play, choosing
missions, and playing during downtime.
The third section, \nameref{MECH COMBAT}, is about
fighting in and with mechs.
The fourth section is the \nameref{COMPENDIUM}, in
which all character options can be found.
The fifth section is the \nameref{GM'S TOOLKIT}, which offers advice for tweaking rules, creating
non-player characters (NPCs), and running missions.
The sixth and final section is the Setting Guide, \nameref{A Golden Age, of a Kind}, an in-depth reference on the canon setting.
\subsubsection{What you Need}
This game uses two sorts of dice: twenty-sided dice
(\textbf{d20}) and six-sided dice (\textbf{d6}). You’ll roll these dice to
determine the outcome of uncertain situations, such
as firing a weapon, hacking a computer, or climbing a
sheer cliff face. When the rules call for you to make a
roll, it will also tell you how many dice to roll. For
example, \textbf{1d20} means you need to roll a single \textbf{d20},
whereas \textbf{2d6} means you need to roll two \textbf{d6s}.
Sometimes the rules will call for you to roll \textbf{1d3}. That’s
just a shorthand way of saying you should roll \textbf{1d6
and halve the results} (rounded up). When you’re
called on to roll \textbf{1d3}, a result of 1 or 2 on a \textbf{d6} equals
1, 3 or 4 equals 2, and 5 or 6 equals 3.
\textit{Lancer} is best played with 3-6 players, but can be
played with as little as two or as many as you feel
comfortable with. Each player needs at least one \textbf{d20,
a number of d6s, and some paper or a character
sheet} to write down information. If you’re playing
online, or welcome computers at the table, the \KeyWord{Comp\slash{}Con character building tool} is recommended.
This game makes use of grid-based tactical combat, so
it can be helpful to have paper with square or hexagonal
grids, such as graph paper or pre-prepared battle maps.
Miniatures aren’t necessary to play this game but they
can sometimes make combat easier to visualize.
Most of the players take on the role of pilots - these
are the player characters, or \textbf{PCs} - but one player is
the \textbf{Game Master}, or \textbf{GM}. The GM acts as a narrative
guide, facilitator, and the arbitrator of the game’s
rules. They help create the story and narrative your
group will explore and portray all of the NPCs. For
more information on the GM role and a list of rules,
tips, and tools for GMs to use, refer to the \nameref{GAME MASTER'S GUIDE}.
Finally, we recommend that all players download our
free companion app, \textbf{Comp/Con}; it isn’t necessary to
have the app to play the game, but it can make it
more accessible to players who aren’t able or don’t
wish to thumb through this book.
\subsubsection{The Golden Rules}
There are two golden rules to remember when playing
\textit{Lancer}: