Register Register

Author Topic: Era Report: 3052  (Read 3566 times)


  • Dominus Erratorum
  • Moderator
  • Lieutenant Colonel
  • *
  • Posts: 10750
  • Professor of Errata
Era Report: 3052
« on: 22 March 2012, 23:40:20 »
This thread is for all issues and problems with Era Report: 3052.

Product Link:

There is no compiled errata for this product at this time.

Please remember to follow the errata report template when reporting issues.  Thanks.
« Last Edit: 20 June 2012, 01:45:24 by Xotl »
3028-3057 Random Assignment Tables -
Also contains faction deployment & rarity info.


  • Captain
  • *
  • Posts: 2413
Re: Era Report: 3052
« Reply #1 on: 17 April 2013, 08:55:32 »
Era Report: 3052, page 151

Upgrade Check Table: does not contain what the Upgrade Check should be for the few Mercs/Periphery results that can feature upgrades.


  • Catalyst Demo Team
  • Master Sergeant
  • *
  • Posts: 209
  • Sweet justice!
Re: Era Report: 3052
« Reply #2 on: 14 January 2022, 00:23:27 »
Pp 111. Tables do not include, nor does text identify, the WP cost for reconfiguring a Clan Omnimech between Tracks.
Does reconfiguring also repair the mech? Can a damaged mech be reconfigured at all?

pp109, force composition table. "Clan players should reduce the Piloting/Gunnery skills of Green, Regular, and Veteran warriors by 1 (only one skill—either Piloting OR  Gunnery—may be reduced in this way)."
It is unclear if this is already accounted for in the table.

General GM notes from running this Chaos Campaign.
Playing Clan the track selection never imposes forced withdrawl on the attacking player, which makes sense, the clans were ruthless and didn't back down. However this makes the objectives for several tracks meaningless or trivial to obtain. Some tracks specify a minimum number of turns that a force must survive, or withdraw after but otherwise most tracks do not specify an end clause to the game. With the clan never backing down, time limits will always be achieved due to the huge disparity in technology fielded in the RATs.
Only once did a clan player fail a mission, when they shot up a Recon mission and one enemy mech was destroyed via ERPPC headshot and another force withdrew off the map without being scanned.
The IS Defender is given little detail as to the objective they are to attempt. Why does the OPFOR in Recon stick around on the map at all, if they are 'leery of a full press engagement'.
Understanding this is all expected to be modified by the GM and players for what is fun, per the insert on p111.
What avarice!

Field Agent #522
Battletech in Brisbane, Australia.