Register Register

Author Topic: (Answered) AToW Companion Expanded Hit Locations funkyness #2  (Read 2838 times)

Acolyte

  • Lieutenant
  • *
  • Posts: 1475
Blagh, sorry. Another few issues just came up.

1. On the Lower Arm chart, it has both Hand and Arm locations on it and the Lower Leg has the Foot and Leg on it. So, if you have different armor values, which do you use?
   a. The Hand or Foot?
   b. The Arm or Leg?
   c. The location as rolled? If you use this one or , it becomes very hard to hit the Forearm if you have good armor due to the - 2 sub location roll. Also true of the one above.
   d. Use the location rolled (doesn't move) but apply the multiplier and effects from the modified location?

2. Lower torso hit chart. The -2 roll modifier for having good armor may make things worse. On a 4 or 5, it becomes a 2 or 3. The multiplier goes up in both cases, although the 4 becoming 2 does remove the Fracture. So really, just the 5 becoming 3 increasing not only the multiplier but retaining the internal bleeding.

Thank you!
   - Shane
« Last Edit: 26 November 2018, 16:54:32 by Xotl »
It is by caffeine alone that I set my mind in motion
It is by the coffee that my thoughts acquire speed
My teeth acquire stains
The stains become a warning
It is by caffeine alone that I set my mind in motion.

Xotl

  • Dominus Erratorum
  • Moderator
  • Lieutenant Colonel
  • *
  • Posts: 10969
  • Professor of Errata
Re: AToW Companion Expanded Hit Locations funkyness #2
« Reply #1 on: 31 March 2017, 19:50:09 »
Bumping this for Paul.
3028-3057 Random Assignment Tables -
Also contains faction deployment & rarity info.

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

Paul

  • dies a lot at the Solaris Melee Challenge!
  • BattleTech Volunteer
  • Colonel
  • *
  • Posts: 15058
Re: AToW Companion Expanded Hit Locations funkyness #2
« Reply #2 on: 02 April 2017, 11:05:58 »
1: C, though I'm not understanding what you're saying under D.

2: I don't see the question here?

(Also, please mention a page ref for convenience next time. :p )

Paul
The solution is just ignore Paul.