Register Register

Author Topic: Experimental Technical Readout: Boondoggles  (Read 8624 times)

Xotl

  • Deus Errata et regulas Exsecutor
  • Moderator
  • Lieutenant Colonel
  • *
  • Posts: 9020
  • Professor of Errata
Experimental Technical Readout: Boondoggles
« on: 14 January 2013, 15:31:02 »
This thread is for all issues and problems with Experimental Technical Readout: Boondoggles.

Product Link: http://bg.battletech.com/?wpsc-product=experimental-technical-readout-boondoggles

Please remember to follow the errata report template when reporting issues.  Thanks.
« Last Edit: 14 January 2013, 15:43:37 by Xotl »
3028-3050 Random Assignment Tables -
Also contains faction deployment & rarity info and Quirk lists.

http://bg.battletech.com/forums/index.php?topic=1219.0

Xotl

  • Deus Errata et regulas Exsecutor
  • Moderator
  • Lieutenant Colonel
  • *
  • Posts: 9020
  • Professor of Errata
Re: Experimental Technical Readout: Boondoggles
« Reply #1 on: 14 January 2013, 15:36:06 »
Liberator, p. 4
both "LRM-5"s should be "LRM 5"
"SRM-2" should be "SRM 2"

Champion LAM, p. 6:
Gyro and Fuel lines are improperly justified

Thorizer, p. 8
"SRM-2" should be "SRM 2"

Neptune Hyper, p. 10
Armour Value improperly justified

MUSE Ironside, p. 11
"LRM-15" should be "LRM 15"

Enterprise, p. 17:
Overview, 4th paragraph, last line: "damage the vessel and leave it’s hoards of fighters stranded."  Change it's to its.

FL/FR (760 Heat): "AMS" is listed in that arc as "AMA"

All AMS ammo entries except the first are improperly justified

Also, while the fluff makes it clear the engines are the inoperable equipment mentioned in the Failure Analysis, it's missing the Non-functional Quirk in the Notes section like the Bright Star has.
« Last Edit: 15 January 2013, 03:24:22 by Xotl »
3028-3050 Random Assignment Tables -
Also contains faction deployment & rarity info and Quirk lists.

http://bg.battletech.com/forums/index.php?topic=1219.0

Schottenjaeger

  • Sergeant
  • *
  • Posts: 172
Re: Experimental Technical Readout: Boondoggles
« Reply #2 on: 14 January 2013, 16:12:43 »
SCP-X1 Scorpion LAM, pg. 4:
"..apparently manufactured and tested
Defiance Industries in secret."
Should be "..tested by Defiance.."

BSE-X2 Banshee, Pg. 14
"The Clan pilot, believing that his opponent was deliberately
under-utilizing his fighter as some kind of track.."
Should be "trick"

Enterprise, Pg. 17
"Holding eighteen wings of fighters internally, in
addition to the capacity of any DropShips on its four docking
points."
Sentence fragment. Suggest "It held eighteen.."

"With a total of fifty four fighter bay doors,.."
Should be "fifty-four"

"In the bowels of the ship, the most complex command
and control system that the Star League had ever designed for a
vessel lay, capable.."
Wrong tense, and putting the object clause prefatory to the verb hurts my linguist's brain. Suggest "In the bowels of the ship lay/laid the most.. .. a ship, capable.."

"damage the vessel and leave it’s hoards of fighters stranded"
Should probably be "hordes", although "hoard" would also be correct ("it's" typo already corrected).

"The ship itself was towed to asteroid
belt where"
Should be "..to the asteroid belt, where.."

"..by scavengers of the Sol system."
Should be "..of Sol system." or "..the scavengers of the.."
Standing proudly on other pilot's cockpits since 1997

Pa Weasley

  • Freelance Writer
  • Major
  • *
  • Posts: 5513
  • Spotted near Lake Springfield.
Re: Experimental Technical Readout: Boondoggles
« Reply #3 on: 15 January 2013, 00:24:10 »
Experimental Technical Readout: Boondoggles
Page 10 Neptune Hyper
First column, third paragraph
"This allowed six  new short-range torpedo tubes to be connected to the existing ammunition bin, protecting the submarine’s art against tailing enemies."
Should be " ... the submarine's aft against tailing enemies."

Page 11 MUSE Ironhorse
First column, second paragraph
"Sixteen tons of combat-grade armor protected the Ironhorse tractor."
Should be "Nineteen tons ..."
Stat block
Armor values for both MUSE Ironhorse (Tractor) and MUSE Ironhorse (Trailer) are 304 points which should equal nineteen tons.
Mass in both instances is listed as "16"
« Last Edit: 15 January 2013, 00:47:15 by Pa Weasley »

S.gage

  • Sergeant
  • *
  • Posts: 162
Re: Experimental Technical Readout: Boondoggles
« Reply #4 on: 15 January 2013, 01:57:18 »
XTRO Boondoggles

I'm sorry to be so hard, but I found a lot of typos.  Many were already reported, but here are more:

p. 3, "Ostscout IIC" entry:
Overview
Fighting in the Inner Sphere has introduced many challenges for the Clans, with one of the most teling being the need for effective electronic warfare and reconnaissance


p. 16, "Bright Star Auto Scout" entry:
Overview, middle of the 5th paragraph
Remote access failed and the last confirmed sighting of it was in the New Samarkand system before it left the known space.


p. 17, "Enterprise" entry:
Overview, middle of the 1st paragraph
The appearance of aircraft carriers in the mid twentieth century signaled the beginning of the end for the battleship. (should be "mid-twentieth")

2nd paragraph
The first draft of the specifications called for a million ton ship that could carry three wings of fighters. (should be "million-ton" because million-ton is an adjective for "ship")


p. 18, "Monitor" entry:
Overview, middle 1st paragraph
During the latter part of the twenty seventh century, a group of SLDF admirals pushed to create a new breed of WarShip, dispensing with the KF drive to double the firepower. (should be "twenty-seventh")

2nd paragraph
The prototype was to be based on the venerable Avatar class cruiser. (should be "Avatar-class" because Avatar-class is an adjective for "cruiser")

middle 3rd paragraph
A member of the anti- camp, Admiral Arthur Ubuntu offered to lead a challenge against the monitors with a group battle, three WarShips and three monitors. (should be "Ubuntu, offered" because the nominative clause ends with a 2nd comma)
Thought the remaining monitors tried to regroup themselves, they were out-maneuvered by the jump-capable craft and lost the battle. (should be "Though")

Steve
« Last Edit: 15 January 2013, 03:13:15 by S.gage »
"WHO PUT 6 ARMOR ON THE RIFLEMAN'S HEAD?!?" - Peter S., while marking damage from a stray PPC, 1994.

"Ich bin Jadefalke!!!! Ich bin MechKrieger!!!!" - A group of students on their field trip to Leipzig, 1998.

Kit deSummersville

  • Precentor of Lies
  • Freelance Writer
  • Lieutenant Colonel
  • *
  • Posts: 9282
  • The epicness continues!
    • Insights and Complaints on Twitter
Re: Experimental Technical Readout: Boondoggles
« Reply #5 on: 15 January 2013, 09:17:20 »

p. 16, "Bright Star Auto Scout" entry:
Overview, middle of the 5th paragraph
Remote access failed and the last confirmed sighting of it was in the New Samarkand system before it left the known space.


No, that's correct without the the.
Looking for an official answer? Check the Catalyst Interaction Forums.

Freelancer for hire, not an official CGL or IMR representative.

Everyone else's job is easy, so tell them how to do it, everyone loves that!

Millard Fillmore's favorite BattleTech writer.

sillybrit

  • Major
  • *
  • Posts: 3923
Re: Experimental Technical Readout: Boondoggles
« Reply #6 on: 15 January 2013, 14:15:09 »
Cheetah II p15:

"Three plans emerged from the commissioned studies: one that called for making the fighter heavier, and two that adjusted its trust"

I'm sure that making a design more trustworthy is laudable, but I think that should be "thrust".

jymset

  • Infinita Navitas
  • Freelance Writer
  • Lieutenant
  • *
  • Posts: 1349
  • the one and only
Re: Experimental Technical Readout: Boondoggles
« Reply #7 on: 16 January 2013, 02:08:05 »
Page 26, Condor Trans-Track RS
change Tonnage from 35 to 50

Pages 25-29
remove crew count from "Crew:"


Page 11 MUSE Ironhorse
First column, second paragraph
"Sixteen tons of combat-grade armor protected the Ironhorse tractor."
Should be "Nineteen tons ..."
Stat block
Armor values for both MUSE Ironhorse (Tractor) and MUSE Ironhorse (Trailer) are 304 points which should equal nineteen tons.
Mass in both instances is listed as "16"

No, this unit uses BAR 10, Tech F armour at 52 kgs per point, to the vehicle's maximum of 304 points.
On CGL writing: Caught between a writer's block and a Herb place. (cray)

Nicest writing compliment ever: I know [redacted] doesn't like continuity porn, but I do, and you sir, write some great continuity porn! (MadCapellan)

3055 rocks! Did so when I was a n00b, does so now.

The Hawk

  • Warrant Officer
  • *
  • Posts: 473
  • Have talons, will travel.
Re: Experimental Technical Readout: Boondoggles
« Reply #8 on: 16 January 2013, 11:13:01 »
p. 7, Matar entry, first column of Overview section, second paragraph, third sentence:

Unit is called the Monster; change to Matar.

p. 15, Cheetah II entry, bottom of first column of Overview section:

"With their stock falling, Imstar’s board of directors was forced to dismiss Gurnstoggle from (albeit with a few-million-eagle “golden parachute”)."

Missing word following "from" -- possibly intended to be "service" or "his position"?  Alternatively, drop the "from" altogether.

Schottenjaeger

  • Sergeant
  • *
  • Posts: 172
Re: Experimental Technical Readout: Boondoggles
« Reply #9 on: 16 January 2013, 21:53:12 »
Pg. 3, Ostscout IIC
"While this last deficiency would be objectionable to many in
the Inner Sphere, to the Clan warriors, it was especially offensive"
Excess comma, should be "..to the Clan warriors it was especially offensive."

"..prototypes, forcing shut downs after.."
Given past precedent, should be "shutdowns", "shutdown", or "shut-downs" for engines.


Pg. 4, Liberator
"..resulted in a complete failure in the ’Mech’s
core cooling system not functioning."
either pull "not functioning", or "..failure, with the 'Mech's core cooling system not functioning."

Pg. 7, Matar
"Amaris was particularly concerned by the
Narc beacon, which could allow missiles to rain down where the Matar
could not reply."
This is just a weird sentence. Suggest "Amaris was particularly concerned by Narc beacons, which could/would allow missiles to rain down while the Matar could not reply" or "..rain down from locations which/while the Matar could not (insert favorite word for counter-attack)".


Pg. 15, Cheetah II
"..made her aware that a new aerospace design that was
going to be introduced."
Should be "..made her aware of.." or "..a new aerospace design was going to be introduced."

"..unable to recover from the loss in building a new fusion engine.."
should be "..loss of/losses from building.."


Pg. 16, Bright Star Scout
"..limited life support capacity and access ways that.."
Should be "accessways"

"..sufficient enough only for the technical teams.."
Should be "..sufficient only for.." or "..though sufficient enough for.."

"As the needs of a survey differed based on the size and how many celestial bodies it contained"
Missing word or phrase modified by "size", possibly "system", as in "system survey" or "a system's size", OR the "survey" is being modified, in which case it should be "..differed based on its size.."

"While the SLDF liaison requested to begin with a five-year mission, Ulsop had planned.."
Mixed tense (past perfect, infinitive). Suggest removing "to begin" as the simplest solution.

"..for the first solo voyage, with it returning to Zebebelgenubi when it was complete.."
Double referent for "it". Suggest "..with a return to Zebelgenubi.." or "..voyage, returning to Zebelgenubi.."

Also, the many run-on sentences in this entry are particularly difficult to unwind.


Pg. 19, Monitors
"..greater, with the pro- and anti- camps both believing that
their views were correct and had little use for data that did not agree with
them."
Mixed tense. should be "..correct, having little use for data..", or split the sentence at "greater" - "..greater. Both the pro- and anti- camps believed that their data was correct, and had little use.."

"A member of the anti- camp, Admiral Arthur
Ubuntu offered to lead a challenge against the monitors with a group
battle, three WarShips and three monitors"
Nonsensical clause break. Possible alternative "..with a group battle between/of three warships and three monitors." or "..Ubuntu offered to challenge a group of three monitors with a group of three WarShips."

No data or record sheet is presented for the "Monitors" entry, although this appears to be deliberate.
« Last Edit: 16 January 2013, 21:57:37 by Schottenjaeger »
Standing proudly on other pilot's cockpits since 1997

Jal Phoenix

  • CamoSpecs
  • Major
  • *
  • Posts: 3332
  • Once, we had gods.
Re: Experimental Technical Readout: Boondoggles
« Reply #10 on: 18 January 2013, 21:44:11 »
Page 16, Bright Star

Introduction date of 2543, with several mentions of the Star League and SLDF in the text, neither of which will exist until 2570. 

Suggest changing the introduction date to sometime later, and thrashing the fact checkers with a wet pirate.

FedComGirl

  • Major
  • *
  • Posts: 4448
Re: Experimental Technical Readout: Boondoggles
« Reply #11 on: 19 January 2013, 03:14:18 »
The fluff for the Scorpion LAM says that the Jump Jets weren't able to generate lift but is missing the Non-Functional Quirk for them.

The fluff for the Champion LAM says its has sluggish performance in fighter mode. If it's possible, I think the Poor Performance Quirk should apply when the Champion LAM is in that mode.


Kit deSummersville

  • Precentor of Lies
  • Freelance Writer
  • Lieutenant Colonel
  • *
  • Posts: 9282
  • The epicness continues!
    • Insights and Complaints on Twitter
Re: Experimental Technical Readout: Boondoggles
« Reply #12 on: 19 January 2013, 14:02:28 »
The fluff for the Scorpion LAM says that the Jump Jets weren't able to generate lift but is missing the Non-Functional Quirk for them.

That is referring to lift in non-Mech modes, not jump capacity.

Quote
The fluff for the Champion LAM says its has sluggish performance in fighter mode. If it's possible, I think the Poor Performance Quirk should apply when the Champion LAM is in that mode.

The design has the Hard to Pilot quirk. Please only report errata in this thread, not suggestions.
Looking for an official answer? Check the Catalyst Interaction Forums.

Freelancer for hire, not an official CGL or IMR representative.

Everyone else's job is easy, so tell them how to do it, everyone loves that!

Millard Fillmore's favorite BattleTech writer.

HABeas2

  • Grand Vizier
  • Major
  • *
  • Posts: 4570
Re: Experimental Technical Readout: Boondoggles
« Reply #13 on: 19 January 2013, 18:08:52 »
Hello,

Page 16, Bright Star
Suggest changing the introduction date to sometime later, and thrashing the fact checkers with a wet pirate.

So, you would suggest trading one continuity error for another? If anything, the introduction date should be moved to 2545 (original SLSB says the Bright Star was "built in 2545"), and the references to the Star League can be fixed by being changed to the Terran Hegemony.

Would you prefer to thrash yourself now or later?

Thank you,

- Herbert Beas

FedComGirl

  • Major
  • *
  • Posts: 4448
Re: Experimental Technical Readout: Boondoggles
« Reply #14 on: 26 January 2013, 03:46:01 »
Page 8, Thorizer
Project Start Date: 2390

Suggest changing the date to 2470 as Prototype Jump Jets weren't introduced until 2464.

HABeas2

  • Grand Vizier
  • Major
  • *
  • Posts: 4570
Re: Experimental Technical Readout: Boondoggles
« Reply #15 on: 26 January 2013, 04:01:29 »
Hello,

Page 8, Thorizer
Project Start Date: 2390

Suggest changing the date to 2470 as Prototype Jump Jets weren't introduced until 2464.

That suggested errata will not work. Per Star League Sourcebook, the Thorizer debuted in 2390.

Better fix: Change "Illegal (Support Vehicle with Bimodal LAM Equipment)" to "Illegal (Support Vehicle with Bimodal LAM Equipment and pre-Prototype Jump Jets)"

Thank you,

- Herbert Beas

HABeas2

  • Grand Vizier
  • Major
  • *
  • Posts: 4570
Re: Experimental Technical Readout: Boondoggles
« Reply #16 on: 27 January 2013, 06:12:37 »
Hello,

The following errata applies to the entry titled "Monitors". Please replace ALL TEXT under this entry with the following:

Quote
Monitors

Outcome Summation: Canceled Prototype
Producer/Site: Blue Nose Clipperships of Mars, Sol
Supervising Technician: Commodore Mortimer Basquiz
Project Start Date: 2683
Failure Analysis: Inefficient Design and Inadequate Infrastructure

     With the advent of the compact KF drive, space became a much more dangerous place. No longer were warships limited to assault DropShips, but they could easily surpass a million tons. Yet, almost half of that mass was still tied up in the KF drive. During the latter part of the twenty-seventh century, a group of SLDF admirals pushed to create a new breed of WarShip, dispensing with the KF drive with the goal of doubling the potential firepower such a vessel could bring to bear. After over a decade of campaigning, funding was finally allocated for project AMHITRITE and Blue Nose Clipperships won the bidding to provide construction for the prototype.
     Though the concept “monitor” was based on the proven hull of the venerable Avatar class cruiser, almost immediately problems emerged when the KF drive was removed from the equation. Without the frame around the KF drive acting as the ship’s primary keel, stress analysis revealed that a great deal of additional structural reinforcement would be needed to avoid integrity failure under combat thrust. The design plans were hastily re-drawn and construction resumed, but the structure reinforcements ate away far more mass than originally expected.
     As construction continued on three prototype hulls, the numerous setbacks and additional costs mounted, drawing greater scrutiny from a number of oversight committees. While these monitors had a potential military impact, the potential political impact of their possible failure was orders of magnitudes greater. Internal divisions, even among the Star League admiralty, quickly formed, with pro-monitor and anti-monitor camps ignoring any data that failed to agree with their positions.
Combat simulations and technical projections won the first victories in favor of the monitors, with most simulations showing overwhelming victories between the heavily armed monitors against larger jump-capable opponents. Unfortunately, these tactical advantages paled in comparison with the logistical studies ordered by Admiral Arthur Ubuntu, who led the challenge against AMHITRITE as the construction effort stretched past eight years without a single prototype emerging from its slip.
     Ubuntu’s studies quickly revealed that, in addition to the greater manpower needs each monitor would need by dint of their extra firepower alone, the support apparatus needed for widespread deployment of monitors would quickly outstrip the Hegemony’s naval resources. This monumental problem primarily stemmed from the monitors’ inability to perform their own jumps. Unbuntu noted that the monitors’ sheer mass—well beyond the scale of the largest DropShips of the day—would force the SLDF to use YardShips to transport and deploy each monitor fleet to its duty station, an expensive proposition as any sizable monitor presence in any given system would thus require dozens—perhaps even hundreds—of such jumps, even for the systems nearest to Terra. Counter-proposals to ship monitors in pieces via specialized DropShips for on-site assembly proved equally untenable, as this would still effectively require the YardShips to do the assembly work in any system that lacked shipyards large enough to do the work locally.
     To make matters worse, after disputing computer simulations that underscored the physical dangers of moving monitors in this fashion, Commodore Basquiz, as head of the project, insisted on a “live test”, in which one of the half-completed prototypes would be moved from Mars to New Earth via the SLS J. Swift, a Newgrange-class YardShip. After tugboats were needed to get the prototype from its shipyard in Martian orbit to the Swift, the YardShip was damaged during the mooring process and suffered severe structural and drive damage after the jump to New Earth. The damage was so severe that a second YardShip was needed to take the monitor back to Mars, while the J. Swift needed five months of repairs before she could jump again.
      Convinced of the inability to properly produce, deploy, and maintain a suitable fleet of monitors for local system defense even in the Sol system, the Star League scrapped the monitor project, and ordered the incomplete hulls dismantled. Not a single one of the prototypes ever flew under its own power.

We apologize for the inconvenience.

Thank you,

- Herbert Beas
« Last Edit: 27 January 2013, 23:57:37 by HABeas2 »

Schottenjaeger

  • Sergeant
  • *
  • Posts: 172
Re: Experimental Technical Readout: Boondoggles
« Reply #17 on: 27 January 2013, 22:25:42 »
Errata, Dev-level errata for the "Monitor" entry.
Unfortunately, these tactical advantages pales in comparison..
Typo, disagreeing verb/noun plurality. Fix: Change "pales" to "paled"
Standing proudly on other pilot's cockpits since 1997

HABeas2

  • Grand Vizier
  • Major
  • *
  • Posts: 4570
Re: Experimental Technical Readout: Boondoggles
« Reply #18 on: 27 January 2013, 23:58:27 »
Hello,

Fixed. Fortunately, I caught that one earlier, in the version sent for inclusion in the update.

Thanks,

- Herbert Beas

FedComGirl

  • Major
  • *
  • Posts: 4448
Re: Experimental Technical Readout: Boondoggles
« Reply #19 on: 29 January 2013, 05:56:12 »
Scorpion LAM

According to this post
http://bg.battletech.com/forums/index.php/topic,25504.msg601040.html#msg601040
The Scorpion's conversion system should be increased from 5.5 tons to 6 tons. Unless the Quad conversion system is different some how?

The Scorpion LAM is also overweight. I keep coming up with 56 tons. 56.5 with the increase in conversion system weight. Possible fixes are:

A) remove 1 heat sink and.5 tons of armor.

B) leave as is and add Illegal: Overweight to the notes. Hey! Maybe that's why it couldn't take off?

Kit deSummersville

  • Precentor of Lies
  • Freelance Writer
  • Lieutenant Colonel
  • *
  • Posts: 9282
  • The epicness continues!
    • Insights and Complaints on Twitter
Re: Experimental Technical Readout: Boondoggles
« Reply #20 on: 29 January 2013, 09:34:28 »
Scorpion LAM

According to this post
http://bg.battletech.com/forums/index.php/topic,25504.msg601040.html#msg601040
The Scorpion's conversion system should be increased from 5.5 tons to 6 tons. Unless the Quad conversion system is different some how?

The Scorpion LAM is also overweight. I keep coming up with 56 tons. 56.5 with the increase in conversion system weight. Possible fixes are:

A) remove 1 heat sink and.5 tons of armor.

B) leave as is and add Illegal: Overweight to the notes. Hey! Maybe that's why it couldn't take off?

Illegal conversion equipment does not round. And you are probably off because...

Scorpion LAM
p. 5
Change SRM-6 weight from 4 tons to 3 tons.
Looking for an official answer? Check the Catalyst Interaction Forums.

Freelancer for hire, not an official CGL or IMR representative.

Everyone else's job is easy, so tell them how to do it, everyone loves that!

Millard Fillmore's favorite BattleTech writer.

HABeas2

  • Grand Vizier
  • Major
  • *
  • Posts: 4570
Re: Experimental Technical Readout: Boondoggles
« Reply #21 on: 29 January 2013, 16:26:02 »
Hello,

Confirmed that the weight of the Scorpion LAM's conversion gear is not in error. After all, the error was having a Scorpion LAM to begin with.

Thank you,

- Herbert Beas

TigerShark

  • Major
  • *
  • Posts: 4789
    • MekWars: Dominion
Re: Experimental Technical Readout: Boondoggles
« Reply #22 on: 06 May 2013, 09:40:31 »
PDF, 1st printing

Page 7 ("Matar")

Error 1: "Against speedy units, a Matar would appear be hard-pressed to track..." (Paragraph III)
Correcton: "The Matar would be hard-pressed to track down speedier units."
  W W W . M E K W A R S - D O M I N I O N . C O M

  "You will fight to the last soldier, and when you die, I will call upon your damned soul to speak horrible curses at the enemy."
     - Orders of Emperor Stefan Amaris to his troops

BloodReaper

  • Private
  • *
  • Posts: 33
Re: Experimental Technical Readout: Boondoggles
« Reply #23 on: 17 October 2013, 23:23:35 »
CONDOR TRANS-TRACK
PAGE 9
Armor is 88 points and 5.5 tons, but 99 points are allocated

RECOMMENDATION:
Ferro-Fibrous was rediscovered in 3040, making it viable, but this was an LCAF design.  But no other Condor has that amount of armor, so I recommend just changing "Armor Factor:" to "Armor Factor (Ferro):"

lrose

  • Master Sergeant
  • *
  • Posts: 217
Re: Experimental Technical Readout: Boondoggles
« Reply #24 on: 30 November 2014, 18:55:30 »
PDF P. 16:
Ulsop attempted to reclaim control of the ship, using HPGs and command circuits to try and catch it before its jumps, but to no avail.

HPGs were not developed until 2630

Correction: remove references to HPGs
« Last Edit: 30 November 2014, 18:59:59 by lrose »

Kharim

  • Master Sergeant
  • *
  • Posts: 335
Re: Experimental Technical Readout: Boondoggles
« Reply #25 on: 24 December 2015, 17:01:25 »
About Ostscout IIC.

On page 3 in the second to last pragraph it says "...technicians used only standard heat sinks." Equipment section also states that the design uses 10 heatsinks.
However on the record sheet (page 20) under Heat Data section it is written that this mech has "10 (23) double heatsinks".

Which one is true?

Also n the record sheet the design appears to have standard cockpit and one slot Angel ECM.

mordel

  • Battletech Volunteer
  • Master Sergeant
  • *
  • Posts: 239
    • Mordel.Net
Re: Experimental Technical Readout: Boondoggles
« Reply #26 on: 25 March 2016, 17:53:05 »
LOCATION: Pg. 20 - Ostscout IIC Record Sheet (multiple errors)

ERROR: Record sheet does not have a Small Cockpit and Angel ECM incorrectly takes up only 1 critical slot when it should be 2.
CORRECTION: Add a Small Cockpit to the record sheet. Sensors will now be slot 4. The Angel ECM will occupy slots 5 and 6.

ERROR: Partial wing in the right torso is not grouped while the 5 jump jets are.
CORRECTION: Remove the grouping around the jump jets and place it around the 3 partial wing slots.