Difference between revisions of "Fleet Contact Management System (CMS)"
Scottsigler (Talk | contribs) (→Friendly Contacts) |
Scottsigler (Talk | contribs) (→Visual Display Conventions) |
||
| Line 67: | Line 67: | ||
| Enemy Ship || Circle (solid) || Red || Assigned codename upon ID | | Enemy Ship || Circle (solid) || Red || Assigned codename upon ID | ||
|- | |- | ||
| − | | Friendly Fighter || | + | | Friendly Fighter || Triangle (outline) || Blue-Green || Sentinels |
|- | |- | ||
| − | | Enemy Fighter || | + | | Enemy Fighter || Triangle (solid) || Red-Orange || Labeled as Fang |
|- | |- | ||
| − | | Friendly Torpedo || | + | | Friendly Torpedo || Chevron || Purple || Mark14/15/16; labeled Tadpole |
|- | |- | ||
| − | | Enemy Torpedo || | + | | Enemy Torpedo || Chevron || Rust || Labeled as Tiger |
|- | |- | ||
| − | | Friendly Missile || Cross | + | | Friendly Missile || Cross || Indigo || Rare use |
|- | |- | ||
| − | | Enemy Missile || Cross | + | | Enemy Missile || Cross || Yellow || Labeled as Mallet or Vampire |
|- | |- | ||
| Friendly APC || Square (outline) || Blue || Ochtheras | | Friendly APC || Square (outline) || Blue || Ochtheras | ||
Revision as of 16:59, 17 April 2025
Fleet Contact Management System (CMS) is the contact tracking and designation protocol used by the Planetary Union Fleet in The Crypt series. It is a comprehensive naming and visualization system used to monitor ships, torpedoes, missiles, fighters, and unknowns within a combat environment, especially within the navigation orb (nav-orb) of the PUV James Keeling.
Contents
Overview
The CMS allows Fleet personnel to:
- Track unknown or hostile contacts in real-time
- Assign unique designators to new contacts (e.g., "Locus One")
- Transition contact names as information becomes available
- Visually identify contacts on tactical displays, such as the nav-orb
Naming Protocol
The CMS assigns alphanumeric codenames to detected contacts based on object type and origin (friendly or hostile). Initial unknowns are designated as "Locus One," "Locus Two," etc. Once classified, these designations are replaced with type-based codenames. Friendly units use class identifiers; hostile contacts receive distinct, non-overlapping labels.
Locus Designation Rules
- All new contacts are assigned a sequential "Locus" identifier (e.g., Locus One, Locus Two).
- Once a contact's type is known (e.g., torpedo, ship, fighter), its name transitions to the appropriate codename (e.g., Tiger-One).
- If the **type** of ship is identified but not the individual vessel, it becomes [Ship Type] + Locus number (e.g., Destroyer Locus Five).
- If the **individual ship** is identified via grav-sig, its codename is replaced with the ship’s name (e.g., ISS Renegade).
CMS Naming Conventions
Hostile Contacts
| Contact Type | Designation Format | Notes | Nav-Orb Icon |
|---|---|---|---|
| Unknown Contacts | Locus One, Locus Two, etc. | Temporary designators until confirmed. | Solid circle (fuzzy if under STC) |
| Enemy Ships | Aardvark, Viper, etc. | Assigned persistent codenames once confirmed. | Solid arrow |
| Enemy Torpedoes | Tiger-One, Tiger-Two, etc. | Numbered in order of detection, not by launch ship. | Solid triangle |
| Enemy Missiles | Mallet-One, Mallet-Two, etc. | Short-range void-to-void missiles. | Solid cross |
| Enemy Ship-Killer Missiles | Vampire-One, Vampire-Two, etc. | Long-range capital-killers. High priority. | Solid cross (highlighted or red) |
| Enemy Fighters | Fang-One, Fang-Two, etc. | Single-pilot voidcraft. | Solid chevron |
| Enemy APCs | Tusk-One, Tusk-Two, etc. | Assault boarding transports. | Solid diamond |
Friendly Contacts
A metal arrow at the center of a nav-orb represents the ship the nav-orb is in. The icons below appear in relation to the ship's orientation. The arrow is fixed, always pointing toward the prow. When the ship maneuvers, the icons below move in relation to their orientation to the ship.
| Contact Type | Designation Format | Notes | Nav-Orb Icon |
|---|---|---|---|
| Friendly Ships | Keeling, Union-class identifiers | Known vessels shown by name or class. | Outlined arrow |
| Friendly Torpedoes | Keeling Mark14-One, Mark15-One, Mark16-One | Display codename: Tadpole. Track by type and launch order. | Outlined triangle |
| Friendly Missiles | Union Mallet-One, etc. | Used by other Fleet ships only. | Outlined cross |
| Friendly Ship-Killer Missiles | Union Vampire-One, etc. | Long-range Fleet anti-capital munitions. | Outlined cross (highlighted or blue) |
| Friendly Fighters | Salamander Echo-Five, etc. | Designated by callsign or tail number. | Outlined chevron |
| Friendly APCs | Ochthera Bravo-One, etc. | Denoted by craft and unit name. | Outlined diamond |
Visual Display Conventions
The nav-orb displays contacts using standardized shapes and colors for quick visual parsing under combat conditions. This table summarizes the conventions used aboard Planetary Union vessels, including the PUV James Keeling.
| Contact Type | Icon | Color | Notes |
|---|---|---|---|
| Friendly Ship | Circle (outline) | Blue | Includes Keeling |
| Enemy Ship | Circle (solid) | Red | Assigned codename upon ID |
| Friendly Fighter | Triangle (outline) | Blue-Green | Sentinels |
| Enemy Fighter | Triangle (solid) | Red-Orange | Labeled as Fang |
| Friendly Torpedo | Chevron | Purple | Mark14/15/16; labeled Tadpole |
| Enemy Torpedo | Chevron | Rust | Labeled as Tiger |
| Friendly Missile | Cross | Indigo | Rare use |
| Enemy Missile | Cross | Yellow | Labeled as Mallet or Vampire |
| Friendly APC | Square (outline) | Blue | Ochtheras |
| Enemy APC | Square (solid) | Rust | Labeled as Tusk |
| Unknown Contact | Hollow Hexagon | White | Labeled Locus One, Locus Two, etc. |
| Under STC Distortion | Any shape (fuzzy) | Gray static overlay | Tracking unreliable |
Transition Examples
- A new blip appears in the nav-orb: it's assigned Locus One.
- Once confirmed as a torpedo, the name changes to Tiger-One.
- If grav-sig confirms it as a Mark16 torpedo, it is renamed Tiger-One (Fleet Mark16).
- If it is intercepted or destroyed, its designation is removed.
Use in STC Environments
Because of STC distortion, contacts often appear distorted, "fuzzy," or incomplete. CMS operators must use experience and limited signal data to update contact designations. Visual aids and callouts help the Conn and Weapons stations react under combat stress.
