BattleTech - The Board Game of Armored Combat
Catalyst Game Labs => BattleTech Game Errata => Topic started by: Xotl on 23 September 2013, 20:59:36
-
This thread is for all issues and problems with Total Warfare.
Product Link: https://store.catalystgamelabs.com/products/battletech-total-warfare-pdf
The current errata version is 11.0, and can be found here:
https://bg.battletech.com/errata/
There are eleven main print revisions of Total Warfare - be sure to cite which release you're working from:
2006 - first printing (FanPro)
2007 - second printing (Catalyst/Wizkids)
2011 - third printing (Catalyst/Topps)
2013 - fourth printing (Catalyst/Topps)
2018 - fifth printing (Catalyst/Topps; retro art cover; reprinted the next year with a 35th Anniversary symbol in the bottom corner but otherwise 100% identical)
2020 - sixth printing (Catalyst/Topps; retro art cover)
2021 - seventh printing (Catalyst/Topps; new Atlas art cover)
2021 - eighth printing (Catalyst/Topps; new Atlas art cover)
2021 - ninth printing (Catalyst/Topps; new Atlas art cover)
2022 - tenth printing (Catalyst/Topps; new Atlas art cover)
2023 - eleventh printing (Catalyst/Topps; new Atlas art cover) - pending
Please remember to follow the errata report template (http://bg.battletech.com/forums/index.php/topic,2412.msg171290.html#msg171290) when reporting issues. Thanks.
Developer-Level Errata
In case of any contradiction, developer-level errata takes precedence over the current errata document.
Forced Withdrawal, p. 258:
A unit making a forced withdrawal must move toward its home map edge as designated by a scenario.
Change to:
A unit making a forced withdrawal must move toward its home map edge as designated by a scenario (even a single hex of movement in that direction satisfies this requirement).
-
Here's the latest big update, intended for the new fourth printing of Total Warfare. The big changes this release are:
- lots of aero fixes and adjustments, including the elimination of hex 0909
- C3 requires LOS
- Stealth Armour and ECM adjustments
- Plasma weapons and conventional infantry finally resolved
- a whole bunch of physical attack clarifications
- even more infantry clarifications
-
Updated to 4.01. The only real rules changes are the correction of the C3 LOS example as pointed out in Errata Discussion, and a slight correction to p. 222's Fighting Off Swarm Attacks errata (damage is measured from how much jump MP the mech used, not how much it had). Thanks.
-
Your errata has errata. :D
Pg 10 of the errata pdf under the section labeled * Changing Levels Inside A Building (p. 169) the actual errata is a repeat of the quad kicking errata from the previous page.
-
Thanks for that catch. It's a phantom entry - something that was going to be inserted, before I realized it wasn't necessary. However, I forgot to delete what I'd started. New version upped that simply removes the useless entry (same version number since it's still issued today and nothing really changed).
-
PDF - Corrected Fourth Printing
P. 53 - Jumping, Section Heat:
Error:
The last sentence repeats itself: "Regardless of what type of jump jets are mounted, if a ’Mech only jumps 1 hex, it builds up 3 heat points for that jump. Even if a ’Mech only jumps 1 hex, it builds up 3 heat points for that jump."
Suggestion:
Delete last sentence.
-
pdf, fourth corrected printing
page 305
The Man-Portable Plasma Rifle has a damage type of "DE" listed. Per this (http://bg.battletech.com/forums/index.php/topic,5943.msg639943.html#msg639943) this post in the previous TW Errata thread, it should be "DE, H".
-
Thank you - I gather this somehow missed incorporation into the new printing. As such, a slight update of the errata will be made to remove this entry from the document, so that the errata matches the latest printing.
It's still an official change however - it will just be moved to this thread for incorporation into the next official errata release.
-
In the aerospace vs airborne non aerospace units section it says to use air to ground attacks, the very next page says only bombs may be used to attack airborne non aerospace units, then later an example has a unit striking a VTOL using an attack other than bombing.
-
You've really got to provide some page numbers and in general read the rules if I'm going to be able to take care of that, I'm afraid.
-
Page 242 changed the way Aerospace Fighters attacked airborne non Aerospace units to use air to ground attack rules.
Page 243 Tells us that airborne non Aerospace units can not be damaged by an air to ground attack, excepting bombs in certain circumstances.
Page 245 Has an example of a VTOL being struck by a Strafing run.
Essentially page 243 needs the first paragraph deleted.
-
PDF, Corrected Fourth Printing.
Page 302 "Pulse weapons, 143" (page 143 contains the entry for Targeting Computer which includes a paragraph on the use of pulse weapons with targeting computers)
Suggest changing to:
Page 302 "Pulse weapons, 113, 143" (page 113 contains the entry for Weapons And Equipment which describes the to-hit modifier rule for pulse weapons and page 143 is entry for Targeting Computer including a paragraph on the use of pulse weapons with targeting computers, together these entries provide the reader with rules required to use a pulse weapon)
-
PDF, corrected Fourth Printing.
Page 131 "Stealth Armor: Armor that inflicts range modifiers against attacking units does not confuse a C3 network. Armor that
inflicts range modifiers against attacking units does not confuse a C3 network."
Suggest deletion of the repeated sentence.
-
Howdy. Here's the latest revision of the Total Warfare errata. There's been a lot of old questions from the old and gone boards answered here. It's mostly little fixes, but the bigger changes this release are:
- Protomechs can move underwater
- added the infantry types from TechManual into the basic game rules
- changed how Flak works to clarify and close a loophole or two
- brought VTOLs in line with the rest of the vehicles in that rotor destruction just means the VTOL is destroyed, like any other vehicle losing a location
- charge damage and timing clarifications
Download link as always is in the first post. After a couple of weeks on the forums, if nothing terrible shows up we'll move it to the main webpage.
-
"Collisions," TW Errata v4.1 p. 2.
I think that this change should be added:
3) Under “Prohibited Terrain”, second sentence
"Group the resulting damage into 5-point groupings, then roll once for each grouping on the appropriate Hit Location Table (always use the Front/Rear column)."
Suggest changing to (it may be process as "Levels"):
"Group the resulting damage into 5-point groupings, then roll once for each grouping on the appropriate Hit Location Table (based on the attack direction: see p. 119). Treat the attack as if it came from the hex that the skidding unit crashed into."
Thanks!
p.s. I changed a wrong page number.
-
Okay, I've sent this to the main webpage. The current version (i.e. the final one, now on the website) is dated 19 May. For those of you who downloaded this when it first came out a few days ago, the following was added between then and now:
* Lift Hoists (p. 137)
Delete the last paragraph of the main entry (Lift hoists cannot be used to lift...) and after the “Combat” subsection insert the following new subsection:
Units Carrying Non-Infantry Units: Lift hoists cannot be used to lift another unit of any kind during combat. However, a unit can begin the scenario transporting another non-infantry unit (infantry units are carried as normal cargo). A transported unit is inactive and so cannot perform any action. Note that inactive units cannot be made active in regular Total Warfare play; see Readying for Deployment on p. 44 of Strategic Operations for details.
Units that are dropped do not risk destruction as cargo does, but instead suffer damage as if falling a number of levels equal to the distance between the transporting unit and the surface directly below it (minimum 1). Area of effect attacks damage both the carrying unit and its transported unit equally; any other attacks may strike either the carried unit or the transport. Roll a D6 after each such successful attack on the carrying unit: on a 1-3 the transported unit is hit instead, with the direction of attack determined as if the transported unit was facing the same direction as its carrier.
* Anti-Personnel Weapons (p. 218)
In between the first and second sentences insert the following:
The standard rules presume the mounting of a single Auto-Rifle as the unit’s anti-personnel weapon. At the players’ option, the damage, ranges and to-hit numbers of alternative anti-personnel weapon types may be used as per TechManual, p. 271.
* Scale (p. 238)
This ruling has changed from previous errata versions.
Under “Spheroid Units”
attacks by standard-scale weapons against capital-scale armor are totaled then divided by 10 and rounded down for each location
Change to:
attacks by standard-scale weapons against capital-scale armor and structure are totaled then divided by 10 and rounded normally
-
Ground Combat Vehicle Critical Hit Effects (p. 194)
Under “Crew Killed”, at the end of the third sentence append the following:
(VTOLs and WiGEs crash and are considered destroyed).
-
C3 Computer (p. 131)
After the third paragraph, before the TAG subsection, insert the following new paragraph:
While a unit may mount both a C3 Master and a C3 Slave, it may not use both at once. For units so equipped, at the start of game designate which C3 system is operational. A unit may only belong to a single network.
-
4th Printing PDF
Pg.5
The heading for the Painting Miniatures section in the second column says it starts on pg, 288. It actually starts on pg. 280.
-
4th printing pdf
Pg. 225
The section of dropping troops from aero units retains the references to Hex 0909 despite 0909-centric rules being removed throughout the book.
Suggestion:
Remove the following sentence:If the carrying units are flying on a low-altitude map, at the end of the aerospace unit’s movement, jump infantry are placed in hex 0909 of the ground mapsheet that corresponds to the low-altitude hex (if the infantry are prohibited from entering that hex they are destroyed), while infantry with VTOL MPs are placed in hex 0909 of the ground mapsheet that corresponds to the low-altitude hex at Elevation 10.
(The pdf already contains the post-0909 rules, so nothing needs to be added in.)
-
Anoter clarification related to this (http://bg.battletech.com/forums/errata/techmanual-9-january-2014-(v3-02)/msg1047320/#msg1047320) TM report.
p. 104, pertaining to ammunition expenditure. Add underlined words.
Infantry Weapons: Infantry units and vehicles mounting Conventional Infantry Weapons do not need to keep track of ammunition, with the exception of certain battle armor missile attacks (see Battle Armor Attacks, p. 217).
-
Given the age of my physical copy by now, this may have been fixed in the interim without me catching on, but I can't seem to find it in the errata proper: p. 139, under the Narc Missile Beacon's writeup:
"Indirect LRM fire: Once a Narc pod is attached to a target, all Narc-equipped missiles may be fired indirectly at a (sic!) target without a spotter; [...]"
Suggest replacing that second "a target" with "that target" to make clear that a single attached homing pod doesn't also allow indirect fire at any other potential target on the board.
-
Per this thread (http://bg.battletech.com/forums/total-warfare/%28answered%29-fuel-cell-movement-heat/), IndustrialMechs with fuel cell engines should be able to move without building up heat just as those with internal combustion engines do. However, neither my (admittedly old) physical copy nor the current errata text actually say so; page 158 only explicitly mentions ICE-powered machines. (As does, for that matter, page 160 when it discusses engine explosions from high heat. As written, those only affect 'Mechs with internal combustion engines and fuel cell-powered ones are immune; this may be as intended, but if not, fuel cell engines should be mentioned there as well.)
-
Total Warfare v4.2 errata has been released - Glorious 6th of June edition.
Major changes this time around are:
Lots of mechanized battle armor changes
Indirect fire and water changed
Flak updated
Protomech frenzy updated
Aerospace altitude changes for striking & dive bombing happen before attacks
-
Version: BT Total Warfare PDF Catalyst/Topps 4th Printing/Catalyst 3rd Printing 2006-2013 p. 40
BattleTech PDF version Corrected 4th Printing/Catalyst Game Labs 3rd Printing
Page 40 Defaulting Skills: Rather than defaulting to these skill ratings, players may use the
Experience Ratings and Skills rules on p. 272.
Page 272 in the PDF copy is an illustration titled 2005 Origins International Games Expo Diorama
The correct page number is 273.
-
BT Total Warfare PDF Catalyst/Topps 4th Printing/Catalyst 3rd Printing 2006-2013 versus Total Warfare Errata v4.2 06/06/15
Version: Total Warfare Errata v4.2 p. 4 and BattleTech Total Warfare PDF p. 199
From Total Warfare Errata v4.2 p. 4
② Damage (p. 199)
Second paragraph, fourth sentence
Because a WiGE vehicle flies above terrain, it does not benefit from woods modifiers for the hex it occupies while in flight.
Change to:
Since a WiGE vehicle operates one elevation above the ground, it remains below the level of a woods hex, and so gains the modifier from woods as would a VTOL at the same elevation. If a WiGE vehicle follows a road through a woods hex, it also gains this bonus by being in the hex.
On p. 199 of the BattleTech Total Warfare PDF the sentence to be changed is found here:
To-Hit Modifiers
Because a WiGE vehicle flies above terrain, it does not
benefit from woods modifiers for the hex it occupies while
in flight.
Suggested change to the errata entry change ② Damage (p. 199)
to ② To-Hit Modifiers (p. 199) first sentence.
-
BT Total Warfare PDF Catalyst/Topps 4th Printing/Catalyst 3rd Printing 2006-2013 p. 35 is different from Total Warfare Errata v4.2 p.8
Total Warfare Errata v4.2
Force Structure (p. 35)
Second paragraph, first sentence
“The smallest formation is a Level I, which comprises a BattleMech, fighter, tank or infantry squad.”
Change to:
“The smallest formation is a Level I, which comprises a BattleMech, fighter, tank or infantry platoon.”
BT Total Warfare Catalyst/Tops 2006-2013 4th Edition p. 35
"The smallest formation is a Level I, which comprises a single BattleMech, fighter, tank or infantry platoon."
The sentence in BT Total Warfare Catalyst/Tops 2006-2013 4th Edition includes the word "single" should the word be deleted or added to the errata?
-
Total Warfare Errata v4.2 06/06/2015 p. 11 versus BT Total Warfare PDF Catalyst/Topps 4th Printing/Catalyst 3rd Printing 2006-2013
Total Warfare Errata v4.2 06/06/2015 p. 11 indicates that the change for
Skidding [example text] (p. 65) third full paragraph, first sentence of
“At the end of the successful charge, the skidding unit is in Hex 2B (even though it would normally have skid for 1 more hex, because it unintentionally charged another unit, it ends its movement in that hex), while the target ’Mech is moved into Hex 3B.” is in the left column of the page.
BT Total Warfare PDF Catalyst/Topps 4th Printing/Catalyst 3rd Printing p. 65 has the sentence in the right column, third full paragraph
Recommend that the errata entry be changed to: "right column, third full paragraph".
-
Total Warfare Errata v4.2 06/06/2015 p. 14
Total Warfare Errata v4.2 06/06/2015 p. 14 indicates that the
Special Maneuvers Table (p. 85)
Under "VIFF"
“A VSTOL unit halts its forward momentum and gains one altitude."
Change to:
“Any VSTOL unit halts its forward momentum and gains one altitude."
In BT Total Warfare PDF Catalyst/Topps 4th Printing/Catalyst 3rd Printing 2006-2013 p. 85 the Special Maneuvers Table has five columns the errata indicates that the required change be made under "VIFF" which is in the first column.
However, the table shows the change to be “Any VSTOL unit halts its forward momentum and gains one altitude" is added to the fifth column with the header of "Effect".
The recommendation is to change p 14
b]Special Maneuvers Table (p. 85)[/b]
Under "VIFF"
to
b]Special Maneuvers Table (p. 85)[/b]
Under "VIFF", "Effect" column
-
Errata PDF (v4.2)
Page 47, in the Ground-To-Air Attacks example
There is a typo in the 7th numbered point:
"Because the closest point on the Shiva's flightline is equidistant to the ’Mech in Hex 2's front and left arm arcs, the player controlling the player may choose what arc applies."
As it's written, it's not clear which player decides the firing arc.
-
I have the first printing of TW and I don't know if paragraphs have been changed since then, but I have caught these two discrepancies:
----
Errata PDF (v4.2)
Page 36, "Damage (p.199)"
On the 1st printing (2006) TW book, there is not a "Damage" paragraph on page 199. The sentence to change is under "To-Hit Modifiers", first (and only) paragraph, first sentence.
-----
Errata PDF (v4.2)
Page 37, "Conventional Infantry Attacks (p.215)", 3rd point.
The sentence to change is not under "Burst-Fire Weapons", not even under "Conventional Infantry Attacks".
It's under "Attacks Against Conventional Infantry", second paragraph, last sentence, same page (215).
----
-
I have the first printing of TW and I don't know if paragraphs have been changed since then, but I have caught these two discrepancies:
Yes, the first one has been pointed out already, but p. 215 has a few inconsistencies there. Here is what it should look like:
① Conventional Infantry Attacks (p. 215)
1) Second paragraph (first on the page), at the end of the first sentence append the following:
(for a platoon with only one trooper remaining the result is always “1”).
2) Third paragraph (second on the page), last sentence
If the target is a conventional infantry platoon, the attacking player simply applies the damage.
Change to:
If the target is a conventional infantry platoon, the damage is instead simply applied all at once.
② Attacks Against Conventional Infantry (p. 215)
1) Second paragraph, last sentence
Successful non-infantry attacks against conventional mechanized infantry double the number of troopers eliminated in this fashion.
Change to:
Successful non-conventional infantry attacks against conventional mechanized infantry double the number of troopers eliminated in this fashion.
2) Under “Burst-Fire Weapons”, first paragraph
Delete the last sentence (“As with attacks from conventional infantry […]”)
-
Hello all,
Total Warfare Errata v4.2 06/06/15 p. 24 C3 Computer (p. 131)
I am puzzled by the errata regarding the requirements between item 3) Under "Stealth Armor", replacing the second sentence and then per item 4 deleting the last sentence.
C3 Computer (p. 131)
3) Under "Stealth Armor", replace the replace the second sentence with the following:
"Armor that inflicts range modifiers against attacking units does not confuse a C3 network. Only apply the additional range modifiers based on the range between the target and the nearest unit in the network; do not apply modifiers based on the range between the target and the attacking unit in the network. The only modifiers to consider between the attacking unit and the target are Minimum Range modifiers.
The PDF copy of Total Warfare copyright 2006-2013 Topps Company, Inc. 4th Printing/3rd Printing by Catalyst Game Labs the Stealth Armor entry on p. 131 appears to be have been corrected in accordance with item 3) instructions.
C3 Computer Errata item 4) Under "Stealth Armor" deletes the last sentence, which I think changes the section to read:
Stealth Armor: Armor that inflicts range modifiers against attacking units does not confuse a C3 network. Armor that inflicts range modifiers against attacking units does not confuse a C3 network. Only apply the additional range modifiers based on the range between the target and the nearest unit in the network; do not apply modifiers based on the range between the target and the attacking unit in the
network.
Am I following the instructions correctly?
I would like to recommend, if the instructions are correct changing item 3) to read
Under "Stealth Armor", replace the replace the second sentence with the following:
"Armor that inflicts range modifiers against attacking units does not confuse a C3 network. Only apply the additional range modifiers based on the range between the target and the nearest unit in the network; do not apply modifiers based on the range between the target and the attacking unit in the network. The only modifiers to consider between the attacking unit and the target are Minimum Range modifiers.
[/quote]
and delete item 4).
-
Total Warfare Errata 06/06/15 (v4.2) pp. 33-34 of 53
Has the following instructions:
Falling Unit Hits Target (p. 152)
1) ① Under “Airborne Units”, delete the second paragraph.
2) ② Under “Airborne Units”, second paragraph, last sentence
Resolve the damage to the airborne unit using the VTOL Rotor Destruction rules, p. 197.
Change to:
Resolve the crash using the VTOL and WiGE Vehicle Crashes rules, page 68.
From TW (PDF) (C) 206-2013 The Topps Company, Inc., Corrected 4th Printing/3rd Printing by Catalyst Games Labs p. 152
Airborne Units: If the to-hit roll is successful striking airborne
unit, and another airborne unit occupies the same hex at a lower
elevation, or if a ground unit also occupies the hex, the controlling
player of the falling unit must still make the standard to-hit
roll, potentially causing further damage to those additional
targets and itself.
If a falling unit strikes an airborne VTOL or WiGE, and the airborne
vehicle takes damage that causes it to crash, it automatically
crashes in the same hex. Resolve the damage to the airborne
unit using the VTOL Rotor Destruction rules, p. 197.
In the TW Errata v4.2 the first entry deletes the enter second paragraph and then the second entry modifies the last sentence of the deleted second paragraph. This does not make sense to me and a recommendation would be as follows:
Falling Unit Hits Target (p. 152)
1) ① Under “Airborne Units”, delete the second paragraph.
Change to:
1) ① Under “Airborne Units”, delete the second paragraph's first sentence.
2) ② Under “Airborne Units”, second paragraph
Resolve the damage to the airborne unit using the VTOL Rotor Destruction rules, p. 197.
Change to:
Resolve the crash using the VTOL and WiGE Vehicle Crashes rules, page 68.
-
The mistake is the second entry, not the first. There's no need to track crashed units in TW, as in TW a unit that is destroyed is simply destroyed. Thus, the subsequent correction, while accurate, is redundant.
Thanks for the catch.
-
Hello Xotl,
Actually my report has a bit of an issue with the page numbers here is the new recommendation with the new information :
On Total Warfare v4.2 06/06/15 pp. 31-32 delete
2) ② Under “Airborne Units”, second paragraph, last sentence
Resolve the damage to the airborne unit using the VTOL Rotor Destruction rules, p. 197.
Change to:
Resolve the crash using the VTOL and WiGE Vehicle Crashes rules, page 68.
the errata entry is now:
Falling Unit Hits Target (p. 152)
1) ① Under “Airborne Units”, delete the second paragraph.
-
Facing Changes (p. 84)
Fourth printing only. Second paragraph
Delete the second sentence (“When moving on the ground map, …”).
-
Hello all,
While looking through the Total Warfare PDF 2013 - fourth printing (Catalyst/Topps) Table of Contents p. 2 Introduction has the following items
Other Avenues 12
Iron Wind Metals 12
Catalyst Demo Teams 12
Classicbattletech.com 12
Battlecorps 12
HeavyMetal Software 13
Camo Specs Online 13
Fighting Pirannha Graphics 13
Virtual World Entertainment 13
Armorcast 13
WizKids 13
HeavyMetal Software is listed on p.2 but is not found on p. 13 as indicated.
Possible recommendation for errata:
Introduction
Other Avenues p. 13
Insert between BattleCorps and Camo Specs Online
HeavyMetal Software
This is the official website for BattleTech, where players can purchase software to customize existing Mechs, combat vehicles, aerospace and other units or created their own designs to fight on the BattleTech battlefield. For more information see: http://www.heavymetalpro.com/index.html
-
And the year's release is out. A nice small one, there are no major gameplay changes.
-
Corrected Third Printing, dead tree format with v4.3 errata
Problem 1: The third paragraph under Air-to-air attacks on p.241 states that an aircraft flying at Altitude 1 (NOE) suffer a +2 to-hit modifier when making attack against air targets. On top of p. 242 we find an exception to this rule stating that OmniFighters suffer only +1 to-hit modifier in this situation, but none of these modifiers appear in Aerospace Attack Modifiers Table.
Suggestion: Add the following lines to the Aerospace Attack Modifiers Table on p. 237 and p. 312 under Attacker Conditions.
Attacker is an Omnifighter flying at altitude 1 (NOE) attacking an air target +1
Attacker is non-OmniFighter flying at altitude 1 (NOE) attacking an air target +2
Problem 2: In the Rolling section (pp. 77-78 TW) the paragraph "Atmospheric Flight: A unit may not roll in atmosphere, but may execute a half-roll special maneuver (see Special Maneuvers, p. 84)" seems slightly incorrect and misleading in it's context. Special Manouveres are defined in such a way, that they have no sense in the space maps even in Atmospheric Rows.
Suggestion: Replace the paragraph with "Low-altitude Flight: A unit may not roll during Low-Altitude Movement, but may execute a half-roll special maneuver (see Special Maneuvers, p. 84)". If rules for reversing left and right sides during High-Altitude Movement are different than in space, add them here.
-
Corrected Third Printing, print edition with v4.3 errata
p. 114 X: Explosive Weapon
Change "see Gauss rifle p. 135" to "see Anti-Battle Armor Pods (B-Pods) p. 130 and Gauss Rifle p. 135".
Note capital "R" in Gauss Rifle.
-
Corrected Third Printing, print edition with v4.3 errata
p. 89 - add "Carrying Units" section (subsection?) title on top of the page.
-
New errata is up, a day early because I have to run. No time to review the changes, but there are more of them this year, as the creation of the BattleMech Manual meant that the mech rules were given a top to bottom going-over.
-
Damage (p. 148)
④ Physical Weapon Attacks Table (p. 148)
Under “Damage Value”, apply the dagger footnote symbol to the Chainsaw and Dual Saw.
The Physical Weapon Attacks Table is on p. 146
Recommend new errata entry:
Physical Weapon Attacks Table (p. 148)
Under “Damage Value”, apply the dagger footnote symbol to the Chainsaw and Dual Saw.
Change to:
Physical Weapon Attacks Table (p. 146)
-
Total Warfare PDF 2006-2013 The Topps Company, Inc. Corrected Fourth Printing. Third Printing by Catalyst Game Labs.
Addtional Clan Weapons and Equipment For Battle Armor p. 305
The single * (asterisk/star) note of *See the Weapon and Equipment Types Table, p. 306, for abbreviation explanations, or Weapons and Equipment, p. 113, for complete details.
There is no Weapon and Equipment Types Table, p. 306 the table is on p. 304.
Footnotes
"*See the Weapon and Equipment Types Table, p. 306, for abbreviation explanations, or Weapons and Equipment, p. 113, for complete details."
Change to:
"*See the Weapon and Equipment Types Table, p. 304, for abbreviation explanations, or Weapons and Equipment, p. 113, for complete
-
P. 142, Nemesis Pod, second sentence
Change "[...]may instead hit the Nemesis-tagged unit, if it is along the LOS between the attacker and the target[...]" to something like "[...]may instead hit the Nemesis-tagged unit, if it is in a hex lying along the LOS between the attacker and the target[...]", as there is no concept of LOS going thru units in Battletech - only thru hexes.
Change or add a clarification to "[...]and a LOS exists between the attacker and the target[...]" to indicate that it is possible to redirect indirect fire even to a unit the attacker has no LOS to (using the rules for indirect LRM fire against Narc-ed targets with no spotter found on p. 139).
See http://bg.battletech.com/forums/index.php?topic=59531.0 for details.
P. 150, Second paragraph under Falls
Problem: In http://bg.battletech.com/forums/index.php?topic=55599.0 it has been determined, that a 'Mech that falls due to an unsuccessful DFA attack takes damage to it's back, but still rolls in Facing After Fall Table to determine it's final facing (see answers to questions 2 and 3 in the thread linked above), however the rules still don't reflect it.
Suggestion: Change the paragraph to something like "On an unsuccessful attack, the attacker automatically falls taking damage as though the 'Mech had fallen 2 levels onto its back, regardless of the facing rolled in the Facing After Fall Table (see Falling, p. 68)".
-
Version 5.0 is out, containing the errata that will appear in the upcoming fifth printing of TW. If you don't have the fourth printing of TW, you should keep your old TW errata document, as this new document just lists every correction that is being made from the fourth to the fifth printing ONLY.
There's nothing really major in this release: mostly clarifications due to the continued streamlining resulting from the release of the BattleMech Manual.
-
Corrected Third Printing, dead tree format with v. 4.4 and 5.0 errata
A small note regarding comparison of the 5.0 TW errata compared to 1.3 BMM errata. The BMM errata under ③ Indirect Fire (p. 31) clarifies, that if a unit is TAG-ed (and thus counts as spotted for LRM fire), and then the spotter fires during Weapons Fire Phase later this turn, then neither the spotter not the unit firing indirectly at the TAG-ed target suffer +1 to hit modifier listed under the final bullet point on p. 30 BMM. The same modifiers are listed i the paragraph directly under the bullet point list on p.111 TW, but no such clarification is made in the TW errata.
Recommendation - add the following sentence between the first and the second sentence of the last paragraph before the example text on p.111 TW: "Neither of those modifiers apply if the spotter successfully designated the spotted unit with a TAG this turn (see p. 142)." or something to that effect.
-------------------------------
By Xotl's request from the errata discussion thread I'm reposting my errata report that did not end up in latest errata document. Note, that some of it is from before the previous errata document (v. 4.4) was published, and could be already rejected by the errata maintainers or simply not included in the document, but still added to new printing, because they were minor editing errors. Since I only own the physical copy of the book, I have no way of checking which. I've marked here all of those pre v. 4.4 reports with a "*".
* Pp. 77-78 Rolling
Problem: In the paragraph "Atmospheric Flight: A unit may not roll in atmosphere, but may execute a half-roll special maneuver (see Special Maneuvers, p. 84)" seems slightly incorrect and misleading in it's context. Special Manouveres are defined in such a way, that they have no sense in the space maps even in Atmospheric Rows.
Suggestion: Replace the paragraph with "Low-altitude Flight: A unit may not roll during Low-Altitude Movement, but may execute a half-roll special maneuver (see Special Maneuvers, p. 84)". If rules for reversing left and right sides during High-Altitude Movement are different than in space, add them here.
* P. 89 - add "Carrying Units" section (subsection?) title on top of the page.
* P. 114 X: Explosive Weapon
Change "see Gauss rifle p. 135" to "see Anti-Battle Armor Pods (B-Pods) p. 130 and Gauss Rifle p. 135". Note capital "R" in Gauss Rifle.
P. 142, Nemesis Pod, second sentence
Change "[...]may instead hit the Nemesis-tagged unit, if it is along the LOS between the attacker and the target[...]" to something like "[...]may instead hit the Nemesis-tagged unit, if it is in a hex lying along the LOS between the attacker and the target[...]", as there is no concept of LOS going thru units in Battletech - only thru hexes.
Change or add a clarification to "[...]and a LOS exists between the attacker and the target[...]" to indicate that it is possible to redirect indirect fire even to a unit the attacker has no LOS to (using the rules for indirect LRM fire against Narc-ed targets with no spotter found on p. 139).
See http://bg.battletech.com/forums/index.php?topic=59531.0 for details.
-
Crossposting from elsewhere. I did a little bit more research to make sure I had all the references before posting.
TW, Third printing, with collected errata:
The Fire-Resistant armor entry on pg. 228 of TW reads:
"Attacks from Heat-causing Weapons (see Weapons and Equipment, p. 113) against a unit equipped with fire resistant armor do not inflict any damage."
This directly contradicts the Plasma Rifle entry on pg. 139:
"Battle armor units that mount fire-resistance [sic] armor are immune to damage from the heat of a plasma weapon. The armor also reduces any standard Damage Value by half, rounded down"
TW, Pg. 139 is the only printed reference to halving plasma weapon damage: TacOps (Corrected second printing, pg. 109) states that the full normal damage gets through, and only the bonus heat damage is ignored. This is, however, referencing only Man-Portable Plasma Rifles in the context of an optional rule.
Also, "Fire-resistance armor" is used instead of "Fire-resistant armor" in the surrounding text of TW,pg. 139 (Plasma weapons) and pg. 141 (Infernos: infantry) of Total Warfare.
-
A new errata release, sort of (hence the tiny version number increase). This release just adds anything that I missed adding to the changelog when I released v 5.0. It still only lists items that are slated to appear in the upcoming TW reprint (the 5th printing). As such, any new reports made above have not been noted here: they'll appear in next year's errata as v5.1.
These releases are not marked PRE because they've effectively been out for six months already, so I've already upped them to the main website's Errata section.
-
Version: 2018 5th printing release.
Location: p. 281
Error: Start of painting essay refers several times to the Volwinkel cover which is not on their book, confusing readers.
Correction: reference should be removed or edited to reflect that the art is on an older book.
Note: 2nd paragraph p. 280 makes a similar reference to the art, but it’s oblique enough to be less problematic.
-
Errata v. 5.01
The description of inferno critical hits on vehicles is incorrect.
Page 142Every missile that strikes the target automatically
causes a roll on the appropriate column of the appropriate unit’s
Critical Hits Table, corresponding to the location hit (see Ground
Combat Vehicle Critical Hit Eff ects, p. 193), with the following
modifi ers to the dice roll result: –2 for Combat Vehicles; no
modifi er for Support Vehicles (unless the Support Vehicle has
the Armor Chassis and Controls modifi cation and a BAR of 10, in
which case it is treated as a Combat Vehicle).
Error 1: The vehicle critical hit table being referenced is on page 194, not 193.
Error 2: The reference to Combat Vehicles getting a -2 means that they could never have their ammunition or fuel tank hit. As per page 194, ammunition or fuel tanks can only be hit on an 11 or 12, respectively. The -2 would make this roll impossible. There are three references to Ammunition or Fuel Tank critical hits for Combat Vehicles in this section, so I assume that Combat Vehicles were intended to be in danger of suffering these effects.
Suggestion: Make the Combat Vehicle get a +0 and Support Vehicles with a BAR of 9 or less suffer a +2 penalty, with a 14 or 13 resulting in the same effects of a roll of 12.
Xotl: This modifier only applies to inferno missiles. Regular critical hits are simply rolled normally, with all the instakill chances therein. Even with infernos, though, results that have already been triggered result in a shift down the chart towards result 12. While it may not be possible to one-shot a vehicle with a single inferno SRM, a full-barrage could easily eliminate a vehicle if enough hits are accumulated in the same location at the bottom of the table.
-
New errata for the year is up; link in the first post. As we've pretty much stabilized the base ruleset (and I continue to be too busy to do much deep diving), there's not much: just three new entries.
-
Upped the final version to the main page. Added one small new piece (a correction to the DFA example, which had the attacker levels wrong). Sorry it took so long.
-
Version: The newest (Corrected Fifth Printing. Fourth Printing by Catalyst Game Labs.) Edition of Total Warfare has this on page 131.
Error:
"While a unit may mount both a C3 Master and a C3 Slave, it
may not use both at once. For units so equipped, at the start
of game designate which C3 system is operational.
While a unit may mount both a C3 Master and a C3 Slave, it
may not use both at once. For units so equipped, at the start
of game designate which C3 system is operational. A unit may
only belong to a single network."
Correction: Recommend removing the 1st paragraph in later printings.
-
Errata for the upcoming sixth printing is up. I left the changes from the previous errata version in the New Arrivals section because it was only two items, and I wanted to be able to show everything that's changing between the fifth and sixth printings in one place. Thanks.
-
New errata for the year is out: v6.1 is linked in the first post. It will be made official in a week or two if no one finds any issues.
-
The page 175 correction still doesn't clearly address whether 'mechs can attack units in the same hex, which they can't normally. What about being in a building enables them to shoot infantry or vehicles they otherwise couldn't? ???
Xotl: That's already covered in that section:
"Unlike standard combat, units in the same building hex (and even at the same level in the same hex) can attack one another."
-
Corrected Fifth Printing.
Page 141, the description of NARC Homing Pod ammunition: Technology Base reads as Inner Sphere only, should instead say Clan or Inner Sphere.
-
Errata updated to final and uploaded to the main website. As it took a while to get to, new additions were made (all listed in "New Additions"), so delete any PRE version.
-
Total Warfare errata document 6.1
Error:Text Duplication
The proposed errata:
Damage [example text] (p. 207)
Replace the fifth paragraph with the following:
“If, on the other hand, the Support Vehicle were struck by an AC/5 using armor-piercing rounds, it would be forced to
make a critical hit check regardless of its BAR (see Armor-Piercing Ammunition, p. 206). If it had a BAR of less than 10, the
vehicle would add a +2 modifier to this check.
Duplicates the text already found in the fourth paragraph of the corrected 6th printing of Total Warfare:
A tracked Support Vehicle with an Armored Chassis
modification and a BAR of 7, with 12 armor points per side,
takes a hit from a large laser to its front side (Hit Location
Roll result of 7). Because the laser’s 8 points of damage
exceeds the Support Vehicle’s BAR, a penetrating critical
hit has occurred, even though 4 points of armor remain in
the front.
Because the Support Vehicle has an Armored Chassis
modification, however, the roll for the penetrating critical
is modified by –1. When the attacker rolls for the critical,
his result of 6 becomes a 5, narrowly saving the unit from
a possible critical hit.
In a later turn, the same Support Vehicle takes a second
large laser hit to its front, in this case from a Hit Location
Roll result of 2. The laser causes a penetrating critical hit, has
breached the armor, and has struck a location that gives the
attacker an additional possible critical hit. The attacker rolls
three times for critical hit effects, modifying only the first
roll—the one for penetrating critical hits—by –1.
If, on the other hand, the Support Vehicle were struck by
an AC/5 using armor-piercing rounds, it would be forced to
make a critical hit check regardless of its BAR (see ArmorPiercing Ammunition, p. 206). If it had a BAR of less than 10,
the vehicle would add a +2 modifier to this check.
If, on the other hand, the Support Vehicle were struck by
an AC/5 using armor-piercing rounds, the vehicle would be
treated as if it had a BAR of 4 (7 / 2 = 3.5, rounding up to
4) rather than 7 for purposes of determining penetrating
critical hits. Both hits might do critical damage because the
autocannon’s damage points exceed the unit’s effective BAR,
even though together the two autocannon hits would only
eliminate 10 of the Support Vehicle’s 12 armor points
Fix:
Replace the 5th paragraph with a different example or eliminate it entirely.
-
All comments and page numbers are for the PDF corrected 6th printing, except page numbers noted for the errata document itself. Some errors are according to the fact that "Entries new to v6.1 are marked with a (1), and can also be found in the New Additions section. All entries not so marked were corrected in the sixth printing." - any such unmarked entries not actually corrected in the PDF corrected 6th printing are noted.
The below notes have been cross-checked against the new 7th corrected printing and v7.0 errata document. Any that were corrected have been removed.
Grammar error:
Page 21, under Protomechs, first paragraph, second sentence currently reads "The pilot rides in a small compartment in the upper chest of the the torso contains the engine, weapons and motive systems." Not sure what the correct sentence(s) should be, but this is clearly incorrect.
Inconsistency:
Total Warfare Errata v7.0, page 3 notes that under Movement Direction, p. 49, under "Backward Movement", third paragraph "VTOL/WiGE Vehicles and submarines," should be changed to "VTOL Vehicles,". The actual text in the PDF corrected 7th printing is "VTOL Vehicles and submarines," so presumably one of these is incorrect - possibly it is the errata document, as the sentence also mentions units expending UMU MP.
Error:
Total Warfare Errata v7.0, page 4 notes that under Jumping, p. 53, under "Water", at the end of the entry a new paragraph should be inserted, but this paragraph is missing.
Change not recorded in errata?
Total Warfare, page 81, under Crashes, after the first sentence, the sentence "If the unit was Out of Control when the crash happened and is a DropShip or larger craft, it is destroyed." seems to have been inserted without being noted in the Errata document. This could be added to the immediately following addition in the same section, "If the unit had no velocity when it crashed, use a value of 2 for the velocity when calculating damage.", which is noted in the Errata document.
Possible issue:
A question involving contradictory rules on whether aerodyne DropShips and small craft can make vertical landings in atmosphere has been removed and posted in the rules question forum instead. Once a ruling has been determined, this will require further errata regardless of the overall ruling, but the nature of the changes will vary depending on the ruling.
Possible issue:
A question involving aerospace unit facing changes on the low-altitude map or ground map has been posted in the rules question forum. This question may end up requiring errata once answered, but that will have to wait until a ruling has been determined.
Error:
Total Warfare Errata v7.0, page 10 notes that under Failed Braking Maneuver Table, p. 87, third effect, second sentence, "the landing gear is destroyed" should be changed to "the landing gear is damaged". In the PDF corrected 7th printing, this text has not been changed as specified.
Error:
Total Warfare Errata v7.0, page 10 notes that under Liftoff, p. 88, second paragraph, second sentence, "A unit cannot lift off if it has a Safe Thrust of 2 or less." should be changed to "A unit must spend 2 Thrust Points to lift off." However, in the PDF corrected 7th printing, this sentence appears to be simply missing, rather than altered as specified.
Error:
Total Warfare Errata v7.0, page 13 notes that under Ammunition Expenditure, p. 104, "Infantry" paragraph, the text should be changed to "Infantry units and vehicles mounting Conventional Infantry Weapons do not need to keep track of ammunition, with the exception of certain battle armor missile attacks (see Battle Armor Attacks, p. 217)." In the PDF corrected 7th printing, this text has not been changed as specified (only infantry units are mentioned, not vehicles).
Error:
Total Warfare Errata v7.0, page 13 notes that under Non-Aerospace Units Attacking Airborne Aerospace Units, p. 107, the entry should be replaced with a new version. This has been implemented in the PDF corrected 7th printing (now located on p. 109 of said PDF due to the rearrangement of the Firing Weapons section), but it contains an error - the final sentence reads "If the attacking unit lies within the airborne aerospace unit’s flightpath, the base range to the target is considered to be 1 hex, plus 2 hexes for each altitude level the aerospace unit is operating at." The italicized text is incorrect and should be removed, although the v7.0 errata document is correct.
Possible error:
Total Warfare Errata v7.0, page 24 notes that under Infernos, p. 141, under "Infantry", the sentence "In neither case is this modified by terrain or infantry type." should be inserted after the first sentence. In the PDF corrected 7th printing, this paragraph has been rearranged, and the sentence has actually been inserted twice - once after the first sentence of the new, rearranged paragraph, and once at the end of the paragraph, which I assume is the correct location (as it places it with the text it was aligned with when applying the errata to the first printing). The first instance of this sentence in the paragraph should be deleted, unless this was intentional.
Inconsistency:
On Total Warfare Errata v7.0, page 31, the note on changes to the Infantry Damage From Attacks Inside Buildings Table, p. 175 does not seem to match the text in the corrected 7th printing. Presumably one of these is incorrect, although the version in the PDF corrected 7th printing seems reasonable, so I suspect the errata document is incorrect.
Error:
Total Warfare Errata v7.0, page 33 notes several changes to text under Frenzy, p. 187. However, out of 3 changes noted, only the 2nd change appears to have been implemented, and the 3rd change as noted in the errata document does not seem fully correct in any case (the text in the PDF corrected 7th printing seems more reasonable).
Error:
Total Warfare Errata v7.0, page 42 notes several changes to text under Dismounting, p. 225. However, the second change involves the "MP Reduction" section, which appears to have simply been removed rather than altered as specified in the PDF corrected 7th printing.
Inconsistency:
Total Warfare Errata v7.0, page 50 notes several changes to text under Hidden Units, p. 259. The text described in the errata document differs fairly significantly from the text actually present in the PDF corrected 7th printing; presumably one of these is incorrect, although it is plausibly the errata document.
Error:
The VTOL Combat Vehicle Critical Hits Table (p. 309) still contains an instance of "Weapon Jam" that should be changed to "Weapon Malfunction" (Rear column, result on a 7).
Error:
The Building Movement Modifier Table (p. 310) is completely missing its headers.
Error:
The Air-To-Ground Attack Modifier Table (p. 312) appears to have had extraneous text ("an additional 8 hexes directly forward.") introduced into its second footnote.
Error:
The Landing Modifiers Table (p. 312), first subtable, fourth line has not been changed to "+1 per point of Velocity above 2" as specified in the errata (p53).
-
TW 6th Printing, PDF version
CREDITS and INTRODUCTION
p. 6, Credits still list Brent Evans as BT Line Developer - replace with current BTLD
pp. 8-13, Introduction, most of the links are wrong or lead to dead/wrong sites:
pp. 8, 11, 13
battlecorps. com - should be replaced with and link to store.catalystgamelabs.com
pp. 9, 10, 13
bg.battletech.com - dead link: links to classicbattletech.com, site does not exist anymore
p. 11
CatalystGameLabs.com - 2x, one is a not clickable link, the other one links to fanprogames.com, again this site doesn't exist anymore
p. 13
www.catalystdemos.com - links to commandohq.com, both links don't work
p. 13
mechjock.com links to fightingpirannhagraphics.com
INFANTRY
p. 226
since dismounting infantry does not cost any MP anymore, remove the Infantry Dismounting Table
Xotl: The introduction has been heavily rewritten in the seventh printing to deal with stuff like the above.
-
Corrected Sixth Printing (Fifth Printing by CGL), pdf version (with an exception explained in point 4.)
1. No clear page number, since the problem is a rule missing from TW.
Problem: As far as I can tell unlike BMM (p. 18) and AGoAC rulebook (p. 11) TW doesn't have any rules which say that an abandoned 'Mech or a 'Mech that lost all four of its limbs (except for Quads, for which the issue is covered on p. 122 TW under "Four destroyed legs" bullet point) are considered Immobile. The case of abandoned 'Mechs is not a problem, since an abandoned unit is pretty much destroyed as far as TW is concerned, but the biped 'Mechs that lost all of their limbs is.
Recommendation: State explicitly somewhere in TW, that any 'Mech tat lost all of its limbs is considered Immobile. A good places to put this rule seems to be in or next to the Leg Destruction section on p. 122 and/or in or next to Firing at Immobile Targets section on p. 110, which seems like a natural place for a full list of conditions under which any kinds of targets (including units, hexes and buildings) covered in TW are considered immobile.
2. p. 227, Falling and Dropping Prone
[...] follow the same rules found under Falling/Dropping Prone, p. 222, in the Swarm Attacks section.
maybe change to:
[...] follow the same rules found under Falling/Dropping Prone, p. 224.
(The change should make finding relevant rules faster, since the reader doesn't need the entire Swarm Attacks section here, just the Falling/Dropping Prone subsection which is on p. 224.)
3. pp. 167-179, 185-187, 213-229, 301, right margins of odd-numbered pages only.
A number of similar minor formatting issues - the Ground Movement title is printed incorrectly - too far to the right on pp. 167-179, 185-187, too far up on pp. 213-229, with too dark lines around the letters on p. 301. I can also confirm that is is not just some software problem with the pdf file or the program I'm using to display pdf-s since the issue is also present in the Third and Fifth Printings of the physical book.
4. An issue with the errata document (version 6.1).
While researching a problem with HAG rules for BMM I've noticed a disparity between my sixth edition PDF and my third edition physical book that requires a change to the following entry in the errata document:
Hyper-Assault Gauss Rifle (p. 136)
[...]
2) After the “Flak” header in the second column, add the following new paragraph:
Targeting Computer: This weapon can use a targeting computer when making attacks, except when using the Flak weapon effect or for aimed shots (see Targeting Computer, p. 143).
The entry needs to be labeled "This ruling has changed from previous errata versions.", because p. 136 of the third printing of the book contains a paragraph about interaction between Hyper-Assault Gauss Rifles and Targeting Computers, which says that you can't use TCs while making aimed shots with HAGs, but doesn't mention anything about Flak attacks.
5. p. 263, Mapsheet Tables
Problem: The list of products in which the maps listed in the Mapsheet Tables can be found are badly outdated (it goes from Map Set 1 to HexPack: Cities and Roads).
Recommendation: Add additional product codes for the maps re-published (or about to be re-published) in HexPack: Mountains and Canyons and products afterwards. Consider adding new maps to the tables. For example maybe some of the more TW-friendly maps from the Battle of Tukayyid and/or Alien Worlds MapPacks could get their own table(s)?
Edit by Alfaryn on 18th of December 2020: I've removed a point in this post that I realized was erroneous and added a couple new ones. Sorry if I'd confused anyone who read this post before the edit.
Edit by Alfaryn on 28th of January 2021: added items number 4 and 5 to the list.
-
Corrected fifth printing, pdf
Page 113, Pulse Weapons
--Recommend changing the passage's text to that of the BattleMech Manual (getting rid of references to a -2 to-hit modifier, as certain "P" weapons give -1 or -3 to-hit modifiers instead.)
-
Corrected Sixth Printing. Fifth Printing by Catalyst Game Labs, pdf
pp. 266-269
Problem: Random 'Mech Assignment Tables direct readers to TROs that have been long out of print. At the same time a lot of these 'Mechs were featured in newer TROs (Succession Wars, Clan Invasion, etc.)
Recommendation: Add the relevant new TROs to the list of Technical Readouts in the fifth paragraph of the Assigning 'Mechs section on p. 266 and annotations pointing to these TROs next to to appropriate 'Mechs in tables on pp. 267-269.
Xotl: This is being corrected for the upcoming seventh printing.
-
Corrected Sixth Printing. Fifth Printing by Catalyst Game Labs, pdf
Pp. 60 and 306, Piloting Skill Roll Table, footnote 7.
Add an additional +1 modifier if unit is charging or being charged (in addition to the +2 modifier normally required in that situation).
change to:
Add an additional +1 modifier if unit is charging or being (in addition to the +2 modifier normally required in that situation).
You may also consider adding an information that a unit displaced into a building hex automatically fails the PSR to avoid damage because of it. Best place to put it would be either in footnote 7, or in Building Movement the table itself.
Years ago TW displacement rules (p. 151 TW) have been changed in such a way, that a unit displaced into a building (including as a result of a charge) takes damage as if it voluntarily moved into it and failed its Piloting/Driving Skill Roll to avoid it. BMM displacement rules (p. 55 BMM) say the same.
-
The 7th printing errata is now live on the website, matching the new PDF release out today.
Some of the last few posts above were not corrected, as there was the usual lengthy lead time between finalizing the errata and new printing and it actually arriving. They will be noted for a possible 8th printing.
-
Updated my big post above for the v7.0 errata / 7th corrected printing.
-
Corrected Seventh Printing. Sixth Printing by Catalyst Game Labs, pdf
P. 51, Movement Dice box
PROBLEM: The box mentions Sprinting rules without mentioning that they are not found in TW, which may be confusing to players who haven't read TO/TO:AR or at least BMM.
RECOMMENDATION :
(if using the optional Sprinting rules,
change to:
(if using the optional Sprinting rules found in Tactical Operations: Advanced Rules rulebook,
P. 109, Minimum Range Modifier (GATOR) section title
PROBLEM: Minor formatting issue. Unlike all other highlighted letters in the "GATOR" acronyms in section titles on pp. 106-109, the "R" in this section title is black, not blue.
SOLUTION: Change color of the 'R' letter in the section title to blue matching the 'R' in "Range Modifier (GATOR)" section title on the same page.
-
7th Printing pdf, Pg 9:
Problem: "Or players can use Alpha Strike, the fast-playing rules designed for the modern wargammer".
Solution: obliterate superfluous M
-
So, even though we just got a 7th printing, today we sent off files for the 8th printing. It's still some months away (because of printing and shipping times), but errata has to be finalized well in advance so here it is.
Special thanks to Alfaryn and ArcFurnace for their in-depth checks, including of the errata docs, which allowed it to be better matched with the actual book.
This errata is pre-release, but only in terms of making sure there's no errors with the document: the book has already been finalized, so any further book changes will be earmarked for a hypothetical 9th printing. If it's solid, I'll put it up on the website after a month for the traditional 6th of June release (so if you want to know what changed between the 6th and 7th printings, keep the old document, as that info is no longer in the current doc).
Please no longer edit older posts in the thread. Thanks all.
-
Oops, I've just noticed an error in my report from 25 March 2021 above.
It should have read:
[...]
Pp. 60 and 306, Piloting Skill Roll Table, footnote 7.
Add an additional +1 modifier if unit is charging or being charged (in addition to the +2 modifier normally required in that situation).
change to:
Add an additional +1 modifier if unit is charging (in addition to the +2 modifier normally required in that situation).
[...]
In other words the entire phrase "or being charged", not just the word "charged" is supposed to be deleted.
-
Yeah, I didn't get that one and since it had no context I had to ignore it because I had no time: this reprint was a rush job.
-
The pre-release document has been updated with a few missed fixes from back in the day. More importantly, it's been fully annotated to state which printing saw which correction, back to the 1st printing.
-
Pg. 263 7th Printing PDF.
Table 2: Hills Terrain - Rolling Hills #2 is listed as being available in the Clan Invasion box set, however the Clan Invasion box set Rolling Hills #2 map is different from the Rolling Hills #2 found in the Grasslands Map Pack. This is likely a misprint on the map from the Clan Invasion map.
Solution - Remove CI from Rolling Hills #2.
Table 6: Wooded Terrain - Same error as above, with same solution.
Table 2: Hills Terrain - There is currently no map sheet named Hilltops #2.
Solution - Rolling Hills #2 from Clan Invasion should be renamed Hilltops #2. See Errata Thread for Clan Invasion.
-
Corrected Seventh Printing, pdf
p. 119, Attack Direction section
If the straightedge crosses at the intersection of two hexsides, the target chooses which side is hit by the attack before the attacking player makes the hit location roll.
change to something like:
If the straightedge crosses at the intersection of two hexsides, the side hit by all attacks from the firing unit depends on the path chosen while determining LOS during the first attack declaration between the target and the attacker during current phase (see Line of Sight section, p. 99).
-
TW, 7th printing, 2021, p. 129f
Page 129, section "ANTI-MISSILE SYSTEM", first sentence states:
Any time a successful to-hit attack is made with a Missile Weapon (see p. 113) against a unit carrying an AMS, and strikes in the attack direction covered by the firing arc where the AMS is mounted, the defending player can choose to engage the AMS.
Page 130, first sentence states:
The player cannot choose for the AMS to not engage, as it is always active until it runs out of ammo or is destroyed
(Emphasis added)
These statements contradict each other or are at least extremely confusing.
Xotl: The activation is optional; p. 129 is correct.
-
* VERSION:
Corrected Seventh Printing; Sixth Printing by Catalyst Game Labs (PDF)
* LOCATION:
Skidding / "Other Units", pg. 63. Paragraph 1, Sentence 2:
The skidding unit takes damage from the target unit as if the target unit had executed a successful Kick attack.
skidding example, pg. 65. Paragraph 5, Sentence 1
The skidding ’Mech also takes damage from the successful charge equal to 1 point of damage for every 10 tons that the target weighs (round fractions up), applied in 5-point Damage Value groupings on the Front/Rear column.
* THE ERROR:
A kick does 1 point of damage for every 5 tons [page 147, Kick Attacks ('Mech Only) paragraph 3, Sentence 1] (and not every unit can kick).
* THE CORRECTION:
I believe the 1st sentence above should read "The skidding unit takes damage from the target unit as if the skidding unit had successfully charged it". Or delete the sentence - damage is dealt to both unit during a charge and only calling out damage to the skidder here just adds confusion.
To back this up:
TW pg 148, Charge Attacks / Damage, Paragraph 1, Sentence 6 says Charging unit takes 1 damage / 10 tons (rounded up)
Battletech Battlemech Manual, corrected second printing (physical), page 69, Skidding Diagram 1 example, paragraph 5, sentence 3 agrees on 1 damage / 10 tons (rounded up).
-
A very old one, dating all the way back to 1st printing:
*VERSION: TW, 7th printing, 2021,
*LOCATION: p. 217, right column, example in italics, 2nd paragraph, last sentence:
Jim marks off 15 troopers killed out of 21, leaving him with 8 troopers.
Change to:
Jim marks off 15 troopers killed out of 21, leaving him with 6 troopers.
In addition, a standard IS LRM Jump platoon should consist of 15 troopers, per the "GENERIC CONVENTIONAL INFANTRY UNITS TABLE" on page 213, so maybe another platoon type might make a better example.
-
7th PDF, checked against 8.0 Errata
Location: p. 69 (nice)
The Grasshopper in the previous example has a Piloting
Skill of 5. It does not have any pre-existing damage, it
did not take 20 points of damage in this turn,
Correction: did not take 20 points of damage in this phase
Looks to be the only phase/turn error still out there.
-
Yes, TW just had an errata release four months ago, but there's been another printing ordered and so another errata release needed to go along with it. Links in the first post as always; thanks a ton for your reports.
The speed at which I had to put this together meant that a couple of reports were missed. I'm flagging these here for future work:
Pg. 263 7th Printing PDF.
Corrected Seventh Printing, pdf
p. 119, Attack Direction section
-
The first post of this thread claims that there are SEVEN printings, the v9.0 PRE.pdf just uploaded claims that there are EIGHT, but then lists NINE by year.
Xotl: Corrected to nine in all cases; thanks.
-
7th edition PDF, checked against 9th errata
Punching While Prone (p.151)
In order to punch while prone, a ’Mech may not have a destroyed arm. As with Firing When Down (see p. 113), the ’Mech props itself up on one arm and may punch once with the other arm.
Add:
A prone ’Mech that has fired any Arm mounted weapons that turn cannot attempt a Punch
-
7th printing, checked against 9.0 PRE
Page 196
"Because a VTOL flies above woods, it does not benefit from woods modifiers for the hex it occupies while in flight."
Change:
"Because a VTOL flies above terrain, it typically does not benefit from woods modifiers for the hex it occupies while in flight unless it follows a road through a woods hex, then it gains this bonus by being in the hex."
Brings the rules in line with two other blurbs,
P. 54; Roads: VTOLs can choose to move along a road, allowing them to traverse woods hexes at a level below the treetops. In order to do this, a VTOL must begin the movement through the woods on a road and stay on the road for the entire movement. Of course, at any point the VTOL can increase its elevation to rise above the trees and continue its movement off the road.
P. 199; To-Hit Modifiers: Since a WiGE vehicle operates one elevation above the ground, it remains below the level of a woods hex, and so gains the modifier from woods as would a VTOL at the same elevation. If a WiGE vehicle follows a road through a woods hex, it also gains this bonus by being in the hex.
-
7th printing pdf
Aerospace Attack Modifiers Table (pp. 237 and 312)
PROBLEM: The left column header of the table is titled Range. This is incorrect, because only first four entries in the table are about range.
RECCOMENDATION:
1. Change all instances of "Range" in the table header to something like "Situation".
2. Insert a new line at the beginning of the table with italicized word "Range" in the left (newly renamed) column, and nothing in the right ("Modifier") column.
-
Version: 9th Printing (Errata)
Location: p. 86-88, 312
Error: 8th Printing enabled aerodyne small craft to perform vertical landings and liftoffs (removed from the list of units that can only make horizontal landings on p. 87, and moved from being able to perform vertical liftoffs only in vacuum to being able to perform vertical liftoffs anywhere on p. 88). However, 8th Printing also modified the Landing Modifiers Table (p. 86 & 312) to the following:
Aerodyne small craft and DropShips making vertical landing NA/+0
Due to this, aerodyne small craft are prevented from making vertical landings and are forced to use stalling rules.
Correction: Edit the Landing Modifiers table, removing the entry for aerodyne small craft and DropShips and replacing it with the following two entries:
Aerodyne small craft making vertical landing +2/+0
Aerodyne DropShips making vertical landing NA/+0
Additional: It may be prudent to add a footnote or additional entries to the Landing Modifiers Table and the Vertical Liftoff Modifiers Table (87 & 312) for aerospace fighters and aerodyne small craft based on TechManual errata from that book's 4th Printing, specifically the change to "Special Enhancements" on p. 109.
-
PDF, 9th
Page 52, footnote 8
"IndustrialMechs can enter a Depth 2…"
Can is in a different font size, possibly a different font
-
This thread (https://bg.battletech.com/forums/tactical-operations/answered-dropship-firing-arcs-and-artillery/msg1536417) from 2019 mentions an errata for indirect fire from nose-mounted weapons in grounded DropShips, that does not appear to have actually made it into the most recent printing or errata document (checked against TW 9th printing PDF, errata document v9.0).
-
Version: 7th Printing
Location: Page 88
Error: Unlike landing, which differentiates between DropShips and small craft vs. VSTOL-capable fighters, short liftoff runway requirements apply universally to all VSTOL-capable units (including aerodyne DropShips and small craft).
Correction:Replace the third sentence in the first paragraph under Liftoff,
Any VSTOL-equipped units can take off in ten hexes.
with the following:
Any VSTOL-equipped fighters can take off in ten hexes.
-
* VERSION:
Corrected Seventh Printing; Sixth Printing by Catalyst Game Labs (PDF)
* LOCATION:
Index, page 301, "Industrial Mech" section
* THE ERROR:
3rd sub-entry, "modifier, 110" refers to the wrong page. There is so mention of Industrial Mechs.
* THE CORRECTION:
The correct page is 108; it mentions Industrial Mechs without an advanced fire control system suffer a +1 to all weapon attacks.
-
* VERSION:
Corrected Seventh Printing; Sixth Printing by Catalyst Game Labs (PDF)
* LOCATION:
page 301, "I" section of the index.
* THE ERROR:
There is no index reference for ICE Engine critical hits. I believe this should be there, as on the same page, in the "F" section this entry exists:
Fission Engine, critical hit, 126
* THE CORRECTION:
Add a new entry in the "I" section ICE Engine, critical hit, 126
* VERSION:
Corrected Seventh Printing; Sixth Printing by Catalyst Game Labs (PDF)
* LOCATION:
page 301, "I" section of the index, "IndustrialMech" sub-section.
* THE ERROR:
There is no reference to the rules for industrial mechs risking destruction if submerged - this is important and easy to miss rule.
* THE CORRECTION:
Add a new entry, water, 52 (or whatever wording seems appropriate - "submerged" would work too) to the "IndustrialMech" sub-section.
*EDIT - found another issue*
* VERSION:
Corrected Seventh Printing; Sixth Printing by Catalyst Game Labs (PDF)
* LOCATION:
page 144, "Physical Attacks" section, IndustrialMechs sub-section.
* THE ERROR:
The controlling player makes only one roll per turn, regardless of the number of successful physical attacks the IndustrialMech suffers
This does not also reference that there is only 1 roll per turn regardless if the source of the roll is from falling or being hit by a physical attack unlike the rules on page 69 ("Falling Damage to a 'Mech" section, "IndustrialMechs" subsection):
The controlling player makes only one roll per turn, regardless of the number of falls (or successful physical attacks) the IndustrialMech suffers.
* THE CORRECTION:
The Physical attack rules should be updated to mention it is only 1 roll per turn regardless of source.
-
Version: 7th Printing (still present in 9th)
Location: Page 80
Error: The section on units restricted from using atmospheric aerospace movement prohibits airships from entering the low- or high-altitude maps. This prevents the unit from lifting off.
Correction: Remove any mention of airships from the sentence paragraph of Restricted Units, and add a new sentence after it which reads:
Airships are only prohibited from entering the high-altitude map.
-
On page 11 of the most recent errata document (v9.0), it mentions that in the "Failed Braking Maneuver table" (on page 87 of Total Warfare), in the third effect, "landing gear is destroyed" should be replaced with "landing gear is damaged". This includes an annotation indicating that this change occurred in the 5th printing of Total Warfare.
However, in my TW 9th printing PDF, this change has not actually been implemented on page 87; it still reads "landing gear is destroyed".
An equivalent change is mentioned on page 54 of the errata document (table on page 311 of TW), but this change appears to have been implemented, so no further action is needed there.
Separately, effects of destroyed landing gear are mentioned on TW pages 86 and 88 (preventing launch or lift-off, and preventing taxiing of aerodyne aerospace units while landed), but after the errata above is properly implemented, there appears to be no remaining ways that landing gear can actually be destroyed. You may wish to adjust this somehow.
-
product link takes you to a video, not the actual total warfare book, purchase page
can you confirm what is the picture on the 9th printing?
-
2021 - ninth printing (Catalyst/Topps; new Atlas art cover)
Page 229
Error: "Additionally, when ever a battle armor trooper that is not equipped with Fire Resistent armor and ..."
Should be: "... Fire Resistant ...
-
9th printing
page 250, GROUND-TO-AIR ATTACKS
If the Shiva had been at Altitude 1 (NOE), the WiGE in Hex 1 would have applied a +1 to-hit modifier, while the ’Mech in Hex 2 would have applied a +2 to-hit modifier for terrain.
must be: "while the ’Mech in Hex 2 would have applied a +3 to-hit modifier for terrain"
because of the rule on p.112, Non-Aerospace Units Firing at Airborne Aerospace Units
Apply a +3 to-hit modifier against any aerospace unit at Altitude 1 (NOE), unless the attacking non-aerospace unit lies in the attack/flight path of the aerospace fighter, or within one hex of the flight path, in which case apply a +1 modifier.
-
9th Printing
Omitted Rule on p. 109, currently only in the C3 example on p. 132.
"The VTOL in Hex B is closest to the enemy, at a Range of 2; even though it is at Elevation 10, elevations are never taken into consideration when determining range to target."
Solution: Add equivalent sentence to p. 109. Alternatively if the absence of this rule means elevation does now affect range, remove this blurb from p.132 and add clarifying language based on p. 81's Low-Altitude Table. Elevations are 6 meters high (p. 31), Altitudes varies in meters of height. If Elevation does add to range then the 1 Altitude=+2 hexes of range (p.109) that could be expanded since VTOLs can reach Elevation 500 (p. 54) which at 3,000 meters is the equivalent of Altitude 9.
-
7th ed print, 9th ed pdf.
The following errata suggestions was discussed earlier in this rules questions thread: https://bg.battletech.com/forums/total-warfare/length-of-multi-hex-vehicles-from-reinforcements-ci-box/ You may want to read it if you find my explanations below insufficient. Just note that the recently published renders of the upcoming Battlefield Support: Objectives Force Pack there most likely won't be any changes to rules which would invalidate my reasoning in that thread (or in this post) regarding lengths of vehicle set, which is why I decided to post the following in this errata thread.
There are three related problems with tractor/trailer vehicle set in TW:
1. As far as I can tell the book fails to explain properly how many tractors/trailers from a single set can be in a single hex. Trailers section on p. 57 say that two small, two medium or one small and one medium trailer together "act as a single Support Vehicle" (and trailer rules on p. 205 say more or less the same on the topic), which combined with the general stacking rules on the same page can lead to conclusion that you can have up to four such trailers belonging to the same vehicle set in a single hex. This is incorrect as far as I can tell. An example on p. 19 TO:AE shows that you should have only up to one large vehicle or up to two small or medium vehicles belonging to the same set on a single hex. Technically that example is for rail support vehicles that aren't covered in TW, but I can't anything in the rules in TO books that suggests that rail vehicles are in any ways an exception in this regard. Recently published renders of the upcoming Mobile Long Tom minis (one medium tractor and three medium trailers taking up two hexes) also seem to support this rules interpretation.
2. TM has has rules for constructing tractor/trailer sets of Combat Vehicles. Other official sources (certain TROs for example) have a number of such vehicles. TW however seems to assume that all tractor/trailer sets may consist of Support Vehicles only.
3. Both p. 57 TW and p. 205 TW say that one small or medium trailer counts as part of a tractor for purposes of movement and stacking. in light of the example on p. 19 TO:AE I believe it should only be the case if the tractor is not a Large Support Vehicle.
I suggest the following:
Ad 1. Add one or two sentences to Trailers section(s) on p. 57 TW and/or p. 205 TW stating clearly that only one large tractor or trailer and only up to two small or medium tractors/trailers belonging to the same set may occupy one hex and any following trailers must be placed in separate hexes down the line.
Ad 2. Since TM doesn't divide combat vehicles into small, medium and large ones change any references to "small and medium Support Vehicle trailers" in Trailers sections on pp. 57 TW and 205 TW so that they refer to something like "small or medium Support Vehicle trailers and combat vehicle trailers". In Combat Vehicles chapter (possibly in or below Movement section on p. 192 TW) add a note that if a Combat Vehicle has any trailers, rules from p. 205 TW of Support Vehicles chapter apply accordingly.
Ad. 3 Change first sentence in the Tractors section on p. 57 TW and the first sentence of the second paragraph on p. 205 TW to make it clear that only one small, medium or combat trailer counts as part of a tractor for purposes of stacking and movement only if the tractor isn't a large support vehicle itself.
Note that due to how TO (p. 77 TO:AR) handles superheavy combat vehicles it may be easier (both to fit on a page and to understand for the reader) to add a blanket statement on p. 57 TW and possibly 205 TW or 192 TW that in TW combat vehicle tractors and trailers are always treated as medium support vehicles for purposes of movement, stacking etc. instead of changing all instances of "small and medium Support Vehicle trailers/tractors" to "small and medium Support Vehicle and Combat Vehicle trailers/tractors" on pp. 57 and 205 TW.
-
* VERSION: Corrected Ninth Printing
* LOCATION: page 178, example text: The modified to-hit target number for the LRM jump platoon is 8 (4 Gunnery, + 2 because the Siren ran, + 2 for the building hex the target occupies and the difference in levels), making that unit the only one suitable for attack. However, even if the attack strikes the infantry unit, the Siren’s machine guns will only do their standard 2 points of damage to the platoon rather than the brutal 2D6 points of damage each, if the LRM jump platoon was not in a building hex. In addition, the 2 points will be reduced to 1 point because the infantry unit occupies a hardened building hex; a quick check of the Infantry Damage From Attacks Inside Buildings Table shows that the building absorbs 50 percent of any damage dealt to an infantry unit.
* THE ERROR: example based on older edition of the section (above): Burst-Fire Weapons and Conventional Infantry
* THE CORRECTION: please update example text in accordance with Burst-Fire Weapons and Conventional Infantry, above (damage to infantry, if both units are in a building, must be half of damage per the Burst-Fire Weapon Damage Vs. Conventional Infantry Table).
-
Corrected seventh printing (sixth printing by CGL), print
1. pp. 118, 307 Attack Modifiers Table, Physical Attacks Only subtable, Other Modifiers section
PROBLEM: Modifiers for Charging and Death from above attacks reference page 40 which does not explain how relative Piloting Skills are calculated.
RECOMMENDATION: Change the reference to Physical Modifiers Table (pp. 144, 308).
2. pp. 144, 308, Physical Modifiers Table, first note
PROBLEM: Assuming that the way a to-hit modifier for unintentional charges should be determined as described in Collisions with 'Mechs section on p. 71 BMM the note question should mention that during unintentional charges you should use a flat +3 to-hit modifier instead of a difference between Piloting Skills of pilots/drivers involved.
RECOMMENDATION: Add a following sentence to the note: "If the attacker is performing an unintentional charge (see Skidding p. 62-63) use a +3 modifier instead." You may also consider changing the second bracket in the first sentence on Other Units section on p. 63 from "[...](including these for unintentional charges)[...]" to a proper explanation that during such unintentional charge you should use a +3 modifier to attack roll instead of the Piloting Skill difference usually used for charge attacks.
-
Errata for the just out in PDF tenth printing is now posted. Please note that due to the lengthy lead times between finalization of the errata and release of the actual book/PDF (the reason the printing is dated as 2022 despite only coming out around now), a bunch of the items directly above are not included. They will be reviewed in any future printing.
-
Errata for the just out in PDF tenth printing is now posted. Please note that due to the lengthy lead times between finalization of the errata and release of the actual book/PDF (the reason the printing is dated as 2022 despite only coming out around now), a bunch of the items directly above are not included. They will be reviewed in any future printing.
For those that got the book via the Humble Bundle, how would they go about getting this, and any other updates?
Xotl: Post in the thread titled "Errata Discussion Thread - Questions HERE, not in Errata Threads"
-
* VERSION: Total Warfare, 8th printing
* LOCATION: Pg 215, Attacks Against Conventional Infantry and pg 216, NON-INFANTRY WEAPON DAMAGE AGAINST INFANTRY TABLE
* THE ERROR: These sections do not directly address rounding. The table's note †<dagger>'s last sentence is
Attacks by non-infantry weapons against mechanized infantry double the number of troopers eliminated; round all fractions up.
Error 1: The semi-colon tells us that the rounding clause is linked exclusively to mechanized infantry.
Error 2: It is unclear when to round. Information is not presented until the example of the Atlas on pg 217. However, the numbers in the example don't add up and the target platoon's type changes inexplicably, making it hard to follow.
* THE CORRECTION:
Error 1: Change semi-colon to a period and make the rounding rule a new sentence.
Error 2: Make note in the rounding rule that rounding occurs as fractions occur rather than as a final step. The final sentence combining both corrections would look something like "Round all fractions up as they occur."
Note: I asked this question here https://bg.battletech.com/forums/ground-combat/big-guns-and-infantry/msg1946439/#msg1946439 before finding how to post in this thread.
Answered here: https://bg.battletech.com/forums/index.php?topic=77025.msg1948690#msg1948690 and will be included in errata at some point. Bottom line, round damage up as part of the initial division.
-
This was raised by a customer, I am just passing it on. I know it's not the correct format, I don't know what the format is, I apologize.
"I wanted to let you know that in Total Warfare, the "Fighters Return Table" is missing from Page 92 as well as the Aerospace Tables in the back of the book. This is present in both the physical copy of the 9th Printing as well as the PDF version of the 9th Printing. I've also found it missing in PDFs of Total Warfare's previous printings. The index refers to the table but it is not present. This table is also not present in the latest errata for Total Warfare.
Will you include this table in a future printing or errata update?"
-
Total Warfare 10th print PDF
Error1: Page 229 indicates Multi-Purpose Missile is only available to LRMs even though it should be available to SRMs too, per Tech Manual page 261 (and TM tables).
Correction: Change Weapon Type line to "Weapon Type: Standard LRMs/SRMs".
Error2: Page 229 section on battle armor torpedoes implies they are available to MRMs even though this is not the case and the Weapon Type line correctly does not list them.
Correction: Change line "Torpedoes use the same statistics as any standard SRM, LRM or MRM the battle armor unit mounts" to "Torpedoes use the same statistics as any standard SRM or LRM the battle armor unit mounts"
-
Total Warfare, 10th printing
Battle Armor Attacks (page 218, second paragraph, second sentence):
"Mark off ammunition on the record sheet for each missile fired."
Change to:
"Mark off one shot of ammunition on the record sheet for each missile weapon fired by the battle armor unit."
(can optionally remove the "by the battle armor unit", but it's definitely not one shot of ammo per missile fired ...)
-
Tenth printing, pdf
P. 144
Attacks Against Large Support Vehicles and Grounded Small Craft: As per page 110, all physical attacks against Large Support Vehicles (including Airships and Fixed-Wing Support Vehicles) and grounded DropShips receive a –2 to-hit modifier.
change to something like:
Attacks Against Large Support Vehicles and Grounded Small Craft and DropShips: As per page 110, all physical attacks against Large Support Vehicles (including Airships and Fixed-Wing Support Vehicles) and grounded Small Craft receive a –2 to-hit modifier, and all physical attacks against grounded DropShips receive a –4 to-hit modifier.
P. 148
ProtoMechs: ProtoMechs cannot be targets of charging attacks
change to:
ProtoMechs: ProtoMechs cannot be targets of standard charge attacks
REASON: ProtoMechs, just like Infantry units, may be targets of unintentional charges - see Skidding rules on pp. 62-64.
P. 215
Delete the last sentence on the page ("Successful non-conventional infantry attacks against conventional mechanized infantry double the number of troopers eliminated in this fashion").
REASON: it needlessly repeats a part of the rule found on p . 217 ("Mechanized Infantry: Successful non-conventional infantry attacks against conventional mechanized infantry double the number of troopers eliminated unless they are made with burst-fire weapons").
-
Tenth Printing, p. 87
Damage taken upon a failed landing attempt is unclear. Per this thread (https://bg.battletech.com/forums/index.php/topic,82144.0.html), make the following edit:
If the roll fails the unit suffers 10 points of standard-scale damage on the nose (or aft for spheroid units) per point of MoF. Divide the damage into groupings of 5 points each, assigning any remaining points to one smaller group. Roll a location for each group of damage on the Nose (for aerodyne units) or Aft (for spheroid units) column of the Aerospace Units Hit Location Table.
Note: This errata borrows phrasing from BattleMech falling damage rules (p. 69).
-
The pre-release errata for the still multiple months out 11th printing of TW has been added to the first post for public review. Any eyes you can give it for errors would be appreciated.
-
The note about conventional infantry weapons on page 216 is still contradicted by TO:AUE page 129. The example in TO specifically cites a "non-infantry weapon" and divides it by the Armor Divisor.
-
The note about conventional infantry weapons on page 216 is still contradicted by TO:AUE page 129. The example in TO specifically cites a "non-infantry weapon" and divides it by the Armor Divisor.
Sorry, can you be more specific about what the contradiction is? Please post your clarification in the Errata Discussion Thread, to keep this clean.
EDIT: TW errata is now locked, so any comments on the errata draft from this point forward should focus on formatting errors only, as I can't make any more changes to the book.
-
Page 84, 9th printing (applicable to 11 Pre as well)
Velocity Loss, Stalling and Overspeed
Issue: Unlike on the Space Map (p. 76) and High Altitude Map (p. 79) there's no explicit mention to the Thrust Point cost to increase velocity on the Low Altitude or Ground Maps.
Correction: Insert language giving the Thrust Point cost.
Xotl: Not resolved in time to make the reprint. My apologies.
-
In the current PDF version of Total Warfare, the table of contents metadata is missing any subchapters under Combat.
(https://i.imgur.com/vIzw1Ku.png)
-
Final errata version uploaded to the main website; a big thanks to those who contributed. At the last minute I managed to get a change to how TAG and torso-twisting works in, so be sure to note that.
EDIT: A minor 11.01 update has been uploaded.
-
Corrected Tenth Printing, pdf
p. 85, Special Maneuvers Diagram
Change "Slide-Slip" to "Side-Slip".
-
Xotl: Questions are for the Errata Discussion thread, not individual errata threads. Thank you.
-
TW, 9th printing PDF.
Page 199: "Engine Damage" heading under WiGE Combat Vehicles: add Water hexes to the list of terrain in which an engine-hit WiGE can make a DSR to avoid crashing.
Clear hexes are already on the list, and page 55 indicates that all WiGE vehicles treat water hexes as Clear terrain; this errata is mostly for clarity.
-
9th printing PDF.
Problem: There are issues with current wording for ProtoMech pilots taking damage, specifically regarding the functionality of shaded critical hit boxes boxes.
Page 28 states "Shaded [ProtoMech critical hit] boxes represent damage to the MechWarrior."
Page 41 states "the ProtoMech pilot takes a point of damage each time the controlling player fills in a shaded critical hit box (see Damage, p. 185)."
However, Page 185 states "Each time an attack forces a player to cross off one or more critical hit boxes, the warrior takes a point of damage."
My reading of this last line is that any critical hit that results in the checking off any number of boxes causes pilot damage - even if none of them were shaded. Also, the entire ProtoMech chapter no longer mentions the functionality of the shaded boxes at all, contrary to the excerpt from page 41.
Solution: The wording in one or more of these sections I have cited needs to be changed to clarify the intent of how damage is assigned to ProtoMech pilots.
If the intent was to remove the functionality of the shaded critical hit boxes altogether, then the references to them need to be removed. (I think it is unlikely that this is the case, but the change to page 185 makes it seem like it is possible.)
If the intent is to damage the pilot in the event of any successful critical hit AND in the event of shaded boxes being checked off (which can happen via section destruction without critical hits) then page 185 should have an additional line that includes an explanation of how shaded boxes work.
If there was no intent to actually change functionality, then the wording on page 185 should be reverted. The current wording is not ideal because it suggests only attacks can cause pilot damage (not any other sort of non-attack damage), and that checking off multiple shaded boxes only results in one pilot hit rather than one hit per box.
-
P146 Total Warfare Finding a club
Beyond what is noted above, carrying a club has no affect other than to occupy both ’Mech’s hands.
Effect is the correct word here, not affect.
-
Corrected 9th Printing.
The entry for Ciritcal Hits to HIPS (page 127) does not match the entry for BATTLEMECH MANUAL (and should), in regards to timing of critical hit in relation to other leg critical hits.
TW:
After a hip critical hit, ignore all modifiers from previous
critical hits on that leg. This means it is possible for a ’Mech’s
performance to improve after a hip critical hit if it had suffered
previous critical damage to the same leg. Since the leg
becomes locked in a straight position, it serves as a sort of
crutch, making movement easier in some cases than moving
on a number of free-flexing damaged actuators.
BATTLEMECH MANUAL entry (page 48):
After a hip critical hit, ignore any other critical hit modifiers
from previous turns due to damage on that leg (even if this actually
reduces the PSR penalty provided by the leg). However, other critical
hits applied to that leg on this turn or later still apply.
-
Corrected 9th printing PDF.
Page 227, under Falling and Dropping Prone subheading: in the sentence "When a unit carrying battle armor fails a Piloting Skill Roll and falls, follow the same rules found under Falling/Dropping Prone, p. 224", change the page reference to "p. 222".