Professional Documents
Culture Documents
MechWarrior Missions
MechWarrior Missions
MechWarrior Missions
Riot Duty – Somewhat similar to garrison duty, but larger groups of ‘Mechs will appear, and you’ll be
paid more. You gotta get ‘em all to complete the mission.
Reconnaissance Raid – You have to locate and collect a specific object on the planet while fighting off
enemy ‘Mechs.
- Ammo stash, detonator to disarm explosives, stolen property, retrieve goods, supplies, LosTech,
cash stash, stolen cash, secret plans,
Objective Raid – One step up from recon raids. The objective is still to collect something, but there’ll be
more ‘Mechs in your way this time, and of course the pay is better.
Planetary Assault – Enemy ‘Mechs are trying to get into a base, and you gotta stop ‘em all. If just one
gets in or if the base gets destroyed, you’ve failed in your mission.
Offensive Campaign – Same as a planetary assault, but there’ll be more ‘Mechs and higher pay.
Security Duty – Protect a base from attack ‘Mechs. You’ll have to destroy them all, and make sure the
base doesn’t get destroyed in the process.
Siege Campaign – You have to locate and destroy an enemy base. It’s protected by ‘Mechs, of course,
and you’ll have to deal with those, too.
https://gamefaqs.gamespot.com/snes/588475-mechwarrior/faqs/24091
Infiltration Scenario: The infiltrating ‘Mech must pass by enemy troops without alerting them to his
presence.
- The infiltrators know when to move and how to move to avoid the defenders. The attacker
(infiltrating team) always wins initiative until they are detected, at which time normal initiative
resolves.
- The defenders are on patrol, making sure the area is clear of invaders, but occasionally failing to
check certain locations The defending troops roll on the ‘Facing After a Fall’ table and move
their full walking MP in the direction indicated (if the unit would exit the map or otherwise make
an illegal move, the unit stops).
- If a defending unit has one or more of the attackers in it’s forward arc, has LOS, and has at least
one weapon with the range to hit the attacker, the defender may make a scanning check (follow
all the normal rules for making an attack, using the longest range weapon). If the scan is
Mission Type Scenario Modifier
https://bt.dylanspcs.com/contracts.php
MISSION TYPES
Regardless of whether or not they are handled through the MRBC, mercenary missions are generally classified as
defense, raids or assaults, indicating their overall intent. A fourth category includes covert operations, but generally
such missions are highly sensitive and often require mercenary commands with a loose code of conduct to carry out.
For this reason, Outreach and other MRBC-approved hiring halls do not sanction many covert missions. The twenty
mission types defined below are recognized by hiring halls across the Inner Sphere and Periphery.
Houserule: Roll 1d6 to determine the number of scenarios the mission will run. Add the Mission Difficulty Modifier
and the Mission Type modifier to the number of scenarios to be played.
Retainer (Defense)
Retainer contracts place a mercenary command at the employer’s beck and call for a designated period, during which
time it may be called upon for unspecified defensive missions that can range from relief to riot duty and even mole-
hunting. The rest of the time, the mercenary force performs standard garrison duty. Retainer contracts typically run
two years, and employers traditionally pick up full transportation costs and reimbursement for out-of-pocket expenses
incurred. Pay is average, with a ten- to twenty-percent bonus if and when combat occurs.
EMPLOYMENT AND CONTRACTS
Riot Duty (Defense)
The most unsavory of all defensive missions, riot duty involves using heavy assets against civilians. Under the Ares
Conventions, such action is only allowed if the civilian targets are engaged in activity that is demonstrably harmful to
a legal, internationally recognized government or civil authority. Furthermore, the conventions prescribe that riot-
control troops use the minimum force necessary at all times. For these reasons, many mercenary commands refuse
riot duty unless they have trained infantry occupation forces. Riot duty does not pay well, and contracts run a
minimum of three months.
Extraction (Raid)
Extraction raids, commonly known as “smash-and-grabs,” are nearly identical to objective raids. In an extraction raid,
however, the mercenary group must capture a target and return it to the employer. Understandably, extraction raids
that target people often become complicated if the target resists. In fact, if a mercenary unit extracts a hostile target
who has no demonstrable military value, the unit, as well as the employer, may be charged with kidnapping and may
be legally compelled to repatriate the target. Most employers are willing to accept such risks, however, because the
extractions of key enemy leaders can severely cripple an opposing force, especially if the extraction is timed to occur
immediately prior to a major raid or assault by or against the enemy. Extraction raid contracts usually run a minimum
of three months but may last considerably longer depending on the complexity and secrecy surrounding the mission.
Similarly, pay may vary greatly, depending on the danger involved and the contract length.
YMENT AND CONTRACTS
Garrison (Defense)
Running anywhere from one to five years, garrison duty is considered “gravy time” by most mercenary commands. A
unit on garrison assignment may guard anything from a facility to a planet, defending against hostile raiders or even
assault forces. Garrison duty on interior worlds frees up regular troops for hostile action. On border worlds, where
combat is a real threat, garrison units maintain a fairly strict order of readiness and receive combat bonuses in the
event of military action.
Cadre (Defense)
Cadre, or training, duty is possibly the lightest duty of all. Generally, a unit on cadre assignment trains corporate
security personnel or a local planetary militia in combat tactics. Cadre duty is usually combined with a garrison
contract when possible; larger mercenary units frequently detach and deploy a part of their forces (from a single lance
to an entire company) on cadre duty while the rest of the unit is employed in another fashion. Normally, cadre
contracts last from six to twelve months.
https://bg.battletech.com/forums/index.php?topic=15085.0 Money
Contract theme and pacing goals:
Guerrilla: 12-24 month contract, frequent convoy assaults/defences and patrol
ambushes. Only salvage is that you can drag off the battlefield, likely low levels of
BLC and Support. Low chance of Base Assault to push the foe off Planet. 1-4 battles
per fortnight.
Recon Raid: 4-8 month contract, frequent probing attacks and recon w/ the odd light
patrol/convoy capture for the first 2/3's of the contract. Last 1/3 of the contract
would be comprised of last minute recon, stand up battles and etc. High possibility
to culminate in a final base defence upon withdrawal/contract end. 1-3 battles per
week.
Pirate Hunting: 16-30 month contract, low monthly payout but fairly average total.
Starts out with recon, convoy assaults, stand up battles and withdrawing battles.
After 6-8 months starting rolling to locate Pirate Base to assault, after said battle
roll to determine if the Pirates have another base and if so continue as before until
the roll determines they have been wiped out/captured or the contract ends. Rich in
low quality salvage, although pirates will launch counter-raids to steal back their
personnel/stuff/loot. 0-2 battles per week.
Planetary Assault: 6-12 month engagement, high risk but high payout, BLC and Support.
Generally consists of heavy fighting, secondary base assaults and patrols. High
possibility of culminating in final Base Assault depending on the performance of the
player Unit, if engaged in said final push then there will be a heavy Allied presence.
Reasonable salvage with approximate exchange for tech not produced by the
employer, base chassis may be kept but rare tech will be sought after. 3-5 battles
per week.
Objective Raid: 2-6 month contract, reasonable to high risk with decent Support and
BLC, Has a high probability to follow on from a Recon Raid and mostly consists of
whittling down the objectives defences before a final Base Assault. Salvage should
be fairly good but will mostly consist of that which can be carried off the battlefield,
only heavy engagements (Stand Up battles and etc) should give the chance to
recover all possible salvage. High possibility of the Objective being shared with the
Player's Unit. So roll against a table to determine what the raid is for and how
much, if any, the employe will reward the Player with. 2-4 battles per week.
Extraction Raid: 2-6 months, generally high risk and a good payout. Support is typically
low but BLC is generally high to offset the risk. Plays out as a reverse Planetary
Assault and tends to start with a Base Assault, followed by every battle there after
being fought with optional withdrawl. Salvage will only be as much as you can drag
off the battlefield, high chance of player contract rewards including new Units from
the employer. Also high possibility of the extracted asset(s) being shared with the
player, so roll on a table to determine the extraction details and how much/many is
to be extracted. Also roll the type of goods transporting it and roll against every
mission to see if the transports (or the goods itself, if stolen 'mechs) are present on
the battlefield, if so adjust mission rewards and subtract a fine for how much of the
extracted assets is lost. 2-6 battles per week.
Garrison: 6-24 months, risk determined by a second contract roll to find out the enemy
objective. Treat a roll of Pirate Hunting as Rebels/Civil Unrest, support and BLC
determined via the OpFor contract type. Good chances for salvage due to the Player
being on "home soil" and fighting a generally defensive battle, although plenty of
counter-attacks as well. Decent possibility of the contract OpFor being defeated
early via a Player Base Assault or their contract length ending, if that happens roll
to determine if there is another attack during the contract and generate a new
enemy contract type. Player pay stays the same, but an extra bonus will be rolled
for each subsequent OpFor that attacks during the contract. Also roll to determine if
the employer opens their stores to the Player's Unit during the course of the
battle. Battles determined by OpFor contract weekly average, Rebels/Civil Unrest,
however, is 2-4 per week.
Cadre: 6-24 months, minimal risk although contract event should allow for the
contract to change to an active combat contract via special event rolls. Otherwise
roll again to determine the type of engagement the Player's Unit will be simulating
for the training, this will be rolled again every six months. Due to the type of
contract this is, the only salvage will come from special event rolls (Officer and Ace
duels will be considered pink slip battles between instructors) or the contract
turning into another type via an event roll. Due to the fact it's a training assignment
and there is minimal salvage chances, the employer will likely issue new weapons
to the Unit each month to increase the type of loadouts used against their
forces. Battles per week decided by simulated contract type.
Relief Duty: 6-8 months, moderate to high risk. Roll the contract again to find out the
type of contract you are the Relief Duty for and if you are aiding the attacking or
defending force, salvage will depend on the contract type but is generally harder to
acquire especially if aiding an attacking force. Contract rewards should include new
potential recruits from the force you relieved and possibly new units, aside from
those of the potential recruits. Battles per week determined by contract type being
relieved, but is always +2 to the upper and lower limits to reflect the need for a
Relief force.
Goals:
1: Provide a more narrative feel to the campaign and give each contract more personality beyond just
required Lance and make battles feel more connected and relevant.
2: Allow more choice in missions and forces used, giving a framework for nonstandard support (aero,
artillery, mines, fun toys). Allow more player determined strategy by separating player forces from opfor
generation.
3: Limit Salvage instead of assuming unlimited time for salvage operations, but give options to work
around this.
4: Flesh out some Officer Skills and Admin roles and make them have a little more impact during a
contract. (Make Strategy and Leadership actually impact something rather than being company size
gates.)
5: Streamline and centralize weekly cycles a bit to remove as much cross referencing as possible.
Civil Disturbance – Local riots and small-scale agitation take place. On a 2d6 roll or 2 or 3, the player characters
must undertake a campaign against a regiment of locals (likely infantry, but possibly some vehicles as well).
Otherwise, the disturbances have no particular impact on the unit.
Sporadic Uprisings – Substantial civil uprisings sweep the planet. A 2d6 roll of 2 – 8 causes an active campaign
against 1d6 local regiments (likely infantry and possibly some light vehicles as well). Otherwise, the disturbances
die out without the unit’s intervention.
Rebellion – The local populace erupts in widespread resistance to the government. Regardless of original
assignments, the unit and its supporting troops are placed on riot duty. Add any rebel troops generated to enemy
forces deployed against the unit.
Betrayal – The mercenaries have been betrayed by their employer. Perhaps all House troops accompanying the
unit are withdrawn, promised supplies and transports are not delivered, or false information regarding the nature
of the mission and the size of the enemy forces facing the unit was provided.
Treachery – The unit is betrayed into the enemy’s power by self-seeking individuals in positions of trust. Mostly
this is restricted to false intelligence about enemy strength and intentions (secretly add enemy forces to the table
that are only revealed when the battle begins), but it could also include the destruction of money for supplies or
repair, an assassination attempt against the unit commander, sabotage of the unit by the enemy, or other
nefarious schemes.
Logistical failure – Bureaucratic snarls, enemy action, profiteering, and other outside interference causes problems
with supply shipments.
Attrition – A natural disaster, disease, or other crisis causes casualties to the unit and is unconnected with enemy
actions.
Sinkholes: Roll 2D6 for the first clear hex each ’Mech
enters during a turn while using Running MP. If the roll is a 10 or
greater, a sub-level 1 sinkhole opens beneath the unit. The player
must then make a Piloting Skill Roll with a +1 modifier for that
unit to avoid falling into the hole. Players should mark that hex for
future reference.
+100 Dawn/Dusk: Apply a +1 to-hit modifier to all weapon attacks. For
every 25 points of heat—on a target unit that tracks heat—apply
a –1 to-hit modifier to any weapon attacks directed at that unit.
Ice Holes: Roll 2D6 for the first clear hex each ’Mech
enters during a turn while using Running MP. If the roll is a 10
or greater, a sub-level 1 hole opens beneath the unit. The player
must then make a Piloting Skill Roll with a +1 modifier for that
unit to avoid falling into the hole. Players should mark that hex for
future reference.
Earthquake
At the beginning of every turn (starting with Turn 2), roll 2D6.
On a result of 10 or higher, a tremor with a strength value of 4
shakes the battlefield. Players must make a Piloting Skill Roll for
each standing ’Mech they control at the start of each Movement
Phase during the tremor. If the Piloting Skill Roll fails, the ’Mech falls
and takes damage per standard rules. If the Piloting Skill Roll result
equals 2, a fissure may open up beneath that ’Mech. Make a second
roll and check the Basements Table (see p. 179, TW) to determine
if one opens and the fissure’s depth. The ’Mech will fall into the
fissure the same way it would fall into a basement. Treat the fissure
as a permanent map feature for the remainder of the track.
Additionally, apply a +4 modifier to all Piloting Skill Rolls and
any Weapon Attacks made during the same turn as the tremor.
The Earthquake only lasts one turn. Once it has passed, no
further rolls need be made.
Four-legged ’Mechs: For four-legged ’Mechs, the Piloting Skill
Roll modifier equals half the strength value of the tremor (their
extra legs provide improved stability). The standard –2 Piloting
Skill Roll modifier for four-legged ’Mechs applies as well. The
earthquake only lasts one turn. Once the earthquake occurs, no
more checks are to be made.
Eruption
Beginning in turn 6, roll 2D6 at the start of the turn. If the roll is 8
or greater, the volcano begins to erupt. For each subsequent turn
beyond 6, add +1 to the roll.
For example on turn 8, a check is made rolling 2D6. A
player rolls a 7. Adding +2 to the roll (it is now two turns beyond
6, which equates to a +2 modifier), the modified roll is now a 9,
which indicates the beginning of the eruption.
During the first turn of the eruption, the player that won
initiative selects one unoccupied hex on the playing area. He then
rolls 2D6; on a roll of 6 or more, that hex dissolves into magma.
Any unit within a two hex radius receives 10 points of damage,
assigned in groups of 5 to the facing of the attack and receives an
additional 2 heat points for the turn.
The player that lost initiative may then select a hex and repeats
the process.
For each additional turn the game continues during the
Eruption phase, each player may select another unoccupied hex.
For example, four turns after the eruption begins, both players
select four hexes for possible magma geysers.
Each hex that dissolves into magma takes on the properties
of magma (see below) and ignores its previous terrain feature,
though it retains its current height.
RA/wb
Combat pauses for a brief second as a massive tremor shakes the battlefield on Rigil Kentarus.
Magma
Any unit that is not a ’Mech that enters a
Magma Liquid hex is automatically destroyed
(it cannot be salvaged in any way). For hover,
VTOL and WiGE Vehicles in such a hex, if they
touch the ground of the hex for any reason (landing,
damage and so on), they are automatically destroyed.
’Mechs that start their Movement Phase in a Magma Liquid hex,
or enters a hex at any point, take 2D6 points of damage to each
exposed location immediately upon entering the hex. If the ’Mech
is moving normally, its legs constitute its exposed locations; if the
’Mech falls, all of its locations are exposed. Make separate damage
rolls for each location; regardless of how much damage is rolled,
it is considered only a single attack. A unit that starts and ends
a Movement Phase in a Magma Liquid hex takes an additional
2D6 of damage to its exposed locations; again, make a separate
damage roll for each location, but this roll is considered a unique
attack from the original 2D6 damage roll.
’Mechs that occupied a Magma Liquid hex (but do not occupy
it during the Heat Phase) generate 5 additional Heat Points in
that turn; occupying a Magma Liquid hex during the Heat Phase,
generates an additional 10 Heat Points that turn.
Entering a Magma hex takes one additional Movement Point.
Any unit in a Magma hex suffers from a +4 modifier to their
Piloting Skill Roll.