30 Minute Missions: Wargame - User contributions [en]

AAR:Operation First Test

2026-04-27T01:05:29Z

Lavtiz29: added teh category

Operation First Test

'''Date:''' 4/25/26

== Teams ==
'''Team 1:'''
* Portanova
** DC:
** System:
** Mods:
** Traits:
** Equipment:
* Dog
** DC:
** System:
** Mods:
** Traits:
** Equipment:
'''Team 2:'''
* Alto
** DC:
** System:
** Mods:
** Traits:
** Equipment:

== Deployment: ==
[[Core Rules#Deployment Areas|Long Side Deployment]]
== Mission:==
[[Core Rules#Core Missions | Control Points]]

== Pre Turn: ==

Team 1: Rolled 3

Team 2: Rolled 2

Team 1 wins initiative.

=== Report ===

I don't have the time or energy to do a proper play by play.

Basically the alto flew in the air, and kept shooting with a gatling gun while the portanova shot back with a shotgun.
neither side killed the other, also the dog was in the back racking up points because *someone* didn't put secondary objectives on the fucking rules so I could test them. So I lost because of being unable to kill the portanova and not moving. Which was stupid of me I realize.

I did get to use both Double tap and whatever improved critical hit traits. That came up a grand sum total of once and I did one extra hit. Still didn't' kill them because I basically couldn't do enough damage because of the cost of the Military weapon gatling.

Outside of this and my own stupidity. I realized that the longest thing we did was figuring out stats and building the units. (Also fiddling with the gatling gun, I could just not get the model to hold it properly.) The game was phenomenally short without the setup. I believe with changes to my cards to be modified stats of associated Units instead of just basic numbers that could improve the overall speed of building. Also I have not included Dog weapons in the equipment of the dog. This will need to be remedied.

[[Category:After Action Reports]]

AAR:Operation First Test

2026-04-27T00:06:40Z

Lavtiz29: Minor Edits to make this slightly more readable

AAR:Operation First Test

2026-04-26T23:29:07Z

Lavtiz29: Created page with "Operation First Test '''Date:''' 4/25/26 == Teams == '''Team 1:''' * Portanova ** DC: ** System: ** Mods: ** Traits: ** Equipment: * Dog ** DC: ** System: ** Mods: ** Traits: ** Equipment: '''Team 2:''' * Alto ** DC: ** System: ** Mods: ** Traits: ** Equipment: == Deployment: == Long Side Deployment == Mission:== Control Points == Pre Turn: == Team 1: Rolled 3 Team 2: Rolled 2 Team 1 wins initi..."

Operation First Test

'''Date:''' 4/25/26

== Teams ==
'''Team 1:'''
* Portanova
** DC:
** System:
** Mods:
** Traits:
** Equipment:
* Dog
** DC:
** System:
** Mods:
** Traits:
** Equipment:
'''Team 2:'''
* Alto
** DC:
** System:
** Mods:
** Traits:
** Equipment:

== Deployment: ==
[[Core Rules#Long Side Deployment |Long Side Deployment]]
== Mission:==
[[Core Rules#Control Points | Control Points]]

== Pre Turn: ==
Team 1: Rolled 3
Team 2: Rolled 2
Team 1 wins initiative.

=== Report ===

I don't' have the time or energy to do a proper play by play.
Basically the alto flew in the air, and kept shooting with a gatling gun while the portanova shot back with a shotgun.
neither side killed the other, also the dog was in the back racking up points because *someone* didn't put secondary objectives on the fucking rules so I could test them. So I lost because of being unable to kill the portanova and not moving. Which was stupid of me I realize.

I did get to use both Double tap and whatever improved critical hit traits. That came up a grand sum total of once and I did one extra hit. Still didn't' kill them because I basically couldn't do enough damage because of the cost of the Military weapon gatling.

Outside of this and my own stupidity. I realized that the longest thing we did was figuring out stats and building the units. (Also fiddling with the gatling gun, I could just not get the model to hold it properly.) The game was phenominally short without the setup. I believe with changes to my cards to be modified stats of associated Units instead of just basic numbers that could improve the overall speed of building. Also I have not included Dog weapons in the equipment of the dog. This will need to be remedied.

Template:WeaponSidebar

2026-04-26T00:50:38Z

Lavtiz29: reverting to old version before shenanigans

<div class="infobox">
<div class="infobox-title">{{{title|{{#if:{{{Name|}}}|{{{Name}}}|{{PAGENAME}}}}}}}</div>
{{#if:{{{WeaponImg|}}}|
<div class="infobox-image">[[File:Filename.{{{WeaponImg}}}|225px]]</div>}}
<table class="infobox-table">
<tr>
<th>Durability:</th><td>{{{Durability|}}}</td>
</tr>
<tr>
<th>Range:</th><td>{{{Range|}}}</td>
</tr>
<tr>
<th>Base Damage:</th><td>{{{BaseDamage|}}}</td>
</tr>
<th>Action Point Cost:</th><td>{{{AP|}}}</td>
</tr>
<tr>
<th>Damage Type:</th><td>{{{DamageType|}}}</td>
</tr>
<tr>
<th>System:</th><td>{{{System|}}}</td>
</tr>
<tr>
<th>Tags:</th><td>{{{Tags|}}}</td>
</tr>
<tr>
<th>Deployment Cost:</th><td>{{{DeploymentCost|}}}</td>
</tr>
</table>
</div>
</div>

<noinclude>
<pre>
{{WeaponSidebar
| Name =
| WeaponImg =
| Durability =
| Range =
| BaseDamage =
| AP =
| DamageType =
| System =
| Tags =
| DeploymentCost =
}}
</pre>

[[Category:Template]]</noinclude>
[[Category:Weapons]]

Weapons

2026-04-26T00:38:31Z

Lavtiz29:

{|
|-
! Name
! Durability
|-
|[[Alto knife]]
| {{#lst:Alto knife|Durability}}
|}
[[Category:Weapons]]

Template:WeaponSidebar

2026-04-26T00:34:03Z

Lavtiz29:

<div class="infobox">
<div class="infobox-title">{{{title|{{#if:{{{Name|}}}|{{{Name}}}|{{PAGENAME}}}}}}}</div>
{{#if:{{{WeaponImg|}}}|
<div class="infobox-image"><section begin="Image" />[[File:Filename.{{{WeaponImg}}}|225px]]<section end="Image" /></div>}}
<table class="infobox-table">
<tr>
<th>Durability:</th><td><section begin="Durability" />{{{Durability|}}}<section end="Durability" /></td>
</tr>
<tr>
<th>Range:</th><td><section begin="Range" />{{{Range|}}}<section end="Range" /></td>
</tr>
<tr>
<th>Base Damage:</th><td><section begin="BaseDamage" />{{{BaseDamage|}}}<section end="BaseDamage" /></td>
</tr>
<th>Action Point Cost:</th><td><section begin= "AP" />{{{AP|}}}<section end="AP" /></td>
</tr>
<tr>
<th>Damage Type:</th><td><section begin="DamageType" />{{{DamageType|}}}<section end="DamageType" /></td>
</tr>
<tr>
<th>System:</th><td><section begin="System" />{{{System|}}}<section end="System" /></td>
</tr>
<tr>
<th>Tags:</th><td><section begin= "Tags" />{{{Tags|}}}<section end="Tags" /></td>
</tr>
<tr>
<th>Deployment Cost:</th><td><section begin="DeploymentCost" />{{{DeploymentCost|}}}<section end="DeploymentCost" /></td>
</tr>
</table>
</div>
</div>

<noinclude>
<pre>
{{WeaponSidebar
| Name =
| WeaponImg =
| Durability =
| Range =
| BaseDamage =
| AP =
| DamageType =
| System =
| Tags =
| DeploymentCost =
}}
</pre>

[[Category:Template]]</noinclude>
[[Category:Weapons]]

Unit Creation

2026-04-26T00:10:56Z

Lavtiz29: modified it

#redirect:[[Unit Datasheet Creation]]

File:Alto-ground-type-olive-drab.png

2026-04-26T00:09:40Z

Lavtiz29:

File:FullArmorAlto.png

2026-04-26T00:06:20Z

Lavtiz29:

Template:KitInfo

2026-04-24T12:09:57Z

Lavtiz29:

{{KitSideNav
| Name = {{{Name|}}}
| Kit ID = {{{Kit ID|}}}
| PDD ID = {{{PDD ID|}}}
| Faction = {{{Faction|}}}
| Release Date = {{{Release Date|}}}
}}
{{{General|}}}
{{#if:{{{Parts List|}}}|
== Parts List ==
{{{Parts List}}}}}

{{#if:{{{Stats|}}}|
== Wargame Stats ==
{{{Stats}}}}}

<noinclude>
{{KitInfo
| Name = 
| Kit ID = 
| PDD ID = 
| Faction = 
| Release Date = 
| General = 
| Parts list = 
| Stats = 
}}
[[Category:Template]]
</noinclude>

{{KitNav}}
{{Sidebar}}

2026-04-21T00:00:01Z

Lavtiz29: fucking changed everything

The Unit Datasheet section provides a detailed breakdown of every module found on a datasheet and explains how each part functions during gameplay.

While the Gameplay Components section introduces the datasheet at a high level, this section serves as the complete guide to understanding, interpreting, and using the information it contains. Each module is examined in depth, covering its purpose, its function during gameplay, and how a player can construct their own datasheets.

For players creating custom Units, a Datasheet Companion PDF is available on the 30MM: Wargame website. This companion tool automates many of the calculations and formatting steps described in this section and is the preferred method for building Units, though manual construction using these rules is fully supported.

Throughout this section, the Parts & Data Document (PDD) is reference. This document can also be found on the 30MM: Wargame website.

== Unit Sections Module ==
'''Purpose:'''

Every Unit is constructed from individual parts. When these individual parts are assembled into functional body components such as arms, legs, torsos, or cockpits, these are referred to as Unit Sections. This module records only the essential Sections that make up the Unit’s base frame. Optional attachments such as extra thrusters, jetpacks, external boosters, fins, or decorative wings are not listed here; those components are treated as Equipment and are recorded in the Weapons & Equipment Inventory instead.

'''Function:'''

Every Unit Section has three categories:
- Name: The name of the Unit Section (head, left arm, right leg, torso, etc).
- Max Durability: The total durability the section has when undamaged.
- Current Durability: A writable field used to track remaining durability as damage is taken.

When naming a Unit Section, any section responsible for providing movement must include the appropriate Movement Mechanism tag. For example, a left leg assembly that enables terrestrial movement would be labeled “Left Leg [TRS]”

When a Unit Section’s Current Durability reaches 0, that section is destroyed and the Unit suffers any associated penalties (loss of movement, weapons, sensors, etc.).
The Total Durability at the bottom of the module is the sum of all Max Durability Points and represents the Unit’s base Deployment Cost before adding weapons, a pilot, or Systems/Mods/Traits.

This gameplay model makes Unit damage highly readable and forces players to adapt as their Unit loses functionality piece by piece.

'''Construction:'''

To build your own Unit Section:
# Identify all Sections the Unit has.
#- Mech Units typically include: head, torso, left arm, right arm, left leg, right leg.
#- Vehicle Units include a cockpit and at least one drive section (wheels, treads, wings, etc).
# Determine the Max Durability of each Section. Use the ‘Parts & Data’ document on the website to find the stats of each part that makes up a Unit or its weapon.
#- Start with the Parts Search tab to locate stats by part name, kit, or another identifier.
#- Then move to the Core Section Calculator tab.
#- Enter the Name and Notation of every part used in a given Unit Section. The calculator totals Max Durability for you. While experienced players may total the values manually, using the calculator ensures accuracy and teaches players the correct process.
# Record the values on the Units Datasheet.
#- Write each Sections Max Durability.
#- Leave the Current Durability field blank. These will be filled during gameplay.
#- Sum all Max Durability Points to generate the Units Total Durability, which directly determines its base Deployment Cost.

== Specifications Module ==
'''Purpose:'''

The Specifications Module provides players with a quick reference to the Unit’s basic performance profile. It defines how the Unit behaves on the battlefield, making it essential for planning movement, combat decisions, and overall strategy.

'''Function:'''

The Specifications module contains the following categories:
- Classification: Indicates the Units overall size. Classification affects rules involving grapples, throws, collisions, and some SMTs.
- Base AP: Represents the number of Action Points the Unit generates at the start of each activation before any modifiers.
- Standard Movement: Defines how many hexes the Unit can move during normal (non-thruster) movement.
- Thruster Movement: Represents the maximum number of hexes the Unit can travel in a straight line when performing a Thruster Movement or Thruster Jump. Thruster Movement enables rapid repositioning maneuvers at the cost of the combat phases. This value is only available if the Unit has thrusters attached.
- Total Thruster Durability: Shows how much damage the Units thrusters can sustain before becoming inoperable. If the Total Thruster Durability is reduced to 0, the Unit loses access to Thruster Movement and any movement mechanisms requiring thrusters (AIR or AQN).

'''Construction:'''

To construct the Specifications Module, begin by completing the Unit Sections Module. If the player is using the Datasheet Companion PDF, this module will be automatically filled out when the Unit Section Module is completed.

If the player is recording their datasheet manually, reference the chart on the right and fill out the appropriate information based on the Total Durability from the Unit Section Module.

Thruster Movement and Total Thruster Durability remain blank until thruster parts are added to the Unit. If the Unit is equipped with thrusters, identify each thruster type in the Parts List tab in the PDD and record them in the Weapon & Equipment Inventory Module. Add their durability values together and record the total in the Total Thruster Durability field. Once durability is established, calculate the Unit’s Thruster Movement value.

A Unit with thrusters gain a Thruster Movement equal to twice its Standard Movement unless otherwise modified by specific parts or SMTs.

== Modified Stats Module ==
'''Purpose:'''

The Modified Stats Module records the three core combat values a Unit uses during gameplay: Accuracy, Assault, and Evasion. These values determine how well the Unit performs offensive and defensive rolls.

'''Function:'''

Each stat is made up of two components:
- Base Value: Represented by the smaller number beneath the stat name. This value is determined by the Unit’s Core Type and reflects the Unit’s natural proficiency before equipment, systems, modifications, or pilot traits are applied.
- Modified Value: Represented by the larger number beneath the stat name. This is the final value after all bonuses, penalties, SMT effects, and equipment modifiers are applied. The Modified Value is always used during gameplay
for attack and defense rolls.

Modified Values cannot be reduced below 3 for any stat, and cannot exceed the Unit’s original Base Value for that stat, regardless of modifiers applied.

Units capable of transforming use a special datasheet that’s marked with a “T” at the bottom right corner and display two distinct stat sets, one for each form. These stat sets represent how the Unit’s performance changes based on its physical configuration.
- Primary Form (Single Arrow): The single upward arrow indicates the Unit’s Base Form, which is always a Mech-type Unit. These values are used whenever the Unit is in its Mech form.
- Alternate Form (Split Arrow): The split arrow indicates the Unit’s Alternate Form, which is always a Vehicle-type Unit. These values replace the Primary Form stats whenever the Unit transforms.

'''Construction:'''

When building a Units datasheet, its Base Values are determined by its Core Type, which is explained on the following page.
Leave all Modified Values blank until the Unit’s equipment, Systems, Mods, and Traits have been fully selected. Once all sources of modifiers are known, apply them together to calculate the final Modified Values, ensuring they remain within the allowed limits.

For Units capable of transforming, modifiers apply only to a single form and do not affect both forms. Choose assignments carefully based on the Unit’s intended role.

== Core Type Module ==
'''Purpose:'''

The Core Type defines a Unit’s baseline performance. It establishes the Unit’s base statistics and provides inherent bonuses that reflect the intended function of the core frame, such as mobility, action efficiency, or battlefield specialization.

'''Function:'''

During gameplay, the Core Type determines the Unit’s Base Stats, which serve as the foundation for all Modified Stats. These values represent the Unit’s natural capabilities before any Systems, Mods, Traits, or equipment are applied.
In addition to base statistics, each Core Type may grant intrinsic bonuses, such as increased Action Points, improved movement values, or other role-defining benefits. These bonuses are always active and apply regardless of the Unit’s current equipment loadout.

On the datasheet, the Core Type is represented by an image of the Standard Unit whose chest part defines the core, allowing for quick visual identification of the Unit’s underlying frame.

'''Construction:'''

When constructing a Units datasheet, the Core Type is determined by the chest piece used on the model. Only one Core Type may be chosen per Unit, and it remains fixed regardless of later modifications, equipment changes, or transformations.

If the player is using the Datasheet Companion PDF, simply select the corresponding Unit from the dropdown menu that matches the chest part being used. All data will autofill in the appropriate areas. The dropdown menu is located in the Pilot Information Module, under the rank. This wont show up when the datasheet is printed.

If the player is recording the datasheet manually, reference the Core Types tab in the PDD for the corresponding Unit and write down the base stats and any bonuses it may have. An image wont be recorded on the datasheet so it can be left blank.

== Unit Information Module ==
'''Purpose:'''

The Unit Information Module identifies what the Unit is at a glance. It defines the Unit’s identity, battlefield role, and how it fundamentally moves through the environment. This module ensures all players can quickly understand how the Unit interacts with core rules such as movement, terrain, and targeting.

'''Function:'''

During gameplay, the information in this module is used to determine which rules apply to the Unit.
- Name is used for identification during play, rules interactions, and scenario objectives.
- Type determines which Unit Type rules apply (Mech, Vehicle, or Both), including core traits,
section layouts, and special restrictions.
- Movement Mechanism determines how the Unit traverses the battlefield, how it interacts with terrain, elevation, and environmental effects, and which movement-related rules it follows.

Together, these entries define the Unit’s core classification within the ruleset and act as a reference point when resolving movement, terrain effects, and unit-specific interactions.

'''Construction:'''

When creating a datasheet, the player assigns each field in this module as follows:
- Name: Choose a unique or thematic name for the Unit. This has no mechanical impact but is required for identification.
- Type: Select the Unit’s type based on its construction and intended role (Mech, Vehicle, or Drone), following the Unit Types rules outlined earlier in the rulebook.
- Movement Mechanism: Assign the appropriate movement mechanism(s) the Unit qualifies for based on its physical components, such as legs, wheels, thrusters, wings, or aquatic systems. A Unit can have multiple movement mechanisms at
once and must list all that are available.

==Pilot Information Module ==
'''Purpose: '''
The Pilot Information Module represents the individual controlling the Unit and defines their level of experience, tactical capability, and overall impact on the Units performance. The pilot acts as a force multiplier, unlocking additional abilities beyond the Units physical construction.

'''Function: '''

During gameplay, the information in this module determines what pilot specific benefits are available to the Unit.
- Name identifies the pilot assigned to the Unit and has no mechanical effect.
- Rank determines how many Mods and Traits the Unit may equip, as well as Stat Reduction Modifiers (SRMs) the player can use to modify the Units Stats.
- DC (Deployment Cost) represents the point cost of assigning the pilot to the Unit and is added directly to the Units total Deployment Cost.

Stat Reduction Modifiers (SRMs) allow a player to fine-tune a Unit’s base stats to better suit its intended battlefield role or playstyle. The number of SRMs available is determined by the pilot’s rank and represents deliberate tradeoffs made during Unit construction.

Artificial Intelligence (AI) pilots function similarly to human pilots but have a reduced Deployment Cost and do not gain access to Traits. AI pilots are required when fielding AI Drone Units and use the AI rank values instead of human pilot ranks.

All Units must have a pilot to be fielded.

'''Construction:'''
When creating a datasheet, the player fills out this module as follows:
- Name: Choose a pilot name or designation.
- Rank: Select a pilot rank according to the Pilot Rank chart.
- DC: Record the Deployment Cost associated with the selected rank.

When applying Stat Reduction Modifiers (SRMs) to a Unit’s base stats, remember that lower values represent better performance.

If the player is using the Datasheet Companion PDF, the ranks row will have a dropdown menu where the desired rank can be chosen. After selection, the proper information will be auto filled, however SRMs need to be added manually.

If the player is recording the datasheet manually, use the chart below to fill in the proper information.

== SMT List Module ==
'''Purpose:'''

Systems, Mods, and Traits (SMTs) represent the unique abilities that define how a Unit performs beyond its base stats and physical construction. These abilities can be active or passive and allow players to customize a Unit’s battlefield role, tactical options, and pilot expression.

The number and type of SMTs a Unit may equip are determined by its Pilot Rank. Higher ranked pilots provide greater access to slots.

'''Function:'''

SMTs modify how a Unit behaves during gameplay by granting special rules, bonuses, penalties, or new actions.

Systems are abilities tied to weapons, armor, or equipment. They only function when slotted and remain active as long as their conditions are met. Systems may affect attack resolution, movement, survivability, or resource use.

Mods represent internal or structural enhancements that improve performance without being visible on the model. Mods are always active and typically provide passive bonuses or rule adjustments.

Traits reflect the pilot’s personality, instincts, and combat style. Traits often influence decision making, reaction timing, or specialized interactions during play.

Unless otherwise stated, SMT effects are always active once equipped and follow all normal stacking, timing, and restriction rules outlined in their descriptions.

'''Construction:'''

SMTs are selected during Unit creation and recorded in the Systems, Mods, & Traits List Module of the datasheet.

'''Systems'''
- Equipping an item does not automatically grant its System.
- All Systems provided by equipped weapons, armor, and equipment are pooled together.
- The player selects which Systems to slot into the Unit’s available System slots.
- Only slotted Systems are active during gameplay.
- If a System has a Deployment Cost, it is recorded on the right hand side of the name then added to the Unit’s total Deployment Cost.
- If multiple items share the same System, it only needs to be slotted once.
- A Unit may equip up to 5 Systems, with Mods capable of increasing this limit to 6.

'''Mods'''

- Mods do not add Deployment Cost; their cost is accounted for by Pilot Rank.
- The number of Mods a Unit may equip is limited by Pilot Rank.
- A Unit may equip up to 3 Mods, with Traits capable of increasing this limit to 4.

Traits
- Trait costs are included in the Unit’s Pilot Rank.
- The number of Traits available is determined by Pilot Rank.
- A Unit may equip a maximum of 2 Traits at Ace Rank.

For Units capable of transforming, SMTs apply to only one form unless otherwise specified.

== Weapons and Equipment Inventory Module ==
'''Purpose:'''

The Weapons & Equipment Inventory Module defines everything a Unit brings to the battlefield beyond its core structure. It records all weapons, gear, and auxiliary equipment a Unit has access to during play and serves as the primary reference for combat capabilities, special interactions, and deployment cost calculations.

'''Function:'''

During gameplay, the Weapons & Equipment Inventory is used whenever a Unit performs an attack, activates a weapon-based System, takes equipment damage, or checks available options.

Each entry in the module provides all information needed to resolve weapon use and equipment effects, including:
- Which weapons can be used at a given range
- How much damage an attack deals
- The AP cost to fire or activate the item
- Any special Tags that modify how the weapon or equipment behaves
- Where the item is mounted on the Unit, which may affect targeting or destruction

If a weapon or piece of equipment is destroyed, disabled, or restricted by a rule, this module is used to track and enforce those effects.

'''Construction:'''

When building a Unit, players populate this module after completing the Unit Section and Specifications Modules.
For each weapons or piece of equipment added, record the following:
- Name: The official name of the weapon or equipment.
- Tags: Any applicable weapon or equipment tags (e.g. [MG], [DR], etc.) that define special rules or interactions.
- Location: The Unit Section where the item is equipped, mounted, or stored.
- Range: The maximum effective range of the weapon, if applicable.
- Base Damage: The damage dealt on a successful hit before modifiers.
- AP: The Action Point cost required to use or activate the item.
- Type: Indicates whether the item is Energy or Kinetic based weapon.
- Durability (Dur.): How much damage the item can sustain before being destroyed.
- Deployment Cost (DC): The point cost to field the weapon.

All weapons and equipment listed here are considered part of the Unit’s loadout and are eligible to provide Systems that may be slotted in the SMT List Module.

== Weapons & Equipment ==
Weapons and Equipment represent the gear a Unit brings into battle. From powerful armaments to specialized tools, these items define how a Unit performs on the battlefield and the roles it can fulfill during a mission.

Each item is constructed from individual parts that determine its overall stats and capabilities. These parts also contain various Tags.

Tags define special properties and rules that influence how an item functions in-game.

===Core Concepts ===
This section explains the basic ideas behind how Items (Weapons and Equipment) function in-game. These rules provide the foundation needed to understand how items are created and used.

==== Item Types ====
Items are divided into two types: Weapons and Equipment. Units have access to both, serving different roles during gameplay.

===== Weapons =====
Weapons are divided into two categories: Ranged Weapons and Melee Weapons.
Ranged Weapons can target Units beyond 1 hex, while Melee Weapons can only target Units within 1 hex. Unless otherwise stated, any Weapon with a range of 1 is considered a Melee Weapon.

Weapons are also classified as either Kinetic or Energy. These types represent different weapon technologies and may affect how a weapon performs. Specific rules and differences between these types are explained later.

===== Equipment =====
Equipment provides utility, abilities, and enhancements to a Unit. Unlike Weapons, it is not primarily used to make attacks but instead offers passive effects or special actions such as radar systems, drones, and defensive modules.

====== Item States ======

Items can exist in different states depending on their condition and availability. These states determine whether an item can be used.

'''Equipped'''

The item is active and available for use.
- Weapons can be used to make attacks.
- Equipment can apply its effects or be activated.
Example: A Unit has two arms, each equipped with a hand-held weapon, and a mounted rocket launcher
ready to attack.

'''Stored'''

The item is not currently in use.
- Stored items cannot be used.
- Rules or abilities may allow a Unit to equip stored items.
Example: A Unit has two hand-held sidearm weapons stored on its back. These weapons cannot be used because the Unit already has two weapons equipped and must swap them using a Command Action.

'''Dropped'''

The item has been placed on the battlefield and is not currently held by a Unit.
- Dropped items cannot be used.
- Dropped items remain in their current hex until picked up.
- A friendly Unit may pick up a dropped item using a Command Action.

Example: A Unit drops its hand-held weapon in its current hex. The weapon remains on the battlefield and cannot be used until a friendly Unit picks it up using a Command Action.

'''Destroyed'''

The item has been removed from play.
- Destroyed items cannot be used for the remainder of the game.
- Some rules may trigger when an item is destroyed.

Example: A Unit has two hand-held weapons and a mounted weapon, all of which are destroyed. When the mounted weapon is destroyed, the player must roll to determine if it explodes and damages the Unit.

====== Tags ======
Before creating Weapons or Equipment, the player must understand Tags. Tags are short identifiers that describe what a weapon or piece of equipment does and how it functions in the game.

Tags are applied to items based on the parts used during construction. Some Tags are required and cannot be freely chosen.

Tags appear inside brackets and are usually made of two or three letters, numbers, or a combination of both. For example, the tag [WN] represents a Hand-Held Weapon. When a Unit’s datasheet lists an item with the tag [WN], it indicates that the item is a Hand-Held Weapon.

Multiple Tags can be combined to customize a weapon or piece of equipment. By combining different Tags, players can create a wide variety of gear when building their Unit datasheets.

Tags follow the standardized order. When created, they only include those that apply, but maintain the sequence shown below.

''' Tag Structure''''
Tags follow this sequence in order:
# Category
# Mechanism
# Prerequisites
# Available Systems

'''Category'''

Defines what type of item the tag represents. Category tags determine the general function of a Weapon or Equipment, such as Weapon, Equipment, or subcategories like Hand-Held or Mounted.

'''Mechanism'''

Defines how a Weapon functions when used. A Weapon may have a maximum of one Mechanism tag. If no Mechanism is selected, the Weapon defaults to a Single Fire attack.

'''Prerequisites'''

Defines any requirements needed to use the item. These tags may restrict usage based on Unit type, conditions, or other factors. If a part used to construct an item has a Prerequisite, that Prerequisite must be included in the item’s final Tags.

'''Available Systems'''

Defines additional systems or effects that modify or enhance the item. These tags provide optional or specialized functionality. Some systems may not be attached to any specific item part. If the player finds a system like this and wanted to use it, simply add it to the Units SMT List and assign its tag to the item.

====== Item Construction ======
This section explains how to manually construct Weapons and Equipment from individual parts. By combining parts and their Tags, players create items with unique functions and roles.

In this section, “Notation” refers to the tag assigned to a part, and each notation is specific to its kit of origin. All parts can be found in the Parts and Data Document (PDD) in the Parts Search tab.

'''Weapons Vs. Equipment'''

When creating items, there are some key differences between Weapons and Equipment.

Weapons are limited to the following Categories:
- Hand-Held
- Mounted
Equipment is limited to the following Categories:
- Shield
- Thruster
- Attachment

When constructing equipment, mechanisms do not apply.

'''Assembly'''

Assemble the item using parts based on a desired function, role, or appearance. Players may follow preexisting guides or create their own designs.

'''Determine Category'''

The items Category is chosen based on its intended purpose and construction (for example, Hand-Held Weapon or Shield).
Assign Mechanism.

If the constructed item is a Weapon, assign one available Mechanism Tag. If none are selected or available, the Weapon defaults to a Single Fire attack.

This step is skipped for Equipment, even if Mechanism Tags are available.

'''Apply Prerequisites'''

Any Prerequisite Tags associated with the selected parts must be applied.

If a part includes a Prerequisite, it is required and must be included in the Weapon’s final Tags.

'''Choose Systems'''

If Systems are available, the player may choose which to include. Systems are optional, and a player may
include none.

Selected Systems add their Tags to the Weapon and are recorded in the Unit’s SMT List along with their Deployment Cost (DC). System DC is applied to the Unit, not the Weapon.

A player may include any number of Systems, up to the Unit’s available System slots.

'''Final Stats'''

An item’s final stats (such as Range, Base Damage, AP Cost, Type, and Durability) are determined by combining the values of its selected parts.

Most Equipment parts do not include stats such as Range, Base Damage, AP Cost, Type, or Mechanism. This is because Equipment primarily serves as a platform for abilities rather than direct combat.

When determining a Weapon’s Type, compare the number of Kinetic and Energy parts used in its construction. The Weapon’s Type is determined by the category with the most parts. If both Types are present in equal amounts, the Type with the higher Base Damage determines the Weapon’s Type.

To determine an item’s Deployment Cost, use the following formula after calculating all other stats:

(Base Damage − AP Cost + Range + Durability)

If the item includes a Mechanism and/or Prerequisite, apply their additional costs to the final
value.

Core Rules

2026-04-06T18:45:07Z

Lavtiz29: Finished the Core rules update. I think that's everything. WE just need pictures now

== Introduction ==
The 30 Minute Missions: Wargame (30MM:W for short) is a mech-based tabletop miniatures game using Bandai Spirit's 30 Minutes Missions line of 1/144 scale mecha model kits. The focus of this game is on:
* The ability to play missions in, roughly, 30 minutes (excluding setup); and
* The customizability and modular designs for model kits.
The game is played over a series of rounds. Each round consists of alternating turns between each player choosing one of their Units, moving to the best position, attacking the enemy, or holding an objective. The battlefield is played with varying terrain, elevations, and structures. Missions can vary from eliminating the enemies to securing intel.

== Objective ==

The game is won after the primary objective of the mission you are playing has been completed. These range from holding an objective for multiple turns, getting an object and moving to your side of the board, or simply destroying the enemy forces.

== Required Components ==
* 30 Minutes Missions Models (assembled)
* Datasheets (filled out)
* Hex Grid Game Mat
* Game Tokens
* D8 Dice
* D20 Dice
* Various Hex Colors

* The hex game mat is roughly 40x60” with 4.5” hexes (vertex to vertex) setup in an 11 hex by 15 hex grid with the flat sides horizontal.

=== Units and Squads ===
Each individual model on the battlefield is referred to as a Unit. All Units controlled by a single player together make up that player’s Squad.
When a rule refers to a Unit, it applies only to that specific model. When a rule refers to a Squad, it applies to all of that player’s Units collectively.

=== Dice ===
To play the 30MM: Wargame, you will need two types of dice: eight-sided dice (D8) and twenty-sided dice (D20). Each player should have at least 5–10 D8s to keep gameplay fast and 1 D20 for every Unit they control.
The D20 is used to track a Unit’s Action Points (AP), while the D8 is used for all attack, defense, and ability rolls.
Occasionally, the rules may reference alternate dice notations such as D4, 2D8, or D8 + 1:

* D4: Roll a D8 and halve the result, rounding up.
* D8 + 1: Roll a D8 and add 1 to the result.

==== Rolls and Rerolls ====
When making a roll, the player must roll equal to or higher than the target value listed under the Unit’s Modified Stat on its Datasheet. Each roll represents a single attack, defense, or action attempt.
Example: Unit A makes two ranged attacks against Unit B, which has a Modified Evasion Stat of 7.
The defending player rolls 2D8, scoring a 6 and a 7.
This means one attack hits (6) and one attack is evaded (7).
If an ability allows you to reroll dice, select the number of dice indicated and reroll them, starting with the lowest results first. The outcome of the reroll is final, even if it is worse than the original roll.

=== Tokens ===

Tokens are used to track various effects, conditions, and states that occur during gameplay.
Whenever a rule or status effect instructs a player to place a token, it should be placed face-up next to the affected Unit to clearly indicate the current condition.

=== Objective Markers ===

Objective Markers represent key tactical points, data nodes, or energy beacons on the battlefield that players must capture, defend, or destroy to complete mission objectives.
The standard Objective Marker model is built using a combination of Roy Roy leg parts (from the 30 Minute Missions Alto or Portanova kits), thrusters from the Option Parts Set 1, and structural components from the J1 runner, included in most 30MM kits.

Players may use Objective Marker tokens in place of the physical kit-built markers if preferred. Alternatively, an Objective Marker can be any model, piece, or object the players agree upon prior to starting the game, so long as all participants clearly understand what represents an active objective.
When placed on the map, Objective Markers do not obstruct movement or Line of Sight unless specified by the mission.

=== Datasheet ===
Each Unit is represented by a Datasheet, which contains all of the information required to operate that Unit effectively on the battlefield. The Datasheet lists every attribute, ability, and piece of equipment necessary to complete a mission.
While Units can differ greatly in how they function, every Datasheet follows the same layout and includes the following elements:

# Unit Sections – Displays each section (Head, Torso, Left Leg, etc.) of the Unit and its Defense Points (DP).
# Specifications – Lists the Unit’s detailed attributes such as classification, base AP, movement (standard and thruster), as well as total thruster durability.
# Modified Stats – The Unit’s Accuracy, Assault, and Evasion values, used when making Attack and Defense Rolls.
# Core Type – Shows the Unit’s base model and core statistics.
# Unit Information – Includes the Unit’s Name, Type, and Movement Mechanism(s).
# Pilot Information – Lists the Pilot’s Name, Rank, and Pilot Cost.
# Systems, Mods, & Traits – Details the Unit’s special abilities and upgrades.
# Weapons & Equipment Inventory – Records all weapons, gear, and equipment equipped by the Unit.
# Deployment Cost (DC) – The total cost required to field the Unit in battle.

== Unit Basics ==

=== Mechs ===
A Mech is a humanoid combat Unit characterized by articulated limbs, modular construction, and the ability to operate across various terrains and elevations. Mechs are designed for front-line combat, tactical flexibility, and diverse loadouts, capable of fulfilling multiple battlefield roles.
Design Choices of Mechs:
* Humanoid Frame: Possesses articulated arms, legs, and a torso, enabling advanced maneuverability such as jumping, climbing, or changing facing independently.
* Combat Versatility: Capable of engaging in both ranged and melee combat; well-suited for precision attacks, flanking, and defensive holds.
* Reactive Posture System: Can assume crouching, and prone positions as well as offensive, defensive, and parry stances to affect LoS, hit zones, and evasion.

=== Vehicles ===
Vehicles are modular support Units designed to augment, transport, or reinforce Mech Units on the battlefield. They can operate independently or in tandem with other Units, often providing specialized mobility, firepower, or utility functions.
Design Choices of Vehicles:
* Dedicated Support Platform: Mech Units can ride on/in various vehicles to move around the battlefield.
* Modular Integration System: Can combine with Mech Units for additional firepower.

=== Classifications ===
There are 5 different classifications that provide different starting bonuses and limitations based on the size of your Unit. This is determined by the Total Defense value of all of Core Parts combined.

{| class="wikitable" style="text-align:center; vertical-align:middle; background-color:#F8F9FA; color:#202122; float:right; margin-left:10px; "
|-
! Total Defense
! Classification
! Base Movement
! Base Action Points
|-
| 0 - 75
| Class 1
| 5
| 1d8 + 2
|-
| 76 - 150
| Class 2
| 4
| 1d8 + 2
|-
| 151 - 225
| Class 3
| 3
| 1d8 + 3
|-
| 226 - 300
| Class 4
| 2
| 1d8 + 4
|-
| 301+
| Class 5
| 1
| 1d8 + 4
|}

== Playing the Game ==
All missions take place on a battlefield overlayed by a hexagonal grid. A single hex measures 4.5” from point-to-point and 3.9” from side-to-side. This is the same size as an Action Base 4/5. A battlefield measures 14 hexes on the long side and 11 hexes on the short side (58.5”x38.3”).

=== Setup ===
Players will first lay out a battlefield mat as preferred or, if playing a scenario, as the scenario specifies.

Before determining turn order, all players must agree on the Engagement Size (the total Deployment Cost limit of all
Units in a players squad). Once the Engagement Size is set, each player assembles their Squad accordingly.

Next, players will roll a 1D8 to determine who goes first. The higher roll then determines who is the attacker or defender. The attacker gets to start first but the defender gets to choose which table side to start on (A or B side). If both players roll the same, then both players conduct a reroll.

In a 3 (or more) player game, players choose which side (attacker or defender) to participate in and share Units and turns with their teammates. At the start of the round, players roll for initiative with the higher roll, giving the first chance to move a Unit.

=== Unit Deployment ===
Once the attacker and defender have been determined, it is now time for the players to deploy their squads to the battlefield. Each side has a dedicated Deployment Area laid out in the mission details. Standard Deployment Areas are the first 3 hexes from the short side table edge on both sides.

Starting with the attacker, they will place one Unit within their Deployment Area on any elevation/terrain they see fit. If their Unit flies/swims, they may start in the air/water but must place a token down notating its elevation. Once the attacker's Unit has been deployed, the defender does the same. In an alternating fashion, both players continue to deploy Units until everyone is on the battlefield.

After both sides have deployed their Units, the Deployment Phase has ended and gameplay can begin.

=== Action Points ===
At the start of a Unit's activation, before moving, the player must roll 1d8 to determine the number of Action Points (AP) available during that turn. Action Points are spent to perform various actions, such as entering a prone position, deploying a drone, or firing a weapon.

After rolling, the result is added to the Unit’s Base AP value as listed on its Datasheet in the Specifications Section.
A Unit may store unused AP from one turn to the next. However, it cannot exceed a total of 16 AP at any time unless stated otherwise.

=== Phases of a Turn ===
The 30MM: Wargame consists of a series of alternating turns that make up a number of rounds. Each turn consists of three phases. The players will execute these phases in sequential order for every Unit that is activated. After a Unit has been activated and completed all three phases, play passes to the next player in the established play order (e.g., Attacker 1, Defender 1, Attacker 2, Defender 2, etc). Once all Units have been activated, progressed through each phase, and become inactive, the round ends and a new one begins.

Each turn includes the following phases, performed in the following order:

# Movement Phase
# Ranged Combat Phase
# Close Combat Phase

=== Movement Phase ===
The player may now choose a Unit to activate and begin its Movement Phase. Once selected, the player rolls for Action Points as explained in the section above.
If a player chooses not to activate a Unit or the Unit is unable to act (due to a status effect, lack of AP, or other restriction), the Unit is immediately marked Inactive and play passes to the next Unit in turn order.

After the player has determined the amount of AP the Unit has, they then can move to their desired location. In the Specifications Section of the Datasheet, there is a section called “Standard Movement”. This section shows how many hexes that Unit can move in a single activation. A Unit can move any number of hexes to a maximum of what that section shows. When moving a Unit, its facing is also important, as it affects both offense and defense. Changing Facing also costs a single movement point. Greater details on how facing works can be found in the [[Core Rules#Facings|Facings Section]]. Below the standard movement you’ll also see “Thruster Movement”. This option is only available to Units that meet certain requirements as found in the [[Core Rules#Thruster Movement|Thruster Movement]] Section below. A Unit also has the option of not moving at all. Outside of this basic information there are other steps that can be taken listed in the next section [[Core Rules#Movement|Movement]].

Any terrain effects gained must be resolved before moving on to the next phase.

=== Ranged Combat Phase ===
After moving the selected Unit to the desired hex, the player may then make attacks with ranged weapons.
All attacks made must subtract the weapons AP cost from the Units current stored AP. If the Unit does not have an adequate amount of AP, then the Unit cannot make an attack with that weapon.

If the player decides to not make a ranged attack (to save AP or any other reason they decide), they may skip this phase and move to the next but cannot return to it.

=== Declaring Weapons Fire ===
The player must then choose a target to attack. Once a target has been established, then the player must declare which Unit Section on that target they are going to attack.

Common Unit Sections include Head, Torso, Left Arm, Right Arm, Left Leg, and Right Leg.

A player must declare all attacks they plan to make at this time, specifying which weapon(s) they intend to fire and at what sections.
Players may not change an attack declaration once made.

=== Resolving Weapons Fire ===
Once a target and Unit Section are declared, the player will then resolve the weapons fire one weapon at a time.
All declared attacks must be made, even if the intended target is destroyed before all attacks against it have been resolved.
The order in which a Units weapons are rolled and resolved is up to the Units player.

=== Close Combat Phase ===
Players repeat the steps given for the Ranged Combat Phase except with close combat weaponry (typically weapons with a range of 1).

Once the player has resolved all close combat damage, the Unit becomes inactive and ends its turn. At which point, the opposing player chooses a Unit and begins the cycle again.

=== Win Conditions ===
Players repeat the sequence of play given above until one side achieves victory. Under normal circumstances, the side with the last surviving Unit on the battlefield wins. If the last Units from each side are destroyed simultaneously or if the last Units from each side are rendered Inoperable, the game is a draw. Players may set other victory conditions by mutual agreement before play begins. In addition, some missions have special victory conditions of their own.

=== Unequal Units on Map ===
When both sides have an equal number of Units, each player takes a turn activating a single Unit, then the other player activates a single Unit, and so on. If the number of units on each side is unequal, this procedure is altered.

If one side has more activatable units than the other, the players will continue to alternate Unit activations until one player can no longer activate their Units for that round. At which point, the other player will continue activating their Units until they are all deactivated and the round is over.

== Movement ==
During the Movement Phase, Units may reposition and adjust their elevation on the battlefield to secure tactical advantage.

=== Standard Movement ===
A Unit’s Standard Movement value is listed in the Specifications Section of its datasheet. This value represents the total number of Movement Points (MP) the Unit may spend during its Movement Phase, determined by its Classification.
A Unit may move into the hex it is currently facing or into the hex directly behind it; movement into any other hex requires a facing adjustment. Entering a clear hex costs 1 MP whether moving forward or backward, while movement costs for other terrain types vary as specified elsewhere in the rules.

=== Standard Jump ===
A Mech Unit may perform a Standard Jump as part of their Standard Movement. A Standard Jump allows the Unit to leap over the hex directly in front of it and land two hexes forward while maintaining its facing, at a cost of 2 MP.
The Unit must remain on the same elevation throughout the jump and cannot leap over a hex, structure, or Unit that occupies a higher elevation level.

A Unit may descend to a lower elevation during a jump as long as it has enough MP to complete the movement; otherwise, [[Core Rules#Fall Damage|Fall Damage]] is applied based on the number of elevation levels dropped.
Upon landing, all terrain effects of the landing hex immediately apply. A Unit may perform multiple Standard Jumps during its Movement Phase, provided it has sufficient MP remaining.

=== Facings ===
Each hex on the battlefield has six sides. A Unit must always face one of these sides; this is referred to as its Facing.

Changing a Unit’s Facing costs 1 Movement Point, deducted from its Standard Movement allowance.

=== Thruster Movement ===
When a Unit is equipped with thrusters, it may perform a Thruster Movement instead of a Standard Movement. Thruster Movement allows the Unit to move up to double its standard movement points in a single turn, as indicated by its Thruster Movement value.

Thruster Movement must be performed in a straight line, and the Unit must normally remain on the same elevation from start to finish.

=== Thruster Jump ===
As part of Thruster Movement, a Unit may perform a Thruster Jump, allowing it to ascend or descend elevations during its movement.

A Unit initiates a Thruster Jump by declaring Thruster Movement.

When performing a Thruster Jump, the Unit may move in a straight line and change elevations at any point along its movement path, up to its Thruster Movement value. The Unit may land on a hex at a higher or lower elevation than where it began.

If a Unit ends its movement on a hex without solid ground beneath it and does not have the [[Core Rules#Aerial Movement|Aerial [AIR] Movement Mechanism]], it immediately falls to the next available elevation and suffers [[Core Rules#Fall Damage|Fall Damage]].

==== Additional Rules ====
* The Unit may move any number of hexes, up to its Thruster Movement value.
* After completing a Thruster Movement, the Unit must maintain its facing direction, forfeit its Combat Phase (unless otherwise stated), and become inactive.
* If all thrusters on the Unit are destroyed, it can no longer perform Thruster Movements.

=== Elevation Changes ===
Units may change elevation during the Movement Phase.
Ascending or Descending one elevation level costs 1 Movement Point in addition to the 1 Movement Point to move into the new hex.

Backward Movement:
Units moving backward cannot change elevation.

Unauthorized Elevation Changes:
A Unit cannot force another Unit to ascend to a higher elevation.
A Unit may force another Unit to descend to a lower elevation. Units forced downward suffer Fall Damage (pg. 32).

=== Terrain ===
Non-Grey terrain types, those with additional environmental effects, require extra Movement Points to move through.
Certain terrain types may also grant bonuses or impose restrictions on movement and other actions while a Unit occupies them.
Refer to the [[Core Rules#Hex Colors|Hex Colors]] for full details.

=== Hex Occupancy ===
A Unit may move through a hex occupied by a friendly Unit. A Unit may not move through a hex occupied by an enemy Unit unless executing a Thruster Impact.
A Unit may end its Movement Phase in a hex containing friendly Units, provided that each Unit maintains at least 80% of its model within the hex, based on best judgment, and the Units do not physically overlap.
Units may be repositioned freely within the hex as long as at least 80% of the model remains inside the hex (this does not require a Command Action to perform) and the Unit maintains the facing established at the end of its movement.
Movement within the hex may be used to set up ambushes, establish firing positions, or improve cover.
Opposing Units cannot occupy the same hex unless otherwise specified or unless they are positioned on different elevation levels.

=== Movement Mechanisms ===
A Unit’s method of traversing the battlefield is defined by its Movement Mechanism. These dictate how a Unit interacts with terrain, elevation, and movement-related effects. A Unit’s assigned mechanism is determined by the components used during its construction and is listed on the Unit’s datasheet as a three-letter tag. Units that are considered Mechs do not qualify for any Vehicle additional rules.
Tags appear as 3 letters within brackets and allows players to quickly identify how a rule or item functions. For a full explanation, see [[Core Rules#Tags|Tags]].
There are three types of Movement Mechanisms.

==== Terrestrial Movement ====
Tag: [TRS]
The standard movement mechanism for all ground-based Units. These Units traverse solid terrain using walking, rolling, or similar locomotion.

This mechanism does not require Thruster Durability unless it is performing a Thruster Movement.

Units with this mechanism must use elevated terrain to move to higher elevations. A Terrestrial Unit cannot move directly to a higher elevation unless there is accessible terrain.

To qualify for this mechanism, a Unit must have at least one of the following Unit Sections: Legs, Treads, Wheels, or comparable locomotion systems.

===== Terrestrial Vehicles =====
Land-based vehicle Units follow additional rules to reflect their unique combat and movement traits.

Requirements:
* Must contain at least one [TRS] marked Unit Section.
* Must not contain an [AQN] or [AIR] tag.
Restrictions:
* Weapon range is halved when firing through green hexes.
* Movement costs 2x when crossing green hexes.
Bonuses:
* Field of View (pg. 18), the area the Unit can target Units, is all 6 hexes around the Unit.
* Main Cannon has an AP reduction of 3 (to a minimum of 4).

==== Aquatic Movement ====
Tag: [AQN]
The standard movement mechanism for all water based Units. These Units traverse and maneuver through aquatic terrain such as oceans, rivers, and lakes, freely adjusting their position within submerged environments.

Units with the [AQN] Movement Mechanism use Movement Points (MP) as normal Standard Movement to navigate Blue Hexes with two exceptions: ascending upward in the water costs 1 MP, while descending to a lower elevation costs no additional MP.

To qualify for this mechanism, a Unit must have at least one of the following: Fins, Thrusters, or comparable propulsion sections. A Unit must also meet or exceed the required Thruster Durability threshold to maintain this mechanism.

If a Unit’s Thruster Durability drops below the required threshold, it immediately loses access to [AQN] movement and becomes subject to Blue Hex terrain effects.

===== Aquatic Vehicles =====
Water-based vehicle Units follow additional rules to reflect their unique combat and movement traits.

Requirements:
* Must contain at least one [AQN] marked Unit Section.
* Must not contain an [TRS] or [AIR] tag.
Restrictions:
* Cannot make normal movements on 0 Elevation (Ground Level).
* Can only move over light/dark blue hexes; failure to do so results in the Unit gaining the Grounded status effect.
Bonuses:
* Attacks made with missile pods do not require LoS.

==== Aerial Movement ====
Tag: [AIR]
The standard movement mechanism for all air based Units. These Units operate above the battlefield, maintaining altitude without reliance on solid ground and freely traversing terrain by air.

Units with the [AIR] Movement Mechanism use Movement Points (MP) to travel between hexes as normal Standard Movement to navigate, but they ignore all ground-based terrain effects unless specified to effect them. These Units can also adjust their elevation up or down by 1 level at the cost of a single MP rather than the standard 2.

Units with this mechanism cannot fly through Green Hexes (dense vegetation or forest terrain).

If a Unit loses access to [AIR] while airborne and without solid ground beneath it, it immediately falls to the lowest available elevation and suffers fall damage as normal. See the Minimum Thruster Durability chart on the next page for more information.

To qualify for this mechanism, a Unit must have at least one of the following: Wings, Rotors, Thrusters, or comparable propulsion systems. A Unit must also meet or exceed the required Thruster Durability threshold to maintain this mechanism.

===== Aerial Vehicles =====
Air-based vehicle Units follow additional rules to reflect their unique combat and movement traits.

Requirements:
* Must contain at least one [AIR] marked Unit Section.
* Must not contain an [AQN] or [TRS] tag.
Restrictions:
* Cannot make normal movements on 0 Elevation (Ground Level).
* Cannot move backwards.
* Must use all movement points (standard or thruster) during activation; failure to do so results in the Unit gaining the Grounded status effect.

Bonuses:
* Strafing Runs: When the Unit passes directly over enemy Units (at one elevation higher) during the Movement Phase, it may pause movement to conduct a single ranged or close combat attack. After resolving the attack, the Unit continues it movement. This can be repeated multiple times during a single movement phase until the Activated Unit's AP is 0 or no more targets are within the movement path.

== Combat ==
Once the player’s chosen Unit completes the Movement Phase, they engage in combat. Units use two forms of combat: Ranged Combat and Close Combat. Ranged Combat utilizes missiles, beam rifles, rockets, and many others. Close combat utilizes beam swords, pile bunkers, heavy metal swords, and even other Units.

=== Targeting Basics ===
This section establishes how a Unit selects and validates a target before making an attack.

==== Defining a Target ====
All targets fall into one of two categories: Units or Structures.
* Units include mechs, vehicles, drones, and any weapons or equipment integrated with them.
* Structures refer to any constructed object of human origin, including buildings, fortifications, or installations.
A player cannot deliberately target an allied Unit.

==== Field of View ====
If an attacking Unit has Line of Sight to its intended target, the player must then check whether the target is within the Unit’s Field of View (FoV).

A Unit’s FoV begins with the hex directly in front of it and includes the adjacent hexes to its immediate left and right, forming a forward-facing arc. This arc expands outward in a cone-shaped pattern from the attacker to the edge of the battlefield.

==== Line of Sight ====
Line of Sight (LoS) is used to determine visibility between an attacking Unit and its designated target.
To determine LoS, the player must use the actual line of sight from the physical model. This is done by lowering their perspective to the eye level of the Unit’s cockpit or sensor array (head) and verifying whether the targeted Unit Section is visible. If any part of the target section is visible, LoS is established.
LoS may be obstructed by terrain, structures, or other Units, friendly or hostile.

Terrain between the attacker and target may partially or fully obstruct LoS. If an attack passes through terrain with visibility modifiers (e.g., forests or debris), apply the listed penalties under Terrain Effects.
When declaring an attack, the player must also ensure that the weapon system being used has an unobstructed LoS to the target. This is verified by physically aiming the weapon at the intended target. The line from the weapon to the target must be free of any obstructions, including terrain features, structures, or other Units.

==== Targeting Conditions ====
This section establishes how terrain, elevation, and other Units may obstruct or alter attacks, covering rules for partial obstruction, height differences, terrain effects, and intervening obstacles.

==== Partial Obstructions ====
In certain situations, a Unit may be partially obscured by terrain, structures, or other Units. Only the visible Unit Sections may be declared as valid targets for attacks.

==== Terrain Elevations ====
Each hex will have its elevation marked on the map. If no elevation marking is present, the hex is treated as Ground Level (Elevation 0) by default.
Hexes with elevations above 0 represent hills or elevated terrain. Hexes with elevations below 0 represent depressions or valleys.
* Water: Water hexes descend to a depth of Elevation -1 to -2 below ground level, with Elevation -2 representing maximum depth. The lower the elevation level, the deeper the water. A Unit occupying a Water hex is always considered to be at the lowest elevation of that hex.
* Forest: Forest hexes share the same elevation as the terrain they occupy. For example, a forest located on Ground Level (0) is also considered to be at Elevation 0. Units occupying Forest hexes are positioned on the base terrain elevation—not atop the treetops.

==== Unit Height & Width ====
Standard Mechs, Vehicles, and Drones positioned at ground level (Elevation 0) occupy less than one full elevation in height.
An exception is made if a Unit’s waist section (where the legs and torso connect) extends into Elevation +1. In such cases, the Unit’s base elevation is considered +1.
Units are considered to be at the elevation of the hex they currently occupy when calculating LoS.
Most Units occupy less than one full hex in width. Large Units must also remain within a single hex but are permitted to extend up to 80% of their model beyond the hex boundary, provided their base remains clearly and visibly within the hex.

=== Weapon & Attack Requirements ===
Defines the conditions a Unit must meet to declare an attack, including weapon availability, range, line of sight, and any special restrictions.

==== Weapon Requirements ====
Before declaring an attack, the player must confirm that the Unit can use the weapons in its inventory by meeting the following conditions:
* AP Cost: Each weapon has a designated Action Point (AP) cost. This is the number of AP required to perform a single attack.
* Range: All weapons have a listed range value. The intended target must be within this range.
* Equipped Weapons Only: A Unit may only attack with weapons that are currently equipped—either mounted or held in-hand.

==== Attack Declaration ====
Once a target has been confirmed within the attacking Unit’s Field of View (FoV), the player must declare an attack. When declaring an attack, the player must state the following (in any order):
* The weapon or weapons being used.
* The target Unit, including the specific Unit Section or Sections being aimed at.
After the attack is declared, the total Action Point (AP) cost of all chosen weapons is subtracted from the Unit’s available AP.
Example: Unit A uses its beam saber to attack 3 times. The beam saber’s AP cost is 5, a total of 15 AP will be subtracted.

=== Combat Roll Resolution ===
This section explains how players resolve combat by making Accuracy, Assault, and Evasion rolls, including the effects of Critical Hits and Misses.

==== Attack Rolls ====
An Attack Roll is a dice roll made by the attacking player to determine whether their Ranged or Close Combat attack is On Target.
On Target simply means the attack that was made has successfully targeted the intended area.
Once all Attack Rolls have been made, the targeted Unit’s player will then make their rolls.

===== Accuracy =====
Also known as rolling for accuracy, is the process used to determine whether a ranged attack is On Target.
To perform an Attack Roll, the attacking player rolls one d8 for each declared attack. The result of each roll is then compared to the Unit's Accuracy Stat:
* If the roll is equal to or higher than the Unit’s Accuracy Stat, the attack is considered On Target.
* If the roll is lower, the attack misses completely.

===== Assault =====
Also known as rolling for assault, is the process used to determine whether a close ranged attack is On Target.
Similar to accuracy rolls, the attacking player rolls one d8 for each declared attack. The result of each roll is then compared to the Units Assault Stat:
* If the roll is equal to or higher than the Unit’s Assault Stat, the attack is considered On Target.
* If the roll is lower, the attack misses completely.

==== Defense Rolls ====
A Defense Roll is made by the defending player to determine whether incoming On Target attacks successfully hit their Unit.
After all Defense Rolls have been resolved, any attacks that successfully hit the Unit must be applied and damage calculated.

===== Evasion =====
Also known as rolling for evasion, this process determines whether On Target attacks actually hit the defending Unit.
To perform an Evasion Roll, the defending player rolls a d8 for each On Target attack made by the attacker. Each result is then compared to the defending Unit’s Evasion stat:
* If the roll is equal to or higher than the Evasion stat, the attack is successfully evaded and no damage is taken.
* If the roll is lower, the evasion fails and the Unit takes damage to the targeted Section.

==== Critical Rolls ====
When making Attack or Defense Rolls, there are two types of Critical Rolls: Critical Hits and Critical Misses.
* Critical Hit: Occurs when the die result is an 8. The attack cannot be evaded and deals 1.5× the weapon’s Base Damage (round up).
* Critical Miss: Occurs when the die result is a 1. The attack automatically misses.

=== Damage & Effects ===
During combat, weapons deal a set amount of damage known as Base Damage. This value can be found in the Base Damage column of the Unit’s Datasheet. Base Damage represents the standard amount of damage a weapon inflicts before other effects are applied. This amount is dealt for each successful hit on a target.

==== Resolving Damage ====
When an attack is successful, the damage is applied to the Unit Section chosen by the attacker. The defending player reduces that section’s Defense Points (DP) by the weapon’s Base Damage value. This happens during the attacking players turn and must be resolved before the turn ends.
If the DP of that section is reduced to zero, that section is destroyed. When a Unit Section is destroyed, it becomes non-operational and can no longer be targeted. All weapons, equipment, and special abilities located in that section are also destroyed and removed from play.

==== Resolution Order ====
All attacks are resolved in the order they occur. When resolving multiple hits on a single Unit from the same weapon, all hits are rolled and resolved simultaneously. When resolving hits made with different weapons, resolve all rolls and resulting damage from one weapon before proceeding to the next.
Example: Unit A successfully hits Unit B’s torso with three beam rifle shots, dealing a total of 15 damage. This value is then subtracted from the torso’s Defense Points. Unit A then hits Unit B’s torso again with two rocket shots, dealing a total of 20 damage. This value is also subtracted from the torso’s Defense Points.
Destroyed Unit Sections
When a Unit Section is destroyed, the player may remove the corresponding piece from the model or place a Destroyed Limb token to mark it. In either case, the associated Status Effect is immediately applied:

==== Destroyed Vs. Inoperable ====
A Unit is considered Destroyed when its Torso (for Mechs) or Cockpit (for Vehicles)

Durability Points are reduced to 0. When a Unit is destroyed, leave its model on the battlefield, placed face down. If the hex it occupies does not already contain a terrain effect, that hex becomes a Black Hex.
A Unit is considered Inoperative when its core section remains intact but it can no longer function effectively:
* Mechs: If the Torso Unit Section is intact but all limbs are destroyed, the Unit is Inoperative.
* Vehicles: If the Cockpit Unit Section is intact but the Unit loses all mobility sections, it is Inoperative.
An Inoperative Unit may still participate in an engagement if it has functional Drones, Mounted Weapons, or Handheld Weapons.

==== Status Effects ====
Status Effects represent ongoing conditions that change how a Unit behaves in combat. They can come from abilities, weapons, or terrain features.
{| class="wikitable" style="margin:auto"
|-
! Name !! Effect
|-
|Abyssal ||* Standard Movement is limited to 2 Movement Points.
* At the start of its turn, the Unit suffers 10 damage to its Torso Unit Section.
|-
|Airborne || * If a Unit has the [AIR] Movement Mechanism, place an elevation token (+1, +2, +3) beside it to indicate its current elevation. This token is removed when the Unit returns to solid ground.
|-
|Blinded ||
* Unit gains -1 to Accuracy and Assault Rolls.
* Reduces non-melee weapon ranges by 50% (rounding up).
|-
|Conceal ||
* Unit gains +1 to Evasion Rolls against Long Ranged Attacks.
|-
|Crippled (Partial) ||
* Standard Movement is reduced by 50% (rounding up).
* Unit gains -1 to Assault Rolls.
|-
|Crippled (Severe) ||
* Standard Movement is limited to 1 Movement Point.
* Unit gains -2 to Assault Rolls.
|-
|Destroyed Limb ||
* Unit cannot use weapons or equipment with the destroyed Unit Section.
* Any handheld weapons are dropped onto the battlefield in the Unit’s hex.
|-
|Euphotic ||
* Standard Movement is limited to 2 Movement Points.
|-
|Grounded ||
* The Unit is considered to be at 0 Elevation (Ground Level).
* Cannot perform Evasions or forward movements (unless otherwise stated).
|-
|Hold ||
* Unit cannot make any attacks or movements.
|-
|Ice Buildup ||
* For each Ice Buildup token attached to a Unit, reduce its Standard Movement Points by 1 and its total AP storage by 4.
* Upon reaching 3 stacks of Ice Buildup, Unit gains System Error status effect.
* Ice buildup represents water freezing and shorting a Units electronics. This effect remains until the tokens are removed.
|-
|Immobilized ||
* Unit cannot perform a movement until condition is removed.
* Cannot Evade.
|-
|Limbless ||
* Unit cannot perform grapples, use handheld weapons/equipment, or interact with objects that require arms.
* Break Grapple Command Action costs 4AP.
* Any handheld weapons are dropped onto the battlefield in the Unit’s hex.
|-
|Sand Buildup ||
* For each Sand Buildup Token attached to a Unit, reduce its Standard Movement Points by 1 and apply a –1 modifier to all attack and defense rolls made by that Unit.
* Upon reaching 3 Stacks of Sand Buildup, Unit gains System Error status effect.
* Sand Buildup represents sand and dust clogging a Unit’s joints and systems. This effect remains until the tokens are removed.
|-
|Static Buildup ||
* Upon reaching 6 stacks, Unit gains System Error status effect.
|-
|Submerged ||
* If a Unit has the [AQN] Movement Mechanism, place an elevation token (-1 or -2) beside it to indicate its current elevation on blue hexes. This token is removed when the Unit returns to solid ground.
|-
|System Error ||
* Unit ends its turn immediately and removes all buildup effects.
|}

==== Close Quarters Combat ====
This sections outlines the rules for direct, physical engagements between Units at close range.

===== Basic Attacks =====
A Unit can make basic attacks during its Close Combat Phase, only if no weapons are equipped. Basic attacks represent using the Units body (punches, kicks, strikes, etc.) to deal minimal damage. All Units can make these attacks and does not need to be on the Units Datasheet.
These do not gain bonuses from Systems, Mods, or Traits unless otherwise stated.
* Cost: 1 AP
* Range: 1
* Damage: 1 Base Damage

===== Grappling =====
Grappling occurs when a Unit physically seizes another. Only Units with manipulators (at least 1) can perform a Grapple, and it can only be initiated during the Close Combat Phase.
To perform a Grapple, follow the chart below:
# Engage Grapple
#* Attacker pays 2 AP.
#* Attacker rolls for Assault.
# Grapple Check
#* Success > Go to Step 3.
#* Fail > Grapple Ends (player may go back to step 1).
# Grapple Options (Attacker chooses one)
#* Throw > Go to Throw.
#* Hold > Go to Hold.
# Collision Damage
#* Formula: 2 x (Defender Class x Throw Distance)
#* Special Cases:
#** Structure Intact
#** Structure Destroyed

'''Throw'''
A Unit physically throws another Unit a set distance. Max Throw Distance (in hexes):
(Attacker Class – Defender Class) + 2

A Unit cannot throw a Unit that has a classification higher than its own.
Landing Outcomes (choose based on destination):

* Into a Structure:
** Defender is placed into the Structures hex (not on the structure), FoV facing the Attacker.
** Apply collision damage to the Defenders Torso Unit Section and the Structure.
* Into a Hex:
** Defender lands supine, FoV facing the Attacker.
** Apply collision damage to the Defenders Torso Unit Section.*
* Into a Hex with other Unit(s):
** Each Unit in the hex must make an Evasion Roll.
** Failure: Apply collision damage to the Unit(s) Torso Unit Section.
** Success: Move into any adjacent open hex within their FoV, facing any direction.
** If no hex is available, the Unit(s) instead applies collision damage to their Torso Unit Section.
** Defender also lands supine, FoV facing the Attacker, and applies collision damage to the Torso Unit Section.
* Blue Hexes:
** Units thrown into a blue hex take half collision damage (rounding up).

'''Hold'''
A Hold represents one Unit grappling and locking down another in close combat, restricting its ability to act.
* Initiating a Hold:
** Move the Attacking Unit into the same hex as the Defending Unit.
** The Defending Unit immediately gains the Immobilized status effect.
* Breaking a Hold:
** The Defending Unit must use the [Break Contact] Command Action to escape.
* Restrictions:
** While holding, the Attacker cannot move but may still attack using mounted weapons or any handheld weapon without the [2H] tag.

'''Structure: Intact'''
If a thrown Unit collides with a structure and the damage deal does not exceed the structures current defense:
* The Unit gains the Immobilized status effect.

'''Structure: Destroyed'''
If a thrown Unit collides with a structure and the damage dealt exceeds the structures current defense:
* The Structure collapses onto the Unit.
* Apply the Structures defense value as bonus damage to the Torso Unit Section.
* Remove the destroyed structure and replace it with a Black Hex.
* Place the Defending Unit supine, with its FoV facing the Attacker.
* On the Defenders next activation, it must use the [Recover] Command Action to stand. If it does not, the Unit remains supine.

Example: Unit A grapples Unit B, spends 2 AP, and succeeds on an Assault Roll. With a higher Classification (4 vs 3), Unit A throws Unit B 3 hexes (4-3)+2. Unit B lands 2 hexes away, supine and facing Unit A, and suffers 12 Torso damage (3x2)x2 from the collision.

===== Thruster Impact =====
A Thruster Impact occurs when a Unit uses thrusters to rapidly advance and collide with an enemy Unit, causing damage and displacement.

When a Unit conducts a Thruster Movement and an enemy lies within its movement path, the Thruster Movement becomes a Thruster Impact.

Thruster Impacts can also be performed in the air or in the water.

Range Requirements:
* Target must be beyond the Units Standard Movement Range.
* Target must be within the Units Thruster Movement Range.

AP Cost:

The attacking Unit pays 2 AP + 1AP per 2 hexes traveled (rounding up).

Resolution:
# Confirm the target is within range and select the endpoint hex.
# Spend the AP cost.
# The attacking Unit makes an Assault Roll:
#* Failure: The Unit moves to the closest hex in its path toward the target and ends its turn.
#* Success: The defending Unit chooses one of the following responses:

Do Nothing
* Attacker slams the defender one hex past the designated endpoint.
* Apply damage to defenders Torso/Cockpit Unit Section.
* Attacker ends it turn immediately.

Evade
* Defender makes an Evasion Roll.
** Success: Move to any open hex within current FoV and out of the attackers path, facing the same direction. Flying Unit may move one elevation higher.
** Failure or no available hexes: Attacker slams the defender one hex past the endpoint. Damage is applied to the defenders Torso/Cockpit Unit Section.
** Attacker continues to the designated endpoint and ends its turn.

Stand Firm
* Defender makes an Assault Roll.
** Success: The defender blocks the charge (see Class Difference) and damage is applied to the attacking Units Torso Unit Section. The attacker stops in the adjacent hex.
** Failure: Attacker slams the defender one hex past the endpoint. Damage is applied to the defenders Torso/Cockpit Unit Section.
* Class Difference: If the defender’s Class is higher than the attacker’s, the charge is stopped completely. If the defender’s Class is equal to or lower, the charge continues as normal and both Units take damage.

Damage:
Thruster Impact damage is determined by the Attacking Units class (see below).

'''Other Situations'''
While engaging in a Thruster Impact, the attacking Unit may run into various situations.

Slamming Unit into Elevated Terrain:

If a Thruster Impact attempts to move a target into a hex with elevated terrain, the target does not enter that hex. Instead, it takes 2x normal Thruster Impact damage to its Torso/Cockpit Unit Section. The attacker ends movement in the adjacent hex.

If the targeted Unit successfully evades the incoming attack, the attacking Unit instead collides with the elevated terrain, takes the full damage from the impact, and ends its turn in a hex adjacent to that terrain.

Slamming Unit into Multiple Units:

If a Thruster Impact attempts to move multiple targets, the action cannot be completed.

== Other Actions ==
This section covers special actions and mechanics outside of standard movement and combat. These include Command Actions that allow Units to alter their behavior, Systems, Mods, and Traits that provide unique abilities or upgrades, and rules for handling falling and fall damage during play.

Command Actions
Command Actions are special actions a Unit can perform during its turn that are not tied to any specific phase. Each Command Action costs 2 Action Points (AP) and may be used multiple times in a single turn unless otherwise stated.

Command Actions are divided into three categories:
* State: Effects that resolve instantly when used and do not remain active..
* Stance: Actions that may be taken out of turn. Activating a Stance immediately ends the Unit’s current turn.
* Order: Commands issued to Drone Units, allowing them to act under the Main Unit’s direction.

{| class="wikitable" style="margin:auto"
|-
!Name !!Category !!Description
|-
|Recover
||State
||A Unit returns to a standing position from knocked down state.

If the Unit is knocked prone or laying on the ground, return to its standing position.
|-
| Press On
||State
||The pilot pushes the Unit beyond safe limits, refusing to yield ground.

Unit gains an additional Standard Movement Point.
|-
|Break Grapple
||State
||With a surge of strength, the Unit tears free from its opponent’s hold.

Perform an Assault Roll: If successful, the Unit breaks free. If unsuccessful, no change.
|-
|Exchange
||State
||The Unit swiftly switches its weapon loadout to adapt to the changing battle.

Allows a Unit to replace an equipped Weapon with one being carried.
|-
|Retrieve
||State
||A mechanical arm or manipulator reaches out to reclaim a dropped item.

A Unit with a free hand may pick up a dropped or disarmed allied weapon from the same hex and equip it.
|-
|Release
||State
||The Unit disregards a weapon or equipment to lighten its load.

A Unit may drop a Weapon or Equipment from one of its hands onto its current hex.
|-
|Transform
||State
||Armor shifts, joints realign, and the Unit reconfigures into its alternate form.

Unit shifts into its Alternate Form, gaining bonuses from that form. Weapons with the [GB] tag may also Transform. Use again to revert.
|-
|Purge Buildup
||State
||The Unit vents pressure and heat, clearing away harmful environmental effects.

Roll a single D8 die. On a 5+, remove one stack of a buildup status effect. On a 4-, no change.
|-
|Kneeling Position
||State
||The Unit braces itself, lowering its stance for improved stability and accuracy.

Mech Units ONLY
Unit kneels, gaining +1 Accuracy Rolls but cannot Evade. May be used once per turn. Unit must use Recover to stand.
|-
|Prone Position
||State
||The Unit drops flat against the ground, becoming a low, steady firing platform.

Mech Units ONLY.
Unit gets into a prone position, gaining +3 to Accuracy Rolls but cannot Evade. Must kneel before getting into or out of the prone position. Cannot enter the prone position if its facing direction is obstructed by a Structure or another Unit.
|-
|Takeoff
||State
||Engines roar to life as the Unit propels itself back into the sky or ocean.

The Unit moves 3 hexes straight and changes Elevation by 1 to regain Airborne or Submerged status. The Unit cannot Evade during this activation. If any hex in its path imposes a movement penalty, the Unit still moves forward but remains Grounded.
|-
|Offensive Stance
||Stance
||The Unit prepares to attack any enemy entering its Field of View (FoV) and weapon range.

Mech Units only
Enter Offensive Stance by choosing a ranged weapon, reserving its AP cost, and selecting a direction to focus the Unit’s Line of Sight. The reserved AP cannot be used for other actions.

If an enemy Unit crosses this Line of Sight while within the weapon’s range, the Unit immediately makes an Attack with that weapon, interrupting the enemy’s movement. The first Unit to do so becomes the target.

A Unit crosses the Line of Sight when its movement path passes across the focused line extending from the Unit.

The stance ends if:
* The Unit makes the Attack (reserved AP is spent).
* The Unit is successfully hit (reserved AP is lost).
* The Unit’s next activation begins (reserved AP is returned).
While in this stance, the Unit cannot Evade.
|-
|Defensive Stance
||Stance
||The Unit braces using a Shield or Two-Handed Weapon, redirecting all incoming damage from its front arc to that item.

Mech Units only
When a Unit enters Defensive Stance, choose one equipped Shield or Weapon. All incoming damage to the Unit is redirected to the chosen item instead.

While in this stance, the Unit cannot change facing or Evade.

The stance ends immediately if the chosen Shield or Weapon is destroyed, or at the start of the Unit’s next activation.
|-
|Parry Stance
||Stance
||The Unit enters a guarded combat posture, prepared to deflect incoming melee strikes.

Mech Units only
While in Parry Stance, the Unit may parry one successful melee attack against it, negating all damage from that attack. The Unit must have at least one Arm Unit Section to perform a parry.

The stance ends after the parry is made or at the start of the Unit’s next activation.
|-
|Deploy
||Order
||The drone launches from its bay, entering the battlefield to extend the Unit’s reach.

Place 1 attached AI or Non-AI Drone on a hex within 2 hex radius of the Main Unit facing any direction.
|-
|Guidance
||Order
||The Unit feeds targeting data to its drone, directing it to assist with precision strikes.

Activate a linked AI Drone. Once the AI Drone becomes Inactive, the Main Unit continues its activation.
|-
|Recall
||Order
||The drone disengages and returns to the Unit, awaiting further commands.

Remove 1 AI or Non-AI Drone from a hex within 2 hex radius of the Main Unit and attach it to the Main Unit.
|-
|Reposition
||Order
||The drone shifts its position across the battlefield to gain a tactical advantage.

Move 1 hex in any direction but it must remain within 2 hexes of the Main Unit.
|}
=== Transforming ===
Some Units are capable of shifting from a Base Form to an Alternate Form. Transforming represents a Unit changing its physical structure and mode of operation to gain new abilities and restrictions.

When a Unit transforms, its stats, movement, and abilities switch to the Alternate Form, while any existing damage or status effects are retained. A Unit may only transform once per activation.

Transforming Units use a Datasheet marked with a “T” in the bottom right corner. On the datasheet, a Unit’s Base Form stats are marked with a single arrow, while its Alternate Form stats are marked with a diverging arrow.

A transforming Unit’s Base Form is always a Mech-type, and its Alternate Form is always a Vehicle-type. The [Transform] Command Action allows the Unit to switch between these forms.

While in its Alternate Form, the Unit gains all bonuses and restrictions associated with that Movement Mechanism

=== Falling & Fall Damage ===
A Unit falls when it is thrown, pushed, or otherwise forced from its position into a hex below its current elevation.

Fall Damage formula:
2 x (Unit Class x Elevation Height)
When a Unit falls:
# Distance – Measure the number of Elevation Levels the Unit descends before reaching a valid impact area.
# Impact – Upon impact, the Unit takes Fall Damage to its Torso or Cockpit Unit Section.

Special Rule:
* Landing in a Blue Hex reduces fall damage by half (rounded up).

''Example: Unit A is a Class 4 mech flying above the battlefield at the +3 elevation. It takes enough damage from Unit B to lose the [AIR] movement mechanism. Unit A immediately falls to Ground Level and suffers [2x(4x3)] 24 Torso damage.''

=== Drone Operations ===
Drone Operations outlines how drones with Artificial Intelligence, and without, function on the battlefield. This section explains what they are, their control requirements, activation timing, and interaction with their assigned Main Units.

==== A.I. Drones ====
AI Drones are autonomous Units controlled by artificial intelligence. Each AI Drone is considered its own Unit and therefore has its own Datasheet. The pilot assigned to an AI Drone must be an AI, selected during Rank/AI selection.
AI Drones cannot be deployed independently and must be deployed with its Main Unit, a Mech or Vehicle Unit with a Human Pilot to which the Drone is linked.

To control an AI Drone, a few requirements need to be met by both the Main Unit and the AI Unit.

Main Unit:
* Must have the Drone Management Mod.
AI Drone Unit:
* Must have the Drone Agent Mod.
* Its deployment cost must not exceed the deployment cost of the Main Unit its linked to.

During gameplay, an AI Drone may be activated during its Main Unit’s activation via the [Guidance] Command Action. Once activated, the AI Drone functions as a normal Unit, following standard activation and combat rules.

If the AI Drone is not activated during its Main Unit’s activation, it may instead activate normally on its own turn.

==== Non A.I. Drones ====
Non-AI Drones are small, remotely controlled auxiliary weapons that operate under the direct control of a Main Unit. These drones serve as extensions of the Main Unit’s offensive or defensive capabilities rather than functioning as independent Units.

Non-AI Drones are listed on the Main Unit’s Datasheet under the Weapons and Equipment Inventory module like any other weapon or equipment. However, they gain the [DR] tag in addition to the tag representing their Movement Mechanism: [TRS], [AIR], or [AQN]. The [DR] tag identifies the weapon or equipment as a Non-AI Drone and allows it to act as such.
To field Non-AI Drones, the Main Unit must have the Drone Management Mod equipped, and each Drone must be physically attached to the Main Unit at deployment. A Unit may have no more than 3 Non-AI Drones deployed on the battlefield at one time, regardless of how many it has equipped unless stated otherwise.

After deployment, Non-AI Drones can be released using the [Deploy] Command Action (one Drone per CA) and placed anywhere within a 2-Hex radius of the Main Unit, facing any direction. Once deployed, drones move in tandem with the Main Unit but maintain their initial facing regardless of the Main Unit’s orientation. They also follow standard Hex Occupancy rules.

Individual Drones may be repositioned after deployment using the [Reposition] Command Action.
If the Main Unit is destroyed, all deployed Non-AI Drones immediately become inactive and fall to the ground.

== Terrain ==
Battlefield terrain can include anything from towering buildings to small rocks and trees. Some features are mission-specific, while others are represented by colored hexes, each providing unique advantages or disadvantages. Terrain can affect movement, line of sight, and combat outcomes, so its placement is a key part of battle strategy.

=== Elevations ===
Elevation adds a tactical layer to the battlefield, providing Units with advantages in movement and combat positioning. The game uses six elevation levels: -2, -1, 0, +1, +2, and +3. Ground Level (0) represents table height and is where most engagements occur unless otherwise specified by the Mission.

Each elevation level represents a 4.5 inch difference from the one above or below it. This can be measured by standing an Action Base 4 or 5 vertically (point-to-point).

Blue Hexes, which represent negative elevations such as lakes or oceans, can only be placed on Ground Level (0).
The +3 Elevation level is reserved for Units with the [AIR] Movement Mechanism, representing high-altitude or flight-level movement. Only Units capable of flight can occupy or move through this elevation.

A Unit’s elevation is determined by its center mass, typically the waist for Mech Units and the cockpit for Vehicle Units. If the Unit’s center mass is higher or lower than 4.5 inches from its current elevation, it is considered to be at the next level. The same rule applies to Structures and Terrain features.

If a Unit moves to an elevation other than Ground Level, place an elevation token beside it to mark its current elevation for reference.

=== High Ground Bonus ===
When an attacking Unit is at a higher elevation than its target, it gains a High Ground Bonus (HGB). The bonus value is determined by the elevation difference between the attacker and the target. Units attacking targets at higher elevations do not receive this bonus. Bonuses do not stack.

=== Hex Colors ===
Hex Colors represent different types of terrain and environmental conditions on the battlefield. Each color corresponds to a specific terrain type that provides unique effects, advantages, or restrictions to Units occupying or moving through those hexes.

When setting up a battlefield, Hex Colors must be placed according to the Mission or Terrain rules, with different colors placed at least one hex apart unless otherwise stated.

Some Hex Colors also indicate elevation changes or environmental hazards, such as water, rubble, or impassable terrain.

'''Grey Hex'''

Grey Hexes represent clear, open terrain. Flat ground free of obstructions or environmental hazards.
Units moving or fighting within Grey Hexes experience no bonuses or penalties. These hexes serve as the standard terrain type for most battlefields.

If a hex isn’t clearly marked as having another color, assume its grey.

'''Green Hex'''

Green hexes represent areas covered in trees and dense foliage.

Standard Move actions cost +1 Movement Point per hex.

Apply a –1 Accuracy modifier for each Green Hex within a Unit’s Line of Sight to its target, representing the trees and dense foliage. This penalty stacks cumulatively.

A Unit occupying a Green hex gains the Conceal status effect.

'''Light Blue Hex'''

Light Blue hexes represent bodies of water that are shallow enough to reveal the bottom, yet deep enough to submerge an entire Unit beneath the surface.

These hexes represent –1 Elevation.

When a Unit enters or moves through a Light Blue Hex without the proper Movement Mechanism to operate in or above water, it gains the Euphotic status effect.

'''Dark Blue Hex'''

Dark Blue hexes represent the deepest regions of a body of water, areas devoid of light, subjected to crushing pressure, and near-freezing temperatures.

These hexes represent –2 Elevation.

When a Unit enters or moves through a Dark Blue Hex without the proper Movement Mechanism to operate in or above water, it gains the Abyssal status effect.

'''Red Hex'''

Red hexes represent superheated terrain, such as lava fields or other high-temperature surfaces, capable of damaging even heavily armored Units and vehicles.

Units using the [TRS] Movement Mechanism take 10 damage to all Unit Sections with the [TRS] tag when moving over a Red Hex.

Units with the [AIR] Movement Mechanism are unaffected.

'''Black Hex'''

Black hexes represent collapsed structures or debris. Thick black smoke and unstable footing make these areas treacherous for movement and targeting.

Standard Move actions cost +1 Movement Point per hex.

Units using [TRS] Movement Mechanisms must also roll 1d8 when entering a Black Hex; on a result of 1–2, the Unit takes 5 damage to all Unit Sections with that tag due to shifting rubble.

[AIR] Movement Mechanisms are affected by the movement penalty but ignore the damage effect.

Apply a –1 Accuracy modifier for each Black Hex within a Unit’s Line of Sight to its target, representing the thick smoke and dust. This penalty stacks cumulatively.

'''Tan Hex'''

Tan hexes represent arid, barren landscapes with minimal precipitation and loose, shifting ground.
Standard Move actions cost +1 Movement Point per hex.

Units using the [AIR] Movement Mechanism ignore this penalty.

For every 2 Tan Hexes moved across in a single activation, a Unit gains 1 Sand Buildup Token.

'''White Hex'''

White hexes represent environments blanketed in snow and ice and are subjected to harsh, cold winds. Mechanical strain is increased under these conditions.

Standard Move actions cost +1 Movement Point per hex.

For every 2 White Hexes moved across in a single activation, a Unit gains 1 Ice Buildup Token.

===Buildings & Structures ===
Structures can serve as cover, obstacles, or tactical objectives, and may be destroyed to alter the battlefield in a player’s favor.

Buildings and other Structures do not need to be placed on Black Hexes, but when destroyed, any hexes they occupy become Black Hexes to represent collapsed debris.

Some Structures are tall enough to reach higher elevations. To determine this, stand a standard hex vertically (4.5 inches); if the Structure’s height exceeds this, it occupies a higher Elevation Level.

Use the chart below to determine a Structure’s Defense Points, based on its size (number of hexes occupied) and height. The green values represent the most common Structure defenses. Use a d20 to track remaining Defense Points during play.
When attacking a Structure, attack rolls are not required since all attacks automatically hit. Apply Base Damage as normal, and subtract any damage dealt from the Structure’s total Defense Value until it is destroyed.

To target a Unit positioned behind or within a Structure, you must first destroy the Structure, then make a separate attack against the intended Unit.

'''Non-Hex Terrain'''

Also referred to as Scatter Terrain, these are pieces of terrain not connected to a specific Hex Color or Structure. They can serve as visual decoration or provide Cover during gameplay. When setting up the battlefield, players should mutually agree on which pieces grant Cover and which are purely decorative.

'''Terrain Placement'''

Before deploying Units, players must construct the battlefield using terrain pieces. Terrain should create meaningful tactical choices without unfairly favoring either side.

Unless a Mission states otherwise, terrain is placed using the following guidelines:
* Players should use enough terrain to break up long lines of sight and provide multiple movement routes across the battlefield.
* Terrain should be distributed evenly across the play area, avoiding large empty zones or overly dense clusters in a single area.
* Elevated terrain should be limited in height and spread across the battlefield rather than concentrated in one area.

Players may place terrain using the following method:

Agreed Placement: Players take turns placing terrain pieces anywhere on the battlefield following the placement guidelines above. This method is recommended for casual play.

Once terrain is placed, players may not move terrain pieces unless a rule or Mission effect allows it.
Missions may override or add to these rules by specifying required terrain features, fixed objective locations, or special placement conditions.

== Missions ==
Missions define the framework in which battles take place. Each mission is built around three core elements: the Deployment Zones, the Primary Objectives, and the Secondary Objectives.
Missions fall into two main categories: Standard and Narrative. Standard missions are designed to emphasize balance and fairness, giving each player an equal opportunity to succeed. Narrative missions prioritize storytelling and scenario-driven play and may result in intentionally uneven or asymmetric battles.
The mission being played should always be chosen before the battlefield is set up.

=== Objectives ===
Objectives define how a game is won. Most commonly, this involves capturing or holding specific locations on the battlefield, but an Objective may be any condition that can be clearly measured with a success or failure outcome.
Objectives defined by a Mission are referred to as Primary Objectives. These represent the main focus and intended method of victory for that mission.

Some missions may also include Secondary Objectives, which provide alternative scoring opportunities and can be used to help balance gameplay when opposing armies are not optimized for the Primary Objectives.

=== Deployment Areas ===
Deployment Areas define where Units are placed on the battlefield and how much space is available for deployment.
Determining Deployment Area: The players can mutually agree on which Deployment Area to begin with or can roll a d8.

[ 1 or 8 ] – Reroll

[ 2 or 5 ] – Standard Deployment

[ 3 or 6 ] – Cornered Deployment

[ 4 or 7 ] – Long Side Deployment

Deployment Order: Players roll a d8; the higher roll chooses who deploys first. The other player chooses table side (A or B). The first player places one Unit in their deployment area, then players alternate placing Units. When one player has no Units left to place, the other deploys all remaining Units.

There are three base types of Deployment Areas:

'''Standard Deployment'''

'''Cornered Deployment'''

'''Long Side Deployment'''

=== Core Missions ===
These are the primary game modes used for regular play. These missions are designed to be balanced, repeatable, and suitable for any army composition. Each Core Mission provides a defined setup, deployment method, and set of objectives that both players follow.

Unlike Narrative Missions, which are story-driven scenarios with highly specific setups, Core Missions use shared rules and formats to ensure fair and consistent gameplay. Only Core Missions are included in this rulebook. Narrative based missions are available separately on the official website.

The following section presents the available Core Missions and their rules in the following format:
* Mission Name
* Engagement Size
* Deployment
* Primary Objective
* Objective Scoring
* Game Length
* Victory Condition

'''High-Value Target (HVT)'''

Deployment:
* Any
Primary Objective:
* Each player chooses one Unit from their squad to be their designated High Value Target.
Objective Scoring:
* For each enemy Unit destroyed, the player who destroyed it gains 1 Victory Point (VP).
* If the destroyed Unit was the enemy HVT, that player gains 3 Victory Points instead.
Game Length:
* The battle lasts 6 rounds or until one player has no Units remaining.
Victory Condition:
* The player with the most Victory Points at the end of the 6th round is the winner.

'''Command & Control'''

Deployment:
* Standard (Recommended)
Primary Objective:
* The player with initiative rolls 1d4 + 2 to determine the total number of Objective Markers to be placed on the battlefield. Players alternate placing these Markers down starting with the player who moves first.
* Each player may place only one Objective Marker within their own Deployment Area.
All Markers must be placed at least 4 hexes away from any other Marker and must also be 1 hex away from the tables edge.
* Markers may not be placed free-floating on higher elevations.
Objective Scoring:
* If a Unit ends it turn on an Objective Marker, that marker is considered captured by that Units player.
* At the end of each round, a player gains 1 Victory Point for each Marker they control. Objective Markers located within the opponents Deployment Area are worth 2 Victory Points instead.
* A captured Objective Marker remains under a players control even if the Unit moves away, until an opposing Unit ends its turn on that Marker and captures it.
Game Length:
* The battle lasts 6 rounds.
Victory Condition:
* The player with the most Victory Points at the end of the 6th round is the winner.
* If tied, the player who lost the fewest Units wins.
* If still tied, the game is a draw.

'''Asset Retrieval'''

Deployment:
* Long Side (Recommended)
Primary Objective:
* The player with Initiative places one Objective Marker on the battlefield. The Marker must be placed at least 4 hexes away from any Deployment Area.
Objective Scoring:
* If a Unit is on the same hex as the Objective Marker and has a free hand or manipulator, it may use the [Retrieve] Command Action to pick up the Marker.
* The hand or manipulator holding the Marker cannot be used for any purpose while carrying it, including for the [Grapple] Command Action or for two-handed weapons.
* A Unit carrying the Marker may use the [Release] Command Action to place the Marker on its current hex.
At the end of each round:
* A player gains 2 VP if one of their Units is carrying the Marker.
* A player gains 1 VP if one of their Units is on the same hex as the Marker but not carrying it.
Game Length:
* The battle lasts 6 rounds.
Victory Condition:
* The player with the most Victory Points at the end of the 6th round is the winner.
* If tied, the player who lost the fewest Units wins.
* If still tied, the game is a draw.

'''Control Points'''

Deployment:
* Cornered (Recommended)
Primary Objective:
* The player with initiative rolls 1d4 + 2 to determine the total number of Objective Markers to be placed on the battlefield. Players alternate placing these Markers down starting with the player who moves first.
* Each player may place only one Objective Marker within their own Deployment Area.
All Markers must be placed at least 4 hexes away from any other Marker and must also be 1 hex away from the tables edge.
* Markers may not be placed free-floating on higher elevations.
Objective Scoring:
* For If a Unit occupies the same hex as an Objective Token at the end of the round, that player gains 2 VP.
* However, if an opposing Unit is within 1 hex of that Objective Token, no VP is awarded for that token this round.
Game Length:
* The battle lasts 6 rounds or until one player has no Units remaining.
Victory Condition:
* The player with the most Victory Points at the end of the 6th round is the winner.
* If tied, the player who lost the fewest Units wins.
* If still tied, the game is a draw.

{{CoreNavigation}}
[[Category:Rules]]

Core Rules

2026-04-01T17:18:00Z

Lavtiz29: Okay so I need to finish the rolls section with bold and then clean up any more bullets. Afterward is the Other Actions section

Core Rules

2026-03-15T21:23:09Z

Lavtiz29: I updated until Unit information. Hopefully it's fine. I know pictures will be aproblem

== Introduction ==
The 30 Minute Missions: Wargame (30MM:W for short) is a mech-based tabletop miniatures game using Bandai Spirit's 30 Minutes Missions line of 1/144 scale mecha model kits. The focus of this game is on:
• The ability to play missions in, roughly, 30 minutes (excluding setup); and
• The customizability and modular designs for model kits.
The game is played over a series of rounds. Each round consists of alternating turns between each player choosing one of their Units, moving to the best position, attacking the enemy, or holding an objective. The battlefield is played with varying terrain, elevations, and structures. Missions can vary from eliminating the enemies to securing intel.

== Objective ==

The game is won after the primary objective of the mission you are playing has been completed. These range from holding an objective for multiple turns, getting an object and moving to your side of the board, or simply destroying the enemy forces.

== Required Components ==
* 30 Minutes Missions Models (assembled)
* Datasheets (filled out)
* Hex Grid Game Mat
* Game Tokens
* D8 Dice
* D20 Dice
* Various Hex Colors

* The hex game mat is roughly 40x60” with 4.5” hexes (vertex to vertex) setup in an 11 hex by 15 hex grid with the flat sides horizontal.

=== Units and Squads ===
Each individual model on the battlefield is referred to as a Unit. All Units controlled by a single player together make up that player’s Squad.
When a rule refers to a Unit, it applies only to that specific model. When a rule refers to a Squad, it applies to all of that player’s Units collectively.

=== Dice ===
To play the 30MM: Wargame, you will need two types of dice: eight-sided dice (D8) and twenty-sided dice (D20). Each player should have at least 5–10 D8s to keep gameplay fast and 1 D20 for every Unit they control.
The D20 is used to track a Unit’s Action Points (AP), while the D8 is used for all attack, defense, and ability rolls.
Occasionally, the rules may reference alternate dice notations such as D4, 2D8, or D8 + 1:

* D4: Roll a D8 and halve the result, rounding up.
* D8 + 1: Roll a D8 and add 1 to the result.

==== Rolls and Rerolls ====
When making a roll, the player must roll equal to or higher than the target value listed under the Unit’s Modified Stat on its Datasheet. Each roll represents a single attack, defense, or action attempt.
Example: Unit A makes two ranged attacks against Unit B, which has a Modified Evasion Stat of 7.
The defending player rolls 2D8, scoring a 6 and a 7.
This means one attack hits (6) and one attack is evaded (7).
If an ability allows you to reroll dice, select the number of dice indicated and reroll them, starting with the lowest results first. The outcome of the reroll is final, even if it is worse than the original roll.

=== Tokens ===

Tokens are used to track various effects, conditions, and states that occur during gameplay.
Whenever a rule or status effect instructs a player to place a token, it should be placed face-up next to the affected Unit to clearly indicate the current condition.

=== Objective Markers ===

Objective Markers represent key tactical points, data nodes, or energy beacons on the battlefield that players must capture, defend, or destroy to complete mission objectives.
The standard Objective Marker model is built using a combination of Roy Roy leg parts (from the 30 Minute Missions Alto or Portanova kits), thrusters from the Option Parts Set 1, and structural components from the J1 runner, included in most 30MM kits.

Players may use Objective Marker tokens in place of the physical kit-built markers if preferred. Alternatively, an Objective Marker can be any model, piece, or object the players agree upon prior to starting the game, so long as all participants clearly understand what represents an active objective.
When placed on the map, Objective Markers do not obstruct movement or Line of Sight unless specified by the mission.

=== Datasheet ===
Each Unit is represented by a Datasheet, which contains all of the information required to operate that Unit effectively on the battlefield. The Datasheet lists every attribute, ability, and piece of equipment necessary to complete a mission.
While Units can differ greatly in how they function, every Datasheet follows the same layout and includes the following elements:

1. Unit Sections – Displays each section (Head, Torso, Left Leg, etc.) of the Unit and its Defense Points (DP).
2. Specifications – Lists the Unit’s detailed attributes such as classification, base AP, movement (standard and thruster), as well as total thruster durability.
3. Modified Stats – The Unit’s Accuracy, Assault, and Evasion values, used when making Attack and Defense Rolls.
4. Core Type – Shows the Unit’s base model and core statistics.
5. Unit Information – Includes the Unit’s Name, Type, and Movement Mechanism(s).
6. Pilot Information – Lists the Pilot’s Name, Rank, and Pilot Cost.
7. Systems, Mods, & Traits – Details the Unit’s special abilities and upgrades.
8. Weapons & Equipment Inventory – Records all weapons, gear, and equipment equipped by the Unit.
9. Deployment Cost (DC) – The total cost required to field the Unit in battle.

== Unit Information ==

Units are the giant robots (mechs) and vehicles used and while any thing can be used the game is designed with primarily with 30 Minute Mission parts in mind
.
=== Unit Sections ===

When a player is creating their Unit, they need to determine its Unit Sections. Unit Sections (US) are groups of individual parts combined to form specific areas that perform a certain function. First, a player needs to determine what type of Unit they created. Whether it be a Mech or a Vehicle each type has different Unit Sections available to it with many being used by the other types. Drones, which may be a Mech Unit, Vehicle Unit, or Equipment, may also require some of these Sections depending on build. Determine what Sections are needed for your Unit type by their movement requirements.
[[File:CS-Units.png| frameless | right| 500px | Battlefield Layout]]
'''Unit Sections:'''
* Head - The upper part of a Mech Units body. Contains complex camera systems to provide visuals to the pilot in real-time.
* AI Cockpit - Main Section of a Drone/Mech/Vehicle. Contains the A.I. pilot.
* Torso - Main Section of a Mech Unit. Holds the pilot.
* Cockpit - Main Section of a Vehicle. Holds the pilot.
* Arm - The upper limb of a Mech Unit. Has the ability to pick up/hold/carry various things.
* Tail - A modified arm, usually used for stability and aesthetics. May have weapons or thrusters attached to it.
* Leg - Each of the limbs on a Unit that provides movement.
* Aquatic Drive - A section that provides movement in Water and Deep Water Tiles. Requires for Aquatic vehicles.
* Aerial Drive - A Section that provides flight in some form either for hovering or actual flight. It is a requirement for Aerial Vehicles.
* Terra Drive - A Section that provides movement across the ground. It grants standard movement and is a requirement for Terrestrial Vehicles.

Next, Identify how many Sections your Unit has and what each one is. Mech Units normally have a head, two arms, two legs, as well as a Torso. Vehicle Units normally have at least one Drive Section and a Cockpit. Drones normally have a single AI Cockpit Section. All of these may vary depending on how you build your Units.

=== Unit Types ===
Units are divided into the following Types:

==== Mech ====
A unit that meets any of the following guidelines:

* Uses legs as its main form of transportation
* Has or relies on arms to perform its primary functions
* Has a clear and obvious torso

This is the standard Engagement Unit.

==== Vehicle ====
Any Unit that relies on jet propulsion, wheels, tracks/treads, or rotors as its primary source of movement and doesn't have any form of arms. Any part that isn't part of a Drive Core Section, weapon, or equipment is considered part of the Cockpit Core Section.

All Vehicle types gain the following changes to their gameplay:
* Must have a Cockpit Unit Section in place of a Torso Unit Section.
* When checking line of sight (LoS), the reference point starts at the Units cockpit.
* Cannot physically pick up or interact with any objects.
* Cannot change elevation [+/-] without appropriate Abilities.
* Cannot obtain the Jump Ability.

Vehicles are broken down into 3 categories: Terrestrial, Aerial, and Aquatic. Each one has specific requirements that must be met in order for a vehicle to be considered one or the other. Below is each category along with its Requirements, Restrictions, and Bonuses.

<div class="toccolours mw-collapsible mw-collapsed" style="width:97%; padding:0.5em">
<div style="font-weight:bold;line-height:1.6;">Terrestrial</div>
<div class="mw-collapsible-content">
Land-based vehicles.

Any Unit that meets the following requirements are to be regarded as a Terrestrial Vehicle Unit:
* Must contain at least two Terra Drive Unit Sections.
* Does not contain Flight Drive Unit Sections.
* Does not contain Aquatic Drive Unit Sections.

The following are restrictions that a Terrestrial Unit must follow:
* Weapon range is halved when firing through green hexes.
* Movement costs 2x when traveling over green hexes.

The following bonuses are given to Terrestrial Vehicles:
* FoV is all 6 hexes around the Unit (360 degrees).
* Main Cannon has an AP reduction of 3 (to a minimum of 4).

</div></div>

<div class="toccolours mw-collapsible mw-collapsed" style="width:97%; padding:0.5em">
<div style="font-weight:bold;line-height:1.6;">Aerial</div>
<div class="mw-collapsible-content">
Usually a plane, helicopter, or other vehicle for flying in appearance.

Any Unit that meets the following requirements are to be regarded as an Aerial Vehicle Unit:
* Must contain at least one Flight Core Part
* Does not contain Aquatic Drive Unit Sections.
* Does not contain Terra Drive Unit Sections.

The following are restrictions that an Aerial Unit must follow:
* Cannot move on 0 Elevation (Ground Level).
* Can only use thruster movement.
* All movement points must be used during activation. Failure to do so will result in Unit taking fall damage to Cockpit Unit Section.
* Standard movement is an exclusive Command Action that can only be gained with the use of rotor parts.

The following bonuses are given to Aerial Vehicles:
Strafing runs: When the unit passes directly over enemy units (a single elevation directly above) during the movement phase, it may pause its movement and conduct a single ranged combat or close combat attack. After the attack has been resolved, the unit can continue with its movement phase. This can be repeated.

</div></div>

<div class="toccolours mw-collapsible mw-collapsed" style="width:97%; padding:0.5em">
<div style="font-weight:bold;line-height:1.6;">Aquatic</div>
<div class="mw-collapsible-content">
Usually a boat, submarine, or other vehicle for navigating the water.

Any Unit that meets the following requirements are to be regarded as an Aquatic Vehicle Unit:
* Must contain at least one Aquatic Drive Unit Section.
* Must not contain Terra Drive Unit Sections.
* Must not contain Aerial Drive Unit Sections.

The following are restrictions that an Aquatic Unit must follow:
* Can only move over light/dark blue hexes.

The following bonuses are given to Aquatic Vehicles:
* Attacks made with missile pods don't need LoS.

</div></div>

==== Drone ====
Drones are typically smaller units or equipment controlled by a larger or more networked unit. Drones can be either mechs OR vehicles.

There are two categories of Drones:

* A.I. Drones
* Non-AI Drones

'''A.I. Drones:'''

AI Drones are drones that are controlled by artificial intelligence. These are considered their own Units and as such, get their own Datasheet. The pilot for this Unit must be an AI and can be selected when choosing the rank/AI.

'''Non-A.I. Drones:'''

Non-AI Drones are drones that need to be controlled by a Main Unit with the Control Management Mod.

</div></div>

=== Classification ===
{| class="wikitable" style="text-align:center; vertical-align:middle; background-color:#F8F9FA; color:#202122; float:right; margin-left:10px; "
|- style="font-weight:bold; background-color:#EAECF0;"
! Total Defense
! Classification
! Base Movement
! Base Action Points
|-
| 0 - 75
| Class 1
| 5
| 1d8 + 2
|-
| 76 - 150
| Class 2
| 4
| 1d8 + 2
|-
| 151 - 225
| Class 3
| 3
| 1d8 + 3
|-
| 226 - 300
| Class 4
| 2
| 1d8 + 4
|-
| 301+
| Class 5
| 1
| 1d8 + 4
|}
There are 5 different classifications that provide different starting bonuses and limitations based on the size of your Unit. This is determined by the Total Defense value of all of Core Parts combined.
<br clear=all>
=== Squads ===
Are groups of units usually no more than 5 as a game of 6 or more can become longer and slow down the game. These are generally called Lances or Fire Teams depending on size and your own preferences.

== Datasheets ==
Datasheets show detailed stats and abilities for each Unit. You will need to create a Datasheet for every Unit in your Squad. Which instructions for can be found [[Unit Datasheet Creation]].

== Gameplay ==
[[File:New Board 1.png| frameless | right| 500px | Battlefield Layout]]
=== Board Setup ===
All Missions take place on a battlefield overlayed by a hexagonal grid. [https://www.usagundamstore.com/products/pre-order-black-action-base-5?variant=49149953167&currency=USD&utm_medium=product_sync&utm_source=google&utm_content=sag_organic&utm_campaign=sag_organic&gclid=Cj0KCQjwjvaYBhDlARIsAO8PkE1rZ7dQrKWyU-YJ7NkAEjGGZ3eeKfcuHnwC42hsgGj3E1ObWF9jf2EaAl8UEALw_wcB Each hex space is the same size as an action base 4/5 - 4.5 inches]. This eliminates the need for measuring tools and makes movement/weapon ranges easier to calculate.

However, if a person wishes to play without hexes all movement can be done with action bases and movement being 4.5 inches per movement point.

A full-sized battlefield measures 14 hexes (58.5 in) on the long side by 11 hexes (38.3 in) on the short side, with the flat sides facing each player.

Missions will give suggestions on more specific terrain setups. It is suggested a matching terrain setup for each side when playing a destroy all targets type mission.

<br/>

=== Pre-Deployment ===

Players roll 1D8 to determine who goes first. The higher roll chooses who gets to be Attacker and who gets to be Defender. The Attacker goes first and has starting initiative, but the Defender chooses their Deployment Area.

In 3+ player games, players choose which team to participate on and share Units and turns with their teammates.
At the start of the round players roll for initiative with the higher roll, giving the first chance to move a unit.

=== Deployment ===
Once the attacker and defender have been selected, it is now time for the players to deploy their squads to the battlefield. Each side has a dedicated Deployment Area laid out in the mission details. Standard Deployment Areas are the first 3 hexes from the short side table edge on both sides.

Starting with the attacker, they will place one Unit within their Deployment Area on any elevation/terrain they see fit. If their Unit flies/swims, they may start in the air/water but must place a token down notating its elevation. Once the attacker's Unit has been deployed, the defender does the same. In an alternating fashion, both players continue to deploy Units until everyone is on the battlefield. If a player has any Units in reserve [Tentative name change] place them off to the side until given orders to deploy.

After both sides have deployed their Units, the Deployment Phase has ended and the beginning of the Round can begin.

=== Rounds ===

Then the player with initiative activates a Unit which starts the Unit's turn. A turn consists of three phases in order: Movement Phase, Ranged Combat Phase, and then Close Combat Phase. Units can only be activated once per Round. After the unit has completed its turn the next player with initative may activate a unit. This continues until all players have activated a unit then the player who started the round may activate another unit. If a player has no Units left to act with, they skip their turn. Once all players have run out of Units with available turns, that Round is over. When the Round is over, a new Round begins with the same player starting first. This continues until the Mission is completed or a player surrenders.

When a Unit has been activated, place down an Activation token next to the Unit. Once the Unit has finished its turn, flip the token over to Inactive. This indicates that the Unit has already been activated during that round and cannot be activated again. When a new round begins, remove all Inactive tokens from the battlefield.

==== Phases of a Turn ====
[[File:PoC.png | frame |right| Phases of a turn are sequential]]
Each turn is separated into 3 phases; Movement Phase, Ranged Combat Phase, and the Close Combat Phase. When the player activates a Unit, that Unit must act in each phase sequentially. They are allowed to skip over phases but they cannot go back to a prior or skipped phase afterward.

===== Movement Phase =====
Steps:
;1. Choose a Unit to Activate
;2. Roll AP
;3. Move the Unit

[[File:Active.png | frame| right| Active Token]]
Choose a Unit to activate then the Movement Phase begins. First, place down an Active Token next to the Unit The token is to keep track of which Units have already been activated during that turn. Then roll 1D8 to see how many Action Points the Unit can add to its Base AP. Action Points can be used throughout that Unit's turn on Attacking or Command Actions. Any Action Points that do not get used are stored and can be used in future turns. This is capped at 16 AP per Unit. Place a D20 next to the Unit to keep track of its stored AP.

Next, a Unit may take a Move action. There are multiple types of movement based on the capacity of the unit. A unit may move onto one of the three hexes within the Units Field of View (represented by Fig 3). When using a unit that sits on multiple hexes rotate and move from the lead hex of the unit where the Field of Vision (FoV) originates.

'''Standard Movement:''' Moving a Unit normally based on the Standard Movement stat available to its Classification. Units may rotate around on the same hex to change their Field of View at the cost of 1 Standard Movement Point. Once per Movement Phase, a Unit can rotate freely around on the same hex without having to use a Standard Movement Point. Units cannot see beneath their elevation or behind themselves unless otherwise stated. When moving up an elevation the movement costs 2 Standard Movement Points. While moving in water it costs 2 Movement Points to leave the water and 2 Movement Points to move between hexes.

'''Thruster Movement:''' The Thruster Movement stat doubles the Units Standard Movement. The direction of travel is linear and must move the full amount listed. Only available to use when the Unit has any thrusters attached. 
<br />

====== Movement Options ======
When a Unit meets the required amount of thruster durability, they have the option to use the following movement options. Use the chart below to determine which option is available to your Unit.

'''Hover:''' Using this movement may gain or lose 1 elevation per turn with the cost of a Standard Movement Point. This Unit may be in the air without support without falling. However, it must keep its Thruster Durability above the cost labeled below or it will lose the Hover Movement Action. If the Unit loses enough Thruster Durability to have it lose the Hover Move Action then it falls to the ground taking fall damage. When falling move the unit to the ground and take fall damage immediately after the damage was dealt. Otherwise, this is the same as a Standard Move.

'''Flight:''' Using this movement may gain or lose as many elevations per turn as it has Movement Points. Otherwise, this is the same as a Standard Move. This Unit may end its Movement Phase in the air without support and without falling. However, it must keep its Thruster Durability above the cost labeled below or it will lose the Flight Movement Action. If it loses the Flight Move Action but still has the Hover Move Action then it does not fall to the ground and instead is still considered to be in the air. Otherwise, this is the same as a Standard Move.

'''Cruise:''' In Water Tiles, the Cruise Move Action only costs 1 Move Action Point to move from one tile to the other. If a unit moves underwater it costs 2 Move Points, and the unit requires 2 Movement Points to move from one elevation in the Water Tile to the other. Moving out of the water to the land only costs 1 Move Point, however, if the unit does not have the Standard Movement action it costs 3 points to move on non-Water Tiles.

'''Swim:''' In Water Tiles, the Swim Move Action only costs 1 Move Action Point to move from one tile to the other. If a unit moves underwater it costs 1 Move Point, and the unit requires 1 Movement Point to move from one elevation in the Water Tile to the other. Moving out of the water to the land only costs 1 Move Point, however, if the unit does not have the Standard Movement action it costs 3 points to move on non-Water Tiles.

[[File:Movement options.png| frame | center | ]]

<br>

[[File:Rsz fovplus.png| frame |left | Fig 3a on the left shows a Top-Down perspective of a Unit's Field of View while fig 3b on the right shows a Side-View perspective with an elevation higher and lower than the Unit. Arrow indicates directional movement.]]

<br />
'''Movement Within a Hex:''' Depending on the size of each Unit and the terrain it's on, you may find that you have a fair bit of room inside the hex your Unit resides on. Your Unit may move around freely inside the hex as long as 80% of the Unit is inside and is facing the direction it stopped in. You may use this to set up ambushes/ firing positions/ or take better cover.

Two friendly Units may occupy the same hex as long as they do not physically overlap with one another. Two Units on opposing sides cannot occupy the same hex unless stated otherwise or one is on another elevation from the other.

[[File:Movement.png | frame |center| Fig 4a on the left shows allied Units 80% within the hex upon which they are standing and multiple Units on the same hex that are not overlapping. Fig 4b on the right shows opposing Units occupying the same hex, Units that are more than 80% outside their respective hex, and multiple friendly Units overlapping on the same hex.]]

==== Combat ====
Steps:
;1. Determine if Target Unit is in Line of Sight
;2. Select Core Part or Equipment to target
;3. Select a Weapon to attack with and measure Range
;4. Roll Attack
;5. Roll Evasion
;6. Allocate Damage

Choose a target that is within your Unit's Field of View (FoV) and Line of Sight (LoS).

FoV is determined by the first three hexes in front of your Unit in the direction it's facing- a Unit's Field of View includes all unobstructed hexes past those first three hexes. LoS is determined by using a straight line directly from the head of your Unit to the target. The Unit's Weapon must also have a clear LoS. If you can clearly see 80% the part you want to attack you may do so. If a unit takes up multiple hexes use the most lead hex to determine FoV. 

[[File:Core Section Targets smol.png| frame |center | The image depicts which Core Sections of the Alto (in red) are exposed when it's behind various pieces of cover. Left: Head, Torso, Left Arm, and Left Leg. Right: Head, Left and Right Arms, and Torso.]]

After you have determined the Unit is within view check the Range stat of the weapon you wish you use. Measure the range from the first hex in front of the Attacking Unit to the Target Unit. If the Target Unit is a distance under or equal to the Range stat then you may complete the attack. Measuring for this may be done at any time as long as it doesn't slow down gameplay.

[[File:Flow chart new.png |frame |center | Order of operations for Attack Rolls]]

Attacking is resolved with D8 rolls using the three stats: Accuracy, Assault, and Evasion. The player needs to roll '''equal to or higher than''' the Modified value shown on the Unit's Datasheet for every attack being made.
* Accuracy is used in Ranged Combat to determine a Unit's chances of hitting its target with a Ranged Weapon.
* Assault is used in Close Combat and determines a Unit's chances of hitting its target with a Melee Weapon.
* Evasion is used throughout combat and determines the chances a Unit has of dodging incoming attacks.

While making attacks Attacking Units will use their Accuracy or Assault stat. If the Attack is a success then the Defending Units will use their Evasion stat. Rolls can be [[Core_Rules#Modified_Rolls | modified by temporary buffs/debuffs]] during Engagements while [[Core_Rules#Modified_Stats | stats can be modified permanently via SMTs on the Unit's Datasheet]]. For a detailed breakdown of how combat is resolved specifically, see [[Core_Rules#Ranged_Combat_Phase | Combat Phases]].

If the weapon succeeded its Attack Roll and the Evasion Roll of the Defending Unit failed then deduct the Damage of the stat from the Durability of the Core Part or piece of Equipment that was Targeted. If that Part was destroyed then it is considered Inoperable and may no longer be used in the game. Core Parts being destroyed have detrimental effects on the Unit as detailed later.

'''Critical Hits:''' Critical Hits are rolls of 8 when making an Attack Roll. They are always considered hits regardless of other modifiers.

'''Critical Misses:''' Critical Misses are rolls of 1 when making an Attack Roll. They are always considered misses regardless of other modifiers.

===== Ranged Combat Phase =====
If a Unit chooses to take the Ranged Combat Phase then it may use any Ranged Weapon it has to attack with. Follow the steps for Combat as shown above and use the Accuracy stat for the Attack stat. If a unit depletes all of its AP before the Melee Combat Phase, the phase is skipped and the unit is moved to the Inactive state.


===== Close Combat Phase =====
The Close Combat Phase is similar to the Ranged Combat Phase with the major difference being that instead of using Ranged Weapons to attack, the Unit uses Melee Weapons. All melee weapons have a range of 1 unless otherwise stated. Instead of conducting an Accuracy Roll, the player will conduct an Assault Roll. The process listed above otherwise applies to this Phase.

Once all phases have ended, unused AP is stored using the D20, and the Active token is flipped over to the Inactive side. This signifies that the Unit cannot be activated again during that round.

'''Basic Attacks'''
Every Unit can use Basic Attacks, which is the name for any unarmed strike using any limb. These attacks are done during the Close Combat Phase. These attacks are not capable of doing Critical Hits on rolls of 8. All basic attacks have the same stats regardless of classification:

* 1 AP Cost
* 1 Base Damage
* 1 Range

====== Grappling ======
This is when one Unit physically grabs another and innates a fight. Grappling can only be performed during the Close Combat Phase and by Units with Arms.

To initiate a Grapple, the attacking Unit must first be within melee range of the target. Then, at the cost of 2 AP, the Unit makes an Assault Roll.

* If unsuccessful: the Unit can reroll for 2 additional AP, otherwise the Unit ends it turn per normal.
* If successful: the target then makes an Evasion Roll.

If the enemy Evasion Roll;

* Is successful: the grapple is evaded and the attacking Unit can no longer initiate another grapple.
* Is unsuccessful: the Units grapple is successful.

When a Unit successfully Grapples, it occupies the same hex as the enemy and is able to do one of two things: Throw or Hold the enemy.

;'''Hold'''
: Place a Hold token next to the Unit. Both Units cannot move from the hex while the Hold token exists. At the start of the next turn, the Unit Holding can attack with any Mounted Weapon or non-2H Weapon. If the grappling Unit wishes to disengage the Grapple, they may remove the token from play and move to the hex they initially started the grapple from.

: While being held, the enemy gains -5 to Accuracy Rolls, cannot make Assault Rolls, and cannot evade incoming attacks. At the start of its next turn, it can use the Break Grapple Command Action to free itself. When used, it moves to the hex directly behind it and faces the attacker. If that hex is unavailable, it may move to one of the other hexes in its blind spot facing the attacker. If no hexes are available, the Command Action cannot be used. Once a hex has been chosen and the Unit moves, remove the Hold token from the map.

;'''Throw'''
: An enemy can only be Thrown within the FoV of the attacking Unit. Use the ''Throw Distance'' formula to determine the maximum distance the enemy can be thrown. The attacking Unit can throw the enemy Unit anywhere within this maximum distance. Units can only be thrown to the same elevation or lower. Units are unable to throw other Units that have a higher Classification. Units that are Thrown to a lower elevation also take ''Fall Damage''.

: Once the attacker specifies a hex for the defending Unit to land on, they then roll for Assault. This is to check Deviation (link). Pass, the Unit goes where intended. Fail, attacking Unit rolls 1d8 for Deviation and lands there instead.

: After the landing hex is determined, the defending Unit is placed on the specified hex on its back, face up, with its feet pointed at the attacker. The defending Unit receives ''Collision Damage'' to its torso. While on the ground, the defending Unit cannot Evade incoming attacks. If the attacking Unit has no more AP to spend, the turn is over. On the defending Unit's next turn, it must use the GetUp Command Action to get back on its feet. Otherwise, it will remain on the ground.

: Enemy Units can also be thrown into structures as well as other Units.

;'''Thrown into another Unit'''
: If the attacker has specified a hex for the defending Unit to land on and its path is occupied by other Unit(s), the other Unit(s) will conduct an Evasion Roll. If successful, the defending Unit lands on the specified hex same as above and the other Unit(s) are untouched. If the other Unit(s) fails its Evasion roll, they take Collision Damage as well as the defending Unit and are now on the ground. This also includes allied Units.

;'''Thrown into a Structure'''
: If the attacker has specified a hex for the defender to land on and it's occupied by a structure, place the defender on the same hex as the structure but not on the structure itself. Then apply Collision Damage to the defender's torso.

: If the damage is less than the current Defense of the structure, the structure remains and the status effect "Stuck" is given to the Unit.

: If the damage is greater than the current Defense of the structure, the structure falls on top of the Unit and the current Defense is applied as Bonus Damage to the Unit's torso. Remove the structure from the battlefield and replace it with a Black Hex. Then place the defending Unit on its back facing up with its feet facing the attacker. On the defending Unit's next turn, it must use the GetUp Command Action to get back on its feet. Otherwise, it will remain on the ground.

===== End of Round =====
Both players will take turns activating their Units and completing each phase. Once all Units have been activated the Inactive tokens are removed from every Unit and a new round begins. This continues until the Mission is completed or the turn limit has been reached.

=== Destroying Unit Sections ===
When a limb is destroyed, remove the physical section from the model* and then apply the respective status effect accordingly:

{| class="wikitable" style="text-align:center;"
|- style="font-weight:bold;"
! Unit Section
! Description
|-
| All Head Limbs
| style="text-align:left;" | Unit gains -1 to all Accuracy Rolls.
|-
| Arm
| style="text-align:left;" | Unit can no longer pick up objects or attack with Weapons in that hand. Weapons that were held are now on the ground.
|-
| All Arm Limbs
| style="text-align:left;" | Unit can no longer perform grapples. The "Break Grapple" Command Action costs 4 Actions Points.
|-
| Half Leg Limbs
| style="text-align:left;" | Unit gains -1 to Assault rolls and reduce standard movement points by 50% (rounded up). This debuff is applied once a Unit has lost half of its leg limbs (rounded up).
|-
| All Leg Limbs
| style="text-align:left;" | Unit gains -2 to Assault Rolls and standard movement points are reduced to 1. This penalty ''replaces'' the "Half Leg Limbs" penalty.
|}

∗A player can opt out of physically removing the section from the model by placing down the respective Destroyed Limb token. Status effects still apply.

Any and all weapons/abilities are lost when the location they are attached to is destroyed.

==== Destroyed vs Inoperative ====
When the ''' Torso Durability Points''' or '''Cockpit Durability Points''' of a Unit are reduced to 0, the Unit is considered destroyed. If a Mech Unit's Torso Core Part remains intact, but its limbs are all destroyed, it is considered Inoperative. If a Vehicle Unit's Cockpit Core Part remains intact, but it loses its ability to move, it is considered Inoperative. An Inoperative Unit can continue participating in the Engagement if it still has Drones or Mounted Weapons that have not been destroyed.

There are 4 unique areas to a Standard Mech Unit:
* Head, Torso, Arm, and Leg

For Standard Vehicles:
* Cockpit, Body, and (wings/wheels/treads/etc).

Destroying each one results in a different penalty for that Unit.

'''NOTE''': If your Unit does not start with one of these sections, they do not suffer the effects of not having them in the game.

=== Command Actions ===
Actions that can be made during a Units turn but aren’t tied to a specific phase. All Command Actions require 2 Action Points to conduct and can be used multiple times within a single turn. Command Actions (CA’s for short) are divided into 3 categories: State, Stance, & Order.

* States are togglable actions.
* Stances are actions that can be taken out of turn. Activating these immediately ends the Units turn.
* Orders are actions given to drones.

<googlespreadsheet width="800px" height="400" style="width:100%">1_C7NQJUp3Mp4f-um1pdjqg1mSETzNeRW1XDPw9KhFiE</googlespreadsheet>

=== Status Effects ===
{| class="wikitable" style="text-align:center; vertical-align:middle; background-color:rgba(249, 249, 249, 0.67); color:#222;"
|- style="font-weight:bold; background-color:#EEE;"
! Name
! Token
! Description
|-
| Conceal
| <>
| style="text-align:left;" | Unit gains +1 to their Evasion Rolls against ranged attacks.
|-
| Overheat
| <>
| style="text-align:left;" | Unit is immediately put into the kneeling position and ends its turn.
|-
| Freeze
| <>
| style="text-align:left;" | Unit ends its turn immediately. Upon its next activation, its max AP storage capacity is limited to 8.
|-
| Euphotic
| <>
| style="text-align:left;" | Standard Movement is reduced by 2 Movement Points.
|-
| Abyss
| <>
| style="text-align:left;" | Standard Movement is reduced by 2 movement points and the Unit takes 10 damage to the torso per turn.
|-
| Stuck
| <>
| style="text-align:left;" | The Unit is unable to move and is considered '''Inoperable''' until the stuck condition is removed.
|-
| Hold
| <>
| style="text-align:left;" | The Unit is being held by another unit. It may only take the '''Break Hold''' Command Action.
|-
| System Error
| <>
| style="text-align:left;" | Unit ends its turn immediately. Before its next activation, roll 1d8 to reboot. On a 5 or higher, the Unit continues activation per normal. On a 4 or lower, the Unit activation is canceled and its turn ends. Upon subsequent activations, the pass requirement is lowered by 1.
|-
| Airborne
| <>
| style="text-align:left;" | If a Unit has the Hover/Fly System, place a corresponding token (+1/+2/+3) next to them to indicate their elevation. Remove if on ground level.
|-
| Submerged
| <>
| style="text-align:left;" | If a Unit has the Cruise/Swim System, place a corresponding token (-1/-2) next to them to indicate their elevation. Remove if on ground level.
|}

== Terrain ==
Scenery on the battlefield can range from tall buildings to small rocks or trees. Some terrain features are included by individual Missions. Different terrain features are represented by different colored hexes. Each colored hex gives different advantages and/or disadvantages.

When placing terrain colors on the battlefield, different colors need to be placed at least 1 hex apart. If a color description states to place it at a specific elevation, the only elevation that it can be placed is at the Zero Elevation (unless otherwise specified by another rule).

=== Elevations ===
{| class="wikitable" style="float:right; margin-left:10px;"
|- style="font-weight:bold;"
! Elevation
! Description
|-
| style="text-align:center;" | +3
| style="text-align:left;" | Exclusively used by Flight Types.
|-
| style="text-align:center;" | +2
| style="text-align:left;" | The highest elevation which a non-flying Unit can maneuver to.
|-
| style="text-align:center;" | +1
| style="text-align:left;" | The most common elevation for Units that have the ability to Fly/Hover.
|-
| style="text-align:center;" | 0
| style="text-align:left;" | Ground Level. All Units can be used at this elevation.
|-
| style="text-align:center;" | -1
| style="text-align:left;" | The most common elevation for Units that have the ability to Swim/Cruise.
|-
| style="text-align:center;" | -2
| style="text-align:left;" | The lowest point Units can reach.
|}
[[File:elevation.png | frame |Right| ]]
Elevation can be used to give Units a strong advantage in combat. Elevation is a factor when choosing where to move or where to attack from. The game has a total of 5 different elevations. Starting from the lowest to the highest; -2, -1, 0, +1, +2, +3. Ground level is represented by 0. This is were all engagements take place unless otherwise stated by the mission or terrain.

Each level of elevation is 4.5 inches below/above the previous/next level. This can easily be measured by placing an Action Base 4/5 on its corner vertically. Everything below that height is on 0 elevation (Ground Level).

Units traveling to higher elevations use 2 Movement Points to do so while Units traveling to lower elevations only use a single Movement Point. A Unit's elevation is determined by where a Mech Unit's waist [where its legs connect] or a Vehicle Unit's cockpit is. This also applies to structures and natural terrain.
<br clear=all>
==== High Ground Bonus ====
{| class="wikitable" style="float:left; margin-right:10px;"
|- style="font-weight:bold;"
! Elevation Difference
! High Ground Bonus Effect
|-
| style="text-align:center;" | 0
| style="text-align:center;" | No Bonus
|-
| style="text-align:center;" | 1
| style="text-align:center;" | +1 to Assault Rolls
|-
| style="text-align:center;" | 2-3
| style="text-align:center;" | +1 to Accuracy Rolls
|-
| style="text-align:center;" | 4-5
| style="text-align:center;" | +2 to Accuracy Rolls
|}
When an attacking Unit is on a higher elevation than its target, that Unit receives a High Ground Bonus (HGB). This bonus is determined by the difference in elevations between the attacking Unit and its target. Units attacking a target at higher elevations do not gain the HGB.
<br clear=all>

=== Hex Colors and Effects ===
{| class="wikitable" style="text-align:center;"
|-
! Name
! Represents
! Description
! Effect
|-
| Grey
| Road or any generic flat land.
| style="text-align:left;" | The default hex. This hex represents nothing more than a place to stand/move on.
| style="text-align:center;" | -
|-
| Red
| Lava
| style="vertical-align:middle; background-color:rgba(249, 249, 249, 0.67); color:#222; text-align:left;" | An extremely hot tile, either lava or some other superheated material dangerous even to ExMac units and vehicles.
| style="text-align:center;" | Causes the '''Overheat''' status effect when ending your turn on the tile.
|-
| Tan
| Desert Area
| style="text-align:left;" | A barren area/landscape where little to no precipitation occurs.
| style="text-align:left;" | Any '''Move''' action costs +1 Movement point per hex. '''Thruster''' and '''Flight''' moves are not affected .
|-
| White
| Snowy Area
| style="text-align:left;" | A blanket of white covers the area. Cold winds and mechanical problems are plenty.
| style="text-align:left;" | Any '''Move''' action costs +1 Movement point per hex. '''Thruster''' and '''Flight''' moves are not affected .
|-
| Green
| Wooded Area
| style="text-align:left;" | Trees and foliage cover the land.
| style="text-align:left;" | -1 to Accuracy rolls for every green hex within the Unit's Line-of-Sight to its target. This effect stacks on itself. If a Unit is on the hex, they gain the '''Conceal''' status Effect.
|-
| Black
| Ruined Structures
| style="text-align:left;" | Piles of concrete and metal litter the area. What used to be structures that touched the sky now hug the ground. Dense black smoke emanates from the rubble.
| style="text-align:left;" | Movement Point cost required to move through a black hex is doubled. -1 to Accuracy rolls for every black hex within a Unit's Line-of-Sight to its target.
|-
| Light Blue
| Shallow Ocean
| style="text-align:left;" | Body of water. Shallow enough to see the bottom yet deep enough to completely lose a Unit to the seas.
| style="text-align:left;" | As soon as a Unit moves on/over this hex, unless they have the Swim/Cruise System, they gain the '''Euphotic''' status Effect.
|-
| Dark Blue
| Deep Ocean
| style="text-align:left;" | The lowest body of water a Unit can go. There is no light, the pressure is extreme, and the tempatures are near freezing.
| style="text-align:left;" | As soon as a Unit moves on/over this hex, unless they have the Swim/Cruise Sytsem, they gain the '''Abyss''' status Effect.
|}

=== Buildings and Structures ===

[[File:Defense structure chart.png| frame | right ]]

Structures can be destroyed to aid or hinder player tactics. Buildings/structures do not need to be placed on black hexes. However, when they are destroyed the hex/hexes they occupy then become a black hex. The chart on the right shows how building Defense is calculated. Some buildings are tall enough that they reach a higher elevation. You can tell by placing a standard hex on its corner. If it's taller than the hex (4.5"), it's on a higher elevation.

When firing at a structure, you are guaranteed a successful hit and do not need to roll for Accuracy. Base Damage is applied as normal. If an attack is made that doesn't completely destroy the building/structure, that damage is subtracted from the building/structure's total Defense. If you wish to attack a Unit through a structure, you will first need to destroy it and then make a separate attack targeting the intended Unit.

<blockquote style="background-color: lightgrey; border: solid thin grey;">
*The building you want to attack through is occupying 1 hex and is in +1 elevation. This means it has a total Defense of 20.
:: If your total damage is less than 20, the building still stands with its remaining Defense left over. If your total damage is more than 20, the building falls and you may then target the enemy Unit on the other side with a new attack.
* NOTE: Since excess damage doesn't pass through the structure, it is advised that you make only the necessary amount of shots needed to bring it down so you still have some attacks for the enemy.
</blockquote>

=== Non-Hex Terrain ===
This terrain is also known as Scatter Terrain. Pieces of Terrain that aren't connected to a hex or hex effect. They may be for decoration or may be used for cover. When building the map come to an agreement with your opponent on which will grant cover and which is purely decorative.

== Battles ==
Battles are waged by following the sequence below:
{| class="wikitable" style="float:right; margin-left:10px;"
|- style="font-weight:bold;"
! Engagement Size
! Deployment Cost Limit
|-
| Scouting
| 600
|-
| Skirmish
| 1200
|-
| Operation
| 1800
|-
| Battle
| 2500
|}
;1. '''Selecting a Engagement Size'''
: Players must first choose an engagement size they wish to play: Scouting, Skirmish, Operation, or Conflagration. This determines the Deployment Cost available for each team.

;2. '''Choosing a Mission'''
: Players determine which Mission will be carried out during the battle; they can only choose from the available Missions in their engagement size. This will determine the Deployment Area the players use as well as specific Mission objectives and certain terrain features. You can either simply agree with your opponent on which Mission to play, or you can roll to randomly select a Mission using one of the following tables:
<center>
{| class="wikitable" style="font-weight:bold; text-align:center; display: inline-table;"
|-
! colspan="2" style="background-color:#9b9b9b;" | Scouting
|- style="background-color:#efefef;"
| D8
| Mission
|- style="font-weight:normal;"
| 1-4
| [[Reconnaissance]]
|- style="font-weight:normal;"
| 5-8
| [[Show of Force]]
|}
{| class="wikitable" style="text-align:center; display: inline-table;"
|- style="font-weight:bold;"
! colspan="2" style="background-color:#9b9b9b;" | Skirmish
|- style="font-weight:bold; background-color:#efefef;"
| D8
| Mission
|-
| 1-2
| [[Winds of War]]
|-
| 3-4
| [[Endless Pursuit]]
|-
| 5-6
| [[Counterattack!]]
|-
| 7-8
| [[The Call of Darkness]]
|}
{| class="wikitable" style="text-align:center; display: inline-table;"
|- style="font-weight:bold;"
! colspan="2" style="background-color:#9b9b9b;" | Operation
|- style="font-weight:bold; background-color:#efefef;"
| D8
| Mission
|-
| 1-2
| [[The Order to Destroy]]
|-
| 3-4
| [[Emissary of Darkness!]]
|-
| 5-6
| [[Burning Sandstorm]]
|-
| 7-8
| [[Protect the Relic]]
|}
{| class="wikitable" style="font-weight:bold; text-align:center; display: inline-table;"
|-
! colspan="2" style="background-color:#9b9b9b;" | Battle
|- style="background-color:#efefef;"
| D8
| Mission
|- style="font-weight:normal;"
| 1-4
| [[Protect the Base]]
|- style="font-weight:normal;"
| 5-8
| [[Marshall Law]]
|}
</center>
;3. '''Assembling a Squad'''
: Players must then assemble a Squad with a sum total Deployment Cost less than the listed Deployment Cost Limit for the engagement size.

;4. '''Reading Mission Briefing'''
: Each Mission has a Mission briefing that will detail the primary objectives that award points to the players. Some Mission briefings also list one or more Mission rules that will apply for the duration of the battle. The players should read and familiarize themselves with these before proceeding.

;5. '''Creating the Battlefield'''
: The players now create the battlefield and set up terrain features. Missions are played on rectangular hex-grid battlefields which measure 16x13 hexagonal tiles, or 202 total hexes, with the flat side facing each player.

;6. '''Placing Objective Markers'''
: The players now set objective markers up on the battlefield. Each Mission’s deployment map will show the players how many to set up and where each should be placed.

;7. '''Determine who is Attacker and Defender'''
: Players roll 1D8 to determine this. The highest value chooses who will be Attacker and Defender. The Attacker goes first in the engagement but the Defender chooses their Deployment Area.

;8. '''Choose a Deployment Area'''
: The Defender chooses their deployment area first followed by the Attacker.

;9. '''Deploy Squads'''
: Squad deployment is done in alternating order. Check [[Core_Rules#Deployment]] for more information. There may be more specific rules in the mission briefing.

;10.'''Begin the Battle'''
: Resolve any pre-battle rules then begin activation with the Attacker's first unit.

;11.'''End the Battle'''
: The battle ends when the number of turns pass in the mission briefing or all of one side's units have become destroyed or inoperable.

;12.'''Determine the Victor'''
: Each player can score a maximum of 7 points from primary objectives and a maximum of 7 points from secondary objectives for a total of 14 possible points (any excess victory points awarded are discounted).

== Terminology ==
{| class="wikitable" style="text-align:center; vertical-align:middle; background-color:#F8F9FA; color:#202122;"
|- style="font-weight:bold; background-color:#EAECF0;"
! Term !! Definition
|-
| Accuracy Roll
| style="text-align:left;" | 1d8 that determines the outcome of a Ranged Attack.
|-
| Assault Roll
| style="text-align:left;" | 1d8 that determines the outcome of a Melee Attack.
|-
| Evasion Roll
| style="text-align:left;" | 1d8 that determines the outcome of an attempted Evasion.
|-
| Critical Hit
| style="text-align:left;" | An attack that cannot be Evaded. Adds .5 of the Weapon's Base Damage as bonus damage (round up).
|-
| On-Target
| style="text-align:left;" | After an Accuracy/Assault Roll is successful but an Evasion Roll has yet to be conducted.
|-
| Classification
| style="text-align:left;" | Determined by the Total Defense Points of a Unit.
|-
| Line of Sight
| style="text-align:left;" | A straight, unobstructed line from an attacking Unit to its target.
|-
| Field of View
| style="text-align:left;" | The hexes in the front-left, front-right, and front-center in the direction a Unit is facing as well as every hex behind those hexes.
|-
| Blind Spot
| style="text-align:left;" | The hexes in the rear-left, rear-right, and rear-center in the direction a Unit is facing.
|-
| Standard Movement
| style="text-align:left;" | Also referred to as Standard Movement Points. The number of hexes a Unit can move in a single turn
|-
| Thruster Movement
| style="text-align:left;" | Only available if thrusters are on a Unit's model. Forfeit Ranged and Close Combat phases if used. The path a Unit takes is linear in the direction the player chooses. If an obstacle blocks the full travel length, the Unit stops one hex prior to that obstacle.
|-
| Action Points
| style="text-align:left;" | Also referred to as AP. Points used to determine how many actions can be performed in a single turn.
|-
| Command Actions
| style="text-align:left;" | Also referred to as CA. Any action NOT dealing with the Movement Phase or either of the two Combat Phases. Requires 2 AP to perform any CA.
|-
| Equipped Weapons
| style="text-align:left;" | Weapons that are being held in the hands of a Unit.
|-
| Mounted Weapons
| style="text-align:left;" | Weapons that are mounted directly to a Units Section. Cannot be swapped. Roll 1d8. If 6+, will explode when destroyed, dealing 100% weapon damage to the section it was attached to.
|-
| Carried Weapons
| style="text-align:left;" | Weapons that are being stored on the Unit but not Equipped. Can be Equipped or Retrieved if space is available in the Unit's hand(s). These Weapons must be Equipped before using.
|-
| Base Damage
| style="text-align:left;" | How much damage a weapon deals before modifications.
|-
| Fall Damage
| style="text-align:left;" | 2 ( Unit Classification * Elevation Height) to the Units Leg Sections (or Torso if no legs).
|-
| Collision Damage
| style="text-align:left;" | 2 ( Moving Unit Classification * Thrown Distance)
|-
| Throw Distance
| style="text-align:left;" | 8 - (Attacker Modified Assault Stat)
|-
| Systems
| style="text-align:left;" | Abilities that directly come from parts on the physical Unit model. Having these parts on the model does not automatically give the Unit the ability.
|-
| Mods
| style="text-align:left;" | Abilities that come from upgrades and tuning of the Unit's internal components which are not immediately visible on the model.
|-
| Traits
| style="text-align:left;" | Abilities granted to the Unit from the pilot.
|-
| Artificial Intelligence
| style="text-align:left;" | RoyRoy heads have their own sentience used for giving Drones autonomy.
|-
| Core Parts
| style="text-align:left;" | Any and all parts that make up the CORE of the unit- limbs and the armor attached to those limbs. e.g. head, head armor, chest, knee armor, etc.
|-
| Unit Sections
| style="text-align:left;" | Core parts that are grouped into individual sections. EG; Head, Arms, Legs, Torso, etc.
|-
| Core Type
| style="text-align:left;" | Determines your Unit's base Stats. Each Core Type provides different Stats.
|-
| Deployment Cost
| style="text-align:left;" | The overall Cost of a Unit toward the Deployment Cost Limit of any Engagement. This includes Weapons, Equipment, Defense, Systems, Mods, etc.
|-
| S.R.M.
| style="text-align:left;" | Stat Reduction Modifiers. This number reperesents how many times a Unit's base stats can be lowered to a minimum of 2 Accuracy, 2 Assault, and 2 Evasion.
|-
| Main Unit
| style="text-align:left;" | Refers to a single Unit that controls drones.
|}

{{CoreNavigation}}
[[Category:Rules]]

Core Rules

2026-03-15T21:14:36Z

Lavtiz29: /* Introduction */ Large Edit Time.

== Introduction ==
The 30 Minute Missions: Wargame (30MM:W for short) is a mech-based tabletop miniatures game using Bandai Spirit's 30 Minutes Missions line of 1/144 scale mecha model kits. The focus of this game is on:
• The ability to play missions in, roughly, 30 minutes (excluding setup); and
• The customizability and modular designs for model kits.
The game is played over a series of rounds. Each round consists of alternating turns between each player choosing one of their Units, moving to the best position, attacking the enemy, or holding an objective. The battlefield is played with varying terrain, elevations, and structures. Missions can vary from eliminating the enemies to securing intel.

== Combat Objective ==

The game is won after the primary objective of the mission you are playing has been completed. These range from holding an objective for multiple turns, getting an object and moving to your side of the board, or simply destroying the enemy forces.

== Required Components ==

=== Dice ===
It is recommended that you have at least 1 eight-sided dice (D8), but having multiple will make it so you can roll all of your attacks at once instead of one at a time. It is also advised that you have a twenty-sided dice (D20) on hand for each unit to use to keep track of how many Action Points a Unit has, however a piece of paper will do as well.

If a rule requires a D8 roll 3 or higher, this is often abbreviated as 3+.

=== Objective Markers ===

Objective Markers can be anything as long as they fit on a hex and do not interfere with the movement of most units. There will be cases where a unit takes up a whole hex or will otherwise cause an issue with the token. In those cases make a mark of where the token was on a piece of paper or other notation.

=== Tokens ===
While playing the game, you may need various tokens to identify a status effect or elevation.

=== Units ===
Described in greater detail later. Units mean the 1/144 scale models built using 30mm Parts. Other models in the same scale may be used as well. We suggest a minimum of 1 unit per person playing. However without a points balance this may skew combat in favor of one player over the other.

=== Datasheet ===
The Datasheet contains your unit's information. Defense, Weapons, and other special abilities will all be listed here. More information is found on the [[Unit Datasheet Creation]] page.

== Unit Information ==

Units are the giant robots (mechs) and vehicles used and while any thing can be used the game is designed with primarily with 30 Minute Mission parts in mind
.
=== Unit Sections ===

When a player is creating their Unit, they need to determine its Unit Sections. Unit Sections (US) are groups of individual parts combined to form specific areas that perform a certain function. First, a player needs to determine what type of Unit they created. Whether it be a Mech or a Vehicle each type has different Unit Sections available to it with many being used by the other types. Drones, which may be a Mech Unit, Vehicle Unit, or Equipment, may also require some of these Sections depending on build. Determine what Sections are needed for your Unit type by their movement requirements.
[[File:CS-Units.png| frameless | right| 500px | Battlefield Layout]]
'''Unit Sections:'''
* Head - The upper part of a Mech Units body. Contains complex camera systems to provide visuals to the pilot in real-time.
* AI Cockpit - Main Section of a Drone/Mech/Vehicle. Contains the A.I. pilot.
* Torso - Main Section of a Mech Unit. Holds the pilot.
* Cockpit - Main Section of a Vehicle. Holds the pilot.
* Arm - The upper limb of a Mech Unit. Has the ability to pick up/hold/carry various things.
* Tail - A modified arm, usually used for stability and aesthetics. May have weapons or thrusters attached to it.
* Leg - Each of the limbs on a Unit that provides movement.
* Aquatic Drive - A section that provides movement in Water and Deep Water Tiles. Requires for Aquatic vehicles.
* Aerial Drive - A Section that provides flight in some form either for hovering or actual flight. It is a requirement for Aerial Vehicles.
* Terra Drive - A Section that provides movement across the ground. It grants standard movement and is a requirement for Terrestrial Vehicles.

Next, Identify how many Sections your Unit has and what each one is. Mech Units normally have a head, two arms, two legs, as well as a Torso. Vehicle Units normally have at least one Drive Section and a Cockpit. Drones normally have a single AI Cockpit Section. All of these may vary depending on how you build your Units.

=== Unit Types ===
Units are divided into the following Types:

==== Mech ====
A unit that meets any of the following guidelines:

* Uses legs as its main form of transportation
* Has or relies on arms to perform its primary functions
* Has a clear and obvious torso

This is the standard Engagement Unit.

==== Vehicle ====
Any Unit that relies on jet propulsion, wheels, tracks/treads, or rotors as its primary source of movement and doesn't have any form of arms. Any part that isn't part of a Drive Core Section, weapon, or equipment is considered part of the Cockpit Core Section.

All Vehicle types gain the following changes to their gameplay:
* Must have a Cockpit Unit Section in place of a Torso Unit Section.
* When checking line of sight (LoS), the reference point starts at the Units cockpit.
* Cannot physically pick up or interact with any objects.
* Cannot change elevation [+/-] without appropriate Abilities.
* Cannot obtain the Jump Ability.

Vehicles are broken down into 3 categories: Terrestrial, Aerial, and Aquatic. Each one has specific requirements that must be met in order for a vehicle to be considered one or the other. Below is each category along with its Requirements, Restrictions, and Bonuses.

<div class="toccolours mw-collapsible mw-collapsed" style="width:97%; padding:0.5em">
<div style="font-weight:bold;line-height:1.6;">Terrestrial</div>
<div class="mw-collapsible-content">
Land-based vehicles.

Any Unit that meets the following requirements are to be regarded as a Terrestrial Vehicle Unit:
* Must contain at least two Terra Drive Unit Sections.
* Does not contain Flight Drive Unit Sections.
* Does not contain Aquatic Drive Unit Sections.

The following are restrictions that a Terrestrial Unit must follow:
* Weapon range is halved when firing through green hexes.
* Movement costs 2x when traveling over green hexes.

The following bonuses are given to Terrestrial Vehicles:
* FoV is all 6 hexes around the Unit (360 degrees).
* Main Cannon has an AP reduction of 3 (to a minimum of 4).

</div></div>

<div class="toccolours mw-collapsible mw-collapsed" style="width:97%; padding:0.5em">
<div style="font-weight:bold;line-height:1.6;">Aerial</div>
<div class="mw-collapsible-content">
Usually a plane, helicopter, or other vehicle for flying in appearance.

Any Unit that meets the following requirements are to be regarded as an Aerial Vehicle Unit:
* Must contain at least one Flight Core Part
* Does not contain Aquatic Drive Unit Sections.
* Does not contain Terra Drive Unit Sections.

The following are restrictions that an Aerial Unit must follow:
* Cannot move on 0 Elevation (Ground Level).
* Can only use thruster movement.
* All movement points must be used during activation. Failure to do so will result in Unit taking fall damage to Cockpit Unit Section.
* Standard movement is an exclusive Command Action that can only be gained with the use of rotor parts.

The following bonuses are given to Aerial Vehicles:
Strafing runs: When the unit passes directly over enemy units (a single elevation directly above) during the movement phase, it may pause its movement and conduct a single ranged combat or close combat attack. After the attack has been resolved, the unit can continue with its movement phase. This can be repeated.

</div></div>

<div class="toccolours mw-collapsible mw-collapsed" style="width:97%; padding:0.5em">
<div style="font-weight:bold;line-height:1.6;">Aquatic</div>
<div class="mw-collapsible-content">
Usually a boat, submarine, or other vehicle for navigating the water.

Any Unit that meets the following requirements are to be regarded as an Aquatic Vehicle Unit:
* Must contain at least one Aquatic Drive Unit Section.
* Must not contain Terra Drive Unit Sections.
* Must not contain Aerial Drive Unit Sections.

The following are restrictions that an Aquatic Unit must follow:
* Can only move over light/dark blue hexes.

The following bonuses are given to Aquatic Vehicles:
* Attacks made with missile pods don't need LoS.

</div></div>

==== Drone ====
Drones are typically smaller units or equipment controlled by a larger or more networked unit. Drones can be either mechs OR vehicles.

There are two categories of Drones:

* A.I. Drones
* Non-AI Drones

'''A.I. Drones:'''

AI Drones are drones that are controlled by artificial intelligence. These are considered their own Units and as such, get their own Datasheet. The pilot for this Unit must be an AI and can be selected when choosing the rank/AI.

'''Non-A.I. Drones:'''

Non-AI Drones are drones that need to be controlled by a Main Unit with the Control Management Mod.

</div></div>

=== Classification ===
{| class="wikitable" style="text-align:center; vertical-align:middle; background-color:#F8F9FA; color:#202122; float:right; margin-left:10px; "
|- style="font-weight:bold; background-color:#EAECF0;"
! Total Defense
! Classification
! Base Movement
! Base Action Points
|-
| 0 - 75
| Class 1
| 5
| 1d8 + 2
|-
| 76 - 150
| Class 2
| 4
| 1d8 + 2
|-
| 151 - 225
| Class 3
| 3
| 1d8 + 3
|-
| 226 - 300
| Class 4
| 2
| 1d8 + 4
|-
| 301+
| Class 5
| 1
| 1d8 + 4
|}
There are 5 different classifications that provide different starting bonuses and limitations based on the size of your Unit. This is determined by the Total Defense value of all of Core Parts combined.
<br clear=all>
=== Squads ===
Are groups of units usually no more than 5 as a game of 6 or more can become longer and slow down the game. These are generally called Lances or Fire Teams depending on size and your own preferences.

== Datasheets ==
Datasheets show detailed stats and abilities for each Unit. You will need to create a Datasheet for every Unit in your Squad. Which instructions for can be found [[Unit Datasheet Creation]].

== Gameplay ==
[[File:New Board 1.png| frameless | right| 500px | Battlefield Layout]]
=== Board Setup ===
All Missions take place on a battlefield overlayed by a hexagonal grid. [https://www.usagundamstore.com/products/pre-order-black-action-base-5?variant=49149953167&currency=USD&utm_medium=product_sync&utm_source=google&utm_content=sag_organic&utm_campaign=sag_organic&gclid=Cj0KCQjwjvaYBhDlARIsAO8PkE1rZ7dQrKWyU-YJ7NkAEjGGZ3eeKfcuHnwC42hsgGj3E1ObWF9jf2EaAl8UEALw_wcB Each hex space is the same size as an action base 4/5 - 4.5 inches]. This eliminates the need for measuring tools and makes movement/weapon ranges easier to calculate.

However, if a person wishes to play without hexes all movement can be done with action bases and movement being 4.5 inches per movement point.

A full-sized battlefield measures 14 hexes (58.5 in) on the long side by 11 hexes (38.3 in) on the short side, with the flat sides facing each player.

Missions will give suggestions on more specific terrain setups. It is suggested a matching terrain setup for each side when playing a destroy all targets type mission.

<br/>

=== Pre-Deployment ===

Players roll 1D8 to determine who goes first. The higher roll chooses who gets to be Attacker and who gets to be Defender. The Attacker goes first and has starting initiative, but the Defender chooses their Deployment Area.

In 3+ player games, players choose which team to participate on and share Units and turns with their teammates.
At the start of the round players roll for initiative with the higher roll, giving the first chance to move a unit.

=== Deployment ===
Once the attacker and defender have been selected, it is now time for the players to deploy their squads to the battlefield. Each side has a dedicated Deployment Area laid out in the mission details. Standard Deployment Areas are the first 3 hexes from the short side table edge on both sides.

Starting with the attacker, they will place one Unit within their Deployment Area on any elevation/terrain they see fit. If their Unit flies/swims, they may start in the air/water but must place a token down notating its elevation. Once the attacker's Unit has been deployed, the defender does the same. In an alternating fashion, both players continue to deploy Units until everyone is on the battlefield. If a player has any Units in reserve [Tentative name change] place them off to the side until given orders to deploy.

After both sides have deployed their Units, the Deployment Phase has ended and the beginning of the Round can begin.

=== Rounds ===

Then the player with initiative activates a Unit which starts the Unit's turn. A turn consists of three phases in order: Movement Phase, Ranged Combat Phase, and then Close Combat Phase. Units can only be activated once per Round. After the unit has completed its turn the next player with initative may activate a unit. This continues until all players have activated a unit then the player who started the round may activate another unit. If a player has no Units left to act with, they skip their turn. Once all players have run out of Units with available turns, that Round is over. When the Round is over, a new Round begins with the same player starting first. This continues until the Mission is completed or a player surrenders.

When a Unit has been activated, place down an Activation token next to the Unit. Once the Unit has finished its turn, flip the token over to Inactive. This indicates that the Unit has already been activated during that round and cannot be activated again. When a new round begins, remove all Inactive tokens from the battlefield.

==== Phases of a Turn ====
[[File:PoC.png | frame |right| Phases of a turn are sequential]]
Each turn is separated into 3 phases; Movement Phase, Ranged Combat Phase, and the Close Combat Phase. When the player activates a Unit, that Unit must act in each phase sequentially. They are allowed to skip over phases but they cannot go back to a prior or skipped phase afterward.

===== Movement Phase =====
Steps:
;1. Choose a Unit to Activate
;2. Roll AP
;3. Move the Unit

[[File:Active.png | frame| right| Active Token]]
Choose a Unit to activate then the Movement Phase begins. First, place down an Active Token next to the Unit The token is to keep track of which Units have already been activated during that turn. Then roll 1D8 to see how many Action Points the Unit can add to its Base AP. Action Points can be used throughout that Unit's turn on Attacking or Command Actions. Any Action Points that do not get used are stored and can be used in future turns. This is capped at 16 AP per Unit. Place a D20 next to the Unit to keep track of its stored AP.

Next, a Unit may take a Move action. There are multiple types of movement based on the capacity of the unit. A unit may move onto one of the three hexes within the Units Field of View (represented by Fig 3). When using a unit that sits on multiple hexes rotate and move from the lead hex of the unit where the Field of Vision (FoV) originates.

'''Standard Movement:''' Moving a Unit normally based on the Standard Movement stat available to its Classification. Units may rotate around on the same hex to change their Field of View at the cost of 1 Standard Movement Point. Once per Movement Phase, a Unit can rotate freely around on the same hex without having to use a Standard Movement Point. Units cannot see beneath their elevation or behind themselves unless otherwise stated. When moving up an elevation the movement costs 2 Standard Movement Points. While moving in water it costs 2 Movement Points to leave the water and 2 Movement Points to move between hexes.

'''Thruster Movement:''' The Thruster Movement stat doubles the Units Standard Movement. The direction of travel is linear and must move the full amount listed. Only available to use when the Unit has any thrusters attached. 
<br />

====== Movement Options ======
When a Unit meets the required amount of thruster durability, they have the option to use the following movement options. Use the chart below to determine which option is available to your Unit.

'''Hover:''' Using this movement may gain or lose 1 elevation per turn with the cost of a Standard Movement Point. This Unit may be in the air without support without falling. However, it must keep its Thruster Durability above the cost labeled below or it will lose the Hover Movement Action. If the Unit loses enough Thruster Durability to have it lose the Hover Move Action then it falls to the ground taking fall damage. When falling move the unit to the ground and take fall damage immediately after the damage was dealt. Otherwise, this is the same as a Standard Move.

'''Flight:''' Using this movement may gain or lose as many elevations per turn as it has Movement Points. Otherwise, this is the same as a Standard Move. This Unit may end its Movement Phase in the air without support and without falling. However, it must keep its Thruster Durability above the cost labeled below or it will lose the Flight Movement Action. If it loses the Flight Move Action but still has the Hover Move Action then it does not fall to the ground and instead is still considered to be in the air. Otherwise, this is the same as a Standard Move.

'''Cruise:''' In Water Tiles, the Cruise Move Action only costs 1 Move Action Point to move from one tile to the other. If a unit moves underwater it costs 2 Move Points, and the unit requires 2 Movement Points to move from one elevation in the Water Tile to the other. Moving out of the water to the land only costs 1 Move Point, however, if the unit does not have the Standard Movement action it costs 3 points to move on non-Water Tiles.

'''Swim:''' In Water Tiles, the Swim Move Action only costs 1 Move Action Point to move from one tile to the other. If a unit moves underwater it costs 1 Move Point, and the unit requires 1 Movement Point to move from one elevation in the Water Tile to the other. Moving out of the water to the land only costs 1 Move Point, however, if the unit does not have the Standard Movement action it costs 3 points to move on non-Water Tiles.

[[File:Movement options.png| frame | center | ]]

<br>

[[File:Rsz fovplus.png| frame |left | Fig 3a on the left shows a Top-Down perspective of a Unit's Field of View while fig 3b on the right shows a Side-View perspective with an elevation higher and lower than the Unit. Arrow indicates directional movement.]]

<br />
'''Movement Within a Hex:''' Depending on the size of each Unit and the terrain it's on, you may find that you have a fair bit of room inside the hex your Unit resides on. Your Unit may move around freely inside the hex as long as 80% of the Unit is inside and is facing the direction it stopped in. You may use this to set up ambushes/ firing positions/ or take better cover.

Two friendly Units may occupy the same hex as long as they do not physically overlap with one another. Two Units on opposing sides cannot occupy the same hex unless stated otherwise or one is on another elevation from the other.

[[File:Movement.png | frame |center| Fig 4a on the left shows allied Units 80% within the hex upon which they are standing and multiple Units on the same hex that are not overlapping. Fig 4b on the right shows opposing Units occupying the same hex, Units that are more than 80% outside their respective hex, and multiple friendly Units overlapping on the same hex.]]

==== Combat ====
Steps:
;1. Determine if Target Unit is in Line of Sight
;2. Select Core Part or Equipment to target
;3. Select a Weapon to attack with and measure Range
;4. Roll Attack
;5. Roll Evasion
;6. Allocate Damage

Choose a target that is within your Unit's Field of View (FoV) and Line of Sight (LoS).

FoV is determined by the first three hexes in front of your Unit in the direction it's facing- a Unit's Field of View includes all unobstructed hexes past those first three hexes. LoS is determined by using a straight line directly from the head of your Unit to the target. The Unit's Weapon must also have a clear LoS. If you can clearly see 80% the part you want to attack you may do so. If a unit takes up multiple hexes use the most lead hex to determine FoV. 

[[File:Core Section Targets smol.png| frame |center | The image depicts which Core Sections of the Alto (in red) are exposed when it's behind various pieces of cover. Left: Head, Torso, Left Arm, and Left Leg. Right: Head, Left and Right Arms, and Torso.]]

After you have determined the Unit is within view check the Range stat of the weapon you wish you use. Measure the range from the first hex in front of the Attacking Unit to the Target Unit. If the Target Unit is a distance under or equal to the Range stat then you may complete the attack. Measuring for this may be done at any time as long as it doesn't slow down gameplay.

[[File:Flow chart new.png |frame |center | Order of operations for Attack Rolls]]

Attacking is resolved with D8 rolls using the three stats: Accuracy, Assault, and Evasion. The player needs to roll '''equal to or higher than''' the Modified value shown on the Unit's Datasheet for every attack being made.
* Accuracy is used in Ranged Combat to determine a Unit's chances of hitting its target with a Ranged Weapon.
* Assault is used in Close Combat and determines a Unit's chances of hitting its target with a Melee Weapon.
* Evasion is used throughout combat and determines the chances a Unit has of dodging incoming attacks.

While making attacks Attacking Units will use their Accuracy or Assault stat. If the Attack is a success then the Defending Units will use their Evasion stat. Rolls can be [[Core_Rules#Modified_Rolls | modified by temporary buffs/debuffs]] during Engagements while [[Core_Rules#Modified_Stats | stats can be modified permanently via SMTs on the Unit's Datasheet]]. For a detailed breakdown of how combat is resolved specifically, see [[Core_Rules#Ranged_Combat_Phase | Combat Phases]].

If the weapon succeeded its Attack Roll and the Evasion Roll of the Defending Unit failed then deduct the Damage of the stat from the Durability of the Core Part or piece of Equipment that was Targeted. If that Part was destroyed then it is considered Inoperable and may no longer be used in the game. Core Parts being destroyed have detrimental effects on the Unit as detailed later.

'''Critical Hits:''' Critical Hits are rolls of 8 when making an Attack Roll. They are always considered hits regardless of other modifiers.

'''Critical Misses:''' Critical Misses are rolls of 1 when making an Attack Roll. They are always considered misses regardless of other modifiers.

===== Ranged Combat Phase =====
If a Unit chooses to take the Ranged Combat Phase then it may use any Ranged Weapon it has to attack with. Follow the steps for Combat as shown above and use the Accuracy stat for the Attack stat. If a unit depletes all of its AP before the Melee Combat Phase, the phase is skipped and the unit is moved to the Inactive state.


===== Close Combat Phase =====
The Close Combat Phase is similar to the Ranged Combat Phase with the major difference being that instead of using Ranged Weapons to attack, the Unit uses Melee Weapons. All melee weapons have a range of 1 unless otherwise stated. Instead of conducting an Accuracy Roll, the player will conduct an Assault Roll. The process listed above otherwise applies to this Phase.

Once all phases have ended, unused AP is stored using the D20, and the Active token is flipped over to the Inactive side. This signifies that the Unit cannot be activated again during that round.

'''Basic Attacks'''
Every Unit can use Basic Attacks, which is the name for any unarmed strike using any limb. These attacks are done during the Close Combat Phase. These attacks are not capable of doing Critical Hits on rolls of 8. All basic attacks have the same stats regardless of classification:

* 1 AP Cost
* 1 Base Damage
* 1 Range

====== Grappling ======
This is when one Unit physically grabs another and innates a fight. Grappling can only be performed during the Close Combat Phase and by Units with Arms.

To initiate a Grapple, the attacking Unit must first be within melee range of the target. Then, at the cost of 2 AP, the Unit makes an Assault Roll.

* If unsuccessful: the Unit can reroll for 2 additional AP, otherwise the Unit ends it turn per normal.
* If successful: the target then makes an Evasion Roll.

If the enemy Evasion Roll;

* Is successful: the grapple is evaded and the attacking Unit can no longer initiate another grapple.
* Is unsuccessful: the Units grapple is successful.

When a Unit successfully Grapples, it occupies the same hex as the enemy and is able to do one of two things: Throw or Hold the enemy.

;'''Hold'''
: Place a Hold token next to the Unit. Both Units cannot move from the hex while the Hold token exists. At the start of the next turn, the Unit Holding can attack with any Mounted Weapon or non-2H Weapon. If the grappling Unit wishes to disengage the Grapple, they may remove the token from play and move to the hex they initially started the grapple from.

: While being held, the enemy gains -5 to Accuracy Rolls, cannot make Assault Rolls, and cannot evade incoming attacks. At the start of its next turn, it can use the Break Grapple Command Action to free itself. When used, it moves to the hex directly behind it and faces the attacker. If that hex is unavailable, it may move to one of the other hexes in its blind spot facing the attacker. If no hexes are available, the Command Action cannot be used. Once a hex has been chosen and the Unit moves, remove the Hold token from the map.

;'''Throw'''
: An enemy can only be Thrown within the FoV of the attacking Unit. Use the ''Throw Distance'' formula to determine the maximum distance the enemy can be thrown. The attacking Unit can throw the enemy Unit anywhere within this maximum distance. Units can only be thrown to the same elevation or lower. Units are unable to throw other Units that have a higher Classification. Units that are Thrown to a lower elevation also take ''Fall Damage''.

: Once the attacker specifies a hex for the defending Unit to land on, they then roll for Assault. This is to check Deviation (link). Pass, the Unit goes where intended. Fail, attacking Unit rolls 1d8 for Deviation and lands there instead.

: After the landing hex is determined, the defending Unit is placed on the specified hex on its back, face up, with its feet pointed at the attacker. The defending Unit receives ''Collision Damage'' to its torso. While on the ground, the defending Unit cannot Evade incoming attacks. If the attacking Unit has no more AP to spend, the turn is over. On the defending Unit's next turn, it must use the GetUp Command Action to get back on its feet. Otherwise, it will remain on the ground.

: Enemy Units can also be thrown into structures as well as other Units.

;'''Thrown into another Unit'''
: If the attacker has specified a hex for the defending Unit to land on and its path is occupied by other Unit(s), the other Unit(s) will conduct an Evasion Roll. If successful, the defending Unit lands on the specified hex same as above and the other Unit(s) are untouched. If the other Unit(s) fails its Evasion roll, they take Collision Damage as well as the defending Unit and are now on the ground. This also includes allied Units.

;'''Thrown into a Structure'''
: If the attacker has specified a hex for the defender to land on and it's occupied by a structure, place the defender on the same hex as the structure but not on the structure itself. Then apply Collision Damage to the defender's torso.

: If the damage is less than the current Defense of the structure, the structure remains and the status effect "Stuck" is given to the Unit.

: If the damage is greater than the current Defense of the structure, the structure falls on top of the Unit and the current Defense is applied as Bonus Damage to the Unit's torso. Remove the structure from the battlefield and replace it with a Black Hex. Then place the defending Unit on its back facing up with its feet facing the attacker. On the defending Unit's next turn, it must use the GetUp Command Action to get back on its feet. Otherwise, it will remain on the ground.

===== End of Round =====
Both players will take turns activating their Units and completing each phase. Once all Units have been activated the Inactive tokens are removed from every Unit and a new round begins. This continues until the Mission is completed or the turn limit has been reached.

=== Destroying Unit Sections ===
When a limb is destroyed, remove the physical section from the model* and then apply the respective status effect accordingly:

{| class="wikitable" style="text-align:center;"
|- style="font-weight:bold;"
! Unit Section
! Description
|-
| All Head Limbs
| style="text-align:left;" | Unit gains -1 to all Accuracy Rolls.
|-
| Arm
| style="text-align:left;" | Unit can no longer pick up objects or attack with Weapons in that hand. Weapons that were held are now on the ground.
|-
| All Arm Limbs
| style="text-align:left;" | Unit can no longer perform grapples. The "Break Grapple" Command Action costs 4 Actions Points.
|-
| Half Leg Limbs
| style="text-align:left;" | Unit gains -1 to Assault rolls and reduce standard movement points by 50% (rounded up). This debuff is applied once a Unit has lost half of its leg limbs (rounded up).
|-
| All Leg Limbs
| style="text-align:left;" | Unit gains -2 to Assault Rolls and standard movement points are reduced to 1. This penalty ''replaces'' the "Half Leg Limbs" penalty.
|}

∗A player can opt out of physically removing the section from the model by placing down the respective Destroyed Limb token. Status effects still apply.

Any and all weapons/abilities are lost when the location they are attached to is destroyed.

==== Destroyed vs Inoperative ====
When the ''' Torso Durability Points''' or '''Cockpit Durability Points''' of a Unit are reduced to 0, the Unit is considered destroyed. If a Mech Unit's Torso Core Part remains intact, but its limbs are all destroyed, it is considered Inoperative. If a Vehicle Unit's Cockpit Core Part remains intact, but it loses its ability to move, it is considered Inoperative. An Inoperative Unit can continue participating in the Engagement if it still has Drones or Mounted Weapons that have not been destroyed.

There are 4 unique areas to a Standard Mech Unit:
* Head, Torso, Arm, and Leg

For Standard Vehicles:
* Cockpit, Body, and (wings/wheels/treads/etc).

Destroying each one results in a different penalty for that Unit.

'''NOTE''': If your Unit does not start with one of these sections, they do not suffer the effects of not having them in the game.

=== Command Actions ===
Actions that can be made during a Units turn but aren’t tied to a specific phase. All Command Actions require 2 Action Points to conduct and can be used multiple times within a single turn. Command Actions (CA’s for short) are divided into 3 categories: State, Stance, & Order.

* States are togglable actions.
* Stances are actions that can be taken out of turn. Activating these immediately ends the Units turn.
* Orders are actions given to drones.

<googlespreadsheet width="800px" height="400" style="width:100%">1_C7NQJUp3Mp4f-um1pdjqg1mSETzNeRW1XDPw9KhFiE</googlespreadsheet>

=== Status Effects ===
{| class="wikitable" style="text-align:center; vertical-align:middle; background-color:rgba(249, 249, 249, 0.67); color:#222;"
|- style="font-weight:bold; background-color:#EEE;"
! Name
! Token
! Description
|-
| Conceal
| <>
| style="text-align:left;" | Unit gains +1 to their Evasion Rolls against ranged attacks.
|-
| Overheat
| <>
| style="text-align:left;" | Unit is immediately put into the kneeling position and ends its turn.
|-
| Freeze
| <>
| style="text-align:left;" | Unit ends its turn immediately. Upon its next activation, its max AP storage capacity is limited to 8.
|-
| Euphotic
| <>
| style="text-align:left;" | Standard Movement is reduced by 2 Movement Points.
|-
| Abyss
| <>
| style="text-align:left;" | Standard Movement is reduced by 2 movement points and the Unit takes 10 damage to the torso per turn.
|-
| Stuck
| <>
| style="text-align:left;" | The Unit is unable to move and is considered '''Inoperable''' until the stuck condition is removed.
|-
| Hold
| <>
| style="text-align:left;" | The Unit is being held by another unit. It may only take the '''Break Hold''' Command Action.
|-
| System Error
| <>
| style="text-align:left;" | Unit ends its turn immediately. Before its next activation, roll 1d8 to reboot. On a 5 or higher, the Unit continues activation per normal. On a 4 or lower, the Unit activation is canceled and its turn ends. Upon subsequent activations, the pass requirement is lowered by 1.
|-
| Airborne
| <>
| style="text-align:left;" | If a Unit has the Hover/Fly System, place a corresponding token (+1/+2/+3) next to them to indicate their elevation. Remove if on ground level.
|-
| Submerged
| <>
| style="text-align:left;" | If a Unit has the Cruise/Swim System, place a corresponding token (-1/-2) next to them to indicate their elevation. Remove if on ground level.
|}

== Terrain ==
Scenery on the battlefield can range from tall buildings to small rocks or trees. Some terrain features are included by individual Missions. Different terrain features are represented by different colored hexes. Each colored hex gives different advantages and/or disadvantages.

When placing terrain colors on the battlefield, different colors need to be placed at least 1 hex apart. If a color description states to place it at a specific elevation, the only elevation that it can be placed is at the Zero Elevation (unless otherwise specified by another rule).

=== Elevations ===
{| class="wikitable" style="float:right; margin-left:10px;"
|- style="font-weight:bold;"
! Elevation
! Description
|-
| style="text-align:center;" | +3
| style="text-align:left;" | Exclusively used by Flight Types.
|-
| style="text-align:center;" | +2
| style="text-align:left;" | The highest elevation which a non-flying Unit can maneuver to.
|-
| style="text-align:center;" | +1
| style="text-align:left;" | The most common elevation for Units that have the ability to Fly/Hover.
|-
| style="text-align:center;" | 0
| style="text-align:left;" | Ground Level. All Units can be used at this elevation.
|-
| style="text-align:center;" | -1
| style="text-align:left;" | The most common elevation for Units that have the ability to Swim/Cruise.
|-
| style="text-align:center;" | -2
| style="text-align:left;" | The lowest point Units can reach.
|}
[[File:elevation.png | frame |Right| ]]
Elevation can be used to give Units a strong advantage in combat. Elevation is a factor when choosing where to move or where to attack from. The game has a total of 5 different elevations. Starting from the lowest to the highest; -2, -1, 0, +1, +2, +3. Ground level is represented by 0. This is were all engagements take place unless otherwise stated by the mission or terrain.

Each level of elevation is 4.5 inches below/above the previous/next level. This can easily be measured by placing an Action Base 4/5 on its corner vertically. Everything below that height is on 0 elevation (Ground Level).

Units traveling to higher elevations use 2 Movement Points to do so while Units traveling to lower elevations only use a single Movement Point. A Unit's elevation is determined by where a Mech Unit's waist [where its legs connect] or a Vehicle Unit's cockpit is. This also applies to structures and natural terrain.
<br clear=all>
==== High Ground Bonus ====
{| class="wikitable" style="float:left; margin-right:10px;"
|- style="font-weight:bold;"
! Elevation Difference
! High Ground Bonus Effect
|-
| style="text-align:center;" | 0
| style="text-align:center;" | No Bonus
|-
| style="text-align:center;" | 1
| style="text-align:center;" | +1 to Assault Rolls
|-
| style="text-align:center;" | 2-3
| style="text-align:center;" | +1 to Accuracy Rolls
|-
| style="text-align:center;" | 4-5
| style="text-align:center;" | +2 to Accuracy Rolls
|}
When an attacking Unit is on a higher elevation than its target, that Unit receives a High Ground Bonus (HGB). This bonus is determined by the difference in elevations between the attacking Unit and its target. Units attacking a target at higher elevations do not gain the HGB.
<br clear=all>

=== Hex Colors and Effects ===
{| class="wikitable" style="text-align:center;"
|-
! Name
! Represents
! Description
! Effect
|-
| Grey
| Road or any generic flat land.
| style="text-align:left;" | The default hex. This hex represents nothing more than a place to stand/move on.
| style="text-align:center;" | -
|-
| Red
| Lava
| style="vertical-align:middle; background-color:rgba(249, 249, 249, 0.67); color:#222; text-align:left;" | An extremely hot tile, either lava or some other superheated material dangerous even to ExMac units and vehicles.
| style="text-align:center;" | Causes the '''Overheat''' status effect when ending your turn on the tile.
|-
| Tan
| Desert Area
| style="text-align:left;" | A barren area/landscape where little to no precipitation occurs.
| style="text-align:left;" | Any '''Move''' action costs +1 Movement point per hex. '''Thruster''' and '''Flight''' moves are not affected .
|-
| White
| Snowy Area
| style="text-align:left;" | A blanket of white covers the area. Cold winds and mechanical problems are plenty.
| style="text-align:left;" | Any '''Move''' action costs +1 Movement point per hex. '''Thruster''' and '''Flight''' moves are not affected .
|-
| Green
| Wooded Area
| style="text-align:left;" | Trees and foliage cover the land.
| style="text-align:left;" | -1 to Accuracy rolls for every green hex within the Unit's Line-of-Sight to its target. This effect stacks on itself. If a Unit is on the hex, they gain the '''Conceal''' status Effect.
|-
| Black
| Ruined Structures
| style="text-align:left;" | Piles of concrete and metal litter the area. What used to be structures that touched the sky now hug the ground. Dense black smoke emanates from the rubble.
| style="text-align:left;" | Movement Point cost required to move through a black hex is doubled. -1 to Accuracy rolls for every black hex within a Unit's Line-of-Sight to its target.
|-
| Light Blue
| Shallow Ocean
| style="text-align:left;" | Body of water. Shallow enough to see the bottom yet deep enough to completely lose a Unit to the seas.
| style="text-align:left;" | As soon as a Unit moves on/over this hex, unless they have the Swim/Cruise System, they gain the '''Euphotic''' status Effect.
|-
| Dark Blue
| Deep Ocean
| style="text-align:left;" | The lowest body of water a Unit can go. There is no light, the pressure is extreme, and the tempatures are near freezing.
| style="text-align:left;" | As soon as a Unit moves on/over this hex, unless they have the Swim/Cruise Sytsem, they gain the '''Abyss''' status Effect.
|}

=== Buildings and Structures ===

[[File:Defense structure chart.png| frame | right ]]

Structures can be destroyed to aid or hinder player tactics. Buildings/structures do not need to be placed on black hexes. However, when they are destroyed the hex/hexes they occupy then become a black hex. The chart on the right shows how building Defense is calculated. Some buildings are tall enough that they reach a higher elevation. You can tell by placing a standard hex on its corner. If it's taller than the hex (4.5"), it's on a higher elevation.

When firing at a structure, you are guaranteed a successful hit and do not need to roll for Accuracy. Base Damage is applied as normal. If an attack is made that doesn't completely destroy the building/structure, that damage is subtracted from the building/structure's total Defense. If you wish to attack a Unit through a structure, you will first need to destroy it and then make a separate attack targeting the intended Unit.

<blockquote style="background-color: lightgrey; border: solid thin grey;">
*The building you want to attack through is occupying 1 hex and is in +1 elevation. This means it has a total Defense of 20.
:: If your total damage is less than 20, the building still stands with its remaining Defense left over. If your total damage is more than 20, the building falls and you may then target the enemy Unit on the other side with a new attack.
* NOTE: Since excess damage doesn't pass through the structure, it is advised that you make only the necessary amount of shots needed to bring it down so you still have some attacks for the enemy.
</blockquote>

=== Non-Hex Terrain ===
This terrain is also known as Scatter Terrain. Pieces of Terrain that aren't connected to a hex or hex effect. They may be for decoration or may be used for cover. When building the map come to an agreement with your opponent on which will grant cover and which is purely decorative.

== Battles ==
Battles are waged by following the sequence below:
{| class="wikitable" style="float:right; margin-left:10px;"
|- style="font-weight:bold;"
! Engagement Size
! Deployment Cost Limit
|-
| Scouting
| 600
|-
| Skirmish
| 1200
|-
| Operation
| 1800
|-
| Battle
| 2500
|}
;1. '''Selecting a Engagement Size'''
: Players must first choose an engagement size they wish to play: Scouting, Skirmish, Operation, or Conflagration. This determines the Deployment Cost available for each team.

;2. '''Choosing a Mission'''
: Players determine which Mission will be carried out during the battle; they can only choose from the available Missions in their engagement size. This will determine the Deployment Area the players use as well as specific Mission objectives and certain terrain features. You can either simply agree with your opponent on which Mission to play, or you can roll to randomly select a Mission using one of the following tables:
<center>
{| class="wikitable" style="font-weight:bold; text-align:center; display: inline-table;"
|-
! colspan="2" style="background-color:#9b9b9b;" | Scouting
|- style="background-color:#efefef;"
| D8
| Mission
|- style="font-weight:normal;"
| 1-4
| [[Reconnaissance]]
|- style="font-weight:normal;"
| 5-8
| [[Show of Force]]
|}
{| class="wikitable" style="text-align:center; display: inline-table;"
|- style="font-weight:bold;"
! colspan="2" style="background-color:#9b9b9b;" | Skirmish
|- style="font-weight:bold; background-color:#efefef;"
| D8
| Mission
|-
| 1-2
| [[Winds of War]]
|-
| 3-4
| [[Endless Pursuit]]
|-
| 5-6
| [[Counterattack!]]
|-
| 7-8
| [[The Call of Darkness]]
|}
{| class="wikitable" style="text-align:center; display: inline-table;"
|- style="font-weight:bold;"
! colspan="2" style="background-color:#9b9b9b;" | Operation
|- style="font-weight:bold; background-color:#efefef;"
| D8
| Mission
|-
| 1-2
| [[The Order to Destroy]]
|-
| 3-4
| [[Emissary of Darkness!]]
|-
| 5-6
| [[Burning Sandstorm]]
|-
| 7-8
| [[Protect the Relic]]
|}
{| class="wikitable" style="font-weight:bold; text-align:center; display: inline-table;"
|-
! colspan="2" style="background-color:#9b9b9b;" | Battle
|- style="background-color:#efefef;"
| D8
| Mission
|- style="font-weight:normal;"
| 1-4
| [[Protect the Base]]
|- style="font-weight:normal;"
| 5-8
| [[Marshall Law]]
|}
</center>
;3. '''Assembling a Squad'''
: Players must then assemble a Squad with a sum total Deployment Cost less than the listed Deployment Cost Limit for the engagement size.

;4. '''Reading Mission Briefing'''
: Each Mission has a Mission briefing that will detail the primary objectives that award points to the players. Some Mission briefings also list one or more Mission rules that will apply for the duration of the battle. The players should read and familiarize themselves with these before proceeding.

;5. '''Creating the Battlefield'''
: The players now create the battlefield and set up terrain features. Missions are played on rectangular hex-grid battlefields which measure 16x13 hexagonal tiles, or 202 total hexes, with the flat side facing each player.

;6. '''Placing Objective Markers'''
: The players now set objective markers up on the battlefield. Each Mission’s deployment map will show the players how many to set up and where each should be placed.

;7. '''Determine who is Attacker and Defender'''
: Players roll 1D8 to determine this. The highest value chooses who will be Attacker and Defender. The Attacker goes first in the engagement but the Defender chooses their Deployment Area.

;8. '''Choose a Deployment Area'''
: The Defender chooses their deployment area first followed by the Attacker.

;9. '''Deploy Squads'''
: Squad deployment is done in alternating order. Check [[Core_Rules#Deployment]] for more information. There may be more specific rules in the mission briefing.

;10.'''Begin the Battle'''
: Resolve any pre-battle rules then begin activation with the Attacker's first unit.

;11.'''End the Battle'''
: The battle ends when the number of turns pass in the mission briefing or all of one side's units have become destroyed or inoperable.

;12.'''Determine the Victor'''
: Each player can score a maximum of 7 points from primary objectives and a maximum of 7 points from secondary objectives for a total of 14 possible points (any excess victory points awarded are discounted).

== Terminology ==
{| class="wikitable" style="text-align:center; vertical-align:middle; background-color:#F8F9FA; color:#202122;"
|- style="font-weight:bold; background-color:#EAECF0;"
! Term !! Definition
|-
| Accuracy Roll
| style="text-align:left;" | 1d8 that determines the outcome of a Ranged Attack.
|-
| Assault Roll
| style="text-align:left;" | 1d8 that determines the outcome of a Melee Attack.
|-
| Evasion Roll
| style="text-align:left;" | 1d8 that determines the outcome of an attempted Evasion.
|-
| Critical Hit
| style="text-align:left;" | An attack that cannot be Evaded. Adds .5 of the Weapon's Base Damage as bonus damage (round up).
|-
| On-Target
| style="text-align:left;" | After an Accuracy/Assault Roll is successful but an Evasion Roll has yet to be conducted.
|-
| Classification
| style="text-align:left;" | Determined by the Total Defense Points of a Unit.
|-
| Line of Sight
| style="text-align:left;" | A straight, unobstructed line from an attacking Unit to its target.
|-
| Field of View
| style="text-align:left;" | The hexes in the front-left, front-right, and front-center in the direction a Unit is facing as well as every hex behind those hexes.
|-
| Blind Spot
| style="text-align:left;" | The hexes in the rear-left, rear-right, and rear-center in the direction a Unit is facing.
|-
| Standard Movement
| style="text-align:left;" | Also referred to as Standard Movement Points. The number of hexes a Unit can move in a single turn
|-
| Thruster Movement
| style="text-align:left;" | Only available if thrusters are on a Unit's model. Forfeit Ranged and Close Combat phases if used. The path a Unit takes is linear in the direction the player chooses. If an obstacle blocks the full travel length, the Unit stops one hex prior to that obstacle.
|-
| Action Points
| style="text-align:left;" | Also referred to as AP. Points used to determine how many actions can be performed in a single turn.
|-
| Command Actions
| style="text-align:left;" | Also referred to as CA. Any action NOT dealing with the Movement Phase or either of the two Combat Phases. Requires 2 AP to perform any CA.
|-
| Equipped Weapons
| style="text-align:left;" | Weapons that are being held in the hands of a Unit.
|-
| Mounted Weapons
| style="text-align:left;" | Weapons that are mounted directly to a Units Section. Cannot be swapped. Roll 1d8. If 6+, will explode when destroyed, dealing 100% weapon damage to the section it was attached to.
|-
| Carried Weapons
| style="text-align:left;" | Weapons that are being stored on the Unit but not Equipped. Can be Equipped or Retrieved if space is available in the Unit's hand(s). These Weapons must be Equipped before using.
|-
| Base Damage
| style="text-align:left;" | How much damage a weapon deals before modifications.
|-
| Fall Damage
| style="text-align:left;" | 2 ( Unit Classification * Elevation Height) to the Units Leg Sections (or Torso if no legs).
|-
| Collision Damage
| style="text-align:left;" | 2 ( Moving Unit Classification * Thrown Distance)
|-
| Throw Distance
| style="text-align:left;" | 8 - (Attacker Modified Assault Stat)
|-
| Systems
| style="text-align:left;" | Abilities that directly come from parts on the physical Unit model. Having these parts on the model does not automatically give the Unit the ability.
|-
| Mods
| style="text-align:left;" | Abilities that come from upgrades and tuning of the Unit's internal components which are not immediately visible on the model.
|-
| Traits
| style="text-align:left;" | Abilities granted to the Unit from the pilot.
|-
| Artificial Intelligence
| style="text-align:left;" | RoyRoy heads have their own sentience used for giving Drones autonomy.
|-
| Core Parts
| style="text-align:left;" | Any and all parts that make up the CORE of the unit- limbs and the armor attached to those limbs. e.g. head, head armor, chest, knee armor, etc.
|-
| Unit Sections
| style="text-align:left;" | Core parts that are grouped into individual sections. EG; Head, Arms, Legs, Torso, etc.
|-
| Core Type
| style="text-align:left;" | Determines your Unit's base Stats. Each Core Type provides different Stats.
|-
| Deployment Cost
| style="text-align:left;" | The overall Cost of a Unit toward the Deployment Cost Limit of any Engagement. This includes Weapons, Equipment, Defense, Systems, Mods, etc.
|-
| S.R.M.
| style="text-align:left;" | Stat Reduction Modifiers. This number reperesents how many times a Unit's base stats can be lowered to a minimum of 2 Accuracy, 2 Assault, and 2 Evasion.
|-
| Main Unit
| style="text-align:left;" | Refers to a single Unit that controls drones.
|}

{{CoreNavigation}}
[[Category:Rules]]

EG GAT-X105 Strike Gundam

2026-03-08T20:49:38Z

Lavtiz29: Redirected page to GAT-X105 Strike Gundam

#Redirect [[GAT-X105 Strike Gundam]]

Welcome to the War

2026-02-11T21:32:44Z

Lavtiz29:

30 Minute Missions: Wargame (30MM:W) is a mech-based tabletop miniatures game using [https://www.gundamplanet.com/30-minutes-missions.html Bandai Spirit's easy-to-build 1/144 scale mech kits]. The focus of this game is on:
# The ability to play missions in roughly 30 minutes (excluding setup); and
# The customizability and modular designs for the model kits.

Our community offers a tailored experience for players ranging from beginner to veteran players. (link to a page for beginners and one for vets)

For more information on getting started, please report to [[Core Rules]].

To join a campaign, find other players, or just chat about the game, we recommend joining the [https://discord.gg/8XZYd5dWGk Discord server]. Additionally, feel free to check out our [https://www.youtube.com/c/AriesTabletopModels YouTube] & our [https://twitter.com/30MM_Wargame Twitter feed] for any news.

<b> 30MM: Wargame is currently undergoing a major update.
The game is actively being revised and expanded as part of ongoing development. Rules, systems, and content may change as improvements are implemented. Thank you for your patience and continued support as the project moves toward its next phase. </b>

== Quickstart ==


<div class="toccolours mw-collapsible" style="width:97%; padding:0.5em">
<div style="font-weight:bold;line-height:1.6;">Recruit</div>
<div class="mw-collapsible-content">
* [[Core Rules]]
* [https://docs.google.com/document/d/1eDKaBn5mceBYUARUQiR2uvK2ZxTd-t0vWfzCqqQ-lwM/edit?usp=sharing Quick Start Guide]
* [[Abilities]]
* [[Unit Datasheet Creation]]
* [[Page Creation Shortcut]]
* [[:Category:Stories|All Writing]]
* [https://docs.google.com/spreadsheets/d/17BZ1F7FpO5finnEYQVINvdjePFtv_WhdVBI6JZ_mXLk/edit#gid=1319329094 Parts List]
</div></div>
<div class="toccolours mw-collapsible" style="width:97%; padding:0.5em; margin-bottom:1em">
<div style="font-weight:bold;line-height:1.6;">Commanders</div>
<div class="mw-collapsible-content">
* [[:Category:Factions |Factions]]
** [[:Category:Byron |Byron Army]]
** [[:Category:Earth | Earth Alliance]]
** [[:Category:Maxion | Maxion Army]]
** [[:Category:Mercenary|Mercenaries]]
** [[:Category:Warmongers|Warmongers]]
** [[:Category:Peacemakers|Peacemakers]]
* [[:Category:Units|All Units]]
** [[:Category:Mech | Mech Units]]
** [[:Category:Vehicle | Vehicle Units]]
* [[:Category:Weapons|Weapons]]
</div></div>
<div class="toccolours mw-collapsible mw-collapsed" style="width:97%; padding:0.5em">
<div style="font-weight:bold;line-height:1.6;">Contributors</div>
<div class="mw-collapsible-content">
* [[Formatting Guidelines]]
* [[#Conduct|Codes of Conduct on this site]]
* [[Special:RecentChanges|Most Recent Updates]]
* [[Special:NewFiles|Newest Uploads]]
* [[:Category:Stubs|Incomplete stub Pages]]
* [[:Category:Articles_in_need_of_cleanup|Pages needing cleanup]]
* [[Special:Lonelypages|Orphaned Pages]]
* [[Special:Wantedpages|Wanted Pages]]
* [[:Category:Needs_Images|Pages requesting Images]]
</div></div>
----

Welcome to the War

2026-02-11T21:30:40Z

Lavtiz29:

30 Minute Missions: Wargame (30MM:W) is a mech-based tabletop miniatures game using [https://www.gundamplanet.com/30-minutes-missions.html Bandai Spirit's easy-to-build 1/144 scale mech kits]. The focus of this game is on:
# The ability to play missions in roughly 30 minutes (excluding setup); and
# The customizability and modular designs for the model kits.

Our community offers a tailored experience for players ranging from beginner to veteran players. (link to a page for beginners and one for vets)

For more information on getting started, please report to [[Core Rules]].

To join a campaign, find other players, or just chat about the game, we recommend joining the [https://discord.gg/8XZYd5dWGk Discord server]. Additionally, feel free to check out our [https://www.youtube.com/c/AriesTabletopModels YouTube] & our [https://twitter.com/30MM_Wargame Twitter feed] for any news.

## 30MM: Wargame is currently undergoing a major update.
The game is actively being revised and expanded as part of ongoing development. Rules, systems, and content may change as improvements are implemented. Thank you for your patience and continued support as the project moves toward its next phase.##

== Quickstart ==


<div class="toccolours mw-collapsible" style="width:97%; padding:0.5em">
<div style="font-weight:bold;line-height:1.6;">Recruit</div>
<div class="mw-collapsible-content">
* [[Core Rules]]
* [https://docs.google.com/document/d/1eDKaBn5mceBYUARUQiR2uvK2ZxTd-t0vWfzCqqQ-lwM/edit?usp=sharing Quick Start Guide]
* [[Abilities]]
* [[Unit Datasheet Creation]]
* [[Page Creation Shortcut]]
* [[:Category:Stories|All Writing]]
* [https://docs.google.com/spreadsheets/d/17BZ1F7FpO5finnEYQVINvdjePFtv_WhdVBI6JZ_mXLk/edit#gid=1319329094 Parts List]
</div></div>
<div class="toccolours mw-collapsible" style="width:97%; padding:0.5em; margin-bottom:1em">
<div style="font-weight:bold;line-height:1.6;">Commanders</div>
<div class="mw-collapsible-content">
* [[:Category:Factions |Factions]]
** [[:Category:Byron |Byron Army]]
** [[:Category:Earth | Earth Alliance]]
** [[:Category:Maxion | Maxion Army]]
** [[:Category:Mercenary|Mercenaries]]
** [[:Category:Warmongers|Warmongers]]
** [[:Category:Peacemakers|Peacemakers]]
* [[:Category:Units|All Units]]
** [[:Category:Mech | Mech Units]]
** [[:Category:Vehicle | Vehicle Units]]
* [[:Category:Weapons|Weapons]]
</div></div>
<div class="toccolours mw-collapsible mw-collapsed" style="width:97%; padding:0.5em">
<div style="font-weight:bold;line-height:1.6;">Contributors</div>
<div class="mw-collapsible-content">
* [[Formatting Guidelines]]
* [[#Conduct|Codes of Conduct on this site]]
* [[Special:RecentChanges|Most Recent Updates]]
* [[Special:NewFiles|Newest Uploads]]
* [[:Category:Stubs|Incomplete stub Pages]]
* [[:Category:Articles_in_need_of_cleanup|Pages needing cleanup]]
* [[Special:Lonelypages|Orphaned Pages]]
* [[Special:Wantedpages|Wanted Pages]]
* [[:Category:Needs_Images|Pages requesting Images]]
</div></div>
----

Welcome to the War

2026-02-11T21:27:40Z

Lavtiz29: Added maintenance update

30 Minute Missions: Wargame (30MM:W) is a mech-based tabletop miniatures game using [https://www.gundamplanet.com/30-minutes-missions.html Bandai Spirit's easy-to-build 1/144 scale mech kits]. The focus of this game is on:
# The ability to play missions in roughly 30 minutes (excluding setup); and
# The customizability and modular designs for the model kits.

Our community offers a tailored experience for players ranging from beginner to veteran players. (link to a page for beginners and one for vets)

For more information on getting started, please report to [[Core Rules]].

To join a campaign, find other players, or just chat about the game, we recommend joining the [https://discord.gg/8XZYd5dWGk Discord server]. Additionally, feel free to check out our [https://www.youtube.com/c/AriesTabletopModels YouTube] & our [https://twitter.com/30MM_Wargame Twitter feed] for any news.

```
30MM: Wargame is currently undergoing a major update.
The game is actively being revised and expanded as part of ongoing development. Rules, systems, and content may change as improvements are implemented. Thank you for your patience and continued support as the project moves toward its next phase.
```

== Quickstart ==


<div class="toccolours mw-collapsible" style="width:97%; padding:0.5em">
<div style="font-weight:bold;line-height:1.6;">Recruit</div>
<div class="mw-collapsible-content">
* [[Core Rules]]
* [https://docs.google.com/document/d/1eDKaBn5mceBYUARUQiR2uvK2ZxTd-t0vWfzCqqQ-lwM/edit?usp=sharing Quick Start Guide]
* [[Abilities]]
* [[Unit Datasheet Creation]]
* [[Page Creation Shortcut]]
* [[:Category:Stories|All Writing]]
* [https://docs.google.com/spreadsheets/d/17BZ1F7FpO5finnEYQVINvdjePFtv_WhdVBI6JZ_mXLk/edit#gid=1319329094 Parts List]
</div></div>
<div class="toccolours mw-collapsible" style="width:97%; padding:0.5em; margin-bottom:1em">
<div style="font-weight:bold;line-height:1.6;">Commanders</div>
<div class="mw-collapsible-content">
* [[:Category:Factions |Factions]]
** [[:Category:Byron |Byron Army]]
** [[:Category:Earth | Earth Alliance]]
** [[:Category:Maxion | Maxion Army]]
** [[:Category:Mercenary|Mercenaries]]
** [[:Category:Warmongers|Warmongers]]
** [[:Category:Peacemakers|Peacemakers]]
* [[:Category:Units|All Units]]
** [[:Category:Mech | Mech Units]]
** [[:Category:Vehicle | Vehicle Units]]
* [[:Category:Weapons|Weapons]]
</div></div>
<div class="toccolours mw-collapsible mw-collapsed" style="width:97%; padding:0.5em">
<div style="font-weight:bold;line-height:1.6;">Contributors</div>
<div class="mw-collapsible-content">
* [[Formatting Guidelines]]
* [[#Conduct|Codes of Conduct on this site]]
* [[Special:RecentChanges|Most Recent Updates]]
* [[Special:NewFiles|Newest Uploads]]
* [[:Category:Stubs|Incomplete stub Pages]]
* [[:Category:Articles_in_need_of_cleanup|Pages needing cleanup]]
* [[Special:Lonelypages|Orphaned Pages]]
* [[Special:Wantedpages|Wanted Pages]]
* [[:Category:Needs_Images|Pages requesting Images]]
</div></div>
----

Unit Datasheet Creation

2025-09-04T01:14:17Z

2025-09-04T00:47:40Z

Lavtiz29: