event - mention CI if BA not avail

Eudicods · Aug 19, 2024 · 5a78da7 · 5a78da7
1 parent 6d92123
commit 5a78da7
Show file tree

Hide file tree

Showing 4 changed files with 12 additions and 5 deletions.
diff --git a/rules/0-Introduction/index.tex b/rules/0-Introduction/index.tex
@@ -34,7 +34,7 @@ \subsubsection*{Acknowledgments}
 \subsubsection*{Version}
 % --------------------------------------------------------------------------------
 
-This \ifthenelse{\equal{\outworldsMode}{mode-web}}{website is current as of \today}{document is \emph{BattleTech: Outworlds Wastes} version 2.0-alpha, August 16, 2024}.
+This \ifthenelse{\equal{\outworldsMode}{mode-web}}{website is current as of \today}{document is \emph{BattleTech: Outworlds Wastes} version 2.0-alpha, August 19, 2024}.
 
 \newpage
 \vspace*{\fill}

diff --git a/rules/10-Errata/0-Errata-1.1.tex b/rules/10-Errata/0-Errata-1.1.tex
@@ -44,3 +44,9 @@ \subsection{DropShip Customization - Maintenance}
 Add the following sentence to the end of the first paragraph on p. 21 of the full rules:
 
 Also, commanders may fix a limited number of through-armor critical hits or motive system damage without paying the \emph{repair} cost.
+
+\subsection{Event Force Construction}
+
+Add the following sentence to the fourth bullet point on p.4 of the Event rules:
+
+If Battle Armor is not available to the faction in the era, then the force must contain at least one non-mechanized conventional infantry unit.
diff --git a/rules/10-Errata/index.tex b/rules/10-Errata/index.tex
@@ -1,4 +1,4 @@
-This errata documet is current as of August 16, 2024.
+This errata documet is current as of August 19, 2024.
 
 \input{10-Errata/0-Errata-1.0.tex}
 

diff --git a/rules/8-Event/1-Force-Construction.tex b/rules/8-Event/1-Force-Construction.tex
@@ -14,8 +14,9 @@
 \item Each force must have at least one 'Mech.
 
 \item Each force must have at least one Battle Armor unit.
+If Battle Armor is not available to the faction in the era, then the force must contain at least one non-mechanized conventional infantry unit.
 
-\item Each force must have one unit capable of carrying the Battle Armor unit.
+\item Each force must have one unit capable of carrying the Battle Armor (or infantry) unit.
 An OmniMech can carry standard Battle Armor with battle claws.
 BattleMechs can carry Battle Armor equipped with magnetic claws, but receive a -1 MP modifier to their Walking MP (p. 227, \emph{TW}).
 
@@ -37,8 +38,8 @@
 
 Commanders may maintain and improve their force between scenarios with the \ifthenelse{\equal{\outworldsMode}{mode-pdf-event}}{\emph{Force Maintenance} rules (see p. \pageref{subsec:event_force_maintenance})}{\hyperref[subsec:event_force_maintenance]{Force Maintenance} rules}.
 An improved force cannot exceed 5,000 BV and must follow the other limitations above.
-See the \ifthenelse{\equal{\outworldsMode}{mode-pdf-event}}{\emph{Sample Scenario Logistics Tracking} (see p. \pageref{sec:sample_event_roster})}{sample \hyperref[sec:sample_event_roster]{force tracking} sheet}.
-Commanders may also use a new force for each scenario.
+See the \ifthenelse{\equal{\outworldsMode}{mode-pdf-event}}{\emph{Sample Scenario Logistics Tracking} (p. \pageref{sec:sample_event_roster})}{sample \hyperref[sec:sample_event_roster]{force tracking} sheet}.
+Commanders may use a new force for each scenario.
 
 Two sample initial forces are provided; the first force is an ilClan era mercenary unit and the second force is an ilClan era Raven Alliance detachment.
 Pilot names are encouraged, as one of the goals is to develop the personalized lore for your force.