Author Topic: Technical Readout: 3145 Lyran Commonwealth  (Read 3005 times)

Moonsword

  • Global Moderator
  • Colonel
  • *
  • Posts: 13009
Technical Readout: 3145 Lyran Commonwealth
« on: 29 July 2013, 16:29:06 »
This thread is for all issues and problems with Technical Readout: 3145 Lyran Commonwealth.

Product Link: http://bg.battletech.com/?wpsc-product=technical-readout-3145-lyran-commonwealth

Please remember to follow the errata report template when reporting issues.  Thanks.
« Last Edit: 06 September 2013, 03:33:08 by Xotl »

Scotty

  • Alpha Strike Guru by appointment to the FWLM
  • Catalyst Demo Team
  • Lieutenant Colonel
  • *
  • Posts: 8278
Re: Technical Readout: 3145 Lyran Commonwealth
« Reply #1 on: 29 July 2013, 17:05:49 »
TRO3145 Lyran Commonwealth, pg. 27
The Weapons and Ammo section lists the base model as having two sets of three Flamers in the Left Arm.  The record sheets (and common sense) disagree with this.

Suggested fix:
Display one set of three Flamers in both the Right and Left Arms on the base model.
Catalyst Demo Agent #679

Kansas City players, or people who are just passing through the area, come join us at the Geekery just off Shawnee Mission Parkway for BattleTech!  Current days are Tuesdays in the afternoon and evening.  I can't make every single week, but odds are pretty good that somebody will be there.

S.gage

  • Corporal
  • *
  • Posts: 90
Re: Technical Readout: 3145 Lyran Commonwealth
« Reply #2 on: 01 August 2013, 17:30:29 »
P. 32, MGL-T1 Mongrel profile:
"Less than two years later gained popularity among younger Exiled Wolf MechWarriors." (missing subject in this sentence, "Less thank two years later it...")
Deployment section:
"Within two days of each other, the First Wolf Guardians landed on Borghese and the Fifth Bear Guards made planetfall on Fort Loudon."
"On Fort Loudon, the Fifth Bear Guards bid a single Star of T2-model Mongrels against seven Points from the Second Wolf Assault Cluster."
"On the Palisade Highlands, the Fifth managed to circle around to the Second’s weakened flank and surprise the Wolves with a brutal, point-blank assault." (in all cases, these prepositional phrases don't need a commas, should be past tense)

P. 42, ZEU-X4 Zeus X profile:
Variants section:
"It was also an ungainly hodgepodge of patchwork armor, reactive composites and counterintuitive short-range weapons whose limited production during the Civil War merely served propaganda." (oxford comma needed, subordinate clause requires a comma)
Notable Units section:
"In battle, his communications officer ensures the battalion’s battlefield coherency while Mündler is free to engage the enemy directly." (Prepositional phrase does not require a comma, subordinate clause requires a comma)
« Last Edit: 01 August 2013, 19:40:53 by S.gage »

chanman

  • Captain
  • *
  • Posts: 2180
  • Architect of suffering
Re: Technical Readout: 3145 Lyran Commonwealth
« Reply #3 on: 03 August 2013, 19:00:05 »
PDF P. 23 Kelswa Assault tank.

2 lines of the fluff from Lt. Carson Jones runs into the stat/art page.

Suggested fix: Trim two lines from the fluff. Most of Carson's write-up overlaps with the Deployment text anyway.

BaldDen

  • Private
  • *
  • Posts: 35
Re: Technical Readout: 3145 Lyran Commonwealth
« Reply #4 on: 04 August 2013, 15:19:56 »
PDF p.36 SCG-WF1 Scourge
In section "Armanent" missed designation of Medium Pulse Laser.

Suggested fix: Insert а line like "1 Defiance P5M Medium Pulse Laser"

dirty harry

  • Warrant Officer
  • *
  • Posts: 563
  • Make my day
Re: Technical Readout: 3145 Lyran Commonwealth
« Reply #5 on: 18 August 2013, 17:39:23 »
p.52 Notable Unit

Karmesinoter Hund doesn't make any sense.

Suggested fix:
Karmesinroter Hund

Wrangler

  • Lieutenant Colonel
  • *
  • Posts: 12565
  • Dang it!
Re: Technical Readout: 3145 Lyran Commonwealth
« Reply #6 on: 02 September 2013, 13:12:16 »
P. 32, MGL-T1 Mongrel profile:

Problem: All entries for the Dominion is listed as Rasalhague Dominion.  Since the MUL profile for the design came out, which shows that 'Mech was produced before 3103 (See 25 Years Art & Fiction p.29 Timeline - 3103), all entries for Dominion should be noted as Ghost Bear Dominion.  Not Rasalhague.


"Men, fetch the Urbanmechs.  We have an interrogation to attend to." - jklantern
"How do you defeat a Dragau? Shoot the damn thing. Lots." - Jellico 
"No, it's a "Most Awesome Blues Brothers scene Reenactment EVER" waiting to happen." VotW Destrier - Weirdo  
"It's 200 LY to Sian, we got a full load of shells, a half a platoon of Grenadiers, it's exploding outside, and we're wearing flak jackets." VoTW Destrier - Misterpants

Xotl

  • Deus Errata et regulas Exsecutor
  • Moderator
  • Lieutenant Colonel
  • *
  • Posts: 7813
  • Professor of Errata
Re: Technical Readout: 3145 Lyran Commonwealth
« Reply #7 on: 06 September 2013, 03:35:29 »
p. 22, Kelswa Assault Tank, first Notable Units entry:

A native of Glengarry, Kilcracken was placed on administrative leave following withdrawal of Lyran troops Hesperus.
Change to:
A native of Glengarry, Kilcracken was placed on administrative leave following the withdrawal of Lyran troops from Hesperus.

Generally absent from the forums at this time.

3028-3050 Random Assignment Tables -
Also contains faction deployment & rarity info and Quirk lists.

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

jymset

  • Infinita Navitas
  • Freelance Writer
  • Lieutenant
  • *
  • Posts: 1327
  • the one and only
Re: Technical Readout: 3145 Lyran Commonwealth
« Reply #8 on: 03 October 2013, 18:02:46 »
dev-level errata:

Gulltoppr, p. 24
Armor: replace "Star Slab/3H Hardened with CASE" with "Star Slab/3 with CASE"
Capabilities delete the word "hardened" in the fourth line

Gulltoppr, p. 25
delete "(Advanced)" from Technology Base
delete "(Hardened)" from Armor Factor, replace total "352" with "704". The Armor Values are in order:
136
104/104
90/90
64
66
50
add "--Advanced" behind "Primary Configuration" and "Configuration B"

Note BV stays identical.

Modify RS on pp. 77-79 accordingly.
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.

Pa Weasley

  • Freelance Writer
  • Major
  • *
  • Posts: 5509
  • Spotted near Lake Springfield.
Re: Technical Readout: 3145 Lyran Commonwealth
« Reply #9 on: 31 May 2014, 00:03:39 »
p.37 & p.95 (record sheet)
SCG-WF1 Scourge
BV: 2,172

p.90 MGL-T2 Mongrel
BV: 1,949

DarkISI

  • Praedonum Dominus
  • Freelance Writer
  • Major
  • *
  • Posts: 5143
  • Schattengalaxis - Trügerischer Frieden
    • My Author Website
Re: Technical Readout: 3145 Lyran Commonwealth
« Reply #10 on: 31 May 2014, 05:24:31 »
FYI:
Those new errata values are dev-level errata made necessary by the AES BV change. (Pa Weasly has taken over BV calculations from me, so I can focus on necessary rules changes, like this one, and new rules. Thank you for that :))
« Last Edit: 31 May 2014, 05:27:10 by DarkISI »
German novelist and part time Battletech writer.



"if they didn't want to be stomped to death by a psychotic gang of battlemechs, they shouldn't have fallen down" - Liam's Ghost

Maelwys

  • Major
  • *
  • Posts: 4029
Re: Technical Readout: 3145 Lyran Commonwealth
« Reply #11 on: 11 March 2016, 18:39:16 »
Pg. 100 ZEU-X Zeus-X Record Sheet

The record sheet only has 8 Reactive armor criticals assigned to the design. Add 1 to the CT, 1 to the head, 2 to the RA, and you'll need to remove the lower arm actuator on the LA so you can slide the LB20-X up a slot, and add 2 criticals to the LA as well.

Pg. 101 ZEU-X2 - The record sheet only has 8 reactive armor criticals assigned to the design. Add 2 to the RA, 2 to LA, 1 to CT and 1 to HD.

The BVs on both should probably be checked as well, but they're different on the MUL already, so that might have happened already.

pg. 102 ZEU-X3 - Not really an error per se, but the arm weapons are on opposite sides from what they were in the original MDA Record Sheet book. Not necessarily an error, but considering the problems with the first 2 Zeus-X designs, I figured I'd mention it just in case.
« Last Edit: 11 March 2016, 18:58:48 by Maelwys »

jymset

  • Infinita Navitas
  • Freelance Writer
  • Lieutenant
  • *
  • Posts: 1327
  • the one and only
Re: Technical Readout: 3145 Lyran Commonwealth
« Reply #12 on: 11 March 2016, 19:15:06 »
Can't comment on BV at this time.

ZEU-X/2 don't share the-X4's full reactive armor. They feature patchwork armor and only the limbs have reactive armor, with current crit nos per TacOps.

The ZEU-X3 is a correction and overrules the older sheet.
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.

mordel

  • Battletech Volunteer
  • Sergeant
  • *
  • Posts: 184
    • Mordel.Net
Re: Technical Readout: 3145 Lyran Commonwealth
« Reply #13 on: 27 February 2017, 21:38:44 »
Pg. 100 Zeus-X ZEU-X
The design is 3 tons overweight. How to fix it might need discussion. Perhaps drop a ton of LB ammo and an X-Pulse? Can also drop two points of armor off each of the arms, legs and left/right torsos.

Pg. 101 Zeus-X ZEU-X2
The design is 2 tons overweight. How to fix it might need discussion. Perhaps drop an X-Pulse? Could also play with armor values.

mordel

  • Battletech Volunteer
  • Sergeant
  • *
  • Posts: 184
    • Mordel.Net
Re: Technical Readout: 3145 Lyran Commonwealth
« Reply #14 on: 27 February 2017, 21:50:58 »
Pg. 100 Zeus-X ZEU-X
The design is 3 tons overweight. How to fix it might need discussion. Perhaps drop a ton of LB ammo and an X-Pulse? Can also drop two points of armor off each of the arms, legs and left/right torsos.

Pg. 101 Zeus-X ZEU-X2
The design is 2 tons overweight. How to fix it might need discussion. Perhaps drop an X-Pulse? Could also play with armor values.

Just to add. I think the issue is because the original designs had Reactive armor instead of Patchwork. Switching it should correct both issues (or at least it did on the ZEU-X, I didn't check the ZEU-X2)

neoancient

  • Warrant Officer
  • *
  • Posts: 417
  • MegaMek team member
Re: Technical Readout: 3145 Lyran Commonwealth
« Reply #15 on: 20 September 2017, 10:31:28 »
I've been working on the patchwork armor code in MML and looking at the Zeus-Xs with patchwork as part of my testing. I believe the weight problems with the ZEU-X/X2 are rounding errors from the patchwork armor. If you calculate the armor tonnage based on total number of armor points the tonnage allocated to weight is correct. However patchwork armor is rounded up to the half-ton in each location. If the armor points are shifted around so to multiples of 8 in each location the weight problem is solved.

mordel

  • Battletech Volunteer
  • Sergeant
  • *
  • Posts: 184
    • Mordel.Net
Re: Technical Readout: 3145 Lyran Commonwealth
« Reply #16 on: 21 September 2017, 09:24:37 »
I've been working on the patchwork armor code in MML and looking at the Zeus-Xs with patchwork as part of my testing. I believe the weight problems with the ZEU-X/X2 are rounding errors from the patchwork armor. If you calculate the armor tonnage based on total number of armor points the tonnage allocated to weight is correct. However patchwork armor is rounded up to the half-ton in each location. If the armor points are shifted around so to multiples of 8 in each location the weight problem is solved.

So, this is not how it's done, though reading TO it still appears to be written ambiguously. I had this discussion with some CGL folks a while back though I can't find the thread (maybe it was in the TO errata thread but is gone because Errata was published since then). The way patchwork is suppose to work is you add up all the points of a given armor type on the unit, and then calculate the weight. This is supported by the various designs out there that use patchwork armor. In TO, there was once a sentence that read "This is done per location, with excess points per location discarded." It was removed because the weight calculation is not done by location. I can see where it's still ambiguous because it still says "...the number of points assigned to the location..."

It really should be raised in the TO errata thread again.

 

Register