No replies to this topic

[HRR Insanity]

Checklist when making a new 'Mech:

Make sure the hitboxes are reasonable. PGI has consistently had to modify/tweak the hitboxes on most 'Mechs after release to make sure they aren't too squishy (or not squishy enough).

• Calculate the cross-sectional total area for each hitbox.
  
• Run a full spherical ray trace (1-2 degree arc spacing) to all points on the hitboxes to determine the total 'effective exposure' area of each hitbox (THE). Potentially weight the exposure by the direction relative to a pure perpendicular vector to the CT of the 'Mech (as in, when an enemy is shooting the 'Mech straight on from the front when firing at someone).
  
• Check to make sure the relative proportions of each hitbox's total effective exposure are appropriate for the size of the 'Mech and the overall concept for the 'Mech. Some variations would be expected, but when plotted vs. 'Mech size/weighclass, it should be possible to create a control chart showing when some hitboxes are way out of way relative to other 'Mechs of similar size/class.
  
• Check to make sure the ABSOLUTE exposure of the head hitbox isn't way out of wack by comparison to other 'Mechs. You can probably calculate the 'right' headsize based on other 'Mechs values of total hitbox exposure (THE).

Create an automatic weapon damage test:

Make sure there aren't unintended weapon damage changes. As the recent missile damage debacle illustrated, there is minimal QA occuring before patches are finalized.

• Create a custom test map that works in the 'live' codebase.
  
• Place a 'Mech to be tested on the map with full armor.
  
• Create a magical turret that can fire any weapon positioned at 2-3 distances (100m, 250m, 500m, 1000m) from each 'Mech' in concentric circles around the target 'Mech at 5 degree arcs.
  
• Fire test shots from each location at each hitbox on the 'Mech from all directions.
  
• Repeat for each 'Mech with all weapons.
  
• Database then has full damage testing for each hitbox for all weapons at a given range after every change.
  
• After each patch, re-run this test on each 'Mech. If weapon damage for any weapon/'Mech combination changes, confirm that this was an intended change.
  
• Also provides consistent detection of 'Mech hitbox/weapon interactions (such as the current missile debacle).