<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|}}}<div id="Durability" visibility="hidden">{{{Durability|}}}</div></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]]

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.