(This is just a quick copy-paste of an old document. If you prefer to see it in its original HTML glory, go here and hit “file” then “download.” -SkilTao)

Every so often on the forums, somebody asks for suggestions about what to put into the Fluff for a 'Mech or vehicle or what-have-you.  It hasn't happened in a while, but I happened to be taking notes from tro3025 over winter break anyways, and I thought a guide might be helpful.  Unfortunately, it's choppier and much longer than I wanted; but since I'm not motivated enough to refine it, without further ado, I give you:

How To Write Fluff-Text

based on tro3025

You are morally obligated to make puns, mock irregularities in the rules (ex, SRM 6 ammo), explore areas not covered by the rules, and to introduce equipment and abilities and skills that contradict normal game rules.  Sprinkle meta-plot to taste; but the text should be heavier on details that help establish the universe setting.  Only try to hit about half the bullet points for each section, and don't repeat information from previous sections (but do have details that connect to information in other sections).

Overview

This section consists of brief statements that are expanded on in later sections.  Alternatively, if the fluff-text is exceptionally short, it can all be mashed together under the "Overview" heading.  But usually it should contain:

Production Information:

•   the design’s intended role, inspiration (if any), and specifications

•   The original patron, manufacturer, and competing manufacturers

•   Begin and end dates for production, factory sites, extent of deployment, and future use

•   Judge if it fulfills specifications and its intended role, and name any acquired roles

•   Note design flaws both in previous versions and in current version

•   Comment on reliability of choice components

•   Note nickname, if it isn’t based on a particular design feature or battle

Capabilities

These five sections are not an outline – mix and mash them together.

General Description:

•   Compare physical appearance, size, profile, and layout to other designs

•   Note maneuverability, and explain with chassis design or ASF guidance systems

•   Note general ease of use, maintenance, and repair

•   Explain the design’s reputation, and note a nickname if it derives from a specific feature

•   Note the design’s most distinguishing feature

Firepower, armor, and mobility:

•   Compare these to contemporary vehicles with the same role

•   Describe combat against vehicles of similar and different mass

•   Use intended role and design limitations to justify strengths and weaknesses

•   Note how certain characteristics encourage or discourage a secondary role

•   Note any companion vehicles it may need

Weapon Use

•   Describe the design’s arsenal, as well as its prowess in melee combat

•   Relate typical attack tactics and expected effects

•   Remark how heatsinks relate to weapon use

•   Note fuel and ammo endurance

•   Note how firepower degrades as damage is sustained

Artwork

•   If it is at least 50 tons, be sure to mention “heavy” or “massive” battle fists

•   If it is at least 50 tons but replaces a hand with a large weapon (autocannon, large laser, etc), then mention that the barrel is in a “shock sleeve” or, for missiles, built around a “punch core.”  Alternatively, discuss how the weapon is often “knocked out of alignment.”

•   Arm-mounted Large Lasers, PPCs, and ACs almost never leave a hand free; they either replace actuators or are held in pistol mounts

•   Describe abnormalities in the art as innovations or as flaws

Item Quirks:

•   Note if the design shares any parts or problems with other designs

•   Note any legends, myths, tall tales, or engineering reports relating to one of the ‘Mech’s features

•   Weapon subsystems include targeting computers, stabilizers, barrels, cooling jackets, ammo feeds, power lines, recoil compensation, shell size, beam size, rate of fire, specialty ammo, and weapon exhaust

•   Detail any flawed or exceptional components; besides the items that normally appear in the TRO, you can also discuss life support, ejection systems, the omni-coupling (where power and coolant lines hook up to the ‘Mech), sensors, battle computers, guidance or navigational systems, landing gear, crew accommodations, armor baffles, air intakes, actuator/rotor/hoverskirt/track design, etc

Battle History

“Deployment” is the first paragraph under this heading; if the unit is too new to have been used in battle, use "Deployment" as the section heading instead of "Battle History."  If the vehicle was designed after the Fall of the Star League, one of the two battles should be the first time it was used in combat.

Deployment:

•   Note who uses the design and in what numbers during each era

•   Note current production status (factories, parts availability)

•   Describe where, in what formations, and with what mates the design tends to deploy

•   Note when and where other factions capture the design, and if they use them in combat

•   Optional: Note prestigious units that use the design, what role, and give a brief example

•   Optional: say how desirable the design is, and why

Two Battles:

•   Required: Identify the battle with either planet and year, or as “The Great Lee Turkey Shoot”

•   Name the factions involved and the mission’s type or objective

•   Note the vehicles and formation sizes involved (optional: name the combat units)

•   State the design’s part in the battle, demonstrating a strength or weakness or other characteristic noted in "Capabilities"

•   State casualties, objectives achieved, effect on subsequent battles and reputation

•   Optional: describe mistakes, misfortunes, terrain, tactics, traps, daring attacks, hasty retreats, bold moves, colorful adjectives, and unique unit variants seen only in this story

Variants

If the base design has a design flaw, there will be a variant that attempts to correct it.  Most designs should have one or two variants – and it is fine to describe a group of related variants in broad, generic terms.

•   Note who produces the variant and why

•   Note how common and how popular the variant is

•   Note whether it is a factory variant or a field refit

•   Note if the change over-taxes the targeting system or causes other problems

•   Compare technology in the refit to technology of the original design

Notable ‘Mechs and MechWarriors

List 1-3 notable ‘Mechs and MechWarriors (or Fighters and Pilots, Vehicles and Crews, etc); Usually one of the Notables has some connection to the Battle History.

•   Required: Give the pilot’s name, nickname, and assignment (lance, regiment, faction)

•   Required: Describe the pilot’s experience, kill count, health, and a notable battle

•   Required: Note any promotions, demotions, reassignments, or chances to change vehicles

•   Optional: state the vehicle’s name (puns encouraged), origin, and current condition

•   Optional: describe the pilot’s reaction to any information in the TRO

•   Optional: describe the pilot’s appearance, personality, motives, or habits