Status: research notes, 2026-11-21. Every fact carries a source tag like [S3] (list at the end). Anything not backed by a source is marked UNVERIFIED. Nothing here comes from memory.
Method: web search; the Info-Mac game/brd abstracts and the current Info-Mac directory listings; Macintosh Repository, discmaster.textfiles.com, ibiblio (sunsite Linux archive), dosgames.com, Aminet, atariuptodate and the Q-Link Reloaded GitHub repository. Small archives were downloaded to a working folder outside the repository (URLs and sha256 in its SOURCES.md) and read without running anything: C source and docs as text, Mac resource forks and a C64 disk directory with read-only Python parsers, and HyperTalk scripts as text from a HyperCard stack's data fork. No game server was contacted.
The game is called Naval Combat in ParlorNet; the real-world names (Battleship, Salvo, Sea Battle, Battleships) are used here only to find the period software.
- The best candidate is batnav (Batalla Naval), 1995-97, GPL v2: a real client-server game. A Linux server (btserver, TCP port 1995) holds every player's fleet and judges every shot; clients exist for X11, ncurses terminals and Windows 3.x (Win16, Winsock) [S1][S2][S3]. The protocol is a fixed 108-byte binary record, fully readable in the GPL source [S3]. A ParlorNet server extension that imitates btserver is straightforward. Its fleet differs from the classic one (four 1-square, three 2-square, two 3-square and one 4-square ships, which may not touch) [S3].
- No Mac client talks to a server. The Mac network Battleship games found are peer to peer: GameMaster's BattleShips rulebook (Dec 1991; MacTCP or AppleTalk ADSP; "can only play remotely") [S5][S6][S7] and HyperBattleship! (Claris, 1991; HyperCard 2.1 sending Apple events over Program Linking) [S11][S12][S13]. HyperBattleship's whole message set is readable HyperTalk; GameMaster's wire format would have to be recovered from 68k code.
- The only online-service Battleship found is Sea Strike on Quantum Link (Commodore 64) [S16]. The original service is gone, but Q-Link Reloaded is a GPL v2+ server (Jim Brain, 2005) that implements Q-Link's game rooms as a relay of opaque move text [S16]. The Sea Strike move format is not documented.
- DOS and Atari ST had peer-to-peer modem games: Battle Fleet 3.01 (DOS, 1991, Hayes modem or null modem, shareware) [S18] and Battle Blips (Atari ST desk accessory, 1987-88, plain ASCII over the modem, freeware) [S19][S20]. Neither documents its wire format.
- Commercial and service games (Hasbro's Battleship, 1996: LAN/IPX, modem, null modem, MPlayer; announced for the Microsoft Internet Gaming Zone in 1997) used undocumented protocols [S21][S22][S23]. No Battleship was found on Outland, GEnie RSCARDS, CompuServe, the ImagiNation Network, MPG-Net, Kesmai, AOL, Prodigy or Yahoo! Games [S27][S28][S31].
- Recommendation: a batnav extension first (server imitation, high feasibility). GameMaster is the most interesting second target, because one GameMaster bridge would also reach its Othello, Connect 4, Chess, Dots and Boxes and TicTacToe rulebooks [S6]; it needs reverse engineering first. (Update 2026-11-21: the GameMaster protocol is now recovered from its Dev Kit sources and code, gamemaster.md; the Mac-wide comparison is in mac-clients.md.)
| Client | Platform | Years | Connection | Protocol documented? | Licence | Download | Verdict |
| batnav (Batalla Naval) 0.40 / 0.50: xbtclient, nbtclient, btwin | Linux X11 (XView), ncurses terminal, Windows 3.x (Win16, Trumpet Winsock) | first public 0.28 Dec 1995; 0.40 Apr 1996; 0.50 Sep 1997 | TCP client-server to btserver, default port 1995 | Yes, by source (protocol.h, btserver.c, GPL) | GPL v2 | https://www.ibiblio.org/pub/linux/games/multiplayer/batnav-0.50.tar.gz | Server we can imitate. High feasibility |
| GameMaster 1.0.0 + BattleShips rulebook | Mac (68k), black and white; MacTCP, or ADSP ("built into system 7") | Dec 1991 | peer to peer: TCP (port 918 read from code) or AppleTalk ADSP (NBP name type "GameMaster") | No; session layer and rulebook messages are in 68k code | "Povertyware" (pay US$10 if you like it; "share the source and executables around") | https://www.macintoshrepository.org/9523-gamemaster ; discmaster BBS in a box Trilogy II (URLs in Sources) | Peer we could bridge after reverse engineering. Medium-low feasibility, but covers 6+ games |
| HyperBattleship! 2.1 | Mac, HyperCard 2.1, System 7 | 1991 (stack modified 1994) | peer to peer, Apple events (send ... to program) over Program Linking (AppleTalk; TCP/IP "eppc" only from Mac OS 9, UNVERIFIED for this stack) | Message set: yes, readable HyperTalk; transport is Apple's | Claris, all rights reserved, given away | https://www.macintoshrepository.org/41164-hyper-battleship- | Peer we could bridge in principle; the transport (remote Apple events) is the hard part. Low-medium |
| Sea Strike on Quantum Link | Commodore 64 (Q-Link client) | Q-Link from 1985 [S17]; Sea Strike's years and Q-Link's end date UNVERIFIED | modem to the Q-Link service; Q-Link Reloaded today: TCP port 5190 | Server side yes (GPL Q-Link Reloaded relays moves); Sea Strike's move text no | Q-Link client: proprietary; Q-Link Reloaded: GPL v2+ | client disks in https://github.com/ssalevan/qlink | Server we could imitate (or bridge from Q-Link Reloaded); payload must be recovered. Medium, large job |
| Battle Fleet 3.01 | DOS, EGA/VGA | 1991 | peer to peer by Hayes modem or null modem; chat | No | shareware, US$15 | https://www.dosgames.com/files/bfleet.zip | Peer we could bridge through a modem emulator; payload unknown. Low-medium |
| Battle Blips 1.6 | Atari ST, GEM desk accessory | 1987-88 | peer to peer over a modem link started from a terminal program; Host and Guest roles; "standard readable ASCII" | No (only "readable ASCII") | freeware | not located online; listed on the Crawly Crypt 1 CD [S20] | Peer we could bridge; payload unknown, copy not found. Low |
| Battleship (Hasbro Interactive, NMS Software) | Windows 95 | 1996-97 | LAN (IPX/SPX, 4 players), modem, null modem, MPlayer; Zone announced 1997 | No | commercial | none (commercial) | None. Undocumented, commercial |
| Multi Player Battleship Door 3.4 | PCBoard BBS door (DOS, QuickBASIC) | 1991 | runs on the BBS; players use a terminal | n/a | shareware, US$10 | discmaster BBS Toolkit CD (batdor34.zip) | Not a client. ParlorNet's telnet extension already serves terminal players |
| Battleship 2.0.2 (John Lindal) | Mac | 1994 | none: vs computer or a friend on the same Mac | n/a | shareware, US$5 | https://archive.info-mac.org/game/brd/battleship-202.hqx | Not networked |
| bs (Bruce Holloway) | Unix curses | 1986 | none: vs computer only | n/a | BSD games | in BSD games/ | Not networked |
| KBattleship | Linux, KDE | KDE 2.2 era (2001, UNVERIFIED) | TCP, "XML based communication protocol" | yes, by source (KDE, GPL UNVERIFIED) | UNVERIFIED | KDE source archives | Out of period; noted only |
- What and who. "Battleship for Linux. Up to 5 players at the same time. X client and ncurses client", TCP network game, GPL, by Ricardo Quesada, posted to sunsite games/networked in April 1996 (0.40) [S1]. Version 0.50 (12 Sep 1997) "Includes the server, the X client, the ncurses client and the Win16 client"; maintainers Ricardo Quesada and Horacio Pe?a; platforms "Linux, ms-windows"; GPL [S2]. The licence file in the tarball is the GNU GPL version 2 [S3].
- History. The X client's first public version was 0.28 on 28 Dec 1995; chat between players came in 0.34 (10 Mar 1996), names in 0.36 [S3] (Docs/HISTORY).
- Win16 client. btwin 0.48, (C) 1996 Horacio Pe?a, written for slow 386/486 machines with Windows; it runs over a loaded TCP/IP stack ("yo uso el Trumpet 2.1f"), and builds with Borland C++ 4.0 [S3] (btwin/LEEME.batnav). The tarball includes btwin.exe and its source (btwin.cpp) [S3].
- Connection. Clients take -s host -p port -u username; the defaults are localhost and port 1995 [S3] (Docs/README). The server listens on 1995 unless given -p [S3] (btserver.c).
- Wire format. Every message in both directions is one fixed record, struct protocolo [S3] (protocol.h):
| Bytes | Field | Meaning |
| 0-2 | bnphead | "BNP" |
| 3 | bnpver | protocol version 0x11 |
| 4 | jugador | player number (1-5) |
| 5 | bnptip0 | message code (token) |
| 6 | bnptip1 | token value |
| 7 | bnptip2 | further value (for example "user" or "supervisor" view) |
| 8-107 | bnpmsg[100] | text or a 10 x 10 board, one byte per square |
All fields are char, so there is no byte-order or padding question; the server read()s exactly 108 bytes per message and writes 108 [S3] (btserver.c bnwrite, main loop). The server treats a short read as an error, so it assumes each record arrives in one piece (a ParlorNet extension should buffer instead).
- Message codes [S3] (protocol.h, btserver.c):
| Code | Name | Use |
| 0x44 | BNJUG | client hello: bnpmsg = name (max 16), bnptip1 = client kind (0x10 X, 0x20 ncurses, 0x30 Win16), bnptip2 = client version. Server answers BNJUG with the player number in bnptip1 and the server's name in bnpmsg, or BNALL (0x46) when all 5 seats are taken |
| 0x58 | BNWRI | client sends its board (100 bytes, square i = column i % 10, row i / 10; 1 = ship). Server checks the fleet and replies BNWRI (board accepted or not, in bnpmsg[0]), or BNWAI (0x47) when a game is already running |
| 0x5C | BNSTR | start the game; BNSOL (0x5B) if alone; on start every player gets BNSTR, then the first player BNTRN |
| 0x5D | BNTRN | "your turn" |
| 0x59 | BNHIT | shot: bnpmsg[0] = x, bnpmsg[1] = y. Only valid on your turn. The server marks the square on every other player's board and sends each of them BNHIT with x, y and the result in byte 2 (-1 water, 2 hit, 3 sunk); then it passes the turn (BNTRN to the next player, BNWHO 0x62 to all) |
| 0x57 | BNREA | read a player's board (bnptip1 = player); the server masks ships unless bnptip2 is BNSUP (0x39). Clients send BNREA after every BNHIT to redraw |
| 0x5E / 0x5F | BNLOS / BNWIN | you lost / you won; then BNEXT (0x43) to all with "The Game is over: Player n is the winner." and the boards are cleared |
| 0x41 | BNMSG | chat: bnptip1 = target player (0 = all) |
| 0x63 | BNSTS | status of all players |
| 0x60, 0x61 | BNVER, BNTST | server version (0.50), test |
| 0x43 | BNEXT | client leaving, or server telling clients to leave |
- Rules. 10 x 10 board; 4 ships of 1, 3 of 2, 2 of 3, 1 of 4; "The ships cant be in diagonal and they cant touch each other" [S3] (Docs/README, and the server's algoritmo check). Several players shoot in turn, and each shot hits the same square on every opponent's board at once [S3]. One btserver runs one game at a time for up to 5 players (MAXPLAYER 5) [S3].
- No accounts. The only identity is the name in BNJUG; the server appends [n] [S3].
- Weaknesses seen in the source. The server honours a client's request for the unmasked (BNSUP) view of any board [S3] (rtable); a ParlorNet extension would refuse that. Whether the stock clients ever send BNSUP for another player's board is UNVERIFIED.
Verdict: server we can imitate; high feasibility. A batnav extension listens on a ParlorNet port, answers BNJUG, takes BNWRI boards, and turns BNHIT into moves at a ParlorNet table, then sends BNHIT/BNTRN/BNWIN/BNLOS back. Points to settle: (1) the fleet: ParlorNet's Naval Combat must offer this fleet as a variant (ships 4x1, 3x2, 2x3, 1x4, no touching) or the extension can only seat batnav players at such tables; (2) multi-player: batnav allows 2 to 5 players and one shot hits all opponents; a 2-seat table is the simple case; (3) one game per server: the extension maps one batnav connection to one ParlorNet table (for example, join the first open Naval Combat table of the right variant); (4) sign-in: names only, so on password or authenticator parlors the password or code would have to travel in the 16-character name field, or the player signs up elsewhere first (as with IOS today, docs/protocols.md). The source is GPL, so it may be read and tested against freely; the extension should still be written from the protocol, not copied.
Later Batalla Naval versions (GNOME client, SourceForge project batnav, GPL v2 per the project page [S4]) are out of period; whether they keep BNP 0x11 is UNVERIFIED.
- What. GameMaster plays "RuleBooks" (game modules), locally or over a network. "GameMaster works over a MacTCP connection or an AppleTalk network (using ADSP) or both." Two players only. It runs in the background and notifies the user when someone connects. If the caller has a rulebook the callee lacks, GameMaster offers to download the rulebook over the same connection ("learn it"), and likewise upgrades it [S5]. The user manual is signed by Rhys Hollow, 5 December 1991; Peter N Lewis wrote the MacTCP code, Marcus Jager the ADSP code, Jonathan Quinn a "RuleBook Programmers manual" [S5].
- Licence. "distributed under the Povertyware banner. If you enjoy this software please send $10 ... If you dont want to pay the $10 you may as well use GameMaster anyway, just share the source and executables around" [S5]. No source was found online (UNVERIFIED whether any copy of the source or the programmers' manual survives; one search lead points to a "GM User Kit" on a BBS in a box CD, not checked).
- BattleShips. "This is the classic game of BattleShips, perfectly suited for playing remotely on computer. It can only play remotely, and doesn't allow games to be saved." Author Rhys Hollow [S6]. Other rulebooks in the kit: Othello, Connect 4, Chess (Quinn), TicTacToe, DerfBall, Dots&Boxes, Global Thermonuclear War, Simple Talk, File Transfer [S6]. A third-party Isolation rulebook was posted to Info-Mac in May 1992 [S9].
- From the binary [S7] (GameMaster 1.0.0, vers "1991 Rhys Hollow"; MacsBug routine names are present):
- TCP: the routine INITTCPDAEMON opens a passive (listening) connection with the constant 0x0396 = 918, and HANDLETCPEVENT re-arms a listener on 918 after a call is accepted. So GameMaster very probably listens on TCP port 918. The port used for outgoing calls was not traced (UNVERIFIED, presumably 918 too).
- AppleTalk: REGISTERMYNAME, FINDZONES, FINDNAMES and the string GameMaster point to an NBP registration of type "GameMaster" for the ADSP listener; the exact NBP object/type strings were not traced (UNVERIFIED).
- Session layer: alerts "Never heard of this game", "Download Code?", "Upgrade Rule Book?", "Incompatible Game", and routines DOWNLOAD, SENDDATA, COLLECTDATA. The rulebook header resource GMRZ (template TMPL 128) holds the game name, author, ID string, rulebook version, required version, memory sizes and Disallow Save/Connect/Restart/Swap flags, which the session handshake likely compares (UNVERIFIED).
- The BattleShips rulebook is one 68k code resource (PROC 128, 13,220 bytes) with routines CONNECTIONMADE, CONNECTIONLOST, FIRESHELL, FIRETURN, INCOMINGTURN, MESSAGERECEIVED, REVEALSHIPS, RESTART and a "Resync" string [S7]. Each Mac keeps its own fleet and answers the other's shots (inferred from the routine names; UNVERIFIED).
Update (2026-11-21, research-mac). The GameMaster Developer's Kit, with the BattleShips source, was found. With a second pass over the application's code, both layers are now recovered; see gamemaster.md [S32]. In short:
- The fleet is carrier 5, battleship 4, submarine 3, destroyer 3 and tug 2, the classic fleet. Ships may touch.
- Each turn is a salvo of six shots, not reduced by losses.
- When a player presses Sail, the whole fleet goes to the other side as one 15-character string (column digit, row digit, h or v per ship). Each Mac then computes the hits itself.
- A shot is two digits. A second click on the same square unmarks it and sends the same two digits. Fire commits the six shots; Done acknowledges the reveal.
- The caller fires first. Calls go to TCP port 918, then to a second port the callee announces.
- A ParlorNet extension as the callee is therefore feasible. navalcombat/1 would need a fixed six-shot salvo, and the ParlorNet player's fleet is disclosed to the Mac client at the start.
The earlier verdict, kept for the record:
Verdict: peer to peer we could bridge, after reverse engineering; medium-low feasibility. ParlorNet would play the remote GameMaster: accept or place a TCP call on port 918, pass the session handshake (and refuse "learn" downloads, which carry 68k code), then speak the BattleShips rulebook's messages, answering for the ParlorNet opponent's fleet. Both layers must be recovered from 68k disassembly. The payoff is wider than Naval Combat: the same session layer serves the Othello, Connect 4, Chess and Dots and Boxes rulebooks [S6]. On a Mac with only AppleTalk, ADSP would be needed (a LocalTalk/EtherTalk bridge), which is a further step.
- "brought to you courtesy of Claris Corporation and the HyperCard Development Team"; needs HyperCard 2.1 and System 7, because it uses Apple events [S11]. Players must be on the same AppleTalk network ("If you are both able to print to the same printer, you're on the same network"), turn on Program Linking in Sharing Setup and authorise users in Users & Groups; "Choose Opponent" picks the zone, the Mac and its HyperCard [S11]. Macintosh Repository lists it as 1991, Claris, "an implementation of the classic Battleship boardgame for AppleTalk networks", with a 236 KB download [S13].
- The message set is in the stack's own script [S12]: "The set of messages sent between copies of HyperBattleship! has been reduced to four ... hbsRequest (ask the opponent to play), hbsSetup (configure both players), hbsMove (moves), hbsMessage (text to the opponent)". They are HyperTalk send "<handler> <args>" to program <address> commands, and the reply comes back as the result:
- hbsRequest returns Play, No or Busy;
- hbsSetup "<address>", "<card id>", "<card id>" exchanges card IDs, answered via hbsMove "Challenger ID", ... with Setup or Busy;
- a shot is hbsMove "<square>", "<id>" and the reply is Hit, Miss, Sunk or End; the loser's side then sends hbsMove "End", "<id>", "<ship locations>" to reveal the fleet;
- the opponent is chosen with answer program ... of type "WILDep01" [S12]. Each Mac holds its own fleet and reports hits [S12].
- The Apple event class and ID that HyperCard 2.1 uses for send ... to program are not in the stack (UNVERIFIED). Remote Apple events ran over AppleTalk Program Linking; Mac OS 9 added Program Linking over TCP/IP (eppc://) [S14], reported to use TCP port 3031 [S15] (mailing-list report, UNVERIFIED). Whether HyperCard's answer program dialog can pick a Mac OS 9 IP-linked host is UNVERIFIED.
Verdict: peer to peer; bridgeable in principle; low-medium feasibility. The game messages are trivial and fully known; the cost is the transport: ParlorNet would have to appear as a Program Linking peer and speak remote Apple events (PPC Toolbox over AppleTalk, or eppc over TCP on Mac OS 9 machines). That piece would also serve any other HyperCard network game, but nothing else in ParlorNet needs it today.
- Quantum Link (Commodore 64) grew out of PlayNET (1984-87), whose system was licensed in 1985 to the company that became America Online [S17]. PlayNET's own list names Checkers, Chess, Backgammon, Hangman, Bridge, Stratego, Connect 4, Chinese Chess and Go, not a Battleship game [S17].
- In the Q-Link Reloaded repository's notes on the client disk, the module list includes "BTL - Sea Strike (AKA Battleship)" next to HMN (Hangman) [S16] (reference/protocol/qlink_mysteries.txt). The repository also keeps a screenshot of the People Connection online-games list (reference/screens/qlink-peopleconnection-onlinegamesold.jpg) [S16]; its contents were relayed by another research agent and not viewed here (UNVERIFIED by me).
- On the client disk images, BTL is a one-block file of 21 bytes [S16] (local .d64 directory read). It is a small loader descriptor, not the game itself. Later reading (8bit-clients.md, section b): BTL lists track and sector pairs of numbered files on the same disk, and the Sea Strike game is files 1401-1404 plus shared 1801, 1803, 1804 and 1806, in C64 BASIC, on every v4 client disk.
- Server side. Q-Link Reloaded is "QLinkServer", (c) Jim Brain and Brain Innovations 2005, GPL v2 or later, a Java server that C64 clients reach on TCP port 5190 [S16] (README.md, source headers). Games are generic: RequestGame (GI: a system-picks-order flag, an ID, a title, 0x90, the game type), GameMove (GM: the client's move as text) and further actions (StartGame, InviteToGame, ObserveGame, PlayBackMoves, ...) [S16] (src/main/java/org/jbrain/qlink/cmd/action/). The server relays the text and does not know any game's rules; the original server's qroomgame.cpp is in reference/source/qserver/ [S16].
Verdict: server we could imitate (or bridge from Q-Link Reloaded); medium feasibility, large job. Imitating the whole Q-Link login and room protocol is a big piece of work, but it is already implemented in GPL Java. A ParlorNet game would also need Sea Strike's GM move text, which is undocumented and must be recovered from the C64 module (and requires finding it first). Because relay games keep the rules in the clients, a ParlorNet bridge must answer as Sea Strike does, including reporting hits on the ParlorNet player's fleet. The same Q-Link work would reach C64 Checkers, Backgammon and Reversi [S16].
- By Wade L. Corby, Redmond, WA; "similar to the Milton Bradley Battleship(R) game"; EGA/VGA; "can be played against your computer or over the telephone via Hayes or 100% Hayes compatible modem" [S18] (BATLSHIP.DOC). Both players need "a copy of the SAME VERSION"; one dials from a dialing directory, the other waits ("WAITING FOR CALL"); chat with Alt-C [S18]. Version 3.01 (15 June 1991) added null-modem play and merged the former BATLCOMM.EXE into BATLSHIP.EXE [S18] (WHATSNEW.DOC). PC-SIG disk 2261, registration US$15 [S18] (FILE2261.TXT). Fleet: carrier 5, battleship 4, submarine 3, destroyer 2, PT-boat 1; grid numbers 0-9 [S18].
- The wire format is not documented (UNVERIFIED; it would need a serial capture under an emulator).
Verdict: peer to peer we could bridge; low-medium feasibility. An emulator's modem (for example a DOSBox-style "dial a host name" modem) could connect to a ParlorNet port that acts as the other Battle Fleet. The byte protocol must first be captured from two copies talking to each other.
- By Patrick Dell'Era, ST-Log 21 (July 1988): a GEM desk accessory; play the computer or a human by modem. The players connect with their own terminal program and open Battle Blips from its menu; one is Host, one Guest; after both place ships "the information is passed to the Host", and the Guest calls heads or tails to start. "BB doesn't care what baud, parity, etc. you choose", and it uses only "standard readable ASCII characters for sending data" [S19]. Written in Personal Pascal 1.11 [S19].
- atariuptodate lists version 1.6, 1987, freeware, 1-2 players, modem and null modem, on the Crawly Crypt 1 CD; no download link [S20].
Verdict: peer to peer we could bridge; low feasibility for now. ASCII over a serial line is friendly to a bridge (an ST emulator's serial port to TCP), but the message format is undocumented and no copy was located online.
- Battleship (NMS Software, Hasbro Interactive), Windows; up to four players "over LAN, modem-to-modem, or online using MPlayer" [S21]. A 1997 box lists Modem 2 players, Null Modem 2 players, IPX/SPX 4 players, Windows 95, and a second-player CD [S22]. Microsoft's June 1997 Internet Gaming Zone release lists Hasbro's Battleship among premium titles "coming soon, with free matchmaking" [S23]. No protocol documentation was found; not a candidate.
- Not found: a Battleship game on Outland (the Outland game folders of Dec 1994 and Aug 1995 hold Backstab, Card Lobby, Chess, Galley (a real-time ship action game, not Battleship), Hearts, Ho!, Reversi, Backgammon and Go) [S27]; on GEnie RSCARDS (Blackjack, Backgammon, Checkers, Poker, Reversi, Chess, Bridge) [S28]; on CompuServe, the ImagiNation Network, MPG-Net, Kesmai, AOL, Prodigy or Yahoo! Games (searches found nothing; not exhaustive) [S31].
- BBS doors: Multi Player Battleship Door by Gerry Freymann (PCBoard, QuickBASIC, US$10, 1991; adapted from a public-domain Commodore program) [S24]. A door runs on the BBS, so its players are terminal users; ParlorNet's telnet extension already covers them.
- Battleship 2.0.2 by John Lindal (Info-Mac, Aug 1994): "Play against the computer or your friend"; three rule sets (one shot per turn, Salvo, shoot until you miss) [S9]. The help text shows that the friend plays on the same Mac ("The person playing on the left grid hides first and shoots first") [S10].
- bs (Bruce Holloway, 1986), the BSD curses Battleship: "against the computer" only [S25].
- Epyx/Elite Battleships (1987; C64, Amiga, Atari ST): one or two players and a tournament mode on one machine; no modem mode found [S29].
- Aminet: the only Battleship found is arosbattleships (2010) [S30]. No native Amiga network Battleship was found.
- KBattleship (KDE): a TCP game with an "XML based communication protocol"; it entered kdegames for KDE 2.2 [S26]. Out of the 1985-2002 focus for vintage machines; noted only.
Added 2026-11-21 from docs/research/pc-clients.md; tags like [pc S1] are that file's sources. Nothing was run.
- NetBattleShip 1.2.0.2 (Hugues Boisvert, G?nie Design, Win32, January 1999, VB5 with the Winsock control): peer to peer over one TCP connection; 6431 and 6432 are probably its ports; freeware [pc S22]. Two matching archive copies: https://discmaster.textfiles.com/browse/33484/PCG%20CD%20Gamer%2068%201999-04.iso/Shware/NetBShip . Verdict: a peer we could bridge over plain TCP, medium-low effort; the best Win32 Battleship found.
- Windows Battleship 1.0 (Richard Foley, Win 3.0, 1992): LAN play through a shared directory only [pc S23]. No.
- Hoyle Battling Ships and War (Sierra, 1998, Win 3.x/95): two-player Internet play through Sierra's SIGS/WON, closed and dead [pc S29][pc S31]. No.
- Local only: WARSHIPS 2.1/2.5 (DOS), S.S. BattleShip and BattleGrid (Win 3.x) [pc S24].
- Battleships 1.0 (Mike Trinder, 1991): a HyperCard 2.1 stack for System 7, "A two player game for the Appletalk network". Like HyperBattleship!, it talks to the other copy with send "..." to program BSOpAddress, which is a remote Apple event over Program Linking. Its whole message set is readable HyperTalk: GreetingsFrom name,address, CheckConnection, Incoming loc, Submovement, OpponentDone, ReceiveRadio text (chat), WhiteFlag, Finalstats, terminate [S33]. Licence not stated. Verdict: a Program Linking peer, the same transport problem as HyperBattleship!.
- BattleShip 4.5 (Pyramid Software, 1999, 68k, freely distributable shareware). Its host and guest share a file, B/S-DATA, on the host's AppleShare volume; the guest mounts the host's disk [S34]. The file format is undocumented. Verdict: only through an AFP server that the extension controls; low.
- No network play was found in Boka Battleships 1.0-2.0 (1999-2005; a later OS X readme reportedly mentions LAN play, UNVERIFIED), Broadside 2.0, Sea Battle, BattleCruiser or Battleship II [S35]. IBS (1990) is "InterMac Bumper Ships", a real-time game over serial or Delphi, not Battleship.
Details and sources are in 8bit-clients.md; tags below are that note's.
- Sea Strike's move text is now known (Q-Link module 1401, C64 BASIC, read from the archive.org and funet client disks [S5][S6]). Each client first sends one GM with CHR$(19), a byte, then two bytes per ship square (CHR$(cell+20) and its content). A shot is CHR$(cell+20) twice, cell = column + 10 x row. The shooter's machine decides hit or miss from the opponent's fleet it received. The fleet is 17 squares in five ships (Carrier, Destroyer, Escort, Sub, PT Boat), the size of the classic fleet; individual lengths UNVERIFIED. A ParlorNet extension must therefore hand the ParlorNet player's fleet to the C64, and can check every C64 shot itself.
- PlayNET (1984-88) also had Sea Strike [S22][S23]; no PlayNET disk survives in the archives searched.
- Tele-Battle (Julian Burger, C64, 1987-88, freeware): peer to peer by modem at 300 baud; the BASIC listing gives the whole protocol (two-byte shots A-J/A-J, one-byte replies C1 miss, C2 hit, C3-C7 sunk) [S111]. A fake-peer extension is small.
- Computer Battleship (Babson and Cleis, Atari 8-bit BASIC, PD): peer to peer through the 850 R: device; protocol decoded from the BASIC (ATASCII lines; shot = column A-J, row 0-9; reply = the cell byte) [S117].
- Battle at Sea v1.1 (Larry Berman, Atari ST): modem or null modem at 1200 baud; tokens HIT! and SURR; the rest needs 68k disassembly [S124]. The GEnie ST library also lists BATTLSHP.ARC (1993, modem Battleship) [S45].
- FujiNet Battleship (Eric Carr and others; Apple II, Atari 8-bit, CoCo, ADAM, MS-DOS and more): HTTP polling with /place, /attack/0-99, /state?bin=1; no licence file [S93][S94]. Feasible, medium work.
- Spectrum "Net Battleships" (1984 partwork) uses Sinclair's ZX Net, not a modem [S121]; MSX Twinslag and Zeeslag use the joystick port [S122].
- GameMaster: the outgoing TCP port, the NBP name and type, the session handshake (rulebook ID/version check, "learn" download), and the BattleShips message format. Whether the GameMaster source or Jonathan Quinn's RuleBook Programmers manual survives.
- HyperBattleship: the Apple event class/ID behind HyperCard 2.1 send ... to program; whether it works over Mac OS 9 TCP/IP Program Linking; the eppc port 3031 (mailing-list report only).
- Sea Strike: where the C64 game code is, its GM move text, its rules (fleet, salvo or single shot), and the years it ran on Q-Link. The online-games screenshot was not viewed by me.
- Battle Fleet and Battle Blips: the byte protocols; a downloadable copy of Battle Blips.
- batnav: whether the stock clients ever request another player's unmasked board; whether later Batalla Naval versions keep BNP 0x11.
- Services not covered by any source found: Prodigy, AOL (Mac/PC, after Q-Link), MPG-Net, Kesmai, Yahoo! Games. Absence is not proven.
- Hasbro Battleship: the network library (DirectPlay or its own) and whether it ran on the Zone.
- KBattleship: first release date and licence.
- [S1] batnav 0.40 LSM, sunsite games/networked (12 Apr 1996): https://www.ibiblio.org/pub/historic-linux/ftp-archives/sunsite.unc.edu/Sep-29-1996/games/networked/batnav40.lsm
- [S2] batnav 0.50 LSM (12 Sep 1997): https://www.ibiblio.org/pub/linux/games/multiplayer/batnav-0.50.lsm
- [S3] batnav 0.50 source tarball (protocol.h, btserver.c, nbtclient.c, Docs/README, Docs/HISTORY, Docs/LICENSE, btwin/LEEME.batnav), read locally: https://www.ibiblio.org/pub/linux/games/multiplayer/batnav-0.50.tar.gz (sha256 in a working folder outside the repository); also 0.40: https://www.ibiblio.org/pub/historic-linux/ftp-archives/sunsite.unc.edu/Sep-29-1996/games/networked/batnav40.tgz
- [S4] SourceForge project batnav (networked battleship, GPLv2), via search result only: https://sourceforge.net/p/batnav/profile
- [S5] GameMaster User Manual (Rhys Hollow, 5 Dec 1991): https://discmaster.textfiles.com/view/27148/BBS%20in%20a%20box%20-%20Trilogy%20II.iso/Files/Game/F-G/GameMaster/GameMaster%20User%20Manual
- [S6] GameMaster "Rulebooks.doc" (1991-12-09): https://discmaster.textfiles.com/view/13893/L'Effet%20Pommier%20-%20Volume%2002.iso/Plateau/GameMaster%20%C6%92/Rulebooks.doc (same text on the BBS in a box Trilogy II CD)
- [S7] GameMaster 1.0.0 application and BattleShips rulebook (MacBinary), resource forks read locally: https://discmaster.textfiles.com/file/27148/BBS%20in%20a%20box%20-%20Trilogy%20II.iso/Files/Game/F-G/GameMaster/GameMaster and .../GameMaster/BattleShips
- [S8] Macintosh Repository, GameMaster (1991, Rhys Hollow; GM_User_Kit.sit): https://www.macintoshrepository.org/9523-gamemaster
- [S9] Info-Mac game/brd abstracts (Battleship 2.0.2, 14 Aug 1994; GameMaster Isolation rulebook, 13 May 1992; other AppleTalk games): https://sunsite2.icm.edu.pl/packages/info-mac/game/brd/00brd-abstracts.txt ; current listing https://archive.info-mac.org/game/brd/
- [S10] Battleship 2.0 help text (TEXT 128), Info-Mac IV CD: https://discmaster.textfiles.com/view/14421/Info_Mac%20IV%20CD-ROM%20(Pacific%20HiTech%20Inc.)(August%201994).iso/Games/Board/Battleship%202.0/Battleship%202.0.rsrc/TEXT_128.txt
- [S11] HyperBattleship! 2.1 read-me (1991-06-21): https://discmaster.textfiles.com/view/13446/Hyper%20Stacks%20(Pacific%20HiTech)(1994)%5BMac%5D.iso/Games/HyperBattleShip/%E2%80%A2READ%20ME%E2%80%A2%20HyperBattleship!
- [S12] HyperBattleship! stack, HyperTalk scripts read from the data fork: https://discmaster.textfiles.com/file/13446/Hyper%20Stacks%20(Pacific%20HiTech)(1994)%5BMac%5D.iso/Games/HyperBattleShip/HyperBattleship%21
- [S13] Macintosh Repository, Hyper Battleship! (1991, Claris): https://www.macintoshrepository.org/41164-hyper-battleship-
- [S14] TidBITS, "Mac OS 9 with a Net" (1 Nov 1999), Apple events over TCP/IP, via search summary: https://tidbits.com/1999/11/01/mac-os-9-with-a-net/
- [S15] applescript-users list, "eppc port is 3031" (Dec 2000), via search snippet: https://lists.apple.com/archives/applescript-users/2000/Dec/msg00788.html
- [S16] Q-Link Reloaded repository: https://github.com/ssalevan/qlink (README.md: port 5190; reference/protocol/qlink_mysteries.txt: "BTL - Sea Strike (AKA Battleship)"; src/main/java/org/jbrain/qlink/cmd/action/RequestGame.java, GameMove.java, GameSend.java: GPL v2+, Jim Brain 2005; reference/source/qserver/qroomgame.cpp; reference/screens/qlink-peopleconnection-onlinegamesold.jpg; disk images QuantumLink.d64, reference/disks/QlinkKeith2001.d64, QlinkKeith2010.d64, directories read locally)
- [S17] Wikipedia, PlayNET: https://en.wikipedia.org/wiki/PlayNET
- [S18] Battle Fleet 3.01 (BATLSHIP.DOC, WHATSNEW.DOC, FILE2261.TXT), read locally: https://www.dosgames.com/files/bfleet.zip ; page https://www.dosgames.com/game/battle-fleet/
- [S19] ST-Log 21 (July 1988), "Battle Blips!": https://www.atarimagazines.com/st-log/issue21/55_1_GAME_BATTLE_BLIPS!.php
- [S20] atariuptodate, Battle Blips 1.6: https://atariuptodate.de/en/9255/battle-blips
- [S21] Wikipedia, Battleship (1996 video game): https://en.wikipedia.org/wiki/Battleship_(1996_video_game)
- [S22] Battleship, Hasbro Interactive 1997 box listing: https://elisoftware.org/wiki/Battleship_(PC,_CD-ROM)_Hasbro_Interactive_(608610990041)_-_1997_USA,_Canada_Release
- [S23] Microsoft press release, 16 June 1997, Internet Gaming Zone: https://news.microsoft.com/source/1997/06/16/microsoft-unveils-first-premium-games-for-its-internet-gaming-zone/
- [S24] Multi Player Battleship Door (BATDOR34.DOC, 1991-11-16): https://discmaster.textfiles.com/view/254/BBS%20Toolkit.iso/doors_1/batdor34.zip/BATDOR34.DOC
- [S25] OpenBSD bs(6): https://man.openbsd.org/bs.6
- [S26] KBattleship: handbook ("XML based communication protocol") and the KDE news item on its move to kdegames for KDE 2.2, via search results only: https://git.trinitydesktop.org/cgit/tdegames/plain/doc/kbattleship/index.docbook , https://dot.kde.org/node/2066
- [S27] Outland game folders (Dec 1994 and Aug 1995 installers), listed locally from the copies in a working folder outside the repository (sources in that folder's SOURCES.md and docs/research/bg-client-outland.md)
- [S28] docs/research/bg-client-genie-rscards.md (RSCARDS game list)
- [S29] ST-Log 31 (May 1989), Battleship review, via search summary: https://www.atarimagazines.com/st-log/issue31/090_1_THE_ST_GAMESHELF_BATTLESHIP.php
- [S30] Aminet search "battleship": https://aminet.net/search?query=battleship
- [S33] Battleships 1.0 (Mike Trinder), "Network Games" folder of the 1000 Games CD, https://discmaster.textfiles.com/browse/29562/1000%20Games.toast/Network%20Games ; HyperTalk read from the stack's data fork (sha256 in a working folder outside the repository).
- [S34] Pyramid BattleShip 4.5.1, B_S Read Me, MACPOWER 2000-03 CD, https://discmaster.textfiles.com/view/10365/MACPOWER-2000-03.ISO/MACPOWER-2000-03.ISO/MacPower%E3%82%AA%E3%83%AA%E3%82%B8%E3%83%8A%E3%83%AB%E2%81%84%E9%80%A3%E8%BC%89/Onlineware%20Collectors/%E5%BE%8C%E8%97%A4%E5%95%93%E6%AC%A1%E3%81%AE%E3%82%B3%E3%83%AC%E3%82%AF%E3%82%B7%E3%83%A7%E3%83%B3/BattleShip%20%EF%BE%84.sea/BattleShip%20%C6%92/B_S%20Read%20Me
- [S35] Boka Battleships, https://www.macintoshrepository.org/44868-boka-battleships and its Classic readme, https://discmaster.textfiles.com/view/17798/macaddict115.cdr/Software/Fun%20&%20Games/Boka%20Battleships%202.0%20For%20Classic%20Mac%20OS/Read%20Me ; Battleship II, https://discmaster.textfiles.com/file/12017/IMG%2029%20JulyAug%201995.iso/Shareware/Battleship%20II/Read%20Me ; strings of the other stacks and applications read locally.
- [S32] docs/research/gamemaster.md (this repository): the GameMaster Dev Kit with BattleShips.p and BattleShipsTypes.unit (Rhys Hollow, 1991), https://discmaster.textfiles.com/browse/5566/Ian%20and%20Stuart's%20One%20(Australia).iso/Australasian%20Legends/Community/Rhys%20Hollow/GameMaster/GM%20Dev%20Kit/Rulebook%20Sources , and the session layer read from the application's code.
- [S31] Searches for Battleship on 1990s services (GEnie, CompuServe, ImagiNation, MPG-Net, AOL, Yahoo! Games) found nothing; background: https://www.atarimagazines.com/compute/issue168/86_Modem_combat.php , https://tedium.co/2017/07/27/yahoo-games-failure-classicgames/
From docs/research/x11-clients.md (sources there):
- batnav 0.50 builds. The server and the ncurses client build on current Debian (arm64 and x86-64) once -lncurses is moved after the objects. The XView X client builds unchanged on Debian 8 x86-64, which has Debian's last XView (there is no arm64 package). The ibiblio and ftp.lip6.fr copies are identical. The tarball also carries prebuilt i386 Linux binaries and btwin.exe.
- **Seascape 0.2 with the shipkill server** (Marco Dettori, Oliver Obst, 1997-98, GPL v2 or later). It has a Qt 1 client and a plain-socket server on TCP 17003. The server pairs two players and relays their shots: two-byte field numbers and one-byte results, with the protocol in the German PROTOKOLL file. shipkill builds on current Debian with one include fix; the Qt 1 client is hard to build today. It is a cheap server to imitate, with a small audience.
- KBattleship (KDE 2.2-3.5) is GPL v2 or later (kmessage.cpp), which settles the licence left open above. One player hosts on TCP 54321, and the players exchange XML <kmessage> messages (GREET, SHIPSREADY, SHOOT, ANSWER_SHOOT, WON, REPLAY, CHAT; protocol "0.1.0"). It is a peer ParlorNet could stand in for. KDE 4.4-4.8 also gave it a GGZ mode (engine "Battleship" v1, same messages), though no GGZ Battleship server was found.
This doc on GitHub
| | These pages cover every ParlorNet server. | Source code | ParlorNet is free software. |