Communication gameplay replacement

General Acid Goop
1

Hello CM players, after 10 mins using chatgpt I have finalized a new and “better" comms for marines.

SEEGSON FIELD — FIELD MANUAL

Operational Field Manual v1.0
Classification: Shipboard/Expeditionary — Restricted Use
Purpose: Deployable communications & motion-detection mast for use during blackout / high-jamming operations. Designed for rapid fabrication, tactical deployment, and manual launch from Torpedo Bay.

I. INTRODUCTION

Seegson Field masts (masts) are field-deployable relay/sensor nodes fabricated from hollowed torpedo frames, radio transmitters, motion-detector modules, and small nuclear fuel cells. Masts provide progressive communications restoration and motion-sensor coverage by forming a short-range mesh and offloading signal processing to nearby Working-Joe / Synthetic units.

Key capabilities

  • Local radio relay and protocol transformation (Morse → hybrid → full-text)

  • Passive motion detection and target classification within local radius

  • Manual launch from Torpedo Bay with autonomous descent, anchor, and activation

Operational constraints

  • No local CPU: WJ/Synth units replacement possible.

  • Fragile hardware; susceptible to EMP, direct fire, and hacking.

  • Fuel-limited (nominal 30 minutes per small nuclear cell).

II. COMPONENTS & TOOLS (Fabrication Kit)

  • 1× Hollowed torpedo casing (structural frame)

  • 1× Radio pack (transmitter/receiver)

  • 1× Motion Detector (MD) module

  • 1× Small Nuclear Fuel Cell (power)

  • 2× Fasteners / Straps / Mounting hardware

  • 1× Lasing device (for coordinate calibration; ground unit)

  • 1x Working Joe/Synthetic unit.

III. FABRICATION PROCEDURE (Bench)

Estimated bench time: 5–7 minutes

  1. Secure torpedo casing; remove warhead/guidance components.

  2. Mount radio pack and MD module in internal cavity; route external antenna port.

  3. Install fasteners and strap components to secure internal modules.

  4. Insert small nuclear fuel cell in its isolated chamber; wire to radio and MD.

  5. Disable local CPU housing; configure mast to broadcast processing-job beacons.

  6. Label unit: SEEGSON FIELD — MAST #[ID]. Run self-test: power heartbeat, MD ping, job broadcast.

Completed masts are to be staged in the Torpedo Bay for manual launch.

IV. OPERATIONAL PARAMETERS

  • Detection radius: 15 tiles (per mast)

  • Mesh link distance: 25 tiles (masts auto-link within this distance)

  • Fuel runtime: 30 minutes (small nuclear cell, baseline) — flight consumes additional fuel (see Flight & Power)

  • Processing dependency: Nearby masts within 15 tiles required for high-quality translation/classification

  • Durability: Low — place redundantly or with cover

V. COMMUNICATION TIERS (Designations & Behavior)

Mast Count Active Designation Transmission Clarity Operational Notes
1 Field Level Alpha Only Morse or burst-coded transmission possible Emergency short-range encoded messages; high ambiguity.
2 Field Level Beta Garbled, partial voice comms with Morse intermix Partial intel; expect corruption and missing characters.
3+ Field Level Gamma Normal full-spectrum communication Restores stable coordination and plaintext transmission.

Processing & Confidence

  • Masts broadcast lightweight processing jobs using nearby Working-Joe / Synthetic units (within 15 tiles).

  • Confidence formula (operational): confidence% = min(90, 40 + 20*(masts_online-1) + 5*(nearby_wj_count)).

  • Confidence affects message clarity and MD classification accuracy. Max cap retains operational uncertainty.

VI. LAUNCH & GUIDANCE (Manual Launch Flow)

Summary: Masts are manually launched from the Torpedo Bay by Command or authorized ordnance personnel, following torpedo-style release procedures. After launch, each mast executes autonomous flight, terminal calibration, anchor, and activation routines.

Launch Preconditions

  • Mast staged and fueled in Torpedo Bay.

  • Command/Torpedo Officer issues GUIDANCE_AUTH { mast_id, mission_id, auth_token }.

  • Ground unit supplies coordinate calibration via LASER_FIX (recommended) or runner delivers authenticated coordinates prior to release.

  • Fuel reserves confirmed for flight + operational time.

Launch Sequence (high-level)

  1. Authorization: Torpedo Room issues GUIDANCE_AUTH.

  2. Preflight Check: Mast self-tests; aborts if failed (PRELAUNCH_ABORT).

  3. Release & Flight: Mast ejected and executes ascent/flight profile; consumes additional fuel for flight.

  4. Terminal Phase: Mast requests LASER_FIX from ground lasing unit within terminal window (default 6 tiles). If validated (delta ≤ 3 tiles) mast proceeds to landing. Otherwise enters hold/await state or aborts to safe-drop.

  5. Landing & Activation: Mast anchors and initiates broadcast and MD operation, joins local mesh.

Telemetry & Operator Interface

  • Monitor MAST_STATUS, INERTIAL_COORD vs LASER_FIX delta, FUEL_ESTIMATE, EXPECTED_MISS_RADIUS, and RISK_INDICATOR.

  • Operator may abort, command return-to-ship, or authorize safe-drop per rules of engagement.

VII. MOTION DETECTION NETWORK

  • Each mast emits MD pings within 15 tiles.

  • Overlap improves confidence but not radius; multiple masts increase detection confidence per formula.

  • MD output structure: { timestamp, tile_x, tile_y, classification, confidence }.

  • Classification categories: MARINE, WJ, SYNTH, SURVIVOR, CLF_AGENT, UNKNOWN.

VIII. SECURITY & MAINTENANCE

  • Known vulnerabilities: EMP, hackable WJ/Synth processors, direct destruction.

  • Mitigations: redundancy, authentication tokens for LASER_FIX, operator review of TARGET_MARK.

  • Regular maintenance: fuel swap every mission, bench diagnostics prior to staging, log retrieval post-op.

IX. EXAMPLES (How Each Comms Level Works — Concrete Scenarios)

Example A — Short Command Order

Intended (original):
BRAVO, HOLD POSITION. CLF AGENTS AT GRID 12,18. PREPARE TORP.

  • Field Level Alpha (1 mast — Morse-only)

    • Transmitted: long Morse string (dots/dashes).

    • Received: audio/visual Morse only; no plaintext.

    • Action: Units must decode Morse or verify visually. Default conservative action: hold and send scout to verify.

  • Field Level Beta (2 masts — Garbled Hybrid)

    • Transmitted: BRAVO, H---D P--SITION. CLF ... / AT GRID 12,18. PREPARE T--P.

    • Received: partial plaintext with corrupted verbs/letters.

    • Action: Confirm grid via lasing or runner prior to committing torpedo assets.

  • Field Level Gamma (3+ masts — Normal)

    • Transmitted/Received: full plaintext identical to intended message.

    • Action: Proceed with standard targeting and torpedo calibration procedures.

Example B — Motion-Detection Ping (MD Classification)

Raw MD intent: Detect moving entity at tile (34,67) and classify as CLF agent.

  • Field Level Alpha

    • Mast report (console): MD_PING { x:34, y:67, classification: UNKNOWN, confidence: 40% } (beep alert)

    • Action: Visual verify; do not engage without confirmation.

  • Field Level Beta

    • Mast report: MD_PING { x:34, y:67, classification: CLF_AGENT?, confidence: 60% } (mixed message)

    • Action: Prepare but require lasing/runner verification before kinetic response.

  • Field Level Gamma

    • Mast report: MD_PING { x:34, y:67, classification: CLF_AGENT, confidence: 85% } (clean)

    • Action: Authorize targeting workflow (lase calibration then launch).

Example C — Target Mark (what Torpedo Control sees)

Mast-origin target proposal: mark at tile (48,12)

  • Field Level Alpha

    • Message: TARGET_MARK { job_id:J-001, x:48, y:12, confidence: 42% }

    • Torpedo Console: TARGET_MARK RECEIVED — CONFIDENCE LOW (42%) — LASER_FIX REQUIRED

    • Action: Do not launch; require ground laser calibration or manual override with justification.

  • Field Level Beta

    • Message: TARGET_MARK { job_id:J-002, x:48, y:12, confidence: 65% }

    • Console: TARGET_MARK — MEDIUM (65%) — LASER_FIX RECOMMENDED

    • Action: Request LASER_FIX; approve on validation with caution.

  • Field Level Gamma

    • Message: TARGET_MARK { job_id:J-003, x:48, y:12, confidence: 88% }

    • Console: TARGET_MARK — HIGH (88%) — LASER_FIX VALIDATION PREFERRED

    • Action: Proceed with lasing validation; expected hit ±1 tile post-validation.

X. QUICK REFERENCE (Pocket Card)

Fabrication: Torpedo casing + Radio + MD + Small Nuclear Cell → bench test → stage.
Range: 15 tiles. Mesh link: 25 tiles. Fuel: 30 min (baseline).
Modes:

  • Alpha (1 mast): Morse-only — decode/verify.

  • Beta (2 masts): Garbled — verify coordinates.

  • Gamma (3+ masts): Normal — standard ops.
    Processing: Offloaded to WJ/Synth within 15 tiles. Confidence = min(90,40+20*(m-1)+5*w).
    Deployment: Manual launch from Torpedo Bay; mast executes flight, terminal lase-calibration, and autonomous anchor/activation. Operator must confirm telemetry before sequential launches.
    Safety: Review EXPECTED_MISS_RADIUS and RISK_INDICATOR before acceptance.

This new system utilizes most of the useless stuffs shipside like the torpedo rooms west of CIC, fuel cells that only used when nuking the ship, and Working Joe. Another plus for the idea, since the laze would need to return to Almayer, command now has another reason to force marines to stay and build FoB for like 10 more mins till they all run away.

It fits with the lore of “Almayer got blasted to hell during an ambush" or whatever the reason for the current state. And since it acts as sensor, command can gamble on where to launch them.

As for the xenos, you can just kill them as they’re crippled Joe’s or synths (xenos hate them anyways).

And to conclude, this system requires minimal works on devs and sprites as it use most of current stuffs.

5 Likes
2

Cool — here’s a simple one you can just copy-paste as your reply:

This actually sounds awesome. Reusing all the ship junk for something useful is peak Seegson energy. Would be sick to see this in-game.

2 Likes
3

You always know a Working Joe.

1 Like
4

-Acid Goop
-Utter beauty and soul

2 Likes