← All spotlightsPrograms / Features

Spotlight › WireFleet

WireFleet

A two-PC naval game with local fleet state, turn-identified serial messages and paired saves.

A battle
The WireFleet window on the os8088 desktop. A navy banner reads OPPONENT'S TURN, Turn 14. On the left, YOUR FLEET: a 10 by 10 grid of navy water with five grey ships, two of them marked with red crosses where they were hit, and white dots for misses. On the right, ENEMY WATERS: three red crosses down column I, one at E3 and two white dots. Below, the lines They fired D10: miss and You fired I3: HIT!, a chat log reading Peer: good shot and You: thanks, and a status bar with COM2, 2400 baud 8N1 and Opponent ready.
WireFleet battle view.
Serial link
2,400 baud
Fleet
5 ships / 17 squares
Executable
26KB

01 / Fleet and turn rules

Fleet and turn rules

Each player places five ships on a 10x10 grid: lengths 5, 4, 3, 3 and 2. Ships may touch but cannot overlap. One shot is allowed per turn, including after a hit. Seventeen occupied cells must be hit to win.

R rotates a ship, A randomises placement and Y commits it. T sends a short peer message. The game discovers a supported serial peer while respecting the desktop's port lease.

02 / Paired-game captures

Paired-game captures

Both views are from emulated PCs connected by a virtual null modem.

Deploy your fleet
The WireFleet window with a navy banner reading DEPLOY YOUR FLEET and the line Opponent found! Place your fleet, then Ready [Y]. On the left, YOUR WATERS: a 10 by 10 navy grid with five grey ships placed. On the right, YOUR SHIPS: the carrier, battleship, cruiser, submarine and destroyer, each with a picture and a ticked box, 5 / 5 placed, the buttons Horiz. [R], Auto [A] and Clear [C], and a large green READY [Y] button.
Local fleet placement.
The other PC
The same battle on the second PC. The banner reads YOUR TURN, Turn 14. Its own fleet on the left has three red crosses down a carrier in column I and one on a ship at E3. Its enemy waters on the right show two red crosses and five white dots. The chat log reads You: good shot and Peer: thanks, and the status bar shows COM1, 2400 baud 8N1.
Other peer at the same turn.

03 / Local fleet authority

Local fleet authority

A shot transmits its coordinates; the receiving peer evaluates its own fleet and replies hit/miss/sunk. The full enemy layout is not transmitted during placement. That limits routine disclosure; it is not cryptographic protection against a modified peer.

Messages include integrity, match and turn fields. Missing replies are retried and duplicate actions are rejected. A quiet link pauses the turn with pending state retained. The supported rate is 2,400 baud; the recorded faster XT test lost bytes.

S/O save and load each peer's state. Both files must identify the same match. Reconnecting or loading does not arbitrarily choose one side's turn history.

04 / Link and save limits

Link and save limits

Two compatible peers are required; no computer opponent, TCP/IP match, USB-controller path or modem mode. A saved file contains that player's hidden fleet and should not be handed to the opponent.

Use the package/protocol generation supported by both systems. A release label alone is not a guarantee that every older peer can negotiate it.

05 / Start WireFleet

Start WireFleet

Launch WIREFLET.O88 on both hosts after connecting a null modem. Identify a serial mouse before peer discovery when needed. Place ships and press Y. make wirefleet-pair supplies the paired 86Box configuration. DB9 three-wire links use crossed 2/3 and common 5; DB25 uses crossed 2/3 and common 7.